Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Multiple Activation Spec not supporting

SA-9065

Summary



We have two application only one application able to send and receive messages from Queue. We have multiple activation spec for MQ integration in WAS7 however at one time we only have one activation spec up and the other activation spec is not coming up.

Error Messages



Not Applicable

Steps to Reproduce



Not Applicable


Root Cause



Issue1: Though the EAR was deployed by adding new Activation spec but it did not show up in WAS admin console Enterprise Applications --> PRPCEAR --> Manage message endpoints. This was due to caching in Websphere server.

Issue2: Below errors were noticed in server startup

[4/21/15 15:57:05:503 CDT] 00000029 ThreadMonitor W   WSVR0605W: Thread "WMQJCAResourceAdapter : 5" (00000020) has been active for 649993 milliseconds and may be hung.  There is/are 1 thread(s) in total in the server that may be hung.
                at java.lang.Object.wait(Native Method)
                at java.lang.Object.wait(Object.java:485)
                at com.ibm.ejs.container.MessageEndpointFactoryImpl.createEndpoint(MessageEndpointFactoryImpl.java:498)
                at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:255)
                at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)
                at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
[4/21/15 15:57:05:536 CDT] 00000029 ThreadMonitor W   WSVR0605W: Thread "WMQJCAResourceAdapter : 9" (00000024) has been active for 649486 milliseconds and may be hung.  There is/are 2 thread(s) in total in the server that may be hung.
                at java.lang.Object.wait(Native Method)
                at java.lang.Object.wait(Object.java:485)
                at com.ibm.ejs.container.MessageEndpointFactoryImpl.createEndpoint(MessageEndpointFactoryImpl.java:498)
                at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:255)
                at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)
                at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
 
This issue only happens if there are messages on the MQ queue upon application start and multiple MDBs exist in the same J2EE application. 

Resolution



Issue was resolved through the following local changes:

Issue1:  
Shut down Server.
Uninstall the PRPC enterprise application completely.  
Delete cached files from temp, tranlog, wstemp and, optionally, logs directories:

            Windows (where the WebSphere location is c:\program files\ibm\websphere\appserver, the application server profile is called AppSrv01, the node is called Node01, and the server is called MXServer). *.* means contents of the named directory:

                            C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\Node01\MXServer\*.*

                            C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\tranlog\Cell01\Node01\MXServer\*.*
                            C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\*.*
                            (optional) C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\logs\MXServer\*.*
            Unix (where the WebSphere location is /opt/IBM/WebSphere/AppServer/profiles/AppSrv01, the application server profile is called AppSrv01, the node is called Node01, and the server is called MXServer). *.* means contents of the named directory:

                            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/Node01/MXServer/*.*
                            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/tranlog/Cell01/Node01/MXServer/*.*
                            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/wstemp/*.*
                            (optional) /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/MXServer/*.*

Delete PRPC.ear from installedApps, both the contents of the directory and the directory itself:

            Windows (locations as above):
                            C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\Cell01\PRPC.ear
            Unix (locations as above):
                            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/Cell01/PRPC.ear
Deploy the new PRPC enterprise application.
Synchronize nodes. System Administration > Nodes, check the node to synchronize, then click the Synchronize button.  

Issue2: 
For WebSphere Application Server: In the console under JMS-->Activation specifications --> Maximum concurrent Endpoints, we need to input 1 as the minimum and maximum size and click on Apply.
 
If you are using WebSphere MQ, the solution for this issue is to set the WebSphere MQ Resource Adapter property: connectionConcurrency to the value 1 at the WebSphere Application Server Cell Scope.

 
- Start WebSphere Application Server.
- Bring up the WebSphere Administrative Console, and log in.
- On the left of the Administrative Console, expand: Resources-> Resource Adapters à All scopes
- Just above the table showing all of the Resource Adapters, you should see a subheading called: Preferences, Expand this, and select the: Show built-in resources checkbox. Click Apply.
- The Administrative Console will now refresh, and show a list of Resource Adapters that have been installed. There should be three entries for the: WebSphere MQ Resource Adapter
- Click on the entry for this Resource Adapter at the Cell Scope.
- This should bring up the configuration panel for the Resource Adapter. On the left of this panel, click on the: Custom properties link.
- When the Custom properties panel appears, you should see a table containing 7 entries. Click on the entry for: connectionConcurrency
- In the next panel, change the value of this property to 1, and click on OK.
- Save the configuration changes, and log off from the Administrative Console.
- The application server needs to be stopped and restarted for this change to take effect.

 

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us