This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 67680 - [50cat] IDE thinks SJS server isn't running, when it actually is
Summary: [50cat] IDE thinks SJS server isn't running, when it actually is
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: _ ludo
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-10-27 14:31 UTC by clever
Modified: 2005-11-18 15:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description clever 2005-10-27 14:31:34 UTC 
[ BUILD # : 200510251800 ]
[ JDK VERSION : 1.4.2_xx ]

Yesterday I started the SJS server. It ran overnight. Today I came in to redeploy my webapp. When I did, I get errors saying it can't be started. Refreshing the Servers tree, it definitely IS running.  The error is simply:

Starting server Sun Java System Application Server
C:\Apps\Sun_AppServer\domains\\domain1\bin\startserv.bat  
The Sun Java System Application Server could not start.

A restart of the IDE allowed NB to properly detect the state of the running server.
Comment 1 Sherold Dev 2005-10-27 16:53:58 UTC 
looks like appserver plugin problem -> sunappserv
Comment 2 _ ludo 2005-10-28 15:41:31 UTC 
Cannot reproduce so you need to give more info:
refresh the server tree: what is the color of the icon? Do you see the sub-nodes?
Refresh does not trigger a restart, so when do you have this message?
Please, attach the server log and the IDE log.
Comment 3 clever 2005-10-28 15:44:56 UTC 
I will do my best to put together a recreatable scenario.  I was hoping that the
engineers may be able to see an issue with the detection algorithm.  I'll do
what I can to provide more info.
Comment 4 _ ludo 2005-10-28 23:56:34 UTC 
The issue might be a timeout due to intermittent network issues...
The plugin is trying to communicate to the server via JSR 88 apis that are using
underlying http requests. If there si a timeout, the plugin believe the server
is not up or anyway non functional because no deployment can happen...
Did the network settings changed during this night? Did you disconnect/reconnect
to a different network (iw switch from home to office or wireless to non wireless?

Update the priority if you have hard time to reproduce. I'll look again at the
detection algo.
Comment 5 clever 2005-10-30 18:17:16 UTC 
Good afternoon!
Well, I can't remember any loss of network connectivity... (as the instance was
on the localmachine).  I remember trying to 'deploy' when the instance was
already running in debug mode when I saw it try to re-start the SJS server.  It
appeared to have 'hung' for a minute before I finally saw an error window.  From
that point on NB was unable to notice the currently running instancce.

I will try to repro on Monday, as I felt I was just doing standard routine stuff.

Thanks!
Comment 6 _ ludo 2005-11-02 22:16:15 UTC 
Random, so far cannot reproduce: P3
Comment 7 _ ludo 2005-11-17 04:28:44 UTC 
Cannot reproduce with current builds
Comment 8 clever 2005-11-18 15:32:15 UTC 
Works for me too. I'll take judicious notes if I can get this to happen again.
Thanks!!