| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IBM MQ Create client session XA TIMEOUT |
« View previous topic :: View next topic » |
| Author |
Message
|
| borram |
 Posted: Thu Dec 23, 2021 9:35 am Post subject: IBM MQ Create client session XA TIMEOUT |
 |
|
Newbie
Joined: 23 Dec 2021
Posts: 4
|
Hi everyone, I may have a problem with a mainframe MQ server, to get a session it takes 15 to 50 seconds, what could I investigate? In my development and testing environments, times are 200 milliseconds.
Application logs:
2021-12-20 14:14:50.934 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsXaSessionProxy : atomikos xa session proxy for resource XXXXXX.ibm.mq.xa: closing session atomikos xa session proxy for resource XXXXXX.ibm.mq.xa - is terminated ? true
2021-12-20 14:14:50.937 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsConnectionProxy : atomikos connection proxy for resource XXXXXX.ibm.mq.xa: close()...
2021-12-20 14:14:50.937 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.i.i.CompositeTransactionManagerImp : createCompositeTransaction ( 30000 ): created new ROOT transaction with id 192.168.XXX.XXX.tm164000609093704464
2021-12-20 14:14:50.938 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosConnectionFactoryBean : AtomikosConnectionFactoryBean 'XXXXXX.ibm.mq.xa': createConnection()...
2021-12-20 14:14:50.938 INFO 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosConnectionFactoryBean : AtomikosConnectionFactoryBean 'XXXXXX.ibm.mq.xa': init...
2021-12-20 14:14:50.938 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsConnectionProxy : atomikos connection proxy for resource XXXXXX.ibm.mq.xa: creating XA-capable session...
2021-12-20 14:15:21.116 WARN 27245 --- [Atomikos:6] c.a.icatch.imp.ActiveStateHandler : Transaction 192.168.XXX.XXX.tm164000609093704464 has timed out and will rollback.
2021-12-20 14:15:40.032 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsConnectionProxy : atomikos connection proxy for resource XXXXXX.ibm.mq.xa: calling hashCode on JMS driver...
2021-12-20 14:15:40.033 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsConnectionProxy : atomikos connection proxy for resource XXXXXX.ibm.mq.xa: calling start on JMS driver...
2021-12-20 14:15:40.041 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsXaSessionProxy : atomikos xa session proxy for resource XXXXXX.ibm.mq.xa: calling createQueue on JMS driver session...
2021-12-20 14:15:40.054 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsXaSessionProxy : atomikos xa session proxy for resource XXXXXX.ibm.mq.xa: calling createConsumer on JMS driver session com.ibm.mq.jms.MQXASession@67d000b4
2021-12-20 14:15:43.605 DEBUG 27245 --- [XXXXXX-ias-Q-1399] c.a.jms.AtomikosJmsMessageConsumerProxy : atomikos MessageConsumer proxy for com.ibm.mq.jms.MQQueueReceiver@7a0b7b64: receive ( 1000)...
 |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Dec 23, 2021 11:13 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Investigate the SYSLOGs of both qmgr and CHIN address spaces. Post interesting items here.
Issue DISPLAY QMGR CHINIT command. Post results here.
Is this a new or changed app? Is this the only app experiencing this issue?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| borram |
| Posted: Fri Dec 24, 2021 8:50 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2021
Posts: 4
|
I don't have access to the server-side logs, but whoever manages them says they have no evidence of malfunctions and claims that the application is the problem. The application is new. I think it is a network problem, also because it is installed on two machines and one of these has many more timeouts than the other, but in theory they should be identical. How can I prove that it is not an application problem, what can I check in the sq-client logs?
It seems to be the only application, but it is also true that it is the only application made with a listener and on those machines, which are new, there is only our application and it is installed from scratch.
I will ask them to execute the command you suggested.
Thank you! |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Dec 24, 2021 10:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please confirm that this app on this platform always fails, and with this same error.
On the client platform (Windoze/Linux, …) look in the MQ error directory/folder for errors logged at the time the app has this issue. Post here.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| hughson |
| Posted: Mon Dec 27, 2021 12:19 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
Do you have any other applications connecting to this z/OS Queue Manager and making use of XA Transactions successfully?
I am surprised to hear you say that there is no mention of anything on the Queue Manager CHIN or MSTR logs. Either something went wrong with the XA session creation, or the TCP socket timed out for some unrelated reason - both would be mentioned.
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| borram |
| Posted: Tue Jan 11, 2022 5:33 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2021
Posts: 4
|
Sorry for the delay, the holidays.
>>Do you have any other applications connecting to this z/OS Queue Manager and making use of XA Transactions successfully?
Apparently yes, there are other applications that work.
>>I am surprised to hear you say that there is no mention of anything on the Queue Manager CHIN or MSTR logs. Either something went wrong with the XA session creation, or the TCP socket timed out for some unrelated reason - both would be mentioned.
I too, am very surprised and worried if none of this is tracked.
>>Please confirm that this app on this platform always fails, and with this same error.
It always fails with the same error and it would appear only from my application, but only towards that MQ server, towards others there are no errors.
I got MQ Clients logs sent to me and I discovered this error:
| Code: |
[16/11/21 12:42:28.255.01] 00000118 @1fefa0fa c.i.m.j.remote.impl.RemoteTCPConnection ----+---- ! receive(byte [ ],int,int)<throwIndex 2>, CC=2;RC=2009;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.SocketException[Socket closed],4=TCP,5=sockInStream.read] [com.ibm.mq.jmqi.JmqiException]
[16/11/21 12:42:28.256.00] 00000118 @23f8800c c.i.m.j.remote.impl.RemoteRcvThread ----+--- X receiveBuffer()
[16/11/21 12:42:28.256.00] 00000118 CC=2;RC=2009;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.SocketException[Socket closed],4=TCP,5=sockInStream.read] [com.ibm.mq.jmqi.JmqiException] at:
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.receive(RemoteTCPConnection.java:1898)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveBuffer(RemoteRcvThread.java:773)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveOneTSH(RemoteRcvThread.java:739)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.run(RemoteRcvThread.java:155)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:319)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:99)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:343)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:312)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1227)
[16/11/21 12:42:28.256.00] 00000118 Object ClassLoader = java.net.URLClassLoader@25f38edc
[16/11/21 12:42:28.256.00] 00000118 CurrentThread ClassLoader = java.net.URLClassLoader@25f38edc
[16/11/21 12:42:28.256.00] 00000118 Cause:
[16/11/21 12:42:28.256.00] 00000118 Socket closed [java.net.SocketException] at:
[16/11/21 12:42:28.256.00] 00000118 java.base/java.net.SocketInputStream.read(SocketInputStream.java:183)
[16/11/21 12:42:28.256.00] 00000118 java.base/java.net.SocketInputStream.read(SocketInputStream.java:140)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteTCPConnection.receive(RemoteTCPConnection.java:1887)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveBuffer(RemoteRcvThread.java:773)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.receiveOneTSH(RemoteRcvThread.java:739)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.mq.jmqi.remote.impl.RemoteRcvThread.run(RemoteRcvThread.java:155)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:319)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:99)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:343)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:312)
[16/11/21 12:42:28.256.00] 00000118 com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1227)
[16/11/21 12:42:28.256.00] 00000118 Object ClassLoader = null
[16/11/21 12:42:28.256.00] 00000118 CurrentThread ClassLoader = java.net.URLClassLoader@25f38edc
|
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 11, 2022 6:40 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
How does this error pop up. Does it work for a little while and then the error shows up (thinking firewall time out)?
Is the connection timeout less than the transaction timeout? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 11, 2022 6:59 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| hughson wrote: |
I am surprised to hear you say that there is no mention of anything on the Queue Manager CHIN or MSTR logs. Either something went wrong with the XA session creation, or the TCP socket timed out for some unrelated reason - both would be mentioned.
Cheers,
Morag |
Me, too.
Look for errors in the SYSLOG for the z/OS TCP address space.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| borram |
| Posted: Tue Jan 11, 2022 7:01 am Post subject: |
|
|
Newbie
Joined: 23 Dec 2021
Posts: 4
|
As I said to have a session always takes from 15 to 50 seconds, the problem always occurs, but sometimes exceeding 30 seconds (timeout set for Atomikos Transaction Manager) it is also evident in the application logs. In my environments it takes 200 milliseconds, apparently there are no errors for now, but we receive few messages.
| Code: |
[16/11/21 12:42:28.255.01] 00000118 @1fefa0fa c.i.m.j.remote.impl.RemoteTCPConnection ----+---- ! receive(byte [ ],int,int)<throwIndex 2>, CC=2;RC=2009;AMQ9213: A communications error for 'TCP' occurred. [1=java.net.SocketException[Socket closed],4=TCP,5=sockInStream.read] [com.ibm.mq.jmqi.JmqiException]
|
I recently discovered the error and I don't know if it is the cause or an effect.
| Quote: |
| Is the connection timeout less than the transaction timeout? |
Under investigation.   |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 11, 2022 7:16 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| borram wrote: |
As I said to have a session always takes from 15 to 50 seconds, the problem always occurs, but sometimes exceeding 30 seconds (timeout set for Atomikos Transaction Manager)
|
First mention of Atomikos here.
What is z/OS involvement in the transaction? What z/OS resource? Is this the first use of Atomikos transaction manager with z/OS? Are other apps involved in Atomikos working? Failing?
For clarity, your test environment includes z/OS MQ qmgr in the transaction, yes?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
