| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP Connector issue - URGENT |
« View previous topic :: View next topic » |
| Author |
Message
|
| Qadeer_824 |
 Posted: Thu Jun 26, 2008 11:01 pm Post subject: SAP Connector issue - URGENT |
 |
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
Hi,
On one of our environments, SAP Connector fails with MQJMS2007 exception. Following is the trace of error:
| Code: |
<EndBO:bo_idoc_artmas02>]
[Time: 2008/06/18 15:57:26.807] [System: ConnectorAgent] [SS: SAPX01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :Delivering subscription delivery CxCommon.BusinessObject@33c587]
[Time: 2008/06/18 15:57:29.838] [System: ConnectorAgent] [SS: BDCSAPP01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :class com.crossworlds.DataHandlers.text.cwxml :Found in typeToSize bo_idoc_artmas02, size 25693727]
[Time: 2008/06/18 16:01:11.964] [System: ConnectorAgent] [SS: BDCSAPP01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :SendProxy.send() caught an error: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2102]
[Time: 2008/06/18 16:01:12.107] [System: ConnectorAgent] [SS: BDCSAPP01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :catch exception when sending msg to broker]
[Time: 2008/06/18 16:01:12.762] [System: ConnectorAgent] [SS: BDCSAPP01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :javax.jms.JMSException: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at CxCommon.Messaging.jms.SecurityProxy.SendProxy.send(SendProxy.java:98)
at CxCommon.Messaging.jms.Sender.sendMessageAsync(Sender.java:126)
at CxCommon.Messaging.jms.SessionMgr.sendAsync(SessionMgr.java:560)
at CxCommon.Messaging.ClientPacketSyncDrvFormatter.deliverBusObj(ClientPacketSyncDrvFormatter.java:804)
at AppSide_Connector.AgentBusinessObjectManager.deliverBusObj(AgentBusinessObjectManager.java:1509)
at AppSide_Connector.BusObjJavaInterface.GotObjectFromApp(BusObjJavaInterface.java:452)
at AppSide_Connector.SubscriptionHandler.gotApplEvent(SubscriptionHandler.java(Inlined Compiled Code))
at AppSide_Connector.ConnectorBase.gotApplEvent(ConnectorBase.java(Compiled Code))
at com.crossworlds.connectors.sap.sapalemodule.VSapALEConnectorAgent.postToICS(VSapALEConnectorAgent.java(Compiled Code))
at com.crossworlds.connectors.sap.sapalemodule.VSapALEConnectorAgent.sendWorkUnittoICS(VSapALEConnectorAgent.java(Compiled Code))
at com.crossworlds.connectors.sap.sapalemodule.VSapALEConnectorAgent.pollforEventsVision(VSapALEConnectorAgent.java(Compiled Code))
at com.crossworlds.connectors.sap.visionframework.VisionConnectorAgent.pollForEvents(VisionConnectorAgent.java(Compiled Code))
at AppSide_Connector.BusObjJavaInterface.poll(BusObjJavaInterface.java(Compiled Code))
at AppSide_Connector.AppCalls.poll(AppCalls.java(Compiled Code))
at AppSide_Connector.AgentBusinessObjectManager.poll(AgentBusinessObjectManager.java(Compiled Code))
at AppSide_Connector.AppPolling.poll(AppPolling.java(Compiled Code))
at AppSide_Connector.AppPolling.doPollingOnWait(AppPolling.java(Compiled Code))
at AppSide_Connector.AppPolling.run(AppPolling.java(Compiled Code))
at java.lang.Thread.run(Thread.java:570)
|
The connector is trying to place the data (about 25MB) in a persistent queue and that queue has max msg length property set to 104857600 (100MB).
MQ has free disk space of about 2GB.
SAP Connector is configured for Xmx of 1024M.
It is seen that the machine on which connector and MQ is installed runs at very high CPU due to other applications.
Can you suggest me if this failure be because of:
1. Incorrect log file size settings on the queue manager? (How do i change these settings and to what values?)
2. High CPU resulting in MQRC 2102?
3. Anything else which you may want me to check.
Your help would be highly appreciated.
Thanx,
Qadeer |
|
| Back to top |
|
 |
| Qadeer_824 |
| Posted: Thu Jun 26, 2008 11:27 pm Post subject: |
|
|
Acolyte
Joined: 04 Oct 2007
Posts: 59
|
I could see the following message is queue manager log:
| Code: |
----- amqalme0.c : 424 --------------------------------------------------------
06/26/08 14:48:07
AMQ7463: The log for queue manager SAPX01 is full.
EXPLANATION:
This message is issued when an attempt to write a log record is rejected
because the log is full. The queue manager will attempt to resolve the problem.
ACTION:
This situation may be encountered during a period of unusually high message
traffic. However, if you persistently fill the log, you may have to consider
enlarging the size of the log. You can either increase the number of log files
by changing the values in the queue manager configuration file. You will then
have to stop and restart the queue manager. Alternatively, if you need to make
the log files themselves bigger, you will have to delete and recreate the queye.
|
folling is the extract of mqs.ini file:
| Code: |
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
|
I think the issue is log files as i expected. I can't recreate the queue manager but can restart it easily. So i'd need a value for primary and secondary log files. Can you please suggest me values if i were to receive message of size upto 50MB / 100MB with the persistent property of queue manager set to true.
Thanx Again!
Qadeer |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Jun 26, 2008 11:32 pm Post subject: Re: SAP Connector issue - URGENT |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| Qadeer_824 wrote: |
[Time: 2008/06/18 16:01:11.964] [System: ConnectorAgent] [SS: BDCSAPP01OUT1Connector] [Thread: appPolling (#874850543)] [Type: Trace] [Mesg: :SendProxy.send() caught an error: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2102]
|
2102 : MQRC_RESOURCE_PROBLEM
There are some resource problem in your system. Please verify the same and get back to us
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| francoisvdm |
| Posted: Fri Jun 27, 2008 4:37 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
I've seen this on one of my machines (also with SAP adapter) but it was not adapter related in the end. It was because the queue manager was running out of log space. Also...that is a BIGish message, it will take time to process and maybe some timeout values are reached.
I solved my problem (many many messages, not big ones) by creating more and bigger log files, linear logging.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| 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
|
|
|
|
