- There are 3 node
SOA-Pservers running cluster talking to a 2 node
JMSserver (e.g. using
JBoss Messagingstack) cluster running on remote
JBoss EAPservers. The
ESBapplications deployed on
SOA-Pare dependent upon the
JMSserver to be up and running. That means before shut-down of
SOA-Pserver takes place someone has to shut down
SOA-Pservers first, then the
JMSserver instances. Is there a way to break that dependency? Perhaps it could be achieved by shutting down certain services on
SOA-Pserver instances so it stops listening on the remote queues?
- The current problem is if the
JMSserver goes down,
SOA-Pserver instances can't be shut down because it will be hung waiting to connect to the
JMSqueues, 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
- Red Hat JBoss SOA Platform (SOA-P)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.