Architecting, installing and maintaining your SAS environment

JMS broker is not up

Reply
Super Contributor
Super Contributor
Posts: 358

JMS broker is not up

hello

 

we have couple web applications running and we just restarted sas servers for web apps

 

/Lev1$./sas.servers status

 

SAS servers status:

SAS JMS Broker is NOT up

SAS Cache Locator Service ins_41415 is UP

SAS Web Server is UP

SAS Web App Server SASServer1_1 is UP

SAS Web App Server SASServer11_1 is UP

SAS Web App Server SASServer11_2 is UP

SAS Web App Server SASServer1_2 is UP

SAS Web App Server SASServer12_1 is UP

SAS Web App Server SASServer12_2 is UP

SAS Web App Server SASServer13_1 is UP

SAS Web App Server SASServer13_2 is UP

SAS Web App Server SASServer2_1 is UP

SAS Web App Server SASServer2_2 is UP

SAS Environment Manager is UP

SAS Environment Manager Agent is NOT up

 

we tried performing some work arround using below sas notes but still same situation - JMS Broker and EVM Agent not starting up

 

http://support.sas.com/kb/57/507.html

http://support.sas.com/kb/54/066.html

http://support.sas.com/kb/52/315.html

 

any suggesiton?

 

Thanks!

 

 

 

 

 

 

 

 

 

 

 

Trusted Advisor
Posts: 1,312

Re: JMS broker is not up

Hello @woo,

 

what nare the error messages in your logs? Have you tried to stop/starte them manually? Did you check the port numbers are not in use while the services are down? Some additional information will help us to understand what is going on, and the more, the best.

 

Juan

Super Contributor
Super Contributor
Posts: 358

Re: JMS broker is not up

[ Edited ]
Posted in reply to JuanS_OCS

your guess is right, we didn't check if services running before we restart services, but here are some logs.

 

activemq.log

date:time | ERROR | Failed to start Apache ActiveMQ (localhost, ID:....com-17792-1501701809286-0:1). Reason: java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:xxxxx due to: java.net.BindException: Address already in use | org.apache.activemq.broker.BrokerService | main
java.io.IOException: Transport Connector could not be registered in JMX: Failed to bind to server socket: tcp://0.0.0.0:xxxxx due to: java.net.BindException: Address already in use
        at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27)
        at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1977)
        at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2468)
        at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2385)
        at org.apache.activemq.broker.BrokerService.doStartBroker(BrokerService.java:684)
        at org.apache.activemq.broker.BrokerService.startBroker(BrokerService.java:642)
        at org.apache.activemq.broker.BrokerService.start(BrokerService.java:578)
        at org.apache.activemq.xbean.XBeanBrokerService.afterPropertiesSet(XBeanBrokerService.java:58)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)

 

console.log

 

ERROR: java.lang.Exception: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
java.lang.Exception: java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext
        at org.apache.activemq.console.command.StartCommand.runTask(StartCommand.java:99)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
        at org.apache.activemq.console.command.ShellCommand.runTask(ShellCommand.java:148)
        at org.apache.activemq.console.command.AbstractCommand.execute(AbstractCommand.java:57)
        at org.apache.activemq.console.command.ShellCommand.main(ShellCommand.java:90)

 

Occasional Contributor
Posts: 6

Re: JMS broker is not up

It seems the previous process was not shut down properly and it is still locking the port.

Try this,

 

netstat -nap |grep 61616

 

check the process ID and Kill it.

 

and then try to start again.

Super Contributor
Super Contributor
Posts: 358

Re: JMS broker is not up

[ Edited ]

we have multiple sas web app + processes running at the moment - if have issue with only one web applicstion and if we want to restart it, how we do it? for example if we have web app running under "SASServer11_1" - thank you-

 

Occasional Contributor
Posts: 6

Re: JMS broker is not up

Steps On Linux:

cd /Web/WebAppServer/SASServer11_1/bin
tcruntime-ctl.sh stop
tcruntime-ctl.sh start
Trusted Advisor
Posts: 1,312

Re: JMS broker is not up

Hello @woo,

 

justan addition to @vrkgali indications. There is an alternative of stoping and starting web applications or web application servers with the SAS Environment Manager GUI and an administrator account. The process is described here: https://platformadmin.com/blogs/paul/2015/09/restart-sas-web-apps-with-sas-environment-manager/

 

Anyway, whi would you need to do that? If you manage to kill the port as described by @vrkgali, you only need to ./sas.servers.mid stop and ./sas.servers.mid start. I just like simpler solutions when available. Smiley Happy

Ask a Question
Discussion stats
  • 6 replies
  • 443 views
  • 1 like
  • 3 in conversation