Home » Language IDEs » ServerTools (WTP) » Tomcat 5.5 won't start (workspace corruption?)
| Tomcat 5.5 won't start (workspace corruption?) [message #175043] |
Wed, 19 July 2006 21:29  |
Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
My workspace seems to get into the state where I can't start my Tomcat 5.5
instance that I set up.
What it does is when I hit the play button, it immediately tells me that it
failed to start. However, the server starts in debug mode rather than non-
debug mode.
This is fine, generally, if all I want to do is debug. But it causes
problems with things like the Web Services wizard.
Eclipse 3.2
WTP 1.5
Tomcat 5.5
What I have found out is if I redo me workspace all is well for a while,
but then something gets corrupted again.
|
|
| |
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175544 is a reply to message #175138] |
Thu, 27 July 2006 00:19  |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Larry,
Thanks for the response.
I took a look at the .launch file and here are the contents:
<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration
type="org.eclipse.jst.server.tomcat.core.launchConfigurationType ">
<booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH"
value="false"/>
<stringAttribute key="server-id" value="7_18_06_4_35_PM0"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_INSTALL_TYPE_ID"
value="org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType "/>
<listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
<listEntry value="<?xml version="1.0" encoding="UTF-8
"?> <runtimeClasspat hEntry
containerPath="org.eclipse.jdt.launching.JRE_CONTAI NER/org.eclipse.j
dt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_07& ;quot;
path="2" type="4"/> "/>
<listEntry value="<?xml version="1.0" encoding="UTF-8
"?> <runtimeClasspat hEntry
externalArchive="V:/dev/tomcat55/bin/bootstrap.jar& amp;quot;
path="3" type="2"/> "/>
<listEntry value="<?xml version="1.0" encoding="UTF-8
"?> <runtimeClasspat hEntry
externalArchive="V:/Java/jdk1.5.0_07/lib/tools.jar& amp;quot;
path="3" type="2"/> "/>
</listAttribute>
<stringAttribute key="org.eclipse.jdt.launching.VM_INSTALL_NAME"
value="jdk1.5.0_07"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
value="start"/>
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-
Dcatalina.base="V:\projects\CDIS\.metadata\.plugins
\org.eclipse.wst.server.core\tmp0" -Dcatalina.home="V:\dev
\tomcat55" -Djava.endorsed.dirs="V:\dev\tomcat55\common
\endorsed""/>
</launchConfiguration>
Nothing spectacular, I don't think. I tried deleting this file and it
didn't fix anything. I removed all deployed applications, nothing.
Any other thoughts?
Larry Isaacs <Larry.Isaacs@sas.com> wrote in
news:e9o3t6$ht9$1@utils.eclipse.org:
> Perhaps a web project is slowing down the startup enough to cause the
> "startup detection" to timeout? If no web projects are added to the
> server, is there still a startup problem?
>
> Running with the assumption that some corruption is getting into the
> workspace, what are the contents of the ???Server_localhost.launch
> file for the server found in the
> <workspace>/.metadata\.plugins\org.eclipse.debug.core\.launches
> folder.
>
> Cheers,
> Larry
>
> Mark Townsend wrote:
>> My workspace seems to get into the state where I can't start my
>> Tomcat 5.5 instance that I set up.
>>
>> What it does is when I hit the play button, it immediately tells me
>> that it failed to start. However, the server starts in debug mode
>> rather than non- debug mode.
>>
>> This is fine, generally, if all I want to do is debug. But it causes
>> problems with things like the Web Services wizard.
>>
>> Eclipse 3.2
>> WTP 1.5
>> Tomcat 5.5
>>
>> What I have found out is if I redo me workspace all is well for a
>> while, but then something gets corrupted again.
>
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175584 is a reply to message #175544] |
Thu, 27 July 2006 13:55 |
 Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
Mark,
What is the significance of drive "V:". Is it a removable or network
drive? I'm not aware this would cause a problem, but who knows. The
launch file looks normal to me too.
At this point, I think I need a more detailed explanation of what you
mean by "the server starts in debug mode rather than non- debug mode".
Are you saying that clicking the play button does start the server, or
that the debug button works but play gives this error?
Larry
Mark Townsend wrote:
> Larry,
>
> Thanks for the response.
>
> I took a look at the .launch file and here are the contents:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <launchConfiguration
> type="org.eclipse.jst.server.tomcat.core.launchConfigurationType ">
> <booleanAttribute key="org.eclipse.jdt.launching.DEFAULT_CLASSPATH"
> value="false"/>
> <stringAttribute key="server-id" value="7_18_06_4_35_PM0"/>
> <stringAttribute key="org.eclipse.jdt.launching.VM_INSTALL_TYPE_ID"
> value="org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType "/>
> <listAttribute key="org.eclipse.jdt.launching.CLASSPATH">
> <listEntry value="<?xml version="1.0" encoding="UTF-8
> "?> <runtimeClasspat hEntry
> containerPath="org.eclipse.jdt.launching.JRE_CONTAI NER/org.eclipse.j
> dt.internal.debug.ui.launcher.StandardVMType/jdk1.5.0_07& ;quot;
> path="2" type="4"/> "/>
> <listEntry value="<?xml version="1.0" encoding="UTF-8
> "?> <runtimeClasspat hEntry
> externalArchive="V:/dev/tomcat55/bin/bootstrap.jar& amp;quot;
> path="3" type="2"/> "/>
> <listEntry value="<?xml version="1.0" encoding="UTF-8
> "?> <runtimeClasspat hEntry
> externalArchive="V:/Java/jdk1.5.0_07/lib/tools.jar& amp;quot;
> path="3" type="2"/> "/>
> </listAttribute>
> <stringAttribute key="org.eclipse.jdt.launching.VM_INSTALL_NAME"
> value="jdk1.5.0_07"/>
> <stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS"
> value="start"/>
> <stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-
> Dcatalina.base="V:\projects\CDIS\.metadata\.plugins
> \org.eclipse.wst.server.core\tmp0" -Dcatalina.home="V:\dev
> \tomcat55" -Djava.endorsed.dirs="V:\dev\tomcat55\common
> \endorsed""/>
> </launchConfiguration>
>
> Nothing spectacular, I don't think. I tried deleting this file and it
> didn't fix anything. I removed all deployed applications, nothing.
>
> Any other thoughts?
>
> Larry Isaacs <Larry.Isaacs@sas.com> wrote in
> news:e9o3t6$ht9$1@utils.eclipse.org:
>
>> Perhaps a web project is slowing down the startup enough to cause the
>> "startup detection" to timeout? If no web projects are added to the
>> server, is there still a startup problem?
>>
>> Running with the assumption that some corruption is getting into the
>> workspace, what are the contents of the ???Server_localhost.launch
>> file for the server found in the
>> <workspace>/.metadata\.plugins\org.eclipse.debug.core\.launches
>> folder.
>>
>> Cheers,
>> Larry
>>
>> Mark Townsend wrote:
>>> My workspace seems to get into the state where I can't start my
>>> Tomcat 5.5 instance that I set up.
>>>
>>> What it does is when I hit the play button, it immediately tells me
>>> that it failed to start. However, the server starts in debug mode
>>> rather than non- debug mode.
>>>
>>> This is fine, generally, if all I want to do is debug. But it causes
>>> problems with things like the Web Services wizard.
>>>
>>> Eclipse 3.2
>>> WTP 1.5
>>> Tomcat 5.5
>>>
>>> What I have found out is if I redo me workspace all is well for a
>>> while, but then something gets corrupted again.
>
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175600 is a reply to message #175584] |
Thu, 27 July 2006 16:18 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
The V: drive is just another partition on my hard drive. It's where all
my Eclipse projects, etc are.
Okay, basically it's I hit the 'play' button and immediately I get a pop-
up that says 'Server Tomcat 5.5 @ localhost failed to start'. However,
the console is showing that it is indeed starting. Once it's done, the
Server view shows a status of 'Debugging'.
The .log file isn't too much help as all it says is the same as the pop-
up.
The only thing that seems to fix it is to delete the .metadata directory
and re-do the workspace. But I don't want to have to do that every time,
it's kind of a pain. So I am trying to narrow down where the problem
could be.
Larry Isaacs <Larry.Isaacs@sas.com> wrote in
news:eaagju$6fh$1@utils.eclipse.org:
> Mark,
>
> What is the significance of drive "V:". Is it a removable or network
> drive? I'm not aware this would cause a problem, but who knows. The
> launch file looks normal to me too.
>
> At this point, I think I need a more detailed explanation of what you
> mean by "the server starts in debug mode rather than non- debug mode".
> Are you saying that clicking the play button does start the server, or
> that the debug button works but play gives this error?
>
> Larry
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175636 is a reply to message #175600] |
Thu, 27 July 2006 20:04 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
I'll see if I can scan the source and get an idea of how clicking 'play'
can display 'Debugging'. Do you recall switching directly from run to
debug, or the reverse, while Tomcat was still running prior to having
this behavior appear?
Larry
Mark Townsend wrote:
> The V: drive is just another partition on my hard drive. It's where all
> my Eclipse projects, etc are.
>
> Okay, basically it's I hit the 'play' button and immediately I get a pop-
> up that says 'Server Tomcat 5.5 @ localhost failed to start'. However,
> the console is showing that it is indeed starting. Once it's done, the
> Server view shows a status of 'Debugging'.
>
> The .log file isn't too much help as all it says is the same as the pop-
> up.
>
> The only thing that seems to fix it is to delete the .metadata directory
> and re-do the workspace. But I don't want to have to do that every time,
> it's kind of a pain. So I am trying to narrow down where the problem
> could be.
>
>
> Larry Isaacs <Larry.Isaacs@sas.com> wrote in
> news:eaagju$6fh$1@utils.eclipse.org:
>
>> Mark,
>>
>> What is the significance of drive "V:". Is it a removable or network
>> drive? I'm not aware this would cause a problem, but who knows. The
>> launch file looks normal to me too.
>>
>> At this point, I think I need a more detailed explanation of what you
>> mean by "the server starts in debug mode rather than non- debug mode".
>> Are you saying that clicking the play button does start the server, or
>> that the debug button works but play gives this error?
>>
>> Larry
|
|
| | |
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175853 is a reply to message #175660] |
Mon, 31 July 2006 23:18 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Larry,
Me again. :)
When running the Web Services Wizard, I actually get a stack trace worth
looking at.
Here it is:
IWAB0213E Error in starting server.
org.eclipse.core.runtime.CoreException: Server Tomcat v5.5 Server @
localhost failed to start.
at org.eclipse.wst.server.core.internal.Server.synchronousStart
(Server.java:1522)
at org.eclipse.wst.server.core.internal.Server.synchronousResta rt
(Server.java:1532)
at
org.eclipse.jst.ws.internal.consumption.ui.command.StartServ erCommand.res
tart(StartServerCommand.java:173)
at
org.eclipse.jst.ws.internal.consumption.ui.command.StartServ erCommand.exe
cute(StartServerCommand.java:108)
at
org.eclipse.jst.ws.internal.creation.ui.extension.PreService RunCommand.ex
ecute(PreServiceRunCommand.java:39)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
runCommand(CommandFragmentEngine.java:413)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
visitTop(CommandFragmentEngine.java:353)
at
org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
moveForwardToNextStop(CommandFragmentEngine.java:251)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManage
r$5.run(SimpleCommandEngineManager.java:250)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread
(ModalContext.java:369)
at org.eclipse.jface.operation.ModalContext.run
(ModalContext.java:313)
at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java: 851)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManage
r.runForwardToNextStop(SimpleCommandEngineManager.java:220)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.runForw
ardToNextStop(WizardPageManager.java:94)
at
org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.getNext
Page(WizardPageManager.java:145)
at
org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizard Page.getNextP
age(SimpleWizardPage.java:119)
at org.eclipse.jface.wizard.WizardDialog.nextPressed
(WizardDialog.java:751)
at org.eclipse.jface.wizard.WizardDialog.buttonPressed
(WizardDialog.java:351)
at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:90)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents
(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.wst.command.internal.env.ui.widgets.popup.Dynami cPopupWizard.
run(DynamicPopupWizard.java:130)
at org.eclipse.ui.internal.PluginAction.runWithEvent
(PluginAction.java:254)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection
(ActionContributionItem.java:539)
at org.eclipse.jface.action.ActionContributionItem.access$2
(ActionContributionItem.java:488)
at org.eclipse.jface.action.ActionContributionItem$5.handleEven t
(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
at org.eclipse.swt.widgets.Display.runDeferredEvents
(Display.java:3348)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
at org.eclipse.ui.internal.Workbench.runEventLoop
(Workbench.java:1914)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:419)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench
(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.IDEApplication.run
(IDEApplication.java:95)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run
(PlatformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati
on(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start
(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)
Can you decipher this at all?
Mark Townsend <mtownsen@nowhere.com> wrote in
news:Xns980DA53ABD775markltownsendbaesyst@206.191.52.34:
> Larry,
>
> To answer you in one word: 'No'. :)
>
> Thanks for taking a look.
>
> Larry Isaacs <Larry.Isaacs@sas.com> wrote in
> news:eab692$ne4$1@utils.eclipse.org:
>
>> I'll see if I can scan the source and get an idea of how clicking
>> 'play' can display 'Debugging'. Do you recall switching directly from
>> run to debug, or the reverse, while Tomcat was still running prior to
>> having this behavior appear?
>
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175900 is a reply to message #175853] |
Tue, 01 August 2006 14:44 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
Mark,
No luck so far scanning the source code. I assume the exception below
is in a workspace with the odd behavior. This stack trace indicates the
Web Services Wizard tried to wait for Tomcat to start and it didn't get
the expected indication that it had started.
A this point, turning on some tracing in your environment might provide
a little more to go on. First you need to add "-debug" and
"-consolelog" to your eclipse startup arguments. If you wish, they can
be added as separate lines at the top of the "eclipse.ini" file that is
located in your Eclipse installation.
Next create a new text file containing the lines:
org.eclipse.jst.server.tomcat.core/debug=true
org.eclipse.wst.server.core/debug=true
Save this file as ".options" in the same directory where "eclipse.ini"
is found. Then start eclipse, from a DOS window or shell if this
doesn't happen in your normal startup.
In addition to some general Eclipse output, you should see some trace
output appear from the plug-ins listed. Try clicking the "play" button
and capture what appears in the output. It might help determine where
the odd behavior is coming from.
Cheers,
Larry
Mark Townsend wrote:
> Larry,
>
> Me again. :)
>
> When running the Web Services Wizard, I actually get a stack trace worth
> looking at.
>
> Here it is:
>
> IWAB0213E Error in starting server.
> org.eclipse.core.runtime.CoreException: Server Tomcat v5.5 Server @
> localhost failed to start.
> at org.eclipse.wst.server.core.internal.Server.synchronousStart
> (Server.java:1522)
> at org.eclipse.wst.server.core.internal.Server.synchronousResta rt
> (Server.java:1532)
> at
> org.eclipse.jst.ws.internal.consumption.ui.command.StartServ erCommand.res
> tart(StartServerCommand.java:173)
> at
> org.eclipse.jst.ws.internal.consumption.ui.command.StartServ erCommand.exe
> cute(StartServerCommand.java:108)
> at
> org.eclipse.jst.ws.internal.creation.ui.extension.PreService RunCommand.ex
> ecute(PreServiceRunCommand.java:39)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
> runCommand(CommandFragmentEngine.java:413)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
> visitTop(CommandFragmentEngine.java:353)
> at
> org.eclipse.wst.command.internal.env.core.fragment.CommandFr agmentEngine.
> moveForwardToNextStop(CommandFragmentEngine.java:251)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManage
> r$5.run(SimpleCommandEngineManager.java:250)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread
> (ModalContext.java:369)
> at org.eclipse.jface.operation.ModalContext.run
> (ModalContext.java:313)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java: 851)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleComman dEngineManage
> r.runForwardToNextStop(SimpleCommandEngineManager.java:220)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.runForw
> ardToNextStop(WizardPageManager.java:94)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.WizardPageMa nager.getNext
> Page(WizardPageManager.java:145)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.SimpleWizard Page.getNextP
> age(SimpleWizardPage.java:119)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed
> (WizardDialog.java:751)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed
> (WizardDialog.java:351)
> at org.eclipse.jface.dialogs.Dialog$3.widgetSelected(Dialog.jav a:660)
> at org.eclipse.swt.widgets.TypedListener.handleEvent
> (TypedListener.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Display.runDeferredEvents
> (Display.java:3348)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at
> org.eclipse.wst.command.internal.env.ui.widgets.popup.Dynami cPopupWizard.
> run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent
> (PluginAction.java:254)
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection
> (ActionContributionItem.java:539)
> at org.eclipse.jface.action.ActionContributionItem.access$2
> (ActionContributionItem.java:488)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEven t
> (ActionContributionItem.java:400)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
> at org.eclipse.swt.widgets.Display.runDeferredEvents
> (Display.java:3348)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2968)
> at org.eclipse.ui.internal.Workbench.runEventLoop
> (Workbench.java:1914)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
> (Workbench.java:419)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench
> (PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.IDEApplication.run
> (IDEApplication.java:95)
> at org.eclipse.core.internal.runtime.PlatformActivator$1.run
> (PlatformActivator.java:78)
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplicati
> on(EclipseAppLauncher.java:92)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start
> (EclipseAppLauncher.java:68)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run
> (EclipseStarter.java:177)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
>
> Can you decipher this at all?
>
> Mark Townsend <mtownsen@nowhere.com> wrote in
> news:Xns980DA53ABD775markltownsendbaesyst@206.191.52.34:
>
>> Larry,
>>
>> To answer you in one word: 'No'. :)
>>
>> Thanks for taking a look.
>>
>> Larry Isaacs <Larry.Isaacs@sas.com> wrote in
>> news:eab692$ne4$1@utils.eclipse.org:
>>
>>> I'll see if I can scan the source and get an idea of how clicking
>>> 'play' can display 'Debugging'. Do you recall switching directly from
>>> run to debug, or the reverse, while Tomcat was still running prior to
>>> having this behavior appear?
>
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #175990 is a reply to message #175900] |
Tue, 01 August 2006 18:54 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Thanks for the tip on looking at trace information.
Looking at the output of the console, I don't see anything obvious. It
just loads all the resources. Here is the snippet where it says that it
fails:
----
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275
synchronousStart 1
org.eclipse.wst.server.core LISTENERS 01/08/06 11:48.06.275 Adding server
listen
er org.eclipse.wst.server.core.internal.Server$11@fcc070 to Tomcat v5.5
Server @
localhost
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275 ->- Adding
server li
stener to notification manager:
org.eclipse.wst.server.core.internal.Server$11@f
cc070 65535 ->-
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275
synchronousStart 2
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275 Starting
server: Tom
cat v5.5 Server @ localhost, launchMode: run
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353 Launch:
org.eclipse.
debug.core.Launch@17368db
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353
synchronousStart 3
org.eclipse.wst.server.core LISTENERS 01/08/06 11:48.06.353 Removing
server list
ener org.eclipse.wst.server.core.internal.Server$11@fcc070 from Tomcat
v5.5 Serv
er @ localhost
org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353 ->- Removing
server
listener from notification manager:
org.eclipse.wst.server.core.internal.Server$
11@fcc070 ->-
!SESSION 2006-08-01 11:46:52.040
-----------------------------------------------
eclipse.buildId=I20060602-1317
java.version=1.5.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog
!ENTRY org.eclipse.wst.server.core 4org.eclipse.wst.server.core RESOURCES
01/08/
06 11:48.06.416 ->- ServerResourceChangeListener responding to resource
change:
1 ->-
org.eclipse.wst.server.core RESOURCES 01/08/06 11:48.06.416 -<- Done
ServerReso
urceChangeListener responding to resource change -<-
0 2006-08-01 11:48:06.447
!MESSAGE Server Tomcat v5.5 Server @ localhost failed to start.
----
Look like anything useful?
Larry Isaacs <Larry.Isaacs@sas.com> wrote in
news:eanpc9$5f8$1@utils.eclipse.org:
> Mark,
>
> No luck so far scanning the source code. I assume the exception below
> is in a workspace with the odd behavior. This stack trace indicates
> the Web Services Wizard tried to wait for Tomcat to start and it
> didn't get the expected indication that it had started.
>
> A this point, turning on some tracing in your environment might
> provide a little more to go on. First you need to add "-debug" and
> "-consolelog" to your eclipse startup arguments. If you wish, they
> can be added as separate lines at the top of the "eclipse.ini" file
> that is located in your Eclipse installation.
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #176022 is a reply to message #175990] |
Tue, 01 August 2006 20:34 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
For me, I see a lot more output, including some from
org.eclipse.jst.server.tomcat.core. For example, when I click the play
button, the output starts with:
org.eclipse.wst.server.core PERF 01/08/06 15:44.56.984
Server.getBehaviourDelegate(): <0> org.eclipse.jst.server.tomcat.55
org.eclipse.wst.server.core FINEST 01/08/06 15:44.56.984 ->- Firing
publish started event ->-
org.eclipse.wst.server.core FINEST 01/08/06 15:44.56.984 Firing
publish started event to
org.eclipse.wst.server.ui.internal.ServerUIPlugin$3@96b1b8
org.eclipse.wst.server.core FINEST 01/08/06 15:44.56.984 Firing
publish started event to
org.eclipse.wst.server.ui.internal.view.servers.ServerTableV iewer$5@4ab8b9
org.eclipse.wst.server.core FINEST 01/08/06 15:44.57.000 -<- Done
firing publish started event -<-
org.eclipse.wst.server.core FINEST 01/08/06 15:44.57.000 -->--
Publishing to server: Tomcat v5.5 Server @ localhost -->--
org.eclipse.wst.server.core FINEST 01/08/06 15:44.57.000 Loading
publish info
org.eclipse.wst.server.core FINEST 01/08/06 15:44.57.000 Loading
publish info from
D:\Java\Eclipse\Workspaces\32WTP15\Testing2\.metadata\.plugi ns\org.eclipse.wst.server.core\publish\publish0.xml
I also see additional output within the output you list. Double check
the "debugging" changes you just made in case that's why there is not
Tomcat plug-in output. If you don't find anything, try creating a new
Tomcat 5.5 Server, start it with the play button, and see if it gives
more output.
Also, "eclipse.buildId=I20060602-1317" says you aren't running with the
final release of Eclipse 3.2. What are the dates you find on the files
in some of the Web Tools plug-in directories. They should be 6/28 for
the released WTP 1.5.
Larry
Mark Townsend wrote:
> Thanks for the tip on looking at trace information.
>
> Looking at the output of the console, I don't see anything obvious. It
> just loads all the resources. Here is the snippet where it says that it
> fails:
>
> ----
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275
> synchronousStart 1
> org.eclipse.wst.server.core LISTENERS 01/08/06 11:48.06.275 Adding server
> listen
> er org.eclipse.wst.server.core.internal.Server$11@fcc070 to Tomcat v5.5
> Server @
> localhost
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275 ->- Adding
> server li
> stener to notification manager:
> org.eclipse.wst.server.core.internal.Server$11@f
> cc070 65535 ->-
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275
> synchronousStart 2
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.275 Starting
> server: Tom
> cat v5.5 Server @ localhost, launchMode: run
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353 Launch:
> org.eclipse.
> debug.core.Launch@17368db
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353
> synchronousStart 3
> org.eclipse.wst.server.core LISTENERS 01/08/06 11:48.06.353 Removing
> server list
> ener org.eclipse.wst.server.core.internal.Server$11@fcc070 from Tomcat
> v5.5 Serv
> er @ localhost
> org.eclipse.wst.server.core FINEST 01/08/06 11:48.06.353 ->- Removing
> server
> listener from notification manager:
> org.eclipse.wst.server.core.internal.Server$
> 11@fcc070 ->-
> !SESSION 2006-08-01 11:46:52.040
> -----------------------------------------------
>
> eclipse.buildId=I20060602-1317
> java.version=1.5.0_07
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
> Command-line arguments: -os win32 -ws win32 -arch x86 -debug -consolelog
>
> !ENTRY org.eclipse.wst.server.core 4org.eclipse.wst.server.core RESOURCES
> 01/08/
> 06 11:48.06.416 ->- ServerResourceChangeListener responding to resource
> change:
> 1 ->-
> org.eclipse.wst.server.core RESOURCES 01/08/06 11:48.06.416 -<- Done
> ServerReso
> urceChangeListener responding to resource change -<-
> 0 2006-08-01 11:48:06.447
> !MESSAGE Server Tomcat v5.5 Server @ localhost failed to start.
>
> ----
>
> Look like anything useful?
>
> Larry Isaacs <Larry.Isaacs@sas.com> wrote in
> news:eanpc9$5f8$1@utils.eclipse.org:
>
>> Mark,
>>
>> No luck so far scanning the source code. I assume the exception below
>> is in a workspace with the odd behavior. This stack trace indicates
>> the Web Services Wizard tried to wait for Tomcat to start and it
>> didn't get the expected indication that it had started.
>>
>> A this point, turning on some tracing in your environment might
>> provide a little more to go on. First you need to add "-debug" and
>> "-consolelog" to your eclipse startup arguments. If you wish, they
>> can be added as separate lines at the top of the "eclipse.ini" file
>> that is located in your Eclipse installation.
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #176043 is a reply to message #176022] |
Tue, 01 August 2006 22:31 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Larry,
You may have hit the nail on the head. I had had a RC version of 3.2. But
when 3.2 came up I just went to the Software Manager and downloaded
updates. I assumed then that I had the latest and greatest...
I reinstalled a fresh copy of 3.2 and download all the WST plugins from
Callisto and without changing anything in my workspace, the server starts
up without a problem.
Thanks,
Mark
|
|
| |
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #176590 is a reply to message #176050] |
Tue, 08 August 2006 18:53 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Hi Larry!
It's me again! It started happening again! And I didn't change
anything! :-)
The only difference that I can think of is that I was in debug mode most
of the day yesterday. Today, I load Eclipse and try and start the server
normally and I get the same error message and behavior that I was talking
about in this thread?
Any more ideas for me to look at? Should I do the trace again and send
the output now that I have the latest Eclipse 3.2?
Cheers,
Mark
Larry Isaacs <Larry.Isaacs@sas.com> wrote in
news:eaooen$8d0$1@utils.eclipse.org:
> That's good to hear. Hopefully it will stay working. If it quits
> again, go ahead an open a Bugzilla report with jst.server as the
> component. That would be a better place to collect diagnostic
> information to try and figure out the cause.
>
> Cheers,
> Larry
>
> Mark Townsend wrote:
>> Larry,
>>
>> You may have hit the nail on the head. I had had a RC version of
>> 3.2. But when 3.2 came up I just went to the Software Manager and
>> downloaded updates. I assumed then that I had the latest and
>> greatest...
>>
>> I reinstalled a fresh copy of 3.2 and download all the WST plugins
>> from Callisto and without changing anything in my workspace, the
>> server starts up without a problem.
>>
>>
>> Thanks,
>> Mark
>
|
|
| |
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #176607 is a reply to message #176602] |
Tue, 08 August 2006 19:43 |
| Eclipse User |
|
|
|
Originally posted by: mtownsen.nowhere.com
Larry,
I think that I found the problem in a repeatable way.
Under Preferences - Run/Debug - Launching
Select "Always" for "Launch in debug mode when workspace contains
breakpoints"
Set up some breakpoints
Start a server in normal run mode. Get error message that the server
failed to start.
If I change the option to "Prompt", I get a prompt when trying to start the
server in normal mode whether I want to go into debug mode. If I say no,
everything works as expected. Oddly enough I get the same prompt when I
try and stop the server.
If I uncheck any breakpoints when the "Always" selected, then the server
will start normally.
This seems like a bug to me. Should I put a bug report in? If I do is
this under the Eclipse JDT or is it Eclipse Platform?
|
|
|
| Re: Tomcat 5.5 won't start (workspace corruption?) [message #176623 is a reply to message #176607] |
Tue, 08 August 2006 20:21 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
Mark,
Thanks for solving this mystery! Yes, file a bug report on the
wst.server component of Web Tools.
The server handling has separate methods for "starting" and "debugging",
which aren't coded to be aware that this choice can be overridden by JDT
in this way. The "start" code doesn't see the "started" state get set,
because it's the "debugging" state that gets set instead, and mistakenly
thinks it failed to start.
Larry
Mark Townsend wrote:
> Larry,
>
> I think that I found the problem in a repeatable way.
>
> Under Preferences - Run/Debug - Launching
> Select "Always" for "Launch in debug mode when workspace contains
> breakpoints"
> Set up some breakpoints
> Start a server in normal run mode. Get error message that the server
> failed to start.
>
> If I change the option to "Prompt", I get a prompt when trying to start the
> server in normal mode whether I want to go into debug mode. If I say no,
> everything works as expected. Oddly enough I get the same prompt when I
> try and stop the server.
>
> If I uncheck any breakpoints when the "Always" selected, then the server
> will start normally.
>
> This seems like a bug to me. Should I put a bug report in? If I do is
> this under the Eclipse JDT or is it Eclipse Platform?
>
|
|
| |
Goto Forum:
Current Time: Fri Apr 19 10:47:29 GMT 2024
Powered by FUDForum. Page generated in 0.02883 seconds |
] 
Search
Help
Register
Login
Home
