| Author |
Message
|
| yupoet |
 Posted: Thu Sep 02, 2010 7:43 am Post subject: WAS JMS issues about MQ 7 migration on new ZFS file system. |
 |
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
I upgraded one MQ on z/OS platform from v6 (latest maintenance) to v7.0.1.
(z/OS now is 1.12 as well.) |
|
| Back to top |
|
 |
| yupoet |
| Posted: Thu Sep 02, 2010 7:47 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
From the install guide below we also set up the new ZFS file
2.7.2.1 Service ZFS
PARMLIB SETUP FOR SERVICE ZFS
+---------------+-----------------------------------------------------------+
| MEMBER | ACTION |
+---------------+-----------------------------------------------------------+
| BPXPRMxx | Mount WWZ038.GSD2010A.MQM701.OMVS.SCSQOJS at mountpoint |
| | '/_SERVICE/WWZ038/GSD2010A/MQM701/usr/lpp/mqm/V7R0M1' |
+---------------+-----------------------------------------------------------+
+---------------+-----------------------------------------------------------+
| BPXPRMxx | Mount &yhlqomvs..MQM*ssid*.*SYS*.V*OVOL*.MQM.ZFS at |
| | mountpoint '/_PRDS/MQM*ssid*/SCSQOJS' |
+---------------+-----------------------------------------------------------+
Now the new ZFS file was mounted into a USS folder in OMVS.
The application should be using the new set of files.
But I met the following WAS job issues after mountting the new mq7 JAVA files-->
Message: BBOO0220E: WMSG0057E: Error on JMSConnection for MDB PricingMessage , JMSDestination jms/queue/PricingAvailable , JMS Linked Exception : com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2012' ('MQRC_ENVIRONMENT_ERROR').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
Error message BBOO0220E :
means following
Java code ported from another platform may issue messages which
do not conform to z/OS message conventions. In that case, error
messages are wrapped with this message to ensure compliance.
Action For more information about this message, refer to the WebSphere
Application Server Server for z/OS Information Center.
Does anyone know where the problem is? |
|
| Back to top |
|
|
| yupoet |
| Posted: Thu Sep 02, 2010 7:50 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
One more question, as I compared the old WAS files with the new ones
V6
-r--r--r-- 1 13143 Mar 23 2009 CL3Export.jar
-r--r--r-- 1 33166 Mar 23 2009 CL3Nonexport.jar
drwxr-xr-x 2 8192 Mar 23 2009 OSGI
-r--r--r-- 1 457831 Mar 23 2009 com.ibm.mq.jar
-r--r--r-- 1 1304544 Mar 23 2009 com.ibm.mqjms.jar
-r--r--r-- 1 17978 Mar 23 2009 connector.jar
-r--r--r-- 1 1997409 Mar 23 2009 dhbcore.jar
-r--r--r-- 1 22769 Mar 23 2009 fscontext.jar
-r--r--r-- 1 25998 Mar 23 2009 jms.jar
-r--r--r-- 1 8809 Mar 23 2009 jta.jar
-r--r--r-- 1 33290 Mar 23 2009 libPgmIpLayer.so
-rwxr-xr-x 1 151552 Mar 23 2009 libmqjbatch.so
-r--r--r-- 1 163840 Mar 23 2009 libmqjbatch64.so
lrwxrwxrwx 1 14 Jul 1 2009 libmqjbatch_g.so -> libmqjbatch.so
-rwxr-xr-x 1 61440 Mar 23 2009 libmqjbnd.so
lrwxrwxrwx 1 12 Jul 1 2009 libmqjbnd_g.so -> libmqjbnd.so
-rwxr-xr-x 1 167936 Mar 23 2009 libmqjrrs.so
-rwxr-xr-x 1 188416 Mar 23 2009 libmqjrrs64.so
lrwxrwxrwx 1 14 Jul 1 2009 libmqjrrs64_g.so -> libmqjrrs64.so
lrwxrwxrwx 1 12 Jul 1 2009 libmqjrrs_g.so -> libmqjrrs.so
-r--r--r-- 1 122880 Mar 23 2009 libmqjstb01.so
-rwxr-xr-x 1 385024 Mar 23 2009 libwmqjbatch.so
lrwxrwxrwx 1 15 Jul 1 2009 libwmqjbatch_g.so -> libwmqjbatch.so
-rwxr-xr-x 1 61440 Mar 23 2009 libwmqjbind.so
lrwxrwxrwx 1 14 Jul 1 2009 libwmqjbind_g.so -> libwmqjbind.so
-rwxr-xr-x 1 372736 Mar 23 2009 libwmqjcics.so
lrwxrwxrwx 1 14 Jul 1 2009 libwmqjcics_g.so -> libwmqjcics.so
-rwxr-xr-x 1 393216 Mar 23 2009 libwmqjrrs.so
-rwxr-xr-x 1 344064 Mar 23 2009 libwmqjrrs64.so
lrwxrwxrwx 1 15 Jul 1 2009 libwmqjrrs64_g.so -> libwmqjrrs64.so
lrwxrwxrwx 1 13 Jul 1 2009 libwmqjrrs_g.so -> libwmqjrrs.so
-rwxr-xr-x 1 385024 Mar 23 2009 libwmqjwmb.so
lrwxrwxrwx 1 13 Jul 1 2009 libwmqjwmb_g.so -> libwmqjwmb.so
-r--r--r-- 1 77116 Mar 23 2009 providerutil.jar
-r--r--r-- 1 889896 Mar 23 2009 rmm.jar
V7
-r--r--r-- 1 13143 Sep 17 2009 CL3Export.jar
-r--r--r-- 1 33166 Sep 17 2009 CL3Nonexport.jar
drwxr-xr-x 2 800 Sep 17 2009 OSGi
-r--r--r-- 1 664535 Sep 17 2009 com.ibm.mq.commonservices.jar
-r--r--r-- 1 355460 Sep 17 2009 com.ibm.mq.headers.jar
-r--r--r-- 1 439542 Sep 17 2009 com.ibm.mq.jar
-r--r--r-- 1 1465905 Sep 17 2009 com.ibm.mq.jmqi.jar
-r--r--r-- 1 103103 Sep 17 2009 com.ibm.mq.pcf.jar
-r--r--r-- 1 3197608 Sep 17 2009 com.ibm.mqjms.jar
-r--r--r-- 1 17978 Sep 17 2009 connector.jar
-r--r--r-- 1 2011813 Sep 17 2009 dhbcore.jar
-r--r--r-- 1 22769 Sep 17 2009 fscontext.jar
drwxr-xr-x 2 352 Sep 17 2009 jca
-r--r--r-- 1 25998 Sep 17 2009 jms.jar
-r--r--r-- 1 98496 Sep 17 2009 jndi.jar
-r--r--r-- 1 8809 Sep 17 2009 jta.jar
-r--r--r-- 1 123717 Sep 17 2009 ldap.jar
-rwxr-xr-x 1 159744 Sep 17 2009 libPgmIpLayer.so
-rwxr-xr-x 1 307200 Sep 17 2009 libmqjbatch.so
lrwxrwxrwx 1 14 Apr 7 17:03 libmqjbatch_g.so -> libmqjbatch.so
-rwxr-xr-x 1 81920 Sep 17 2009 libmqjbnd.so
lrwxrwxrwx 1 12 Apr 7 17:03 libmqjbnd_g.so -> libmqjbnd.so
-rwxr-xr-x 1 303104 Sep 17 2009 libmqjcics.so
lrwxrwxrwx 1 13 Apr 7 17:03 libmqjcics_g.so -> libmqjcics.so
-rwxr-xr-x 1 368640 Sep 17 2009 libmqjrrs.so
-rwxr-xr-x 1 794624 Sep 17 2009 libmqjrrs64.so
lrwxrwxrwx 1 14 Apr 7 17:03 libmqjrrs64_g.so -> libmqjrrs64.so
lrwxrwxrwx 1 12 Apr 7 17:03 libmqjrrs_g.so -> libmqjrrs.so
-rwxr-xr-x 1 122880 Sep 17 2009 libmqjstb02.so
lrwxrwxrwx 1 14 Apr 7 17:03 libmqjstb02_g.so -> libmqjstb02.so
-rwxr-xr-x 1 376832 Sep 17 2009 libmqjwmb.so
lrwxrwxrwx 1 12 Apr 7 17:03 libmqjwmb_g.so -> libmqjwmb.so
-r--r--r-- 1 77116 Sep 17 2009 providerutil.jar
-r--r--r-- 1 893748 Sep 17 2009 rmm.jar |
|
| Back to top |
|
|
| yupoet |
| Posted: Thu Sep 02, 2010 7:53 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
There are a number of libwmqj* components that are only in V6 and not in V7. And there are also some new files in V7 only.
One example is
The indication was that: libwmqjbind.so
had been replaced with: libmqjbnd.so
Some applicatoin is looking for libwmqjbind.so but we don't have. We only have libmqjbnd.so .
Is there any official announcement or solution to this? |
|
| Back to top |
|
|
| yupoet |
| Posted: Fri Sep 03, 2010 3:55 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
Here are some more logs -->
0BossLog: { 0147} 2010/09/03 18:35:26.088 01 SYSTEM=AAIB SERVER=WDSCH3B PID=0X03000446 TID=0X00000039 0X91DF9278 c=./bbgrjtr.cpp a
t line:+955 ... BBOO0220E: CNTR0020E: EJB threw an unexpected (non-declared) exception during invocation of method "onMessage" on be
an "BeanId(XPRTDataCollector_800Dev#XPRTDataCollectorEJB.jar#PricingMessage, null)". Exception data: java.lang.reflect.InvocationTar
getException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:96)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:132)
at com.ibm.ejs.jms.listener.WS390ServerSession.runMR(WS390ServerSession.java:196)
at com.ibm.ejs.jms.listener.MDBCppUtilitiesInterfaceImpl.onMessageReference(MDBCppUtilitiesInterfaceImpl.java:290)
at com.ibm.ws390.mdb.MDBCppUtilities.onMessageReference(MDBCppUtilities.java:132)
at com.ibm.ws390.orb.CommonBridge.nativeRunApplicationThread(Native Method)
at com.ibm.ws390.orb.CommonBridge.runApplicationThread(Unknown Source)
at com.ibm.ws.util.ThreadPool$ZOSWorker.run(ThreadPool.java:1697)
Caused by: com.ibm.msg.client.jms.DetailedJMSException: JMSCMQ0002: The method 'MQCMIT' failed. A WebSphere MQ call failed. Please s
ee the linked exception for more information.
at com.ibm.msg.client.wmq.common.internal.Reason.reasonToException(Reason.java:608)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:236)
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:275)
at com.ibm.msg.client.wmq.internal.WMQSession.syncpoint(WMQSession.java:1544)
at com.ibm.msg.client.wmq.internal.WMQSession.commit(WMQSession.java:774)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.notifyMessagePostConsume(JmsSessionImpl.java:2203)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.notifyMessageConsumed(JmsSessionImpl.java:2233)
at com.ibm.msg.client.jms.internal.JmsSessionImpl.consume(JmsSessionImpl.java:2948)
at com.ibm.mq.jms.MQSession.consume(MQSession.java:939)
at com.ibm.ejs.jms.JMSSessionHandle.consume(JMSSessionHandle.java:2170)
at com.ibm.ejs.jms.listener.WS390ServerSession.onMessage(WS390ServerSession.java:437)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:642)
... 13 more
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2012' ('MQRC_ENVIR
ONMENT_ERROR').
at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
... 23 more |
|
| Back to top |
|
|
| yupoet |
| Posted: Mon Sep 06, 2010 4:06 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
emm, it seems there is already some fixed ready -->
http://www-01.ibm.com/support/docview.wss?uid=swg1PM13765
APAR statusClosed as duplicate of another APAR.
Error descriptionMQCMIT fails with: linked exception:com.ibm.mq.MQException:
JMSCMQ0001: WebSphere MQ call failed with compcode '2'
('MQCC_FAILED') reason: '2012' ('MQRC_ENVIRONMENT_ERROR').
.
The JmsSessionImpl.notifyMessagePostConsume() method is
attempting to acknowledge a consumed message by committing
the MQ transaction. However, this is a bindings mode connection
on z/OS, so the MQ transaction is managed by RRS coordination.
In these circumstances, it is not valid to commit the MQ
transaction via an MQCMIT call.
We need to alter the processing so that it does not commit for
RRS coordinated bindings mode sessions.
Local fix
Problem summary
Problem conclusion
Temporary fix
CommentsProblem summary:
In WebSphere Application Server Version 6, an MDB listener is
configured to monitor a queue or a topic. When a message is
identified for processing by the MDB, a destructive get is
performed to obtain the message prior to invoking the onMessage
method of the MDB.
If the MDB listener is using a bindings mode connection to the
queue manager, WebSphere manages the transaction in which the
message has been got, and the application server is
responsible for committing or backing out the message.
However, the MQ V7 JMS client incorrectly determines that it is
responsible for committing the MQ work.
This causes the commit request to fail with compcode 2 and
rsncode 2012 (MQRC_ENVIRONMENT_ERROR).
Exceptions similar to the following are seen in the servant
region:
com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call
failed with compcode '2' ('MQCC_FAILED') reason '2012'
('MQRC_ENVIRONMENT_ERROR').
.at com.ibm.msg.client.wmq.common.internal.Reason.
createException(Reason.java:223)
.at com.ibm.msg.client.wmq.common.internal.Reason.
createException(Reason.java:275)
.at com.ibm.msg.client.wmq.internal.WMQSession.
syncpoint(WMQSession.java:1544)
.at com.ibm.msg.client.wmq.internal.WMQSession.
commit(WMQSession.java:774)
.at com.ibm.msg.client.jms.internal.JmsSessionImpl.
notifyMessagePostConsume(JmsSessionImpl.java:2203)
Problem resolution:
The MQ JMS code has been updated so that MDB listeners do
not issue a commit when consuming a message in bindings
mode on z/OS.
This fix changes the Java component of MQ, and will be
included in FixPack 7.0.1.3 (PM09662).
http://www-01.ibm.com/support/docview.wss?uid=swg1PM09662 |
|
| Back to top |
|
|
| yupoet |
| Posted: Thu May 03, 2012 4:38 am Post subject: |
|
|
Apprentice
Joined: 26 Nov 2008
Posts: 36
|
Confirmed that the fix works for this issue.
Thanks all the same. |
|
| Back to top |
|
|
|
|
