What are the best practices to shut-down a hung SOA-P node during it's processing existing requests from remote JMS server?
Issue
- There are 3 node
SOA-P
servers running cluster talking to a 2 nodeJMS
server (e.g. usingJBoss Messaging
stack) cluster running on remoteJBoss EAP
servers. TheESB
applications deployed onSOA-P
are dependent upon theJMS
server to be up and running. That means before shut-down ofSOA-P
server takes place someone has to shut downSOA-P
servers first, then theJMS
server instances. Is there a way to break that dependency? Perhaps it could be achieved by shutting down certain services onSOA-P
server instances so it stops listening on the remote queues? - The current problem is if the
JMS
server goes down,SOA-P
server instances can't be shut down because it will be hung waiting to connect to theJMS
queues, and it's process needs to be killed. - What are the best practices to shut-down a hung SOA-P node during it's processing existing requests from remote
JMS
server?
Environment
- Red Hat JBoss SOA Platform (SOA-P)
- 5.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.