cofactor
asked on
stop jboss server in Linux
Hi, Here I have tried to stop jboss server in Linux . This seems does not work. Could you please tell where is the problem ?
Please find the file attached. Sensitive information has been masked.
serverstart.txt
Please find the file attached. Sensitive information has been masked.
serverstart.txt
also, if you have multiple IPs on that server, JBoss might bind some ports only to some IP
issue a "netstat -na" and find out the listening port and IP
issue a "netstat -na" and find out the listening port and IP
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
kill -9 should be the almost the last thing you try (before rebooting)
Hi,
try to Set up all the permissions and run levels like this:
sudo chown root:root /etc/init.d/jboss
sudo chmod ug+x /etc/init.d/jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc3.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc4.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc5.d/S84jboss
ln -s /etc/rc.d/init.d/jboss/etc /rc6.d/K15 jboss
ln -s /etc/rc.d/init.d/jboss/etc /rc0.d/K15 jboss
ln -s /etc/rc.d/init.d/jboss/etc /rc1.d/K15 jboss
ln -s /etc/rc.d/init.d/jboss/etc /rc2.d/K15 jboss
and try to start up like :
$ /etc/init.d/./jboss start or $ /etc/init.d/./jboss stop
OR
Stopping JBoss, if you launched JBoss from the command line, the easiest way to stop it is to press ctrl-C. JBoss should begin it's shutdown. (OR) ./shutdown.sh -S in jboss bin folder.
try to Set up all the permissions and run levels like this:
sudo chown root:root /etc/init.d/jboss
sudo chmod ug+x /etc/init.d/jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc3.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc4.d/S84jboss
ln -s /etc/rc.d/init.d/jboss /etc/rc5.d/S84jboss
ln -s /etc/rc.d/init.d/jboss/etc
ln -s /etc/rc.d/init.d/jboss/etc
ln -s /etc/rc.d/init.d/jboss/etc
ln -s /etc/rc.d/init.d/jboss/etc
and try to start up like :
$ /etc/init.d/./jboss start or $ /etc/init.d/./jboss stop
OR
Stopping JBoss, if you launched JBoss from the command line, the easiest way to stop it is to press ctrl-C. JBoss should begin it's shutdown. (OR) ./shutdown.sh -S in jboss bin folder.
ASKER
>>/home/jboss/bin/shutdown .sh -S
my jboss start is a bind to host and started as a service . Is not we should stop as a service ?
>>>just use the kill command
>>kill pid
Is it not good to stop the service ? is there any way for that ?
Also, how do we know the startup status when I start jboss as a service ? it does not return anything ..seems things are in the background . How do I know the startup status ?
my jboss start is a bind to host and started as a service . Is not we should stop as a service ?
>>>just use the kill command
>>kill pid
Is it not good to stop the service ? is there any way for that ?
Also, how do we know the startup status when I start jboss as a service ? it does not return anything ..seems things are in the background . How do I know the startup status ?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
Use this following command to stop the server:-
% ./shutdown.sh --host=myremotemachineOrIP -S
Try providing your machine's ip address instead of "localhost".
and also check the boot & server logs in jboss
MS
Use this following command to stop the server:-
% ./shutdown.sh --host=myremotemachineOrIP
Try providing your machine's ip address instead of "localhost".
and also check the boot & server logs in jboss
MS
ASKER
>>>look at boot.log - notice the timestamp
>>>look at server.log from the timestamp of the boot.log
why timestamp is required here ? I dont understand why you are telling to note the timestamp . why do I need that ?
>>>look at server.log from the timestamp of the boot.log
why timestamp is required here ? I dont understand why you are telling to note the timestamp . why do I need that ?
to see the log at the time the server started ....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
>>>Could you post
Yes. But I may not post the entire server details in public . Would you like to see any specific portion ?
Please tell me which portion you would like to check ..I'd copy that part and post it here.
You may tell me which Tag to copy from those files so that it would be helpful to check
Yes. But I may not post the entire server details in public . Would you like to see any specific portion ?
Please tell me which portion you would like to check ..I'd copy that part and post it here.
You may tell me which Tag to copy from those files so that it would be helpful to check
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
>>>>Please tye to use
>>/home/jboss/bin/shutdown .sh -S
>>to see if this typical command can stop your jboss smoothly
when I run the above I get this ..
/home/jboss/bin/shutdown.s h -S
Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavai lableExcep tion [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused]
at javax.management.remote.rm i.RMIConne ctor.conne ct(RMIConn ector.java :338)
at javax.management.remote.JM XConnector Factory.co nnect(JMXC onnectorFa ctory.java :248)
at org.jboss.Shutdown.main(Sh utdown.jav a:235)
Caused by: javax.naming.ServiceUnavai lableExcep tion [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused]
at com.sun.jndi.rmi.registry. RegistryCo ntext.look up(Registr yContext.j ava:101)
at com.sun.jndi.toolkit.url.G enericURLC ontext.loo kup(Generi cURLContex t.java:185 )
at javax.naming.InitialContex t.lookup(I nitialCont ext.java:3 92)
at javax.management.remote.rm i.RMIConne ctor.findR MIServerJN DI(RMIConn ector.java :1886)
at javax.management.remote.rm i.RMIConne ctor.findR MIServer(R MIConnecto r.java:185 6)
at javax.management.remote.rm i.RMIConne ctor.conne ct(RMIConn ector.java :257)
... 2 more
Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
java.net.ConnectException: Connection refused
at sun.rmi.transport.tcp.TCPE ndpoint.ne wSocket(TC PEndpoint. java:601)
at sun.rmi.transport.tcp.TCPC hannel.cre ateConnect ion(TCPCha nnel.java: 198)
at sun.rmi.transport.tcp.TCPC hannel.new Connection (TCPChanne l.java:184 )
at sun.rmi.server.UnicastRef. newCall(Un icastRef.j ava:322)
at sun.rmi.registry.RegistryI mpl_Stub.l ookup(Unkn own Source)
at com.sun.jndi.rmi.registry. RegistryCo ntext.look up(Registr yContext.j ava:97)
... 7 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.s ocketConne ct(Native Method)
at java.net.PlainSocketImpl.d oConnect(P lainSocket Impl.java: 351)
at java.net.PlainSocketImpl.c onnectToAd dress(Plai nSocketImp l.java:213 )
at java.net.PlainSocketImpl.c onnect(Pla inSocketIm pl.java:20 0)
at java.net.SocksSocketImpl.c onnect(Soc ksSocketIm pl.java:36 6)
at java.net.Socket.connect(So cket.java: 529)
at java.net.Socket.connect(So cket.java: 478)
at java.net.Socket.<init>(Soc ket.java:3 75)
at java.net.Socket.<init>(Soc ket.java:1 89)
at sun.rmi.transport.proxy.RM IDirectSoc ketFactory .createSoc ket(RMIDir ectSocketF actory.jav a:22)
at sun.rmi.transport.proxy.RM IMasterSoc ketFactory .createSoc ket(RMIMas terSocketF actory.jav a:128)
at sun.rmi.transport.tcp.TCPE ndpoint.ne wSocket(TC PEndpoint. java:595)
... 12 more
>>/home/jboss/bin/shutdown
>>to see if this typical command can stop your jboss smoothly
when I run the above I get this ..
/home/jboss/bin/shutdown.s
Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavai
java.net.ConnectException:
at javax.management.remote.rm
at javax.management.remote.JM
at org.jboss.Shutdown.main(Sh
Caused by: javax.naming.ServiceUnavai
java.net.ConnectException:
at com.sun.jndi.rmi.registry.
at com.sun.jndi.toolkit.url.G
at javax.naming.InitialContex
at javax.management.remote.rm
at javax.management.remote.rm
at javax.management.remote.rm
... 2 more
Caused by: java.rmi.ConnectException:
java.net.ConnectException:
at sun.rmi.transport.tcp.TCPE
at sun.rmi.transport.tcp.TCPC
at sun.rmi.transport.tcp.TCPC
at sun.rmi.server.UnicastRef.
at sun.rmi.registry.RegistryI
at com.sun.jndi.rmi.registry.
... 7 more
Caused by: java.net.ConnectException:
at java.net.PlainSocketImpl.s
at java.net.PlainSocketImpl.d
at java.net.PlainSocketImpl.c
at java.net.PlainSocketImpl.c
at java.net.SocksSocketImpl.c
at java.net.Socket.connect(So
at java.net.Socket.connect(So
at java.net.Socket.<init>(Soc
at java.net.Socket.<init>(Soc
at sun.rmi.transport.proxy.RM
at sun.rmi.transport.proxy.RM
at sun.rmi.transport.tcp.TCPE
... 12 more
ASKER
>>>ps -ef | grep jboss
This shows the list but not formatted . Hence I find difficult to identify the jboss process id.
Could you please modify the above command so that this prints a nicely formatted listing . This will help me to dentify the process id for jboss and thereafter to kill this process.
I'm using putty.exe to connect to server.
This shows the list but not formatted . Hence I find difficult to identify the jboss process id.
Could you please modify the above command so that this prints a nicely formatted listing . This will help me to dentify the process id for jboss and thereafter to kill this process.
I'm using putty.exe to connect to server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
kill pid
it will not kill the JBoss, just will signal it to close
JBoss will shutdown gracefully