Shutdown procedure for the BPEL-SE

The idea is to first stop the incoming messages and allow those already in process to complete. Once the processes are complete, the BPEL SE can be shutdown for maintenence or upgrade. The incoming messages are stopped by suspending the endpoint which receives the messages. At present this is only supported for sun-http-binding component (HTTP BC).

Follow the steps outlined below to shutdown BPEL-SE for maintenence or upgrade

• Launch JConsole (jconsole.exe under your JDK/bin). Select "Remote Process". Enter the address, username and password to connect to GlassFish. The address is usually "localhost:8686". Navigate to sun-http-binding custom MBean as shown in the picture below.
• Locate the endpoint by doing clicking on "listActiveEndpoints" button. Copy and paste the endpoint to be suspended in the text box for "suspend". Click on "suspend". Any messages received for this endpoint will receive a "HTTP/1.1 404 Not Found" message.
• Wait for all the process instances that are already running, to complete. You can do this using the BPEL-SE Command Line Monitoring Tool.
• Shutdown BPEL-SE and do the maintenance or upgrade. Note that if you use the "Upgrade" option from Nebeans Services->Servers->GlassFish V2->JBI->sun-bpel-engine->Upgrade, the BPEL-SE will be automatically shutdown.
• Resume the suspended endpoint by copying and pasting the endpoint in the text box for "resume" and clicking on the button.

Your upgrade is complete.

FAQs Q. I have a BPEL process that has a receive-reply pair. What happens to the active process instances for which the responses have not been received yet and the HTTP BC endpoint is suspended? A. The suspend functionality only suspends the incoming messages. The responses will be sent to the client by the HTTP BC whenever the BPEL process instance executes the reply activity.

Q. I have a BPEL process: Receive-Invoke-Reply. If I suspend the endpoint for Receive, does it affect the Invoke which consumes a web service via HTTP BC. A. No, the Invoke is not affected

Q. Does the HTTP BC suspend functionality correspond to any of the JBI lifecycle actions for the Service Unit. A. No, the HTTP BC suspend functionality is a custom functionality and has nothing to do with the JBI specification.

Q. What if the business process has a wait activity, how would these instances be handled. A. If the business process has a wait, then after the endpoint is suspended, the user must wait for all the process instances to complete before he/she shuts down the BPEL-SE.

Q. What if the business process is waiting for a correlated receive. A. The user can suspend the endpoint which initiates the business process, then wait for all the correlated messages (related to another endpoint) to arrive. Once this is done and the instances are completed, the user can shutdown the BPEL-SE.

This page (revision-1) was last changed on 22-Apr-08 18:54 PM, -0700 by Prashant Bhagat.

More info...