NOTE: Transferring this from BugTraq.  According to Nanyan Xiong, this is a 
known problem that the Tomcat module cannot start the JWSDP from the IDE.  
Starting the external JWSDP via the "Deploy" or "Execute actions works properly 
but not explicitly starting the server from the server registry.  This is 
perhaps related to issue #30257.

Description: 


Name: dpR10070			Date: 10/06/2002


I've installed a copy of JWSDP 1_0_01 from sun.com
Then I added Tomcat from this instalation to SunONE Studio 4 update 1
I chose a minimal level of integration.

After this I supposed the new instance of Tomcat to Start normally from S1S4
I chose "Start server" from context menu and recieved the following exception.

java.net.UnknownHostException: jwsdp-services
        at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:143)
        at java.net.Socket.connect(Socket.java:425)
        at java.net.Socket.connect(Socket.java:375)
        at java.net.Socket.<init>(Socket.java:290)
        at java.net.Socket.<init>(Socket.java:118)
        at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.testPortAvailability
(Tomcat40Installation.java:937)
        at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.createNewTomcatProcess
(Tomcat40Installation.java:1101)
        at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.startServerInExecMode
(Tomcat40Installation.java:1086)
        at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.synchronizeStart
(Tomcat40Installation.java:1211)
        at 
org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.incrementalDeploy
(Tomcat40Installation.java:603)
        at org.netbeans.modules.tomcat.tomcat40.Tomcat40Instance.deploy
(Tomcat40Instance.java:259)
        at org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.doDeploy
(DefaultServerInstanceManager.java:145)
        at 
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.startExecution
(DefaultServerInstanceManager.java:159)
        at 
org.netbeans.modules.j2ee.impl.DefaultServerInstanceManager.serverInstanceStartE
xecution(DefaultServerInstanceManager.java:104)
        at org.netbeans.modules.j2ee.impl.DefaultExecPerformer.startExecution
(DefaultExecPerformer.java:105)
        at 
org.netbeans.modules.web.execution.WebDefaultExecPerformer.startExecution
(WebDefaultExecPerformer.java:246)
        at org.netbeans.modules.j2ee.impl.ServerExecutor.execute
(ServerExecutor.java:74)
        at org.netbeans.modules.j2ee.impl.ServerExecutor.execute
(ServerExecutor.java:64)
        at org.netbeans.modules.tomcat.tomcat40.Tomcat40DataObject.start
(Tomcat40DataObject.java:644)
        at org.openide.actions.ExecuteAction.execute(ExecuteAction.java:140)
        at org.openide.actions.ExecuteAction.execute(ExecuteAction.java:237)
        at org.openide.actions.ExecuteAction.performAction
(ExecuteAction.java:102)
        at org.openide.util.actions.NodeAction.performAction
(NodeAction.java:180)
        at org.openide.util.actions.NodeAction.actionPerformed
(NodeAction.java:171)
        at org.netbeans.core.ModuleActions$1.run(ModuleActions.java:105)
        at org.openide.util.Task.run(Task.java:152)
[catch] at org.openide.util.RequestProcessor$ProcessorThread.run
(RequestProcessor.java:622)
 
Despite of the exception some portion of Tomcat was unexpectedly executed and 
this was 
reflected on Execution window. 

The version of S1S4 I'm using
 -- System Info ----------------------------------------------------------------
Product Version       = Sun ONE Studio 4 update 1, Enterprise Edition (Build 
020923)
IDE Versioning        = IDE/1 spec=1.43.3.1 impl=020923
Operating System      = SunOS version 5.8 running on sparc
Java; VM; Vendor      = 1.4.0; Java HotSpot(TM) Client VM 1.4.0-b92; Sun 
Microsystems Inc.

======================================================================

Evaluation: 

dmitry, did you set this up according to the getting started guide?  The error 
suggests that the host/port information is incorrect.  Can you use the steps in 
bug 4726974 (public summary) and see if it helps?  

Name: dpR10070			Date: 10/08/2002


Lark, this does not solve the problem. 
The cure you've mentioned lets develop web-centric webservices.
The process of deployment web-services on Tomcat(localhost:8080) 
runs fluently. 
But as I expected after installing Tomcat into S1S4
user would first check the correctness of performes procedure by running
installed Tomcat. It fails. This may confuse a user and would add some
job to Sun's customer service at least.
 
 

======================================================================

thanks, dmitry.  I see two problems. 
Problem 1 is that the user has to install an external tomcat to run a 
webcentric web service.  Unfortunatly we were unable to upgrade the internal 
tomcat for sierra, this will be done for dublin. 
Problem 2 is that once you add an external tomcat (minimum or full) you cannot 
start it from the IDE.  This should be supported and if not, the menu item 
should be disabled.  Unfortunately, this could be a compatibility problem 
between tomcat 4.0 and tomcat 4.1.





A comment.