Jms receive timeout problem
Hi guys,
I want to receive messages on a timeout basis. However, my code always stuck at a certain point. Here is my source code:
import javax.jms.*;
import javax.naming.Context;
import javax.naming.NamingException;
import javax.naming.spi.NamingManager;
import java.util.Hashtable;
public class JmsRecv {
public static void main(String[] args) throws JMSException, NamingException {
Context JndiContext = createContextForWeblogic(args[0]);
QueueConnectionFactory TheQueueConnectionFactory = (QueueConnectionFactory) JndiContext.lookup("weblogic.jms.ConnectionFactory");
Queue q = (Queue) JndiContext.lookup("Queue_A");
QueueConnection qc = TheQueueConnectionFactory.createQueueConnection();
qc.start();
QueueSession qs = qc.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
QueueReceiver qr = qs.createReceiver(q, null);
Message mrecv = null;
long elapsed = 0;
int index = 1;
while (mrecv == null && elapsed < 200) {
long start = System.currentTimeMillis();
mrecv = qr.receive(10);
elapsed = System.currentTimeMillis() - start;
System.out.println("index=" + index++ + " elapsed=" + elapsed);
qr.close();
qs.close();
qc.close();
static Context createContextForWeblogic(String connectionURL) {
Context ctx = null;
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
env.put(Context.PROVIDER_URL, connectionURL);
try {
ctx = NamingManager.getInitialContext(env);
} catch (Exception e) {
e.printStackTrace();
MSFException msfException = new MSFException(e.getMessage());
msfException.initCause(e);
throw msfException;
return ctx;
}And the result is always:
index=1 elapsed=31
index=2 elapsed=16
index=3 elapsed=15
index=139 elapsed=16
index=140 elapsed=15
index=141 elapsed=9391
It always stops at index 141. Why the jms receive with timeout works initially then doesn't work as expected? Any ideas?? I have a similar problem with send too. Send works quickly initially but at a certain point sending takes too much time. Thanks.
Gurkan
try moving
long start = System.currentTimeMillis();
outside your while loop. That is your starting point and it should change after you start. But having it in the loop resets it.
Similar Messages
-
JMS Receiver FCC Problem After Upgraded from SP19 to SP22 in XI3.0
Hello,
I am facing a problem in my Receiver JMS adapter in FCC just after the upgrading it from SP19 to SP22 in XI 3.0 by our basis consultant. Before that everything was working perfect in DEV.
I am getting the below mentioned error in CC monitoring.
> MP: Exception caught with cause com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException''; nested exception caused by: java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.NullPointerException'
This problem is happening in other scenario too in our DEV system.
But at the same time since we have not applied any upgrade in QA therefore same scenario is working fine.
Regards,
SarveshOk Friends...
I got the solution from SAP.. there was a problem in the SP22 for XI 3.0 which I donloaded from Service Market Place. Now I have applied the correct SP22 to my system and now it is working fine...
I hope this may help you...
Regards,
Sarvesh -
JMS Receiver Adapter Conversion problem
Hi All,
My Scenario.
Websphere MQ(JMS Adapter)--->SAP XI--->Webspher MQ(Receiver Adapter)----->Mainframe MQ
I am using Module parameters in JMS Receiver Adapter.
Module Sequence in the Receiver Channel
No. Module Name T Module Key
1 localejbs/AF_Modules/MessageTransformBean L XML2Plain
2 localejbs/SAP XI JMS Adapter/ConvertMessageToBinary L CallJMSService
3 localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService L Exit
Module
Key
Parameter Name Parameter Value
XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
XML2Plain Transform.ContentType text/plain;charset=utf-8
XML2Plain xml.conversionType SimpleXML2Plain
XML2Plain xml.addHeaderLine 0
XML2Plain xml.fieldFixedLengths 3,5,10
XML2Plain xml.fixedLengthTooShortHandling Cut
Output of JMS Adapter message in Websphere MQ
abc def sahafhhjf .
fdh hdh jfjfjdjdjgjjjd .
This "." giving error in Mainframe MQ.plz help me how to remove dot(".") end of the record.
thanks,
pachikaHi
Reduce the field length where this "." is coming. As you are using fixedLengthTooShortHandling Cut this will trim the dot.
Try it
Else you can remove this in Mapping as well.
Thanks
Gaurav -
JMS receiver to JMS sender Problem
Hi,
Please find the scenario
IDOC 'A' -
> PI -
>JMS(WebSphere) Receiver
IDOC 'B' <-- PI <--
JMS (WebSphere) Sender
now here I need to pass the response to some other IDOC.
I have follwoing 2 questions:
1. Please let me know adapter module to build this async to sync thru JMS receiver and sender.I am using JMS WebSphere.
2. JMS receiver is getting request but its not getting successfully as its missing SOAP envelope and SOAP body.
how to add SOAP envelope and SOAP body in JMS receive? is there any adapter module for this?
Thanks,
BhupeshHello Bhupesh,
This will do it as XSLT (copies all of your payload into an SOAP Envelope):
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body>
<xsl:copy-of select="/"/>
</soap:Body>
</soap:Envelope>
</xsl:template>
</xsl:stylesheet>
With best regards
Sebastian -
Problem with JMS Receiver.
Hello,
I am using JMS Receiver, I want to convert the XML to Plain text. Below are the parameters that i have used whle conversion.
Please let me know whats going wrong,
1 AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain
2 SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
3 SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
XML2Plain Transform.Class com.sap.aii.af.sdk.xi.adapter.Conversion
XML2Plain Transform.ContentType text/plain;charset=utf-8
XML2Plain xml.addHeaderLine 0
XML2Plain xml.conversionType SimpleXML2Plain
XML2Plain xml.documentName MTXYZ
XML2Plain xml.documentNamespace http://test
XML2Plain xml.fieldFixedLengths 5,6,7,8
XML2Plain xml.fieldNames X,Y,Z,A
XML2Plain xml.fieldSeparator -
XML2Plain xml.fixedLengthTooShortHandling Cut
XML2Plain xml.processFieldNames fromConfiguration
Thanks,
Siddhesh
Edited by: Siddhesh Pathak on Oct 22, 2009 12:09 PM> XML2Plain Transform.Class com.sap.aii.af.sdk.xi.adapter.Conversion
> XML2Plain Transform.ContentType text/plain;charset=utf-8
> XML2Plain xml.addHeaderLine 0
> XML2Plain xml.conversionType SimpleXML2Plain
> XML2Plain xml.documentName MTXYZ
> XML2Plain xml.documentNamespace http://test
> XML2Plain xml.fieldFixedLengths 5,6,7,8
> XML2Plain xml.fieldNames X,Y,Z,A
> XML2Plain xml.fieldSeparator -
And the second thing is you cannot use both FixedLength & fieldSeparator altogether. No need to give the field names unless you are using the complex structure. In your case you have used SimpleXML2Plain which means it is a simple structure. Please make sure of it. -
Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper
Hello,
I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
In the module tab, I added a new module:
Module Name Module Type Module Key
localejbs/Seeburger/AttribMapper Local Enterprise Bean map
And I added the following parameter:
Module Key Parameter Name Parameter Value
map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
When processing a message, I get the following error on the Communication Channel Monitoring:
Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
Does anyone has an idea on how to fix this problem?
Thanks for your help!
BenoitHI,
Refer the discussion of
Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
Dynamic subject in AS2 receiver
Thanks
Swarup -
Hello,
I have maintained a JMS receiver adapter to an existing MQ system (IBM WebSphere 6.0)
After deploying the modules to PI (7.11) the adapter goes green but allways says "Sucessfully disconnected from destination".
When sending a message through this adapter I get the error message:
"Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: No transition found from state: STARTING, on event: process_commence for DFA: JMSReceiver_ATLAS_MQ:4b9d8e8dfe883ebeb7ab5af79e59cdf6"
I can not find out where the problem can be....I played arrounf with the several options for QM Manasger, channels.....
I do not use any "Advanced Adapter options"
Anybody who can help me????
best regards
WernerI still have checked all the notes and blogs....
But nothing helps, I still have the same problem.
The problem can be, that I am not a MQ specialist, but I have access to the MQ and I can see the settings.
Do I have to use adapter specific atributes???
I only use QManager, Chanell, queue....
ANd there is somehting other really strange.
I have create several components for different scenarios.
When I create an Adapter in one component, I get the error I listed before.
But in some components I get the error:
"Channel Has Internal Error" in the RWB overview and in the node
"Adapter had not provided any status infomration about this channel"
I tried with Creating new channel, copy channel between the components....
but allways the same...in some components I get this error
in other components I get the message "Successfully discponnected from destination"
Werner
Edited by: Werner Magerl on Sep 28, 2010 1:59 PM -
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,
MarcusHi Marcus,
Have a look at below thread
Connecting to PI 7.11 JMS Queue from other PI 7.11 Server -
JMS receiver Adapter - Weblogic
Hi,
Could you please help us.
We are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic we are able to ping the Weblogic server from XI Server. The port is right one.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory: javax.jms.QueueConnectionFactory
JNDI Lookup Name of JMS Queue:com.nyc.OmsQueue
Name of JNDi Initial Context Factory: weblogic.jndi.WLInitialContextFactory
JNDI Server Address:http://nyc-d01:7001
JNDI Logon User: (Emty)
JNDI Password: (Emty)
There is no User Name and Password
Could you please help us. this is very urgent.
The Error message as follows
Error during channel initialization; exception trace: javax.naming.CommunicationException [Root exception is java.rmi.UnmarshalException: failed to unmarshal class java.lang.Object; nested exception is:
java.io.OptionalDataException]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:83) ...
Regards
RamidiHi,
>>Error during channel initialization; exception trace: java.lang.ClassCastException
at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:419)
at com.sap.aii.af.service.jms.WorkerHandlerImpl.run(WorkerHandlerImpl.java:369)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
The error u posted is from Weblogic server side, not from XI side.
The problem is that the channel created in weblogic server is not opened. For this you have specific setting while creating channels and queues in weblogic server.
Contact the concerned weblogic server guys in ur team to help you in this issue.
I faced the same error while configuring JMS receiver adapter.
Ravi. -
We are using a JMS receiver Adapter Channel to send data from XI to MQ Series. In our environment, we have 2 Java Server instances configured. The system is successfully sending files that hit the first Java instance, but the messages drop off and don't even make it to MQ Series when they hit the second Java instance. Has anyone ever seen this problem with JMS receiver Adapter channels?
ChrisHi Chris
I think you are talking about High availability.
In that case please check whether two instances installed same support pack or not.
Thanks
Sai -
JMS Receiver Adapter - com.ibm.websphere.naming.WsnInitialContextFactory
Hello experts,
I am trying to configure JMS Adapter to Access Websphere Application Server via JNDI. The configuration is as follow:
Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
Connection Factory: jms/messageQueueCF
Server URL: iiop://ammtnode.iubs.intra:2809/
Queue Name: jms/EXT_INPUT_QUEUE
I deployed all required jar files but Iu2019m still unable to connect to WAS because adapter cannot initialize ORB:
javax.naming.NamingException: Failed to initialize the ORB
I wrote a small java class to check where the problem was:
============================================================================
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://ammtnode.iubs.intra:2809/");
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
Context jndiContext = null;
try {
jndiContext = new InitialContext(env);
ConnectionFactory connectionFactory = (ConnectionFactory) jndiContext.lookup("jms/messageQueueCF");
Connection qConn = connectionFactory.createConnection();
Session qSession = qConn.createSession(false,Session.AUTO_ACKNOWLEDGE);
Queue q = (Queue) jndiContext.lookup("jms/EXT_INPUT_QUEUE");
MessageProducer producer = qSession.createProducer(q);
TextMessage message = qSession.createTextMessage();
message.setText(text);
producer.send(message);
producer.close();
qSession.close();
qConn.close();
} catch (Exception e) {
e.printStackTrace();
============================================================================
I got the same error until I wrote this line:
env.put("java.naming.corba.orb",org.omg.CORBA.ORB.init((String[])null,null));
And everything worked fine. Now I want to do the same in my JMS Receiver adapter but I donu2019t know how to introduce this line in the Initial Context Environment. I tried as JMS additional parameters and additional properties as well. However, nothing worked. Does anybody know what Iu2019m doing wrong?
Thank you in advance!Here I post the entire error:
0#0#Warning##Java###Catching #1#com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up connection fact
oryjms/messageQueueCF, for profile: ConnectionProfile of channel: CC_I002_AMM_JmsReceiveron node: 5949650 having object id: 0
360697bc61b3666aba07a2708ca095a: javax.naming.NamingException: Failed to initialize the ORB
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:134)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class
com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:libra
ry:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
... 11 more
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
... 19 more
Caused by:
javax.naming.NamingException: Failed to initialize the ORB [Root exception is java.lang.ClassCastException: class com.sap.eng
ine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incompatible with class com.ibm.CORBA.iiop.ORB:library:com.sap.
aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClassLoaderAT131b92e6ATalive]
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:364)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:421)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:123)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:798)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory(JndiConnectorImpl.java:130)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:247)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:185)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connectIfDisconnected(ConnectorImpl.java:170)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:153)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:279)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:166)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl$1.run(AdapterImpl.java:411)
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:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: java.lang.ClassCastException: class com.sap.engine.system.ORBProxy:sun.misc.Launcher$AppClassLoaderAT5d0385c1 incom
patible with class com.ibm.CORBA.iiop.ORB:library:com.sap.aii.adapter.libATcom.sap.engine.boot.loader.ResourceMultiParentClass
LoaderAT131b92e6ATalive
at com.ibm.ws.orb.GlobalORBFactory.init(GlobalORBFactory.java:92)
at com.ibm.ejs.oa.EJSORBImpl.initializeORB(EJSORBImpl.java:179)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:83)
at com.ibm.ejs.oa.EJSClientORBImpl.<init>(EJSClientORBImpl.java:59)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:102)
at com.ibm.ws.naming.util.Helpers.getOrb(Helpers.java:356)
... 19 more -
Error in JMS receiver channel - XI - Weblogic
Hi Experts
We are also having the situation that we are sending messages from XI to Weblogic server with the help of JMS Adapter. The Queue is available in Weblogic server.
Our configuration of JMS receiver Adapter is
JNDI Lookup Name of Queue Connection Factory----
ConnectionFactory
JNDI Lookup Name of JMS Queue----
queue/IntegrationQueue
Name of JNDi Initial Context Factory: -
weblogic.jndi.WLInitialContextFactory
JNDI Server Address:----
weblogic server ip
JNDI Logon User: -
user
JNDI Password: -
password
We are getting the error in the adaptor like " com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA:"
Could you please tell me if there are any other JAR files for this as i have already deployer weblogic.jar. If yes, Can you please give me some more details on that.
Thank you very much for your time and help.
Manjunath
Edited by: Manjunath Achar on May 23, 2010 4:12 PMHi Manju
There could be some problem while deploying the libraries. please check you have deployed the JAR Files correctly.
You need to include the Weblogic Thick client driver 'weblogic.jar' - with all classes under the package 'javax.jms' removed in your aii_af_jmsproviderlib.sda (releases 3.0/7.0) or com.sap.aii.adapter.lib.sda (releases 7.1).
The below links might be helpful for you,
http://wiki.sdn.sap.com/wiki/display/XI/FAQ+J2EEJMS+Adapter
Note 1090516 - XI JMS Adapter and BEA Weblogic JMS: FAQ
Regards
Ramg -
Dynamic Queue names at JMS receiver
HI All,
I have a scenario where sender is an RFC and receiver is via JMS and also get a reply back . JMS is asynchonous but as suggested in other threads it is possible to capture the response by setting some Adapter specific parameters.
But my problem is the queue name for the response is not constant and it varies from request to request for the response. I have no clue how to achieve this , I tried searching some threads but couldn't come to a conclusion.
Possibility of dynamic MQ queue selection in one receiver JMS channel
help on Dynamic queue name in JMS Adapter
Has anyone come across such a situation ? Please suggest.
Also In one of threads it was suggested to use Java Proxy? Please suggest a way forward in this approach too
Regards,
Mohan.> please refer the link what you provided in section 2.8 mentioned JMS Receiver communication channel will give response back,but i never tried.
Yest because this document is applicabe for a scenario where request msg will come form sender JMS to XI and then Response will be sent back again to JMS by using receiver JMS adapter. So senario is JMS request --- R3 (via XI) --- R3 response to JMS.
But here case is different. e.g. RFC --> PI --> JMS and reply will get back from JMS to RFC. So definetly in this case response will come from sender JMS and not from receiver JMS.
Read sec 2.8 throughly, you will come to know how to set the queue names dynamically for RECEIVER JMS Adapter.
Regards,
Sarvesh -
JMS receiver channel Error !!
Hi All,
We are facing problem in all JMS receiver communication channels, all rcevr channels are failing with following error,
Error while processing message '498499a3-e65c-0086-e100-80000a05260c';
detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Pending message discovered: 498499a3-e65c-0086-e100-80000a05260c.
The channel is configured throw an recoverable, temporary error for this warning (default). Decide whether you want to bypass this message. If so, set the Pending Handling channel parameter to 'Bypass' and restart the message afterwards. at
com.sap.aii.adapter.jms.core.channel.filter.OutboundDuplicateCheckFilter.filter(OutboundDuplicateCheckFilter.java:153) ...
does anybody know whats the exact error??
is it due to Adpater engine message buffere is full ?
regards
biplabBiplap,
1) Did you restarted the Java Engine ? If so deactive & active the JMS Adapter,
2)Check any EOIO message got struck in Adapter Engine ( RWB-Communication channel- JMS Adapter )
3) Sxmb_moni - Look for the below message status - 498499a3-e65c-0086-e100-80000a05260c
Cheers
Agasthuri Doss -
Heartbeat possibilty in JMS receiver channel?
Hi,
Does anyone know if it is possible to define a heartbeat interval in JMS receiver channels.
Is there maybe a possibility in the additional JMS paramters fields?
We need this to prevent connections being shut down by firewalls due to long inactivity. Once a JMS receiver channel is inactive due to this there is no automatic activation of the channel possible (I think).
The sending JMS channels pose no problem since XI AF seems to poll these every 5 seconds and thu sthe connection remains alive.
thanks
TomHi Shai,
We are using XI 7.0 with SP 12 and we entered this parameter in advanced settings in JMS receiver adapter called "CONNECTION_TEST_POLL" as true and it does the polling to see if the adapter is active...
Hope this helps.
Regards,
TJ
Maybe you are looking for
-
NVIDIA issue on MacBook Pro retina 15 (bootcamp)
hello guys! merry christmas everybody i have such problem: i bought MacBook Pro retina 15, when i came home i installed windows 7 thru bootcamp, after that i decided to check how many points of perfomance do i have, (in windows you can see that in co
-
How to cancel an active/running job in BW?
Hi All, I have a job running in the system for 2 hrs now. I want to cancel it, please suggest, how to do the same. Thanks, Raj
-
Calculations For parent periods
Hi All, I am able to calculate for month and i want to calculate for quarter seprately........ when i tried that calculate option was not highlighted................ hi friends please help me how to calculate the data for quarter,Halfyear,Year With b
-
How do I attach a picture to e-mail message
I am trying to attach a picture to send with my e-mail message. How do I accomplish this?
-
Query way slower as APEX report than in SQL client
Hi, I know that this topic has been discussed many times. Usually the problem is that the query returns at least thousands of data. Unfortunately, not in my case. The query returns the top 10 applications for the current month only, ordered descendin