Eclipse Community Forums: ServerTools (WTP) » SEVERE: Error filterStart and Context Startup

Home » Language IDEs » ServerTools (WTP) » SEVERE: Error filterStart and Context Startup

SEVERE: Error filterStart and Context Startup [message #145908]

Wed, 02 November 2005 10:40

Eclipse User

I recently ugraded from Eclipse 3.1 M6 to 3.1.1 and since then I have been
receiving some strange and unpredictable errors. Most recently, when I go
to startup my Web Service (Aapche Tomcat 5.0) I get the following errors
displayed on the console:

Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors

I receive this whether I start the server from the server tab or whether I
start it by right clicking on the client and running the Web Service
Client.

I never received these errors before with Eclipse 3.1 M6 and am currious
if anyone else has received these errors and if there is a fix for this.

Thanks,
Ben

Re: SEVERE: Error filterStart and Context Startup [message #145917 is a reply to message #145908]

Wed, 02 November 2005 10:44

Eclipse User

The full console message for the server startup is as follows, I wanted to
include it so that all the information is available and not just the error
message:

Nov 2, 2005 10:24:11 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
Nov 2, 2005 10:24:11 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 970 ms
Nov 2, 2005 10:24:11 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Nov 2, 2005 10:24:11 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.28
Nov 2, 2005 10:24:12 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Nov 2, 2005 10:24:12 AM org.apache.catalina.core.StandardHost getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Nov 2, 2005 10:24:12 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /axis from URL
file:C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\axis
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /balancer from URL
file:C:\Program Files\Apache Software Foundation\Tomcat
5.0\webapps\balancer
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardContext start
SEVERE: Context startup failed due to previous errors
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path
/BASS_WebServicesClientMod from URL file:C:\Program Files\Apache Software
Foundation\Tomcat 5.0\webapps\BASS_WebServicesClientMod
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /jsp-examples from URL
file:C:\Program Files\Apache Software Foundation\Tomcat
5.0\webapps\jsp-examples
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path from URL file:C:\Program
Files\Apache Software Foundation\Tomcat 5.0\webapps\ROOT
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /servlets-examples from
URL file:C:\Program Files\Apache Software Foundation\Tomcat
5.0\webapps\servlets-examples
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /tomcat-docs from URL
file:C:\Program Files\Apache Software Foundation\Tomcat
5.0\webapps\tomcat-docs
Nov 2, 2005 10:24:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /webdav from URL
file:C:\Program Files\Apache Software Foundation\Tomcat 5.0\webapps\webdav
Nov 2, 2005 10:24:14 AM org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
Nov 2, 2005 10:24:14 AM org.apache.jk.common.ChannelSocket init
INFO: JK2: ajp13 listening on /0.0.0.0:8009
Nov 2, 2005 10:24:14 AM org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/47 config=C:\Program Files\Apache Software
Foundation\Tomcat 5.0\conf\jk2.properties
Nov 2, 2005 10:24:14 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 2548 ms

Thanks,
Ben

Re: SEVERE: Error filterStart and Context Startup [message #145924 is a reply to message #145917]

Wed, 02 November 2005 11:50

Eclipse User

I believe that I have traced it back to the actual clean of the project.
I have multiple projects that I build but it appears the Web Service
project has an error. I get the following two error messages when I try a
clean build of the project:

JavaBuilder handling ImageBuilderInternalException while building:
BASS_WebServices

JavaBuilder handling CoreException while cleaning: BASS_WebServices

I would appreciate any help on this.

The full length error messages are as follows:

org.eclipse.core.internal.resources.ResourceException: Problems
encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource .java:677)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.clea nOutputFolders(BatchImageBuilder.java:126)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.buil d(BatchImageBuilder.java:36)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(J avaBuilder.java:213)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.build(Java Builder.java:136)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:593)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:168)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:202)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:231)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:234)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop (BuildManager.java:253)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:282)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBu ildJob.java:139)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJ ob.java:200)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

and

org.eclipse.core.internal.resources.ResourceException: Problems
encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource .java:677)
at
org.eclipse.jdt.internal.core.builder.BatchImageBuilder.clea nOutputFolders(BatchImageBuilder.java:126)
at
org.eclipse.jdt.internal.core.builder.JavaBuilder.clean(Java Builder.java:247)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildMan ager.java:595)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:168)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:202)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildMan ager.java:231)
at
org.eclipse.core.internal.runtime.InternalPlatform.run(Inter nalPlatform.java:1044)
at org.eclipse.core.runtime.Platform.run(Platform.java:783)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(Bui ldManager.java:234)
at
org.eclipse.core.internal.events.BuildManager.build(BuildMan ager.java:303)
at org.eclipse.core.internal.resources.Project.build(Project.ja va:106)
at
org.eclipse.ui.internal.ide.dialogs.CleanDialog.doClean(Clea nDialog.java:237)
at
org.eclipse.ui.internal.ide.dialogs.CleanDialog$1.runInWorks pace(CleanDialog.java:124)
at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run (InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)

Thanks,
Ben

exception: Axis engine could not find a target service to invoke [message #145941 is a reply to message #145924]

Wed, 02 November 2005 13:11

Eclipse User

I believe I have a solution for this error. I have multipple projects
taht rely on each other as dependencies. When I do a clean all 3 of the
projects flag as in error. When I select the first of the three and
perform a clean on it the error flags go away for all the projects. I
thought this had resolved my issues but it didn't.

I then went back and tried to do a clean build on the other two projects
that had originally been flagged with an error, but after the clean of the
first project the error flag went away and these projects produced new
errors after the build. I found that I needed to go into the
properties/build path/Order and Export and change the order of the build
so that the projects were built in a dependency order. I then needed to
go into window/preferences/workspace/build order and change the order of
the build there. I also had to uncheck the default build order.

Once I had done this I went back and did a clean build on all the
projects. This resulted in no errors and this eliminated all the error
messages that I show here so far.

However, I now have a new issue. The project is a Web Service, I launch
my client from Eclipse and it shows all the available methods. When I
select the method that I want to run, enter my parameters and hit the
"invoke" key I now get a new message that I didn't get before:
"exception: The AXIS engine could not find a target service to invoke!
targetService is ExerciseSupportServicesSoap"

I would have thought with a clean build and no errors that I wouldn't have
received this error message. I did a few new things to try and relieve
this message: (1) I performed the undeploy.wsdd; (2) I went to the Axis
directory within my server and deleted all the old Web Service files; (3)
I created a new JAR file for my Web Service and moved it to Axis
directory; (4) I ran the deploy.wsdd script; (5) I shutdown and the
restarted the WebService again. After all these steps I still get the
same exception message.

I would appreciate any help on this.

Thanks,
Ben

Re: exception: Axis engine could not find a target service to invoke [message #145959 is a reply to message #145941]

Wed, 02 November 2005 13:59

Eclipse User

I think this may help in resolving the issue. When I start up the Server
it provides a list of the Web applications that are being installed along
with a context path. What I notice is that the other Web Services are
being installed but the Web Service that I just deployed is not on the
list of installed Web applications.

I can't figure out why it is not on the list though. It exists within the
same directories as the other Web applications. When I log onto Axis it
is listed as a valid Web Service.

I would appreciate any help, I think that I'm getting closer but I believe
I'm missing one small piece in my Eclipse application that is not
deploying the service and I can't figure out what that is.

Thanks,
Ben

Re: exception: Axis engine could not find a target service to invoke [message #145977 is a reply to message #145959]

Wed, 02 November 2005 14:45

Eclipse User

Latest result, I went back to a backup copy of my workspace and opened up
Eclipse with my Web Service project in it. I right clicked on my jsp
client and selected run on server. The server was launced, the client
appeared, I entered my parameters and the expected result was returned.

I then did a clean build of all projects. Which I indicated before would
result in three of my projects having errors (dependency). I went to
Windows/preferences/workspace/build order and changed the order so that
the file that needed to be compiled first was first. I did not change
the build path in the properties for each of the projects as I did before.
I just wanted to keep it simple.

I did another clean build all and everyone of the projects was returned
without an error. I checked the Problems log and there were no errors in
it. This is a project that I have been working with for more than 6
months using Eclipse 3.1 M6.

I attempted to run the client again. I right clicked on it, selected run
on sever, the client appeared and I entered the expected parameters. This
time though I got the "exception: The AXIS engine could not find a target
service to invoke! targetService is ExerciseSupportServicesSoap".

The only thing that I did was change the build order and do a clean build
of all the projects and now the Web Service won't run.

Thanks in advance for any help or guidance regarding this.

Ben

Re: exception: Axis engine could not find a target service to invoke [message #146025 is a reply to message #145977]

Thu, 03 November 2005 02:53

Eclipse User

Originally posted by: mvdb.ibl-software.nl

It may also help to physically delete the deployed webapp and redeploy
again..

Mvgr,
Martin

Ben wrote:
> Latest result, I went back to a backup copy of my workspace and opened
> up Eclipse with my Web Service project in it. I right clicked on my jsp
> client and selected run on server. The server was launced, the client
> appeared, I entered my parameters and the expected result was returned.
>
> I then did a clean build of all projects. Which I indicated before
> would result in three of my projects having errors (dependency). I went
> to Windows/preferences/workspace/build order and changed the order so
> that the file that needed to be compiled first was first. I did not
> change the build path in the properties for each of the projects as I
> did before. I just wanted to keep it simple.
> I did another clean build all and everyone of the projects was returned
> without an error. I checked the Problems log and there were no errors
> in it. This is a project that I have been working with for more than 6
> months using Eclipse 3.1 M6.
> I attempted to run the client again. I right clicked on it, selected
> run on sever, the client appeared and I entered the expected
> parameters. This time though I got the "exception: The AXIS engine
> could not find a target service to invoke! targetService is
> ExerciseSupportServicesSoap".
> The only thing that I did was change the build order and do a clean
> build of all the projects and now the Web Service won't run.
> Thanks in advance for any help or guidance regarding this.
>
> Ben

Re: exception: Axis engine could not find a target service to invoke [message #146159 is a reply to message #146025]

Thu, 03 November 2005 11:13

Eclipse User

Martin,

I want to thank you for your help but unfortunately this did not solve the
problem. I took the old backup copy of my workspace that worked fine
(right click on the client, run on server, select method w/ parameters and
returns valid result). I then performed the following tasks:
1) Adjusted the preference build order so that there would be no errors.
2) Did a clean build on all the projects (no errors reported or returned).
3) Test the Web Service through the client and received the "exception:
The AXIS engine could not find a target service to invoke!" exception
error.
4) Ran the undeploy.wsdd for the desired Web Service, stopped and
restrated the server.
5) Ran the deploy.wsdd for the desired Web Servie.
6) Right clicked on the client, select run on server.
7) Selected my method, entered the parameters and hit the Invoke button.
8) Instead of the expected results I recieved the following error message:
exception: The AXIS engine could not find a target service to invoke!

I'm concerned that the clean build is causing this error. I also want to
verify that these are the steps that you suggested that I test. If you
have additional suggestions please let me know.

Thanks for your help,
Ben

Re: exception: Axis engine could not find a target service to invoke [message #146221 is a reply to message #146159]

Thu, 03 November 2005 14:39

Eclipse User

I believe that I have found the error. I went back to the archived
workspace that existed before we upgraded to Eclipse 3.1.1 and it
contained a server-config.wsdd file in it. The workspace that existed
after we upgraded to 3.1.1 did not contain this file. I noticed when we
did the Clean build that it stated there was no server-config-wsdd file
and that it was creating a new one. I did a file system inport from the
old workspace (3.1 M6) to the new workspace (3.1.1) and then reopened up
Eclipse. At this point a did another Clean build of all projects. Now
when I select the client to run on the server, then the method, and pass
the parameters. The returned resuslt is what should be expected.

I hope this is helpful to others in case they experience this same issue.
I am a bit confused still how this file was deleted from the workspace.
When we converted from 3.1 M6 ot 3.1.1, we created a copy of the 3.1 M6
workspace and renamed it 3.1.1. We then opened that workospace with
Eclipse 3.1.1 to use in our development.

Thanks for you help, support and suggestions,
Ben

Re: exception: Axis engine could not find a target service to invoke [message #146230 is a reply to message #146221]

Thu, 03 November 2005 15:03

Eclipse User

As a result of this research and my findings I do have a question
regarding the results. In my testing, within Eclipse 3.1.1, within the
Server view, I opened the Tomcat 5.0 server that I'm using. This opened
an edit window with two tabs (Overview and Modules). I selected the
modules tab and saw two of my web services displayed as web modules. The
web service that I was having issues with I selected and then selected the
remove button. I then selected the "Add Web Module" button where a list
of available web modules was displayed. The Web Module that I had just
deleted was displayed and I selected it to add back.

That is where the odd thing took place. It added all the information to
the list of Web Modules just like before except it did not fill anything
into the Module column. It filled in the path, document base, and auto
reload columns but left the Module column blank. I went back to the
backup workspace, reopened it and opened up the server page again. In the
backup the Module name appeared. I tried several different things to
make it appear again. I did the clean build all, I removed it again and
again and kept adding it back in but it never filled in this field.

Does anyone have any suggestions on why this field isn't filled in, what
the result of this field not being filled in is, and how I might be able
to get this filled in again?

Thanks,
Ben

Previous Topic:	Help with Eclipse - BIRT
Next Topic:	how is .deplyables updated

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Apr 19 11:54:00 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter