Bugzilla – Full Text Bug Listing
| Summary: | Won't start and acknowledge that a server has started either using tomcat or jboss | ||
|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | Steve <steve.morin> |
| Component: | jst.server | Assignee: | Tim deBoer <deboer> |
| Status: | CLOSED WONTFIX | QA Contact: | Tim deBoer <deboer> |
| Severity: | major | ||
| Priority: | P2 | CC: | david_williams, naci.dai, steve.morin, thatnitind |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Attachments: | |||
Created attachment 44470 [details]
Server file from my eclipse:workspace/.metadata/.plugins/org.eclipse.wst.server.core
this is the configuration that I have used for the servers
Assigning concrete component owner for this critical bug. Any one know of other Mac Users who can test or confirm a working configuration? Steve ... as much as I love the callisto update site ... you might try using "zips" , starting from the WTP build page, to make doubly sure you are getting a compatible set, as listed on the WTP build page. (Or, if you'd like to experiment first, some have noted that to get *all* the most recent Callisto versions, you have to "update' from there a couple of times ... I doubt that is the case here, but ... might depend on exactly when you got it, when it was last changed, etc.) Ran update this morning and only got updates for DTP and CDT modules. Please let me know if there is anything else you would specifially like me to try or information that you need. Running ps aux after starting JBoss 4.0.4 minimal I get following command, is it the fact that it is using program run.bat the problem. Running it manually I usually use run.sh. I don't believe that this is a problem but figured I would point it out. /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/java -Dprogram.name=run.bat -Djava.endorsed.dirs=/usr/local/jboss-4.0 Goes from "Stopped." "Starting..." Then a dialog box appears with "Timeout waiting for JBOSS 4.0 10.10.10.45 to start. Server did not start after 50s." Looking at the log messages looks like the server started fine but was send a signal to shutdown. I compared a manually started file to the eclipse started version. Created attachment 44538 [details]
Jboss Console output from Eclipse
Created attachment 44539 [details]
Jboss Boot output from Eclipse
Created attachment 44540 [details]
Jboss Server output from Eclipse
Created attachment 44541 [details]
Jboss Console output from Command Line
Created attachment 44542 [details]
Jboss Boot output from Command Line
Created attachment 44543 [details]
Jboss Server output from Command Line
Created attachment 44545 [details]
Server file from my eclipse:workspace/.metadata/.plugins/org.eclipse.wst.server.core
Reducing severity to major according to the severity definitions, as discussed on the WTP status call. adding Naci since he is maintaining the jboss adapter Can you set the server time out delay factor to Longer and try it again. You can set this from Preferences>Server>Server Timeout Delay. Server Time out delay: was Normal Tried as "Long" and "Longer" Both popped up the usual message "Timeout waiting for JBOSS 4.0 10.10.10.45 to start. Server did not start after 50s." Both I noticed the time didn't actually change for it to timeout. I shutdown and restarted eclipse to make sure the preference would take effect. The setting stayed but didn't seem to do anything. Is there anything else anyone would like me to try or extra information? If you put in requests tonight, I'll have you the info by tommorow. Steve, did you deliberatly set this back to critical, after we discussed in status call and set it to major? If so, please read https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_severity and see if you still think 'critical' and please explain why. Seem's "major loss of function" to me, but maybe for your situation its "blocking" and you just didn't explain your situation? In either case, though, I don't see "crashes or loss of data" ... so, asking you to clarify. Steve, this is marked for "mac", that's accurate, right? Do you happen to have access to windows or linux to try that out? Just to see? Also, just checking, are you able to run JBoss "stand alone" on your mac ok, independent of Eclipe? Just wonderng. (not that I know much about either). Or, where's 10.10.10.45 come from. That sounds like a "private network" ... is it your machine, or are you "running remotely"? Lastly, Steve, its unclear from the history if you've tried this starting completely fresh, from a new set of compatible zip files, new workspace, new project, etc. That sometimes help -- both you to get past the problem and us to help narrow down possible sources of the problem. (In reply to comment #16) > Steve, did you deliberatly set this back to critical, after we discussed in > status call and set it to major? > > If so, please read > https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#bug_severity > and see if you still think 'critical' and please explain why. > > Seem's "major loss of function" to me, but maybe for your situation its > "blocking" and you just didn't explain your situation? In either case, though, > I don't see "crashes or loss of data" ... so, asking you to clarify. > Didn't mean to switch it's status, might have hit the back button and submitted a file again with the old status. (In reply to comment #17) > Steve, this is marked for "mac", that's accurate, right? > > Do you happen to have access to windows or linux to try that out? Just to see? > > Also, just checking, are you able to run JBoss "stand alone" on your mac ok, > independent of Eclipe? Just wonderng. (not that I know much about either). > > Or, where's 10.10.10.45 come from. That sounds like a "private network" ... is > it your machine, or are you "running remotely"? > > Lastly, Steve, its unclear from the history if you've tried this starting > completely fresh, from a new set of compatible zip files, new workspace, new > project, etc. That sometimes help -- both you to get past the problem and us to > help narrow down possible sources of the problem. > This is a Mac and will try to run it on a Linux machine. I am able to run Jboss standalone. 10.10.10.45 is my machine(the machine I was running eclipse on) Basically everything is fresh with Jboss and Eclipse(Downloaded that same morning). I didn't even have a project started. Unzipped that morning with fresh downloads of each and tomcat 5.5. Using Neither tomcat or jboss worked standalone with out a project. Then tried to use tomcat with a project and it worked, I am not exactly sure why that is. Haven't had time to try Jboss with a project. Thanks, Steve, I'll change back to 'major' then, though agree it is a major ++ problem if prohibts JBoss on all macs. Sadly, we don't have many Mac users in our list of active WTP developers, so its harder for us to test and diagnos (we do have some a round, and someone can eventually, just takes longer). I do not know how "loop back adapters" work on Mac, so this is a big trial-error guess here, but, seems like it might help if you can get all your "IP addresses" to agree ... I see some in the defintion are 127.0.0.1 and some (one) are 10.10.10.45. So, if you can manually set them all to 127.0.0.1 that might help (and, again, I really am guessing based entirely on very old experience where, in past versions at least, there was no real "resolution" of addresses and sometimes, for example, I could not use my "domain name", but had to use 127.0.0.1 explicitly. So, apologies I can't test myself, or give more concrete advice ... hopefully we can find some other JBoss + Mac users to report experiences too. Basically I found out that I couldn't start either Jboss or tomcat with out defining a project to use with them. All my initial attempts didn't include a project to deploy. Not I have setup project to deploy with them and they now run. The problem is probably somewhere down in the server tools framework, since this happens for both Tomcat and JBoss passing to Tim. Tim, I have tried this on windows and can not repro and unfortunately I have no acces to Mac. I also found the same bug. Because my project is very large, the jboss server always starts after 50s. Therefore a pop up window messages "Time out waiting for Jboss to start. Server did not start after 50s". Server did not shutdown immediately, but it did a short time later. I dont know why since jboss server always start standalone successfully without eclipse. Hi Steve, A few questions: * It works once you add a project to the server, but not without? * I also notice that the error is related to running in debug mode - have you tried in regular (run) mode as well, and is the behaviour any different? * Also (to knock out one possibility) does the server start within the specified timeout externally? I don't think this is related to the timeout, but just want to rule this out. Tuananh - Unless you are on a Mac, I don't think this is related. Does the server start within the timeout outside of WTP? If you are on 1.5.1 you can change the server timeout preference to increase the length of time before the start times out. Yes it works once you add a project to the server. I tried it in both regular and debug mode the behavior was similar but gave a different error message for debug. When I get a minute I'll test if the server starts within the specified timeout externally. (In reply to comment #24) > Hi Steve, > A few questions: > * It works once you add a project to the server, but not without? > * I also notice that the error is related to running in debug mode - have you > tried in regular (run) mode as well, and is the behaviour any different? > * Also (to knock out one possibility) does the server start within the > specified timeout externally? I don't think this is related to the timeout, but > just want to rule this out. > > Tuananh - Unless you are on a Mac, I don't think this is related. Does the > server start within the timeout outside of WTP? If you are on 1.5.1 you can > change the server timeout preference to increase the length of time before the > start times out. > Hi Tim, I tried it many time but no effect. I think you should check it again. (In reply to comment #24) > Hi Steve, > A few questions: > * It works once you add a project to the server, but not without? > * I also notice that the error is related to running in debug mode - have you > tried in regular (run) mode as well, and is the behaviour any different? > * Also (to knock out one possibility) does the server start within the > specified timeout externally? I don't think this is related to the timeout, but > just want to rule this out. > > Tuananh - Unless you are on a Mac, I don't think this is related. Does the > server start within the timeout outside of WTP? If you are on 1.5.1 you can > change the server timeout preference to increase the length of time before the > start times out. > Steve - Do you still have this problem in WTP 2.0 or 3.0? (WTP can't detect that an empty server is started, but is ok once a project is added) I don't have access to a Mac and this has never been reported or reproducible on other platforms. I assume that there is either a Mac IP stack difference or the JBoss & Tomcat's default configuration is different (e.g. no default port or root webapp configured by default), but since I have no way to debug and there is a workaround I'm going to mark this as 'helpwanted' for now. If someone can isolate and provide a patch I'll gladly accept, and otherwise this will wait until we at least have a Mac developer who is able to help debug. Tuananh's issue is an unrelated timeout issue. If you're still having problems with newer timeout settings since this bug, please feel free to open a new bug. I haven't tried this problem in a while. I have moved to a new company and off developing on a mac so can't test it again. Steve Since we haven't had any new reports of this bug and we have nobody available to retest or debug on Mac, I am closing this bug for now. If anyone else becomes available we can retest to see if this is still an issue and use them to help debug. Closing bug. |
For example using start of a Won't start and acknowledge that services have started on tomcat or jboss. Give the message "Timeout waiting for JBOSS 4.0 to start. Server did not start after 50s". Gives the same message for Tomcat v5.5 @localhost replacing the name and after 45s Machine: Mac OSX 10.4.6 Darwin steve.local 8.6.0 Darwin Kernel Version 8.6.0: Tue Mar 7 16:58:48 PST 2006; root:xnu-792.6.70.obj~1/RELEASE_PPC Power Macintosh powerpc Eclipse Version: 3.2.0 Build id: I20060602-1317 Tomcattomcat-5.5.17 Jboss 3.2.3 and 4.0.4 Web Standard Tools Downloaded version that updates with Calisto This is the example I get from trying to run tomcat in debug. ERROR: transport error 202: connect failed: Operation timed out ["transport.c",L41] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L500] JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initializedFATAL ERROR in native method: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113) here is my server config file <?xml version="1.0" encoding="UTF-8"?> <servers> <server hostname="127.0.0.1" id="6_14_06_3_57_PM13" name="JBOSS 3.2.3 TP" runtime-id="JBoss v3.2.x" server-type="org.eclipse.jst.server.generic.jboss323" server-type-id="org.eclipse.jst.server.generic.jboss323" timestamp="2"> <map jndiPort="1099" key="generic_server_instance_properties" port="8080" serverAddress="127.0.0.1" serverConfig="tp"/> </server> <server hostname="127.0.0.1" id="6_14_06_6_17_PM0" name="JBOSS 3.2.3" runtime-id="JBoss v3.2.x" server-type="org.eclipse.jst.server.generic.jboss323" server-type-id="org.eclipse.jst.server.generic.jboss323" timestamp="0"> <map jndiPort="1099" key="generic_server_instance_properties" port="8080" serverAddress="127.0.0.1" serverConfig="all"/> </server> <server hostname="steve.local" id="6_14_06_6_23_PM2" name="JBOSS 3.2.3 1" runtime-id="JBoss v3.2.x" server-type="org.eclipse.jst.server.generic.jboss323" server-type-id="org.eclipse.jst.server.generic.jboss323" timestamp="0"> <map jndiPort="1099" key="generic_server_instance_properties" port="8080" serverAddress="steve.local" serverConfig="all"/> </server> <server hostname="localhost" id="6_14_06_6_33_PM3" name="JBOSS 3.2.3 2" runtime-id="JBoss v3.2.x" server-type="org.eclipse.jst.server.generic.jboss323" server-type-id="org.eclipse.jst.server.generic.jboss323" timestamp="0"> <map jndiPort="1099" key="generic_server_instance_properties" port="8080" serverAddress="localhost" serverConfig="all"/> </server> <server hostname="localhost" id="6_14_06_6_44_PM3" name="JBOSS 4.0" runtime-id="JBoss v4.0" server-type="org.eclipse.jst.server.generic.jboss4" server-type-id="org.eclipse.jst.server.generic.jboss4" timestamp="0"> <map jndiPort="1099" key="generic_server_instance_properties" port="8080" serverAddress="localhost" serverConfig="default"/> </server> <server auto-publish-setting="2" auto-publish-time="1" configuration-id="/Servers/Tomcat v5.5 Server @ localhost-config" debug="true" hostname="127.0.0.1" id="6_14_06_6_57_PM7" name="Tomcat v5.5 Server @ localhost" runtime-id="Apache Tomcat v5.5" server-type="org.eclipse.jst.server.tomcat.55" server-type-id="org.eclipse.jst.server.tomcat.55" testEnvironment="true" timestamp="1"/> </servers> Also even when it fails it still says that it's starting tomcat. Stoping tomcat fails too