0 Replies Latest reply on Oct 20, 2014 5:35 PM by Praneshkumar Pandian

    AJP Port still listening after JBoss 6.2.0 EAP shutdown making it to hung.

    Praneshkumar Pandian Newbie

      Hello,

       

      I'm using JBoss 6.2.0 EAP in linux with Apache as front end and once after issuing "./jboss-cli.sh -c --controller=localhost:$mgmt_native_port --commands=:shutdown", I do see all the JBoss ports are closed but AJP port still listening making JBoss not to shutdown completely. I noticed in server.log posts message till deployment stops but not seeing server shut down message. Is this a default behaviour in JBoss 6.2.0 or any setting to make it close explicitly while server goes down? Also I did notice JBoss PID is still shows as running. Please advice.

       

      14:28:56,368 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment xyz.war (runtime-name: xyz.war) in 78ms

       

      Below message is from another instance which stops the server completely.

      14:28:56,368 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment xyz.war (runtime-name: xyz.war) in 78ms

      14:28:56,373 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 62ms

      14:28:56,373 INFO  [org.jboss.as] (MSC service thread 1-4) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 62ms

       

      Thanks.