JMS error reprocessing an syntax error edifact. Loopin error

Hello all,
The problem I have found is that the adapter is trying to process an not well formed edifact. As I read in the JMS FAQ
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/604e2b64-e689-2910-64b3-ffd650f83756
In chapter 13 it is said that is the standard behavior. Does anybody know the way to fix this error?
P.S. libraries installed v7.0
This topic was discussed here JMS adapter does not recover from error
Thank you for your time,
P.S.This issue is urgent Points will be given for sure if the answers help

Hi Sergio
Is your scenario transactional? Just try to uncheck "Transactional JMS Session" and try.
It may help
Thanks
Sai

Similar Messages

JMS Error when using OJMS/AQ in OC4J 9.0.2 but not in OC4J 9.0.3

Hi,
I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
During the start-up of 9.0.2 container, it successfully connects with Oracle AQ, finds queues in AQ but finally comes back with an error message saying "JMS Error: invalid arguments in call". It does not provide any more information about the error.
Does any one have got any clue why this error message occur during startup? Any assistance is appreciated.
The following is the definition of Resource provider in config/application.xml:
<resource-provider class="oracle.jms.OjmsContext" name="ispojms">
<description> OJMS/AQ </description>
<property name="url" value="jdbc:oracle:thin:@Hduna1.corporatetesth.nsw.edu.au:1527:ISP"></property>
<property name="username" value="ISPDBA"></property>
<property name="password" value="******"></property>
</resource-provider>
The user ISPDBA is given all privileges for AQ in Oracle DB.
The Message Driven Bean's definition in deployment descriptors:
Ejb-jar.xml:
<ejb-jar>
<enterprise-beans>
<message-Long postings are being truncated to ~1 kB at this time.

Hi Balaji,
What most likely is happening is that you have mismatched versions of apapi.jar (client side) and the database, thus the reason for the "invalid arguments in call" error you're seeing.
If you're using 9.0.1.3 of the database it should be patched with patch #2416054. Go to Metalink and do a search for this patch to find it. You can then use the apapi.jar that comes with the patched version of the DB or the apapi.jar that comes with v9.0.3.
By the way, v9.0.3 and 9.0.1.3 + patch is a J2EE 1.3 compatible JMS server.
I'm guessing that you used the apapi.jar that came with v9.0.2 with the v9.0.1.3 database and that you've probably already applied the above patch. If you have then just take the apapi.jar that came with v9.0.3 and use it in your v9.0.2 environment.
In short:
v9.0.3 apapi.jar matches with v9.0.1.3 + patch
v9.0.3 apapi.jar also matches with v9.0.1.4
v9.0.2 apapi.jar matches with v9.0.1.3
Hope this helps...
John
Hi,
I tried to use OJMS/AQ as the JMS provider in OC4J 9.0.2 and OC4J 9.0.3. Resource providers in both the containers point to the same Oracle database (9.0.1.3.0) using the same user account.
JMS works fine with OC4J 9.0.3 but not with OC4J 9.0.2.
During the start-up of 9[i]Long postings are being truncated to ~1 kB at this time.

XI 7.0 NW 2004s install - JMS Errors in applications.log & defaultTrace

We just installed XI 7.0 NW 2004s. The installation of XI 7.0 NW 2004s is a lot simpler than XI 3.0 NW 2004 since the Template installer runs most of the post installation steps.
However, there are a few issues that I am encountering that i did not see with XI 3.0 installations. The installation is on Windows 2003 server and SQL server 2005.
Checking the applications.log file through Visual Administrator LogViewer, I see that the Applications log is filing up every few seconds with the following repeating errors:
Message -
Exception on server occured! Internal error.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070D0000013000041A845FCB659B
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
Message -
Exception on server occured! Cannot write to transaction log TXf48.tx.
Additional Information -
Category : /Applications/JMS
Message ID : 001422B146E800750000070A0000013000041A845FCB4CC8
Source Name : /Applications/JMS
Thread : SAPEngine_Application_Thread[impl:3]_26
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d16ec30026fd11dbb450001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : com.sap.jms.client.session.Session
Resource Bundlename :
Session : 0
Source : /Applications/JMS
ThreadObject : SAPEngine_Application_Thread[impl:3]_26
Transaction :
User : J2EE_GUEST
In the defaultTrace.trc file, i see the JMS error too:
Message -
Error From List = javax.jms.JMSException: Internal error.
     at com.sap.jms.protocol.notification.ServerExceptionResponse.getException(ServerExceptionResponse.java:271)
     at com.sap.jms.client.session.Session.checkReceivedPacket(Session.java:1808)
     at com.sap.jms.client.session.Session.rollback(Session.java:300)
     at com.sap.jms.client.session.Session.close(Session.java:158)
     at com.sap.jms.client.xa.SessionAdapter.close(SessionAdapter.java:52)
     at com.sap.engine.services.jmsconnector.spi.ManagedSession.sessionClosed(ManagedSession.java:279)
     at com.sap.engine.services.jmsconnector.cci.SessionImpl.close(SessionImpl.java:119)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession.close(ISPEventSession.java:262)
     at com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPTimerEvent.timeout(ISPTimerEvent.java:361)
     at com.sap.engine.services.timeout.TimeoutNode.run(TimeoutNode.java:56)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Additional Information -
Category : /Version
Message ID : 001422B146E8008B000007340000013000041A847A0F6CB9
Source Name : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
Thread : SAPEngine_Application_Thread[impl:3]_98
Application :
Argument Objs :
Arguments :
Dsr Component :
Dsr Transaction : d815880126fe11db9edc001422b146e8
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives : /Version
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.protocol.ispeak.services.timer.impl.ISPEventSession
ThreadObject : SAPEngine_Application_Thread[impl:3]_98
Transaction :
User : J2EE_GUEST
This is filing up both the applications.log and defaultTrace files. I cannot find any information through Service Marketplace. Has anyone encountered this issue? This is new installation - no messages are running on it so I am not sure why there is a JMS error.
Regards,
Jay

Hi Jay,
The exception means that the JMS Provider is not able to write to the transaction log file upon close of a transacted session. In NW04s, JMS transactions are stored as files on the local file system. The location of the root folder where the transactions are persisted is configured by the JMS service property "transactionStorePath". You can check its value through the Visual Administrator -> Services-> JMS Provider -> Properties. Please check if it contains a correct directory path and that nothing prevents the server from writing to this path - access rights, enough disk space, etc. If there is something wrong with the path, you can change it, save the change and restart the JMS provider service for the change to become effective.
You can also have a closer look at the server trace file: the root cause of the above exception is some other exception, probably I/O one, and it should be logged somewhere in adjacency to the JMS exception.
There is ongoing JMS communication even in a new server installation - in this case (judging from the stack trace) the component that performs this JMS activity is the timeout service.
Hope this helps,
Stoyan

JMS Error destination..

Hi,
I am developing a JMS application where i am processing message in a Queue and configured redelivery delay and redelivery limit. When the maximum redelivery limit has reached, i will move the message to an error destination which is again a Queue. I can send an email to the administartor with the message information indicating that the processing for the message has failed. But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? If that is the case what can be value for time-to-live for the message? I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?
Thanks in advance for your replies,
Sam

Hi,
I am using ServiceBus 10.3 and using the underlying weblogic server as JMS provider. I think OSB tends to decorate JMS messages with its own private information, so I don't know if it can support arbitrarily moving them between destinations. You may be better off posting to an OSB specific forum.
But the requirment is, the administrator wants to view the message from the persistent store and resubmit the message. Is it possible? That said, you can view, delete, move, and file import/export WebLogic JMS messages using the message management screens on the console. If you need a more sophisticated capability than the console provides, it is possible to write Java or WLST program's for the purpose.
If you're interested in scripting, the following might be enough to get you started:
For scripting and tracing examples, see the July 29th and August 10th 2009 newsgroup post with subject "Example using of getMessage(s) with JMS error queues?" [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3657916] and the June 10th 2009 newsgroup post with subject "JMSDestinationRuntimeMBean - possible STATE values " [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3531603 ]. Also take a look at the +Sept 23 2009 newsgroup posts with subject "Enable JMS - Queue/Topic Trace on console"+ [ here | http://forums.oracle.com/forums/thread.jspa?messageID=3782486].
+WARNING: Exporting too many messages at a time can cause out-of-memory errors.+
Besides, i have a question on the relationship between redelivery delay, redelivery limit and time-to-live override. When i tested, if time-to-live is less than the redeliverylimit*redelivery delay, then will the message be deleted and the redelivery limit(number of retries) is not taking into effect. But if time-to-live is greater than also the message is deleted after maximum retry means time-to-live doesn't have effect. This means i am i right to say, if i specify time-to-live and there is no need to specify redeliverylimit and redelivery delay. If that is the case on what basis, the retry is made?By definition, an expired message is automatically deleted -- no matter what the delivery count is. If you want expired messages to be automatically redirected to a destinatin's error destination you can configure an "expiration policy" of "redirect" on the destination.
Whether you want to use message expiration, redelivery limit, or redelivery delay very much depends on your specific use case.
-- Redelivery limits detect messages that are rolled back many times by receiving applications (rollbacks can occur due to any number of reasons, such as database failure, application bug, etc.)
-- Redelivery delays prevent rolled back messages from being immediately redelivered. This helps prevent zooming up CPU usage to 100% with tight loop retries of processing a problem message, assumes that whatever condition caused the original rollback is temporary, and assumes that if the message is immediately redelivered that this is too soon for the problem condition to have cleared up.
-- Expiration detects if a message has been sitting around for a long time. It doesn't detect whether the application has attempted to process the message...
In general, if you are coding a new application, it is sometimes helpful to avoid error destinations. Instead, let your application decide what to do with problem messages (such as queue them to another destination). This helps your application provide more customizable behavior.
Hope this helps,
Tom
PS Especially for developers new to WebLogic JMS, I highly recommend purchasing a copy of the book "Professional Oracle WebLogic". In addition, I recommend reading the new "Best Practices" chapter of the JMS configuration guide, and the new "Tuning Checklist" in the JMS chapter of the Performance and Tuning guide. These new sections are in the 10.3.2 documentation.

Examples for JMS Error Queue implementation in BPEL

Hi ,
Please anyone provide me examples for JMS error queue implementaion in BPEL.
Regards
Narsi p

Hi Narsi p,
Please remember to mark answers accordingly... Helpful or correct, following the forum rules
https://forums.oracle.com/forums/ann.jspa?annID=330
Can you tell us more about what are you trying to achieve here?
If you are just trying to configure an error queue to put the messages that couldn't be delivered, you can do this in weblogic directly.
Configuring an Error Destination for Undelivered Messages
http://docs.oracle.com/cd/E17904_01/web.1111/e13727/manage_apps.htm#JMSPG254
Cheers,
Vlad

JMS error while configuring SLD

HI folks,
I'm, encountering a tricky problem while connecting the SLD to the SolMan - running on the same host.
During making all neccessary steps it was no longer possible to log on to the
J2ee-Engine by /nwa or whatever application.
It just shows User locked or ONKNOWN ERRR
We unlocked the J2ee_admin again (strage, because the cause in Configtool was "locked after 0 unsuccessfull logins" weired! )
Then unset again the Superadmin, restartet the server... and again:
Application cannot be started.
Details: com.sap.engine.services.deploy.container.ExceptionInfo: JMS error.
Back to Superadmin Mode, Unlocking J2ee_admin, starting application manually in this mode, it comes up - I can see a loginscreen again but of course cannot login while superadmin mode is active...
After restarting cluster... same effect.
It seems, that the JMS cannot start due to locked User J2ee_admin and afterwards no other application is able to run.
Does anybody know, why this User J2ee_admin might be locked just before the JMS Service is started ?
Many many thanks in advance for any hint. Struggling since 2 days with this issue.
Nicolas

Problem is solved... Logging in to Abap Part in UME-Linked CLient 001 and unlocking j2ee_admin did what VA was not able to...

Problem creating JMS Error Destination via Ant in WLS 8.1

We've got several JMS queues in our application. We create the server via Ant (using the wlconfig task).
All is well, the queues have been working fine, until we try to add an error destination queue (after several attempts to handle the message, it'll be sent to the error queue for later troubleshooting).
Here's an example of what we've got now:
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
 <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
 <set attribute="RedeliveryLimit" value="5"/>
</create>We create another queue to handle the errors, and then add an attribute to the first to point to the second:
<create type="JMSQueue" name="batchErrorQueue" property="batchErrorQueue">
 <set attribute="JNDIName" value="net.nike.cdm.batchErrorQueue"/>
 <set attribute="RedeliveryLimit" value="5"/>
</create>
<create type="JMSQueue" name="batchQueue" property="jmsqueue">
 <set attribute="JNDIName" value="net.nike.cdm.batchQueue"/>
 <set attribute="RedeliveryLimit" value="5"/>
 <set attribute="ErrorDestination" value="${batchErrorQueue}"/>
</create>This seems logical, because if we do this same exact operation via the console, the config.xml goes from this:
<JMSQueue JNDIName="net.nike.cdm.batchQueue"
 Name="batchQueue" RedeliveryLimit="5"/>to this:
<JMSQueue ErrorDestination="batchErrorQueue"
 JNDIName="net.nike.cdm.batchQueue"
 Name="batchQueue" RedeliveryLimit="5"/>
<JMSQueue JNDIName="net.nike.cdm.batchErrorQueue" Name="batchErrorQueue"/>The error we get when trying to do this via Ant is:
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue" on JMS server "cdmdomain"). Also, an ErrorDestination can not be null if the ExpirationPolicy for a destination is "redirect" and a destination can not specify itself as its ErrorDestination.Flipping on -verbose in Ant, the actual exception is:
[wlconfig] SET -mbean cdmdomain:Name=batchQueue,Type=JMSQueue -property ErrorDestination cdmdomain:Name=batchErrorQueue,Type=JMSQue
[wlconfig] A destination and its ErrorDestination must both be on the same JMS server. (The problematic destination is "batchQueue"
s its ErrorDestination.
 [if] Error in class net.sf.antcontrib.logic.IfTask
BUILD FAILED
file:C:/viewstore/CDM_R6.5_Development/B2B_CDM/dev/build.xml:1399: Error invoking MBean command: java.lang.NullPointerException
 at weblogic.ant.taskdefs.management.WLConfig.handleException(WLConfig.java:567)
 at weblogic.ant.taskdefs.management.WLConfig.invokeCommand(WLConfig.java:381)
 at weblogic.ant.taskdefs.management.WLConfig.invokeSetCommand(WLConfig.java:235)
 at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:163)
 at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
 at weblogic.ant.taskdefs.management.WLConfig.invokeCreateCommand(WLConfig.java:167)
 at weblogic.ant.taskdefs.management.WLConfig.executeCommands(WLConfig.java:106)
 at weblogic.ant.taskdefs.management.WLConfig.execute(WLConfig.java:89)
 at org.apache.tools.ant.Task.perform(Task.java:341)
 at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:117)
 at org.apache.tools.ant.Task.perform(Task.java:341)
 at net.sf.antcontrib.logic.IfTask.execute(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
 at org.apache.tools.ant.Task.perform(Task.java:341)
 at org.apache.tools.ant.Target.execute(Target.java:309)
 at org.apache.tools.ant.Target.performTasks(Target.java:336)
 at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
 at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
 at org.apache.tools.ant.Main.runBuild(Main.java:609)
 at org.apache.tools.ant.Main.start(Main.java:196)
 at org.apache.tools.ant.Main.main(Main.java:235)So, my question is, what are we doing wrong? What IS the syntax to set an error destination for a JMS queue via Ant for WLS 8.1?
Any help would be greatly appreciated
Thanks,
Douglas Bullard

I get exactly the same problem - was a resolution to this issue found?
Thanks,
Richard Marriott
[email protected]

JMS error while looking up from Client

Hi
I am looking up a JMS factory though a stand alone client in SAP web as Sp 15. While looking up through JNDI we are getting a deserialisation error . I have included all the j2ee client jars in the classpath. Any idea do we need to include some other jars also ..
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name jmsFactory/CXLQueueConnectionFactory, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: Cannot lookup ManageConnectionFactory "CXLQueueConnectionFactory". Cannot deserialize object: com.sap.engine.services.jmsconnector.exceptions.BaseClassNotFoundException: Deserialization Error: java.lang.NoClassDefFoundError: com/sap/jms/server/SynchronousNetworkAdapter
 at java.lang.Class.forName0(Native Method)
 at java.lang.Class.forName(Class.java:141)
 at com.sap.engine.services.jndi.persistent.ClientCPOInputStream.resolveClass(ClientCPOInputStream.java:52)
 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513)
 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
 at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sap.engine.services.jmsconnector.spi.ManagedConnectionFactoryImpl.readObject(ManagedConnectionFactoryImpl.java:318)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
 at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:165)
 at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:522)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:204)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:172)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:261)
 at com.sap.engine.services.jmsconnector.spi.ManagedConnectionFactoryImpl.readObject(ManagedConnectionFactoryImpl.java:334)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)
 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)
 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)
 at com.sap.engine.services.jndi.persistent.RemoteSerializator.toObject(RemoteSerializator.java:70)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeObject(ClientContext.java:3349)
 at com.sap.engine.services.jndi.implclient.ClientContext.deserializeDirObject(ClientContext.java:3303)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:385)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:165)
 at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:301)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:522)
 at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:639)
 at javax.naming.InitialContext.lookup(InitialContext.java:347)
 at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:204)
 at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:172)
 at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:261)
Any help on this will be appreciated.
regards
rajesh kr

Hi Rajesh,
Please add the jar file "sapjms.jar" to your classpath,
it is situated at
\usr\sap\<sid>\<id>\j2ee\cluster\server0\bin\services\jms_provider
HTH
Peter

JMS error- Exception in thread "Main Thread" java.lang.NoClassDefFoundError

Hi guys,
I am new to JMS programming and i'm have the following error...I have set up a simple weblogic server on my local machine and i am trying to send a message to a queue i've created on a JMS server. I am trying to manually run an example provided by BEA WebLogic... the code follows.
//package examples.jms.queue;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.Hashtable;
import javax.jms.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
/** This example shows how to establish a connection
* and send messages to the JMS queue. The classes in this
* package operate on the same JMS queue. Run the classes together to
* witness messages being sent and received, and to browse the queue
* for messages. The class is used to send messages to the queue.
* @author Copyright (c) 1999-2006 by BEA Systems, Inc. All Rights Reserved.
public class QueueSend
// Defines the JNDI context factory.
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
// Defines the JMS context factory.
public final static String JMS_FACTORY="weblogic.examples.jms.QueueConnectionFactory";
// Defines the queue.
public final static String QUEUE="weblogic.examples.jms.exampleQueue";
private QueueConnectionFactory qconFactory;
private QueueConnection qcon;
private QueueSession qsession;
private QueueSender qsender;
private Queue queue;
private TextMessage msg;
 * Creates all the necessary objects for sending
 * messages to a JMS queue.
 * @param ctx JNDI initial context
 * @param queueName name of queue
 * @exception NamingException if operation cannot be performed
 * @exception JMSException if JMS fails to initialize due to internal error
public void init(Context ctx, String queueName)
 throws NamingException, JMSException
 qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
 qcon = qconFactory.createQueueConnection();
 qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
 queue = (Queue) ctx.lookup(queueName);
 qsender = qsession.createSender(queue);
 msg = qsession.createTextMessage();
 qcon.start();
 * Sends a message to a JMS queue.
 * @param message message to be sent
 * @exception JMSException if JMS fails to send message due to internal error
public void send(String message) throws JMSException {
 msg.setText(message);
 qsender.send(msg);
 * Closes JMS objects.
 * @exception JMSException if JMS fails to close objects due to internal error
public void close() throws JMSException {
 qsender.close();
 qsession.close();
 qcon.close();
/** main() method.
* @param args WebLogic Server URL
* @exception Exception if operation fails
public static void main(String[] args) throws Exception {
 if (args.length != 1) {
 System.out.println("Usage: java examples.jms.queue.QueueSend WebLogicURL");
 return;
 System.out.println(args[0]);
 InitialContext ic = getInitialContext(args[0]);
 QueueSend qs = new QueueSend();
 qs.init(ic, QUEUE);
 readAndSend(qs);
 qs.close();
private static void readAndSend(QueueSend qs)
 throws IOException, JMSException
 BufferedReader msgStream = new BufferedReader(new InputStreamReader(System.in));
 String line=null;
 boolean quitNow = false;
 do {
 System.out.print("Enter message (\"quit\" to quit): \n");
 line = msgStream.readLine();
 if (line != null && line.trim().length() != 0) {
 qs.send(line);
 System.out.println("JMS Message Sent: "+line+"\n");
 quitNow = line.equalsIgnoreCase("quit");
 } while (! quitNow);
private static InitialContext getInitialContext(String url)
 throws NamingException
 Hashtable<String,String> env = new Hashtable<String,String>();
 env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
 env.put(Context.PROVIDER_URL, url);
 return new InitialContext(env);
}when i run the main method with args[0] = "t3://localhost:7001", i get the following errors:
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/security/subject/AbstractSubject
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at QueueSend.getInitialContext(QueueSend.java:122)
at QueueSend.main(QueueSend.java:91)
Could someone please help. thanks.

when i run the main method with args[0] = "t3://localhost:7001", i get the following errors:
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/security/subject/AbstractSubject
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at QueueSend.getInitialContext(QueueSend.java:122)
at QueueSend.main(QueueSend.java:91)
Could someone please help. thanks.This is Java 101:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rtrb_classload_viewer.html
You've got to have the WebLogic JAR that contains the necessary .class files in your CLASSPATH when you run.
Don't use a CLASSPATH environment variable; use the -classpath option when you run.
%

JMS error

Hi All,
I am getting this error in my JMS adapter.
Error while processing message '721d1a60-257a-11dc-cd56-001125bfd700'; 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(Compiled Code)) ...
Thx in advance
Ranjeet

I have one more question,
In Adapter module if I have a customized module deployed in XI server, what should be the sequence of the different modules in communicaion channel:
SAP XI JMS Adapter/ConvertJMSMessageToBinary
SAP XI JMS Adapter/ConvertBinaryToXMBMessage
CallSapAdapter
Where in this sequence should I put my customized texttoxml module.
Thx in advance
Ranjeet

JMS Error MalformedInputException

Hello,
I am getting the error bellow in a jms adapter.
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error converting Message: sun.io.MalformedInputException: TransformException: Error converting Message: 'sun.io.MalformedInputException' at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:94) ...
I have double checked the jms configuration and it looks like in version 7.0:
localejbs/SAP XI JMS Adapter/ConvertJMSMessageToBinary ReceiveMsg
localejbs/SAP XI JMS Adapter/ConvertBinaryToXMBMessage ConvertMsg
localejbs/AF_Modules/MessageTransformBean Plain2XML
localejbs/CallSapAdapter 0
I checked in the module configuration table that the fields and lengths are matched and I also checked that the sample file format is saved as utf before putting it in the queue as the declaration in this table (text/xml;charset=utf-8)
Does anybody solved this problem before?
Thank you for your time.

Hello Yaghya Nana,
I need to do a conversion into xml fomat because after this step the incoming message is mapped to another structure via graphical mapping.
To set up the channel I have used the doc https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
the inbound structure of mygraphical mapping is identical to the page four.
I think that the problem is in the file but I don´t know what else can I check.
Thank you for your quick answer

Sender JMS Error

Hi
I have to pick up message from WMS (MQ Series), and I have set up JMS adapter, it is showing me message as
'Sucessfully connected to destination 'queue://DTA.WMS.VIC_PRCONF.IN?CCSID=819&targetCleint=1'
But it is not picking up any message from the queue.
Can you please let me know what could be the reson for not picking up messages.
Regards
Ria

Hi Ria Sen,
They are somany reasons for not picking the data from Queue.
1) First Check ADAPTER is active or not.
2)Once its not pick up the data from queue its shows the error in ADAPTER MONITORING, So check adapter monitoring in RWB.
3) Is their any special chacters (or) any imporper data in the queue , its not pick up the data.
So check these reasons and again put the data in queue.
Regards,
Skumar

Receiver JMS error

Hi all,
i am using websphere MQ .
i am getting error in rcvr jms.in audit log....its showing
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_XXXXXXXXX:15fa03eb9fd837849906f512610314c4
i have checked...all the parameters ... all r correct...
have anyone faced this problem......?
thnx

Hi,
Refer below links
XI to IBM Websphere Default JMS Provider with JNDI
JMS receiver adapter configuration error
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Thanks
Swarup

Oracle 10G JMS error : Failed to handle dispatch message ... exception ORABPEL-05002

Hi All,
We are using a JMS adapter as partner link in a BPEL process to produce messages to JMS Queue.
We are getting an error while producing a message to a JMS Queue.
The error comes for 1 or 2 instances among 5 to10 intsances. (all these instances ran with in 1 or 2 seconds).
We are using Oracle 10G SOA suite.
This error is getting in the Production environment.
The error is as follows (took error from server log).
Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{summary=file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
file:/sw/appaia/product/SOA/bpel/domains/default/tmp/.bpel_CurrencyExchangeListEbizJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrencyExchangeListEbizJMSProducerV1.wsdl [ Produce_Message_ptt::Produce_Message(OutputParameters) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: oracle.j2ee.connector.proxy.ProxyInterceptException: javax.resource.ResourceException: RollbackException: Transaction has been marked for rollback: null [Caused by: RollbackException: Transaction has been marked for rollback: null]
; nested exception is:
ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
I tried the below JMS tunings with differnt combination, but no improvement.
 <property name="useJCAConnectionPool">true</property>
 <property name="maxSizeJCAConnectionPool">500</property>
 <property name="retryMaxCount">10</property>
 <property name="retryInterval">60</property>
Please let me know if any other logs or any other information is required.
Thanks,
Pershad

sorry, I forgot the below things which I tried to tune the JMS.
<property name="retryMaxCount">10</property>
<property name="retryInterval">60</property>
<property name="useJCAConnectionPool">true</property>
<property name="maxSizeJCAConnectionPool">500</property>
Thanks.

JMS error with SQL Server 2005 SP1

Hi all,
I have set up LC 8.0 with a SQL Server and the server seems to be running, however I get some errors in the log that I don't like. Can you help me fix this problem?
2008-07-23 12:06:49,197 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
2008-07-23 12:06:49,213 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected:
javax.naming.NameNotFoundException: XAConnectionFactory
at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:223)
at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:229)
at $Proxy181.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:173)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java :605)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvok er.java:1471)
Sincerely
Kim

Hi,
I found that in the log file. I follow the preparing to install livecycle Es guide to configure JMS with SqlServer 2005 SP1
jboss.mq:service=DestinationManager
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=juddi
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager

JMS error reprocessing an syntax error edifact. Loopin error

Similar Messages

Maybe you are looking for