« Accessing an HTTPS web service from WAS web client
Creating a Business Integration Module, Library and Mediation Module »

com.ibm.websphere.management.exception.AdminException: CWWBF0024E: Process XXX of application xxxx is not stopped.

2 votes Vote!!

Published April 17th, 2008 in WebSphere, Websphere Process Server / Integration Developer

When we try to uninstall a Business Integration module, we will get an error message in the admin console “An error occurred while uninstalling XXX. Check the logs for more details.” If we look into SystemErr.log we can see the exception stack trace

[4/18/08 9:40:40:107 GMT] 00000166 SystemErr     R com.ibm.websphere.management.exception.AdminException: CWWBF0024E: Process XXXProcess of application XXX is not stopped. Stop the templates manually before updating or uninstalling a process application.
        at com.ibm.bpe.processarchive.ProcessServerTask.checkIfApplicationRemovable(ProcessServerTask.java:142)
        at com.ibm.bpe.processarchive.ProcessComponentUninstallTask.performTask(ProcessComponentUninstallTask.java:134)
        at com.ibm.ws.management.application.SchedulerImpl.run(SchedulerImpl.java:253)
        at java.lang.Thread.run(Thread.java:570)
:570)

This error is because we have some business processes still running on the server. Now to uninstall the application we need to stop all the running business processes. If we cannot stop all the running processes there is an easy way to uninstall the application.

Click on your application under Enterprise Application page. From the page opened up we can see a section called Related Items. Click on EJB Modules link under Related Items. The EJB modules present in your application will be displayed. Select the EJB Module and click on Remove button. The EJB modules will be removed from the enterprise application. Now save the changes to Master Repository. Go back to Enterprise Applications page and we can uninstall the application without any issues.

The problem with this approach is that none of the existing business processes will be available any more.

The same method can also be used if we are getting the following exception too.
CWWBF0057E: The application cannot be stopped because of existing process instances.: [XXXProcess]

Did you like this? If so, please
tell a friend
about it, and subscribe to the blog RSS feed.

Share/Save/Bookmark

If you enjoyed this post, make sure you subscribe to my RSS feed!


Related Posts:
  • UNAUTHENTICATED is not granted any of the required roles: eventAdministrator eventCreator catalogAdministrator
  • org.xml.sax.SAXException: WSWS3047E: Error: Cannot deserialize element
  • Invoking an external web service from WebSphere Process Server.
  • Creating a Business Calendar in WebSphere Integration Developer 6.1.2
  • Querying human task based on custom property using EJB API


    • 4 Responses to “com.ibm.websphere.management.exception.AdminException: CWWBF0024E: Process XXX of application xxxx is not stopped.”  

    Feed for this Entry Trackback Address
    1. 1 Akram Chotu Apr 19th, 2008 at 1:57 am

      I also work with WID, WPS, WTX etc. in Healthcare domain. Your blog is really useful to me and I thank you for taking time in sharing your knowledge. Keep up the good work.

    2. 2 Albin Joseph Apr 19th, 2008 at 3:34 am

      Thanks Akram. I just want to share my experiences on WPS and WID.

    3. 3 Dan Zrobok May 21st, 2008 at 4:11 am

      Just wanted to add that if this isn’t a production server, there is an option in the admin console’s server config for “Development Mode” which relaxes the BPEL engines insistence that you not destroy business processes when installing new flows. It’ll just turf automatically them without exception.

    4. 4 Albin Joseph May 22nd, 2008 at 9:03 pm

      Thanks Dan.

    Leave a Reply