Hello,

We are having a platform with 4 appservers of which 2 are using JMSMDB listeners.

Our platform runs on Websphere and according to this link on the PDN we have to stop and start our appservers each time we are deploying an new JMSMDB listener

https://docs.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7

When we do perform a stop and start, it triggers an automatic restart of the other appserver. Off course, this is not what we want to happen.

We've raised a request at the IBM support site and got this link back.

https://www.ibm.com/docs/en/was-nd/8.5.5?topic=files-hot-deployment-dynamic-reloading

On this site, the text underneath is clearly stating

It talks about the two steps to take for hot deployment.

----------------------------------

Required: If you are running WebSphere Application Server on a group of

machines using WebSphere Application Server, Network Deployment and you

are changing an application on a particular node, disable automatic

synchronization.

    Click System Administration > Node agents > node_agent_name > File

synchronization service in the console navigation tree.

    On the File synchronization service page, clear the check box for

Automatic synchronization and click OK.

When you run WebSphere Application Server on a group of machines using

WebSphere Application Server, Network Deployment and you change a file

on the disk in the expanded application directory for a particular

node, you can lose those changes the next time node synchronization

occurs. In the WebSphere Application Server, Network Deployment

environment, the configuration stored by the deployment manager is the

master copy and any changes detected between that master copy and the

copy on a particular machine trigger the master copy to be downloaded

to the node.

--------------------------------------

Also it clearly states that hot deployment is NOT meant for production

systems as it could cause unpredictable results.

-----------------------------------

Important: Do not use hot deployment to update components in a

production deployment manager managed cell. Hot deployment is

well-suited for development and testing, but poses unacceptable risks

to production environments. Full or partial resynchronization might

erase hot deployed components. Also, running the restoreconfig command

might overwrite changes made to expanded application files. Further,

hot deployed components are not migrated between versions of WebSphere®

Application Server. To add new components or modules to an enterprise

application, reassemble the application EAR file so it has the new

components or modules and then redeploy the EAR file.

Given the above, you have two properties be set to false in the server.xml file for the nodeagent:

As for as I understand so far, this all is recommended by both PEGA en IBM, thus, STOP appserver, add JMSMDB listener, START appserver.

We allthough want a 24/7 running platform.

Is it possible to achieve that goal or do we need to stop using JMSMDB listeners then and what would be the alternative?

Kind regards,

Arjan Maus