[JBoss-user] [Beginners Corner] - Re: shutdown hangs
Check your jboss-service.xml file for the JBoss NamingService port:
mbean code=org.jboss.naming.NamingService
| name=jboss:service=Naming
| !-- The listening port for the bootstrap JNP service. Set this to -1
| to run the NamingService without the JNP invoker listening port.
| --
| attribute name=Port11099/attribute
| !-- The bootstrap JNP server bind address. This also sets the default
| RMI service bind address. Empty == all addresses
|--
| attribute name=BindAddress${jboss.bind.address}/attribute
| !-- The port of the RMI naming service, 0 == anonymous --
| attribute name=RmiPort11098/attribute
| !-- The RMI service bind address. Empty == all addresses
|--
| attribute name=RmiBindAddress${jboss.bind.address}/attribute
|/mbean
|
My guess is shutdown.sh hasn't been working since the port was changed from the
default port 1099 to 11099.
Specify the same port (port 11099) in your shutdown.sh command:
shutdown.sh -S -s servername:11099
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3871840#3871840
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871840
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-user mailing list
JBoss-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Beginners Corner] - shutdown hangs
Hi, The shutdown.sh script hangs when it reaches the following line: exec /usr/java14/bin/java -classpath /aifs/op/java/lib/jboss/jboss-3.2.7/bin/shutdown.jar:/aifs/op/java/lib/jboss/jboss-3.2.7/client/jnet.jar org.jboss.Shutdown -S However, it shuts down okay using the jmx.console, and with a control-C from the terminal. shutdown.sh used to work. Remedies I have tried (after extensive searches through the forums) include increasing memory (both of the JVM and message cache) and upgrading from 3.2.5 to 3.2.7 What else can I try? Cheers, Mal. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=3871091#3871091 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3871091 --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
