[ http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40?page=comments#action_12362879 ]
Sachin Patel commented on GERONIMODEVTOOLS-40: ---------------------------------------------- I found the cause of the problem. When creating and starting the server programatically, the setServerStarted implementation in GeronimoServerBehavior requires the RMI port to be set something that would be specified if you had created the server using the wizard. So even though the server is started, the server startup times out since it could never connect to the kernel since the port was never set. During tracing you can see the port is null in the connection URL. org.apache.geronimo.devtools.eclipse.core: service:jmx:rmi://localhost/jndi/rmi://localhost:null/JMXConnector org.apache.geronimo.devtools.eclipse.core: Kernel connection failed. The http port never got set either, even though the server definition file in the plugin contains defaults for both these values, they never get set when defining the server programatically. My initial guess is that this is WTP bug because when defining a server programitcailly the servers.xml file should have default specified for all properties . > Cannot start server programmatically > ------------------------------------ > > Key: GERONIMODEVTOOLS-40 > URL: http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-40 > Project: Geronimo-Devtools > Type: Bug > Components: eclipse-plugin > Environment: Windows XP > Reporter: Kathy Chan > Priority: Critical > > I was using the following drivers on Windows XP: > - WTP 1.0 > - Geronimo 1.0 server > - Geronimo 20060109 plugin > With a new workspace, do the following: > - install Geronimo 1.0 server runtime > - create Geronimo server using server tooling > - start server > - create Web project "a1" with EAR > - In the Web project, create a simple Echo.java with a "hello" method that > takes a String and returns it. > Here are the procedure to create a bottom-up Web service: > - right-click on Echo.java, select Web Services -> Create Web service > - select "test Web service" and "overwrite file" on the 1st page of Web > service wizard > - click Finish > - when the Web Services Explorer comes up, you should be able to invoke the > hello method > Now, if you remove the Web project "a1" from the server and ensure that the > server is still in "started" state, then you can repeat the above steps to > create a bottom-up Web service. > However, if you do not remove the Web project from the server first, then > you'll run into the problem reported in bug > http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-39. > If you remove the Web project from the server first but stop the server > before creating the bottom-up Web service, when the Web service wizard tried > to start the server programmatically, you'll notice that the server console > indicates that > Geronimo startup complete > but server tooling still thinks that the server is started. The server start > will eventually times out. > Now, even if I use server tooling to start the server, server start would not > complete. This problem persist even if I delete the server and recreate > another one. The only way I could recover is to use a new workspace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
