Skip to main content

Timeout waiting for Sun Application Server 8.1 to start.

12 replies [Last post]
caryaclark
Offline
Joined: 2006-01-12
Points: 0

I've had the SAS 8.1 installed for awhile and have deployed a couple of web apps to it. I added the Plugin to my Eclipse 3.1.1 + WTP 1.0 install. I added a project to it and started the app server. Its log had all the normal stuff in it, including the following line:

[#|2006-01-12T13:55:48.406-0600|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]

But after 5 minutes of it starting I get this in my Eclipse .log and an accompanying dialog in the IDE:

!ENTRY org.eclipse.wst.server.core 4 0 2006-01-12 13:59:39.125
!MESSAGE Timeout waiting for Sun Application Server 8.1 to start. Server did not start after 300000s.

I'm running Sun JDK 1.4.2.

Any suggestions?

Thanks,
Cary

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
ludo
Offline
Joined: 2003-06-10
Points: 0

Are you on Windows or Linux?
On Linux systems, we are facing some issues mostly on the Eclipse side of WTP...

Also, can you confirmed that the http port you configured when adding the server was 8080?

Finally, you mention Eclipse 3.1.1 and I am not sure the level of support of WTP 1.0 for it.

Let us know,
Thanks

caryaclark
Offline
Joined: 2006-01-12
Points: 0

I checked the server ports. I had, in fact, built the server using 8081 and the server def in Eclipse @ 8080. So, I whacked the server def and rebuilt it specifying 8081. A suggestion for the plugin would be to allow specifying the ports on the server def page.

Now, I'm getting a "Publish failed using Ant publisher" error when I publish. It puts this up after several "Copying from XXX to XXX" status messages. I get this stack trace in the .log file:
===========================================
!ENTRY org.eclipse.jst.server.generic.core 4 0 2006-01-13 11:41:18.953
!MESSAGE Publish failed using Ant publisher
!STACK 1
org.eclipse.core.runtime.CoreException[0]: java.lang.Exception: Error renaming C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.core\tmp16606.class to C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\Citizen Portal\WEB-INF\classes\com\axinym\cp\actions\SaveComplaintTypeAction.class
at org.eclipse.jst.server.core.PublishUtil.copyFile(PublishUtil.java:127)
at org.eclipse.jst.server.core.PublishUtil.copyFile(PublishUtil.java:154)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:260)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.generic.core.internal.publishers.AbstractModuleAssembler.copyModule(AbstractModuleAssembler.java:126)
at org.eclipse.jst.server.generic.core.internal.publishers.WarModuleAssembler.assemble(WarModuleAssembler.java:28)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.assembleModule(AntPublisher.java:103)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.publish(AntPublisher.java:90)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:90)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:800)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:789)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
!SUBENTRY 1 org.eclipse.jst.server.core 4 0 2006-01-13 11:41:18.953
!MESSAGE Error copying file to C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\Citizen Portal\WEB-INF\classes\com\axinym\cp\actions\SaveComplaintTypeAction.class: Error renaming C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.core\tmp16606.class to C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\Citizen Portal\WEB-INF\classes\com\axinym\cp\actions\SaveComplaintTypeAction.class
!STACK 0
java.lang.Exception: Error renaming C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.core\tmp16606.class to C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\Citizen Portal\WEB-INF\classes\com\axinym\cp\actions\SaveComplaintTypeAction.class
at org.eclipse.jst.server.core.PublishUtil.copyFile(PublishUtil.java:127)
at org.eclipse.jst.server.core.PublishUtil.copyFile(PublishUtil.java:154)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:260)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.core.PublishUtil.smartCopy(PublishUtil.java:266)
at org.eclipse.jst.server.generic.core.internal.publishers.AbstractModuleAssembler.copyModule(AbstractModuleAssembler.java:126)
at org.eclipse.jst.server.generic.core.internal.publishers.WarModuleAssembler.assemble(WarModuleAssembler.java:28)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.assembleModule(AntPublisher.java:103)
at org.eclipse.jst.server.generic.core.internal.publishers.AntPublisher.publish(AntPublisher.java:90)
at org.eclipse.jst.server.generic.core.internal.GenericServerBehaviour.publishModule(GenericServerBehaviour.java:90)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:658)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:738)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:596)
at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:800)
at org.eclipse.wst.server.core.internal.Server.publish(Server.java:789)
at org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
===========================================

It appears to get another directory under WEB-INF published properly. And, I've run the publish several times and it's always SaveComplaintTypeAction.class
that it fails on.

Thanks for the port tip.

Cary

caryaclark
Offline
Joined: 2006-01-12
Points: 0

It's the JDK level. I was running 1.4.2x doing some testing with Geronimo 1.0.

I switched back to running Eclipse with 1.5.0_04 and it publishes fine. I'll test the actually app now.

Thanks,
Cary

ludo
Offline
Joined: 2003-06-10
Points: 0

Great to hear you have it working now...
We'll check the JDK version issue...We do not want to force people to use JDK1.5 if they are not using the GlassFish Java EE 5 server as a target:-)

Keep sending your comments and feedback,
Ludo

caryaclark
Offline
Joined: 2006-01-12
Points: 0

Ok, I tried to publish. It gets nearly all the way through, but fails with this in the Eclipse console:
==================================
Unknown argument: -Dmodule.name= deploy.j2ee.web
Buildfile: C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef\sunappsrv-ant.xml
deploy.j2ee.web:

BUILD FAILED
C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef\sunappsrv-ant.xml:65: C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\${module.name} not found.

Total time: 1 second
==================================

I've experimented and found that the value it's using is from the .component file . This seems odd to me since that's tieing the WAR file name to the context path value. I don't think this works well, especially in the case of running in the root context. I think it should create the WAR with the value from the [b]deploy-name[/b] attribute since this is just a physical file name anyway and then use the value for just that in the app server's web app definition (as the equivalent to the Context Root when manually deploying a Web Module via the console).

I did try a different value in the (/CitizenPortal) but still got an error:

BUILD FAILED
C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef\sunappsrv-ant.xml:65: C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\Citizen Portal\com.sun.enterprise.jst.server.sunappsrv\CitizenPortal not found.

Thanks,
Cary

ludo
Offline
Joined: 2003-06-10
Points: 0

To isolate the issue (Eclipse or the plugin), csn you try to
run the short tutorial:

https://glassfishplugins.dev.java.net/specifications/introduction.html

Maybe you started with Geronimo and the switch would cause the issue?

${module.name} value is supposed to be calculated by WTP and passed to any server plugin, so I am clueless about why WTP did not evaluate this property...

caryaclark
Offline
Joined: 2006-01-12
Points: 0

Your tutorial works fine. WTP 1.0 has a bug in it that prevents the creation of a web project that runs in the root context.

I made several projects trying different ways to get WTP to put it in the root context and was unsuccessful. The wizard proceeds regardless of what you put in for the Context Root. If you leave it blank, WTP puts the project name in the .component & sun-web.xml files. If you put a / in it, the .component file has a /, but the sun-web.xml has the project name. Neither publish correctly.

So, I guess I'll see what the WTP guys have to say.

Thanks,
Cary

ludo
Offline
Joined: 2003-06-10
Points: 0

Thanks for following up with the WTP group. If you are aware of a bug #, let us know...
I suspect the same behaviour would be visible for all the other servers supported in WTP 1.0.

So far, it seems that WTP 1.0 is still shaky: for example, it has not been tested on the Linux or Mac platforms for the Oracle target and JBoss target (possibly others...).
See bugs
https://bugs.eclipse.org/bugs/show_bug.cgi?id=121415
https://bugs.eclipse.org/bugs/show_bug.cgi?id=123227

I have published the list of current bugs impacting our integration under
https://glassfishplugins.dev.java.net/Eclipse/CurrentBugs.html

Thanks

caryaclark
Offline
Joined: 2006-01-12
Points: 0

Well, it's definitely the presence or absense of a context path being specified that causing problems.

I don't have an environment set up to do plugin debugging. So I have a few questions for you.
1) Have you run through your own tutorial and not specified a context root? If so, what were your results?

2) Can you get the context root value from the wizard and use it instead of hard coding the context root in the generation of the sun-web.xm file with this line in the SunWebXmlCreate.createDeploymentPlan(...):
plan.getSunWebApp().setContextRoot("/" + moduleName);

This pretty much makes it impossible to change the context path without then hand modifying the sun-web.xml file. I haven't successfully deployed from Eclipse yet, but I assume the deployment is actually using the sun-web.xml file and hence its context root value.

3) The latest maintenance build has added a properties page to set the Context Root and it applies the value to the .settings/.component file properly. Is there a way for you to hook to that change somehow and keep the sun-web.xml file in sync?

4) What's firing the ant process that runs sunappsrv-ant.xml? Is it a something under your control or the framework? In the case of having no context path, the console has this in it:
=====================
Unknown argument: -Dmodule.name= deploy.j2ee.web
Buildfile: C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef\sunappsrv-ant.xml
deploy.j2ee.web:

BUILD FAILED
C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.jst.server.generic.core\serverdef\sunappsrv-ant.xml:65: C:\Documents and Settings\caclark\My Documents\WSAD Workspaces\Eclipse 3.1\.metadata\.plugins\org.eclipse.core.resources\.projects\SunTestNCR2\com.sun.enterprise.jst.server.sunappsrv\${module.name} not found.

Total time: 1 second
=====================

I had not noticed the first line (Unknown argument...) before while looking at failures because it scrolled out of view. Not intimately familiar with the framework, I don't know if that's something under your control or if it's a framework bug similar to some of those that have been reported.

5) Do you think this is going to get into a finger pointing game between you and the WTP team since the project that I originally tried to deploy on the SAS 8.1 can be successfully deployed to Tomcat 5.5.x with no context root? My fear is that if I open up a WTP bug, I'll get a reply along the lines of "it deploys to Tomcat fine, get ahold of your server definition writer and make them fix their code". At that point, I'm stuck in the middle and don't know who to push on.

Thanks,
Cary

caryaclark
Offline
Joined: 2006-01-12
Points: 0

Hello? Still watching this forum, Ludo?

ludo
Offline
Joined: 2003-06-10
Points: 0

For point 1, the way you specify the context root is within the sun-web.xml (created via the Sun DD facet), so you need this file for a correct deployment where you control the context root.

For point 2, I think WTP 1.0.1 will provide new APIs to do that.
Point 3: see point 2 :-)
Point 4: WTP is doing that.
Point 5: There is no finger pointing there.

We are waiting for a stable 1.0.1 build and will update the plugin. Stay tune.

ludo
Offline
Joined: 2003-06-10
Points: 0

GlassFish Eclipse plugin, milestone 2 is out...
Try it, it should now work on linux as well and with wtp 1.0 or 1.0.1 latest build