JMS-MQ Series error( MQJMS2002)

Hi,
I have an MDB listening to a queue. I am using MQ Series instead of Jboss mq. It has been working fine but I have faced the below error a fews days back and i am unable to solve it.
For a particular message , I get an error javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue , when I remove it from the queue , it works fine i.e the messages starts being processed by the MDB. But if i again place the message back in the queue the same error keeps appearing again and again in the log and no further messages gets proceesed by the MDB.
In our application the length of the message is more than 4mb so we have modified all the queues to 10mb in mqseries and it has been working fine from a long time. But for this particular message the above situation is occuring. Note size of dead letter queue is still 4mb.
Can the below be happening:-
For some reason the queue manager cannot deliver a message and so it attempts to put the message on its dead-letter queue , but since the DLQ max size is 4mb , it goes into a loop.....may not sound very convincing thought...........but if i change the size of DLQ to 10mb ...will it help my cause.....below is the full stack trace ..........
44526 2007-07-25 09:16:24,162 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
44527 javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
44528 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
44529 at com.ibm.mq.jms.MQSession.consume(MQSession.java:3113)
44530 at com.ibm.mq.jms.MQSession.run(MQSession.java:1612)
44531 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
44532 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
44533 at java.lang.Thread.run(Thread.java:534)
44534 2007-07-25 09:16:24,162 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] innerStop
44535 2007-07-25 09:16:24,162 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] unset exception listener
44536 2007-07-25 09:16:29,138 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] connection stopped
44537 2007-07-25 09:16:29,138 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destroyService
44538 2007-07-25 09:16:29,162 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Clearing 1 from ServerSessionPool
44539 2007-07-25 09:16:29,163 DEBUG [org.jboss.jms.asf.StdServerSession] closed
44540 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopping DLQHandler
44541 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopped DLQHandler
44542 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler
44543 2007-07-25 09:16:29,166 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler
44544 2007-07-25 09:16:29,166 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10000 ms
44545 2007-07-25 09:16:39,164 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
44546 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing
44547 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/WSMQ JMSProvider
44548 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JN DIProviderAdapter@15e0638
44549 2007-07-25 09:16:39,165 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
44550 2007-07-25 09:16:39,165 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: com.ibm.mq.jms.MQQueueConnectionF actory@895ab1c7
44551 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection: com.ibm.mq.jms.MQQueueConnec tion@bd7301
44552 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: queue://OMNT031P/SYSTEM.DEAD.LETTER .QUEUE
44553 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
44554 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@1c 95c92
44555 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: ossToNpgQueue
44556 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for OssJmsMd bOm
44557 2007-07-25 09:16:39,187 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory: com.ibm.mq.jms.MQQueu eConnectionFactory@895ab1c7
44558 2007-07-25 09:16:39,188 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/null
44559 2007-07-25 09:16:39,190 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created QueueConnection: com.ibm.mq.jms.MQQueue Connection@dcb4bb
44560 2007-07-25 09:16:39,190 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
44561 2007-07-25 09:16:39,190 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not find the queue destination-jn di-name=ossToNpgQueue
44562 2007-07-25 09:16:39,190 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] looking up session pool factory: java:/ StdJMSPool
44563 2007-07-25 09:16:39,190 DEBUG [org.jboss.jms.asf.StdServerSessionPool] initializing with connection: com.ibm.mq.jms.M QQueueConnection@dcb4bb
44564 2007-07-25 09:16:39,191 WARN [org.jboss.jms.asf.StdServerSessionPool] Using a non-XA QueueConnection. It will not b e able to participate in a Global UOW
44565 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX ): org.jboss.jms.asf.StdServerSessionPool@1dd92ab, com.ibm.mq.jms.MQQueueSession@1c8363b, null, false
44566 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSessionPool] added server session to the pool: org.jboss.jm s.asf.StdServerSession@1605c66
44567 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Server Session pool set up
44568 2007-07-25 09:16:39,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Server session pool: org.jboss.jms.asf. StdServerSessionPool@1dd92ab
44569 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Connection consumer: com.ibm.mq.jms.MQC onnectionConsumer@1526ddf
44570 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initialized with config org.jboss.ejb.p lugins.jms.JMSContainerInvoker@9ba786{ maxMessagesNr=1, maxPoolSize=1, reconnectInterval=10000, providerAdapterJNDI=j ava:/WSMQJMSProvider, serverSessionPoolFactoryJNDI=java:/StdJMSPool, acknowledgeMode=1, isContainerManagedTx=false, i sNotSupportedTx=false, useDLQ=true, dlqHandler=org.jboss.ejb.plugins.jms.DLQHandler@ab5354{ destinationJNDI=queue/WSM Q/DLQ, maxResent=1, timeToLive=0 }, destinationJNDI=ossToNpgQueue }
44571 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Starting DLQHandler
44572 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Started DLQHandler
44573 2007-07-25 09:16:39,196 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider
44574 2007-07-25 09:16:39,226 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
44575 javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
44576 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
44577 at com.ibm.mq.jms.MQSession.consume(MQSession.java:3113)
44578 at com.ibm.mq.jms.MQSession.run(MQSession.java:1612)
44579 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
44580 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
44581 at java.lang.Thread.run(Thread.java:534)
44582 2007-07-25 09:16:39,226 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] innerStop
44583 2007-07-25 09:16:39,226 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] unset exception listener
44584 2007-07-25 09:16:44,204 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] connection stopped
44585 2007-07-25 09:16:44,204 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destroyService
44586 2007-07-25 09:16:44,204 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Clearing 1 from ServerSessionPool
44587 2007-07-25 09:16:44,205 DEBUG [org.jboss.jms.asf.StdServerSession] closed
44588 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopping DLQHandler
44589 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopped DLQHandler
44590 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler
44591 2007-07-25 09:16:44,206 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler
44592 2007-07-25 09:16:44,206 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10000 ms
44593 2007-07-25 09:16:54,211 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to
Thanks

Hi,
This is with reference to your CV Posted in jobsite. Let me introduce myself Kranti, working with Techpoint Solutions! as IT Recruiter. We have job opening matching your profile.
Send your update Resume to
[email protected]
Note:
1. Check list below is mandatory, without the check list we cannot process your CV.
Full Name:
DOB:
Current CTC:
Exp CTC:
Notice Period:
Current Location:
Ready to relocate to Hyderabad :
Job Location : Hyderabad
Once your profile gets short-listed, you would be called for a face to face interview.
JOB SPECIFICATION �
Senior Developer/ Lead
Experience Required:
Total Years of Experience: 4+years experience in IT
At least 1 -2 years experience leading a team.
Education: Should be a BE/ B Tech/ ME/ M Tech/ ! MCA/ M Sc in IT/ Systems/ Computers.
- Consistent 60% academic record is a must.
- Candidates interviewed by us in the last 6 months are not eligible.
- Correspondence / Part time Courses does not qualify.
- Gaps in Education / Career should not be more than 2 yrs (If any).
- At least 50% of yo! ur Post Qualification experience should be relevant to IT or to the skill set that we are looking at.
Description
Develop web pages and backend programs
Technical Skills
Must haves:
Operating System worked on: Experience on Unix at least 3 years.
Scripting language: Worked on She ll and Perl scripts minimum 3 years.
Database exposure/Worked on : Experience on Sybase development. WebLogic Server or WebSphere. Java J2EE, JMS
MQ, VSS (should on Application side)
Actuate Reporting is a plus.
Domain: Investment Banking
Job! Location: Hyderabad
Thanks & Regards,
Kranti Punjala
Executive (Recruitments)
Techpoint Solutions.
[email protected]

Similar Messages

PI 7.0 SP15 alerts JMS Duplicate message error

Hi all,
We have a scenario where in we receive BAPI calls to R/3 from web through MQ and XI.
WEB -> MQ->XI->R/3 (Request / Response send back similarly)
We have modular configuration in the channel.
All these BAPI messages are queries needed to build an order for example product information / customer information etc.
We have PI 7.0 SP15
Sometimes we receive the error ' Duplicate JMS message with JMS ID##### detected.Duplicate will be ignored' in the sender JMS channel.Because of this error XI is not able to process subsequent messages and the channel keeps on throwing the same error.We need to clear the queue and then restart the channel to make it work.
Can any one please tell me what is the reason for occurence of this error..?
Is this ID generated in JMS or in XI?If so how this could be handled without clearing the queue's..?
When we analyzed the messages in the queue we found out same xml messages been send twice which i would imagine the query been send twice(which is a possiblity from the web) would that have caused this JMS duplcate message error??!!
Also because of this error XI is throwing multiple alert messages at the rate of 3 per second which is causing the huge performance hit as the alert inbox gets filled up..We did put the suppress multiple alert check..but before somebody reacts to these alerts there are numerous of them created..any suggestions on this is much appreciated..
Thanks for your help in advance
Larry

Larry,
Is that alert rule is generic or interface specific? If it is generic then please make it interface specific.
Thanks,
Sunil

JMS-204: An error occurred in the AQ JNI layer

Approach 1) works fine but not 2).
Approach 1
=================
// Use the DriverManager to get the DB Connection
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
java.sql.Connection dbConnection = DriverManager.getConnection("the url" , "the uid", "the pwd");
javax.jms.QueueConnection queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
Approach 2 (doesn't work)
=================
// Use the JNDI Lookup to get the DB Connection
Context ctx = get the context;
DataSource dataSource = (DataSource)ctx.lookup("datasoruce jndi");
dbConnection = dataSource.getConnection();
queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
Please note that I'm able to get the Queue Connection. But when I try to send the message, I get the exception.
Exception: JMS-204: An error occurred in the AQ JNI layer
Linked Exception: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[java.rmi.MarshalException: failed to marshal setORAData(ILoracle.sql.ORAData;); nested exception is:
java.io.NotSerializableException: oracle.jms.AQjmsTextMessage_C]
App Server: WebLogic 8.1
Any thougts...
Thanks in advance.

It is complaining about the AQjmsTextMessage not being serialized. I have seen errors with not using the actual oracle connection directly. Usually the datasource has some wrapper database connection. However, i would expect a different error. I will have to experiment with this.

Time series error in class /SCF/CL_ICHDM_DATAAXS method /SCF/IF_ICHDMAXS_2_

Hi,
In SNC system, the supplier is getting the following error when he is trying to update the planned receipt quantity.
Due to that error the ASN canu2019t be created and sent to ECC system.
Time series error in class /SCF/CL_ICHDM_DATAAXS method /SCF/IF_ICHDMAXS_2_CNTL~SAVE
Please give your inputs as to how to resolve this error.
Regards,
Shivali

Hi Shivali,
This is not related to time series data issue.
ASN (ASN number:122593)XML failed may be because of there no Purchase order(Reference order) exists for supplier 0000104466 which will be there in failed XML.(see the DespatchedDeliveryNotification_In XML check XML tag <PurchaseOrderReference> value under tag <Item>)
Login as a supplier 0000104466 and search for purchase order (or replenishment order) and this PO(or RO) won't be there in supplier 0000104466 .
That's why ASN got failed.
Regards,
Nikhil

Document numbering series error

Hi Experts,
Our client has been using SBO 2005A for a long time but recently they are having document numbering series error regardless what users and even the manager account that has full authorization to all and a superuser cannot add document. No updates or modification recently with SBO settings.
Steps taken:
Restarted the server and workstation - no good
Used manager account with full access and superuser - no good
Tried different database - working in different database
Tried different series - no good
Restarted License Server - no good
Here are some of the logs I got from the event viewer:
Failure Audit:
The description for Event ID ( 1 ) in Source ( B1Logger ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Wrong user name or password (User: manager)
What could be the problem?
Thank you.

Hi Gordon,
It was just a slight in configuration settings. We did noticed that the last number series of the Journal Entry was already consumed, which resulted to this error. We just defaulted another document series for Journal Entry and it was already ok.
Thanks.

• Hewlett-Packard - Imaging - Null Print - HP Deskjet 3520 series - Error 0x8024200b

have never been able to install imaging null print update on my destop on win 7/8/8.1 and now update appears on win 10 to update and again failure. Get error message:• Hewlett-Packard - Imaging - Null Print - HP Deskjet 3520 series - Error 0x8024200b

Hello , and welcome to the HP Forums! I see you're having issues with an update. I would like to help! I'd recommend starting with a power reset. Disconnect the power cord from the printer and the power outlet, then wait 60 seconds. After 60 seconds, plug the printer back in. Ensure you plug the printer directly to a wall outlet. Make sure to bypass any sort of surge protector or power bar.
I would also recommend downloading and running the HP Print and Scan Doctor. Once the Doctor has been run, re-run the update. Good luck and please let me know the results of your troubleshooting steps. Thank you for posting on the HP Forums!

Win10-Update, Null Fax - HP Officejet 4630 series - Error 0x80070490

REF:
http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-Setup/hp-4630e-driver-updates-via-windows-update-fail/td-p/3778226 REF:
http://h30434.www3.hp.com/t5/Printer-All-in-One-Install-Setup/Error-0x80070490-on-HP-windows-update/td-p/5007952
Still have the same problem with Windows 10 Update:There were problems installing some updates, but we'll try again later. If you keep seeing this and want to search
the web or contact support for information, this may help:
HP - Enterprise WSD Multi-Function Printer, Other hardware - Null Fax - HP Officejet 4630 series - Error 0x8007049 Used:
http://windows.microsoft.com/en-ca/windows/windows-update-error-80070490#1TC=windows-7MS Fix software... found 1 error and fixed it But still cannot update, I have the same above error Jean3riv
Rayonline.com
[email protected]

having the same problem. Installed windows 10 and not only will my printer no longer print wierlessly but my phone and tablet no longer recognize my printer. the entire reasonw why i purcahsed this printer was to print wierlessly from my phone and tablet.

JMS Sender Channel Error with MQ Series

Hi,
I am trying to send a message from MQ Series to XI via JMS Adapter. I am getting this error message, and I have searched the forums for this error message with no luck. Can someone please help? I have asked the BASIS team to double check and make sure the JMS drivers have been deployed. I am still waiting for their reply.
Thanks in advance
Zeshan Anjum

Sorry, I forgot to append the error message.
Here it is:
0 XI inbound processing failed for message at 2006-10-19|09:54:30.925-0500. JMS and XI identifiers for the message are ID:414d51205a3153505420202020202020448dda5420003f01 and b9be54c0-5f81-11db-a551-001125a6015a respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Value with name enableDynConfigSender not available
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java(Compiled Code))
at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java(Compiled Code))
at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code))

JMS - MQ Series

Hello,
we try to set up a receiving JMS adapter to connect to MQ series, but so far we are unsuccessful. In the dapter framework monitor we get a "MQJMS2008: failed to open MQ queue" error message. In the RWB not much useful information exists. Our Configuration is as follows:
QueueConnection Java Class com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class   com.ibm.mq.jms.MQQueue
Queue Manager Name QM00191
Channel Name       CQM00191.CLSAPCM
JMS Queue          AQG.CREDITINFO.SOPIC.R3.3530
JMS Compliant      WebSphereMQ (non-JMS)
The IBM JMS JAR files are deplyed according to the SAP How To guide.
Any suggestions on how to proceed?
Kind regards Johan

Hi Johan,
could you explain the different between the WebSphereMQ (not JMS) and JMS-konform. Why and when should use which mode?
When you configure the JMS-Adapter which how to guide do you mean? Where to find it?
Thanks,
Ly-Na Phu

Document Series Error after creation of a new Posting Period

Hi
While Creation of a new Document Series for user created UDO (after creation of new Posting Period
with Period Indicator) on update its showing a message box
"Application Error occurred, Dump file created in path C\Program Files\SAP\..\Log......"
And soon SAP B1 gets exit.
Can any one help me to come out of this problem.

Hi,
Whenever Dump file created, it is high time to log a message to SAP support. This problem is beyond forum function.
Thanks,
Gordon

MQ Series - Error while reading messages from MQ in Sender adapter if EOIO

Dear all,
we've configured a scenario with a sending JMS-adapter (MQSeries). With configured Quality-Of-Service = EO everything works fine. If we switch to Quality-Of-Service = EOIO we get the following error message:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException: DeliveryException: Could not assign next free EOIO sequence number for SC: OUTBOUND_TEST_MQ_SERIES_QUEUE_4__. Reason: Problem inserting b315acf4-61f3-42dc-3642-85450666fe91(OUTBOUND) into the database: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105)
Any ideas?
Kind regards, Stefan

We have the same issue, how did you solve yours?
For us it works fine with EO but EOIO fails with the same error message...
Kr,
Frederik-Jan.

JMS receiver adapter Error

Hi Experts,
Any idea about this error. We are getting following in JMS receiver adapter in PI 7.1.
Delivering the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connector for ConnectionProfile of channel: JMS_Receiver_THQPRD2_Slow_Replyon node: 284760550 having object id: cf2f6eb7d6c93902b64b27bfcaad0ba5 encountered error: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>' in sending to destination queue:///QR.EAIPRD.THQPRD2.REPLY.SLOW?targetClient=1, the message message: JMS Message class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID:ID:414d5120504c535748353533202020204e6324ae23eb5b2d JMSDestination: null JMSReplyTo: null JMSRedelivered: false XPLOR PIPXSDI2030 45219q00282YSDI2030PROCESS_MQSERIES PLSWH553 Another 12,761 character(s) omitted: javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: java.lang.NullPointerException: while trying to read the field 'ccsid' of an object loaded from field com.ibm.mq.MQSESSIONClient.comms of an object loaded from local variable '<0>'.
Thanks,
Hari

Hello,
The error indicates a JMS driver issue.
Another customer resolved this issue by updating their MQ and the MQ drivers version (in their case to 6.0.2.8.)
You could try contacting IBM for advice on a similar upgrade.
#1086303 XI JMS Adapter and IBM Websphere MQ: FAQ
12)What is the recommended version of MQ drivers for the PI JMS
Adapter - IBM MQ connectivity ?
Kind regards,
Sarah

Error in JMS receiver adapter: "Error creating initial context with environment"

Hello,
I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
The message in adapter monitoring is:
A channel error occurred. Detailed error (if any) :
com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
(JndiConnectorImpl.java:152)<br> ....
Message processing failed. Cause:
com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
Might there be a problem with the JMS drivers?
Regards,
Marcus

Hi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

JMS Adapter configuration error

Hi All
      My scenario is file to jms.i configured the webspher MQ and i created queues manager and channals.I done JMS receiver like this,
1)Transport protocol:WebspherMQ JMS provied
2)Message porotocol:JMS x.1
3)Adapter Enigen:   Integration Server
4)QueueConnecation Factery Java           Class:com.ibm.mq.jms.MQQueueConnectionFactory
5)Queue Java Class:com.ibm.mq.jms.MQQueue
6)IP Address or server name:Localhost
7)Server port:1414
8)Queue Mannager Name:QM_sapxi
9)channal name:CHANNAL1
10)JMS queue:MQCONN.OUT
11)Transport/netwrok protocol:TCP/IP
12)JMS compliant:WebSpherMQ(non jms)
13)Deliver mode of message Producer:Persist JMS Messages in the JMS provider
14)mapping of the message:Entier message=JMS Payload
finaly i checked my Adapters status,it was red and i got the error Receiver channel. Details: (No detail information set. so pls help me .pls suggest me
thanking u
regards ,
ramesh

Hello Ramesh,
I assume you deployed your jms libraries via SDM.
You can check a successfull deployment in the libraries of the server node via the J2EE Admin tool.
To get a more detailed log, you can augment the log level to debug for destinations
com.sap.aii.af.service.jms & com.sap.aii.adapter.jms. You can do so in the logConfigurator of the J2EE Admin tool.
Afterwards reactivate your comm channel in the configuration. (Just change the short text, so you can change and reactivate.)
When you then go to the defaultTrace file via the logViewer, you should see more details on the error.
Greetings,
Bart

JMS Sender Adapter error.

Hello all.
I get an error trying to recieve pick up a JMS message from a Websphere-MQ:
Error while processing message 'a17728a0-99ba-11dc-af52-0017a4f51c91'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Could not begin a AF transaction: TxManagerException: Unable to open transaction: com.sap.engine.services.ts.exceptions.BaseSystemException at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:103) ...
Ps. Already connected successfully to this MQ with a receiver channel so all authorizations should be correct.

Hi Saurabh,
Queue Manager is restarted again but my problem is not resolved...
secondly there is an admin user of PI ensure that the user has all access to open queue manager . if it not working you can request to profile DL-ALL access to PI user .
please explain in detailed above information..
here i am using there modules and the processing sequence is
CallSapAdapter    Local enterprise Bean call_AF_MS
AP XI JMS Adapter/ConvertJMSMessageToBinary                      Local enterprise Bean Convert_JMS2Bin
SAP XI JMS Adapter/ConvertBinaryToXMBMessage                         Local enterprise Bean                       convert_Bin2XI
sequence is correct or wrong?

JMS-MQ Series error( MQJMS2002)

Similar Messages

Maybe you are looking for