| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP Adapter issue in WMB7 |
« View previous topic :: View next topic » |
| Author |
Message
|
| mapa |
 Posted: Tue Mar 08, 2011 1:49 am Post subject: SAP Adapter issue in WMB7 |
 |
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Hi,
We are experiencing a very troublesome problem in our production environment that we currently can't reproduce in test.
Thought I'd check with you before contacting IBM.
My main concern is that I am not sure in what component that is the problem.
It is part of a migration. It works without problems in V6.1 broker.
Broker log:
| Code: |
( BK_NONAME.default1 ) An adapter error occurred during the processing of a message. The adapter error message is ''The context with the session id [100rfcmsgbroker.737243] scope type [null] is currently used in thread Thread-13 [0x12].Current thread is Thread-11 [0x10].
''.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''The context with the session id [100rfcmsgbroker.737243] scope type [null] is currently used in thread Thread-13 [0x12].Current thread is Thread-11 [0x10].
''.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
|
From adapter trace:
| Code: |
Thread-12 [16:45:33:953]: SAP Java Connector (JCo) runtime information
Thread-12 [16:45:33:953]: Java Runtime:
Thread-12 [16:45:33:953]: Operating System : Windows Server 2008 R2 6.1 build 7600 for amd64
Thread-12 [16:45:33:953]: Java VM : 1.6.0 IBM Corporation
Thread-12 [16:45:33:953]: Java Codepage : Cp1252
Thread-12 [16:45:33:953]: Versions:
Thread-12 [16:45:33:953]: JCo API : 3.0.6 (2010-08-24)
Thread-12 [16:45:33:953]: JCo middleware name : JavaRfc
Thread-12 [16:45:33:953]: JCo middleware : 2.2.4
Thread-12 [16:45:33:953]: JCo middleware native : 720.63
Thread-12 [16:45:33:953]: JCo library : D:\SAPJCO\sapjco3.dll
Thread-12 [16:45:33:953]:
Thread-12 [16:45:33:953]: ******************** Configuration ***************************
jco.delta_management = 1
jco.jdsr_provider = 0
jco.trace_path = D:\Logs\gardena
jco.cpic_maxconv = 202
jco.cpic_keep_alive_period = 300
jco.trace_level = 8
jco.use_repository_roundtrip_optimization = 0
jco.jarm = 0
jco.jdsr = 0
jco.ignore_jdsr_error = 1
jco.cpic_keep_alive_timeout = 10
|
It occurrs seldomly, it can't run fine for an hour before any errors.
Broker version is:
WMB 7.0.0.2
Any ideas? |
|
| Back to top |
|
 |
| napier |
| Posted: Tue Mar 08, 2011 7:50 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2007
Posts: 48
Location: USA
|
| This is known problem. IBM provided us a interim fix for this problem. Open a PMR. |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Mar 08, 2011 7:53 am Post subject: PMR |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Super thanks.
PMR opened, waiting feedback.
Great to know that it is a know problem. |
|
| Back to top |
|
|
| napier |
| Posted: Mon Mar 14, 2011 10:01 am Post subject: |
|
|
Apprentice
Joined: 09 Oct 2007
Posts: 48
Location: USA
|
The interm solution for this issue
If you have multiple sap request flows in a single execution group, then deploy in to seperate execution groups. Which will resolve your issue temporarily. |
|
| Back to top |
|
|
| mapa |
| Posted: Wed Mar 16, 2011 4:36 am Post subject: exec groups |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Thanks for the tip, but it is a RAD broker that only allows 2 exec groups.
However the interim fix worked just fine. |
|
| 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
|
|
|
|
