[GLASSFISH-4152] Not able to re-start the domain after stopping it with out detaching the java debugger from a JCAPS project. Created: 11/Feb/08  Updated: 06/Mar/12

Status: Open
Project: glassfish
Component/s: other
Affects Version/s: v2.1
Fix Version/s: not determined

Type: Bug Priority: Minor
Reporter: us159569 Assignee: Bhavanishankar
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Attachments: Text File JMS1Q1T.zip     Text File server.log.zip    
Issuezilla Id: 4,152
Status Whiteboard:



When Java debugger is attached to the JVM, if we stop the domain, we can't start
it back.

Steps to reproduce:

0. Do a complete installation of JCAPS using the installer build: 20080128-0200
1. Import the attached JMS1Q1T.zip in to the netbeans IDE.
2. enable debugging in the GF domain you wish to deploy the application to.
3. checkout all the components of the project and its environment.
4. modify the integration server url in env to point to a running GF.
5. modify the debug port in the env to point to the correct debug port.
6. Create a dp, called Deployment1 for the JMS1Q1T_PROJECT; build it and deploy
it to the GF.
7. right click on the IS component in the environment and click on java debugger.
8. click ‘ok’ when the 'stop in class' screen appears.
9. Now stop the domain by running 'stopserv.bat'
10. Try re-starting the domain and notice that you would not be able to start it
back. Attached server.log

Comment by us159569 [ 11/Feb/08 ]

Created an attachment (id=1325)
JCAPS project

Comment by us159569 [ 11/Feb/08 ]

Created an attachment (id=1326)
server logs

Comment by harpreet [ 15/Feb/08 ]

JCAPS issue - assigned to Bhavani for preliminary investigation.

Comment by harpreet [ 12/Mar/08 ]

I have installed a standalone GF server, started GF in a debug mode from NB, built, deployed and
debugged a servlet. Stopped server and restarted in a normal/debug mode and the server starts up.

Bhavani can you look into the issue and see why is it different for a JCAPS server.

Comment by harpreet [ 25/Mar/08 ]

Based on input from Bhavani - marking it as as911-na. Issue seems to stem from sun-http-binding.

Comment by sanandal [ 11/Jan/09 ]

"Reclassifying as P4 because this issue is not deemed "must fix" for this v2.1
release whose primary release driver is SailFin.
This issue will be scrubbed after this release and will be given the right
priority for the next release."

Comment by kumara [ 01/Sep/09 ]

Changing version from 9.1.1 to v2.1 to reflect new name/version.

Comment by Tom Mueller [ 06/Mar/12 ]

Bulk update to change fix version to "not determined" for all issues still open but with a fix version for a released version.

Generated at Thu Mar 30 21:45:46 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.