JMS Adapter enqueue - batch commits

Hi,
I was looking at the SOA Best Practices 10.1.3.3 and while it talks about improving performance for enqueue operation it talks about batching commits (pg 9-9). I could not find the property on the JMS adapter that can Batch the commits of enqueue. I would appreciate if somebody could point me to the property for setting batch commits on JMS Adapter for enqueue operation.
Regards,
Mahesh.

Similar Messages

How to set property for Cluster Environment for JMS Adapter

Hi All,
I am moving from DEV to Prod environment which is cluster.
Can you Please explain me what property I need to Set for Cluster Environment for JMS Adapter, so that I could avoid race condition for Dequeue/enqueue.
I am using soa suite 10.1..3.4
Thanks in Advance.
Edited by: vikky123 on Jul 12, 2010 7:03 AM

put something like this
<activationAgents>
      <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PARNERLINKNAME">
        <property name="clusterGroupId">SOMEUNIQUEVALUE</property>
        <property name="portType">PARTNERLINK_PORTTYPE</property>
      </activationAgent>
    </activationAgents>

Error log on jms adapter

Hi,
I have an XI 3.0 connected to an MQ via jms adapter in an Adapter Engine
I have this log when sending a message:
15:39:18 (3130): JMS message ID:414d51204d51584944573120202020207a07c64442701b00 sent successfully
15:39:18 (3140): Session commited
15:39:18 (3180): Se produjo un error java.io.IOException: Error during rendering: Missing mandatory element <sap:queueId> for quality of service EOIO
15:39:18 (3190): Session rolled back
I'm trying to discover the mandatory element.
Regards
Gonzalo

Hello Michal,
Yes we need and we are using EOIO, and is not specified in SAP documentation to specify this parameter in the receiver JMS.
The thing is: Why is missing the mandatory element
<sap:queueId> for quality of service EOIO?
I really apreciate any help with this issue.
Thanks,
Regards,
Gonzalo

How to send message to a queue using JMS adapter

Hi,
I need to send messages to the default queue(demoQueue) available in the server using a JMS adapter in a BPEL process.
I tried doing the same by using an invoke activity that invokes the JMS adapter service to send the message to the queue. I deployed this process in the server and gave an input to send it to the queue. The prcoess executed without any errors in the BPEL console.
I am also using Hermes v1.0 to monitor the queue but it says that it dint receive any messages in the queue to read.
I am sorry that i have restrictions from the client that i can't post the code here. Please let me know if anyone has got any solution or if you know any other way of doing the same.
Thank you
Message was edited by: prince
the_prince

You can use the following procedure :
DBMS_AQ.ENQUEUE (
queue_name IN VARCHAR2,
enqueue_options IN enqueue_options_t,
message_properties IN message_properties_t,
payload IN "<ADT_1>",
msgid OUT RAW);

SOA 10g JMS adapter does not pick up large messages in Oracle AQ

I am using SOA 10g 10.1.3.4 MLR #9. When I enqueue a large JMS message ( of type SYS.AQ$_JMS_TEXT_MESSAGE ) into the AQ from SOA 11g it goes into the TEXT_LOB portion of the USER_DATA column in AQ. In addition to this GROUPID and GROUPSEQ do not seem to get set. When that happens, my JMS adapterfrom SOA 10g does not seem to dequeue the message. But if I enqueue the same message using sql and set the GROUPID and GROUPSEQ my JMS adapter from 10g picks up the clob message.
How do we make the 10g adapter always pick up the large message in TEXT_LOB? I don't have this problem when the message is small because it goes into TEXT_VC field instead of TEXT_LOB field.

We are having this problem and have not figured it out yet. We need help. An oracle SR is opened but no progress from Oracle yet. I need to get some traction on this so anyone's help is appreciated. Our suspicion is that the AQ client in the wls 10.3.1 is incorrectly choosing to put the xml payload in TEXT_LOB even though the character size is less than 4000.
Here is a summary of our observations....
Today we did some testing with our old 6.3.1 OSM environment and our new 7.0.2 environment. We tested each against our QA1 environment and then our QA2 environment. Scenrio 1 is our problem. Scenario 2,3,and 4 all behave similar to each other. Why does Scenario 1 behave differently. It is causing AIA a problem when it dequeues the message.
Scenario 1:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the Box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA1 environment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. Wehn we sent messages to the AIA QA1 table we saw that everything under TEXT_LEN 1000 went to TEXT_VC, Over 1000 went to TEXT_LOB. This is causes AIA to throw an exception if the message is over 1000 when it dequeus the message, because it thinks it shoudl look in the TEXT_VC which is null for AIA.
Scenario 2:
We pointed our 7.0.2 OSM/Weblogic 10.3.1/Out of the box AQ (which is part of our QA1 environment) to send messages to the AIA AQ table in our QA2 enviornment. The AIA database uses UTF8 character set. We don't know what character set the 7.0.2 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 3:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our QA2 environment) to send messages to the AIA AQ table in our QA2 environment. The AIA database uses UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA2 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.
Scenario 4:
We pointed our 6.3.1 OSM/Weblogic 9.2.1/Custom AQ Solution (which is part of our DEVINT1 environment) to send messages to the AIA AQ table in our QA1 enviornment. The AIA database uses ALT32UTF8 character set. We don't know what character set the 6.3.1 OSM/Weblogic/AQ uses. When we sent messages to the AIA QA1 AQ table we saw that everything under TEXT_LEN 4000 went to TEXT_VC. Over 4000 went to TEXT_LOB. This is fine for us.

Jms Adapter Consume and produce

Hai guys,
i don't know anything in soa. i have got a usecase which is to
1) Read a .csv file
2) Send it to a bpel (in bpel do nothing to payload). Again i have to send the payload to jms adapter( which i dnt knw how )
3) From the same jms adapter passing the payload to mediator
4) Pass the input to another jms( jms2 ). from jms2 pass the payload to another bpel
5) from bpel to db adapter
am using
Oracle jDevloper 11.1.13
Weblogic server is a 10.3.6
my problem is how to create the same jms in two ways like consuming and producing
Thanks in advance
Edited by: Beckyard on Sep 26, 2012 9:49 PM

Hi,
Why do you need 2 JMS queues? Can't you consider following pattern?
Read .csv --> BPEL --> JMS Q
JMS Q --> Mediator --> BPEL (only if some payload processing required) --> Db Adapter
Assuming the above pattern, you'll have to develop 2 processes (in your pattern 3 processes).
- One that will enqueue the data in JMS in which the JMS Adapter will be placed in the External references and will be invoked with Produce operation.
- Another process in which Mediator will consume the message using Consume operation from JMS and pass it to BPEL for inserting into database. In this case, JMS Adapter will be placed in Exposed Service swim-lane.
Let us know how you proceed.
Regards,
Neeraj Sehgal

JMS Adapter Tuning in Oracle 10G SOA suite - Fixing the Errors

Hi All,
We are getting an error in Production environment while a BPEL process producing (enqueue) a message to a JMS queue by using JMS adapter. (partener link)
The error is as follows.
Adapter Framework unable to create outbound JCA connection.
file:/sw/appnew/product/SOA/10.1.3/bpel/domains/default/tmp/.bpel_CurrenListJMSProducer_1.0_4ec528ec93a8a6ff0278fab9701dcc71.tmp/CurrenListJMSProducerV1.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]
Please note that we are not getting this error every time, few BPEL instances are getting this error, around 3 out of 10 instances.
We are using Orcacle 10G SOA suite.
The BPEL process will take the messages from Oracle Apps adapter and send to the JMS queue, where we are getting error.
I can see in the BPEL.xml the "retryInterval" property set to '60' for both partner links (Apps adapter and JMS adapter).
But not set any other values. So,these values may be default.
We need to fix this issue soon.
I am requesting you all the Experts and Gurus, please let me know what can be done to fix this issue.
Thanks a lot in advance,
John.

Hi All,.
Is there any work around for the above issue?
I tried all the below JMS tunings, but not 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 in order to analyse the issue.
Thanks,
John

JMS Adapter timeout property

How do I set timeout property for JMS adapter in BPEL in SOA Suite 10g ?
Scenario :
In one of the business scenarios, a JMS message in enqueued to WebLogic JMS queue from BPEL process.
There is a asyncronus invoke activity to the JMS adapter partner link.
This invoke activity to the JMS adapter took 15 mins in one of the invocations and hence giving timeout to the bpel client.
Query :
Is there any way I could set the timeout for this invocation, either at partner link level or a JMS adapter connection factory level.

Hi,
This is supposed to solve ERRJMS_PROVIDER_ERR error for JMS adapter.
Please refer metalink NOTE:393468.1.
I am not sure if it works for 10.1.2.0.2 version but probably it works on 10.1..3.X version.
Regards,
Ved

AQ queueing using JMS adapter

hi,
I am trying to enqueue the message to Oracle database Queue(i.e. AQADM.QUEUE_MESSAGE) by using JMS Provider Oracle Enterprise Messaging Service (OEMS) using the potion Oracle Advance Queuing .I am Reading the message from xml file using File adapter to enqueue it to database queue. I have configured the JMS Configuration at WebLogic console.
I have created the queue in database by using following Script
CREATE USER aqadm IDENTIFIED BY aqadm;
GRANT my_aq_adm_role TO aqadm;
/* create AQ queue user: */
CREATE USER aquser IDENTIFIED BY aquser;
GRANT my_aq_user_role TO aquser;
CONNECT aqadm/aqadm;
/* create a message type: */
CREATE OR REPLACE
TYPE AQADM.QUEUE_MESSAGE_TYPE AS OBJECT
title VARCHAR2(30),
text VARCHAR2(500)
GRANT EXECUTE ON AQADM.QUEUE_MESSAGE_TYPE TO my_aq_user_role;
GRANT UNLIMITED TABLESPACE TO aqadm;
begin
DBMS_AQADM.CREATE_QUEUE_TABLE(
queue_table => 'aqadm.queue_message_table',
queue_payload_type => 'aqadm.queue_message_type');
END;
begin
DBMS_AQADM.CREATE_QUEUE(
queue_name => 'aqadm.message_queue',
queue_table => 'aqadm.queue_message_table');
END;
/* individual queues are started using the start_queue procedures */
begin
DBMS_AQADM.START_QUEUE(
queue_name => 'aqadm.message_queue');
END;
I am using the following XSD for input message :-
<?xml version= '1.0' encoding= 'UTF-8' ?>
<schema targetNamespace="http://xmlns.oracle.com/xdb/AQADM" xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:AQADM="http://xmlns.oracle.com/xdb/AQADM" elementFormDefault="unqualified" attributeFormDefault="qualified">
<complexType name="QUEUE_MESSAGE_TYPE">
<sequence>
<element name="TITLE" nillable="true" minOccurs="0">
<simpleType>
<restriction base="string">
<maxLength value="30"/>
</restriction>
</simpleType>
</element>
<element name="TEXT" nillable="true" minOccurs="0">
<simpleType>
<restriction base="string">
<maxLength value="500"/>
</restriction>
</simpleType>
</element>
</sequence>
</complexType>
<element name="QUEUE_MESSAGE_TYPE" type="AQADM:QUEUE_MESSAGE_TYPE"/>
</schema>
During AQ queuing by using JMS adapter. i am geting following error message:-
JMS-108: Messages of type TextMessage not allowed with Destinations containing payload of type AQADM.QUEUE_MESSAGE_TYPE.
Please help me

hi,
I am trying to enqueue the message to Oracle database Queue(i.e. AQADM.QUEUE_MESSAGE) by using JMS Provider Oracle Enterprise Messaging Service (OEMS) using the potion Oracle Advance Queuing .I am Reading the message from xml file using File adapter to enqueue it to database queue. I have configured the JMS Configuration at WebLogic console.
I have created the queue in database by using following Script
CREATE USER aqadm IDENTIFIED BY aqadm;
GRANT my_aq_adm_role TO aqadm;
/* create AQ queue user: */
CREATE USER aquser IDENTIFIED BY aquser;
GRANT my_aq_user_role TO aquser;
CONNECT aqadm/aqadm;
/* create a message type: */
CREATE OR REPLACE
TYPE AQADM.QUEUE_MESSAGE_TYPE AS OBJECT
title VARCHAR2(30),
text VARCHAR2(500)
GRANT EXECUTE ON AQADM.QUEUE_MESSAGE_TYPE TO my_aq_user_role;
GRANT UNLIMITED TABLESPACE TO aqadm;
begin
DBMS_AQADM.CREATE_QUEUE_TABLE(
queue_table => 'aqadm.queue_message_table',
queue_payload_type => 'aqadm.queue_message_type');
END;
begin
DBMS_AQADM.CREATE_QUEUE(
queue_name => 'aqadm.message_queue',
queue_table => 'aqadm.queue_message_table');
END;
/* individual queues are started using the start_queue procedures */
begin
DBMS_AQADM.START_QUEUE(
queue_name => 'aqadm.message_queue');
END;
I am using the following XSD for input message :-
<?xml version= '1.0' encoding= 'UTF-8' ?>
<schema targetNamespace="http://xmlns.oracle.com/xdb/AQADM" xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:AQADM="http://xmlns.oracle.com/xdb/AQADM" elementFormDefault="unqualified" attributeFormDefault="qualified">
<complexType name="QUEUE_MESSAGE_TYPE">
<sequence>
<element name="TITLE" nillable="true" minOccurs="0">
<simpleType>
<restriction base="string">
<maxLength value="30"/>
</restriction>
</simpleType>
</element>
<element name="TEXT" nillable="true" minOccurs="0">
<simpleType>
<restriction base="string">
<maxLength value="500"/>
</restriction>
</simpleType>
</element>
</sequence>
</complexType>
<element name="QUEUE_MESSAGE_TYPE" type="AQADM:QUEUE_MESSAGE_TYPE"/>
</schema>
During AQ queuing by using JMS adapter. i am geting following error message:-
JMS-108: Messages of type TextMessage not allowed with Destinations containing payload of type AQADM.QUEUE_MESSAGE_TYPE.
Please help me

JMS adapter appears on wrong side in the BPEL

JDeveloper 11g (11.1.1.5.0)
I drag & drop a JMS adapter(for enqueue) on the right swim lane of composite, and wired a BPEL with it.
However when I open the BPEL, the JMS adapter appears on the left side of the Partner links, not
the right side. What's wrong? and How to fix it? Thanks.

Hi,
It has to do with the operation type that you select when you're configuring the JMS adapter...
Cheers,
Vlad
Give points - it is good etiquette to reward an answerer points (5 - helpful; 10 - correct) for their post if they answer your question
https://forums.oracle.com/forums/ann.jspa?annID=330

JMS-Adapter with persistent Queues (DB): ORABPEL-12166

Hi,
does anybody know what the error:
file:/C:/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/Provisioning/tmp/.bpel_SenderProvisioning_1.0_bb735430814144c8f5f279c73842c3d4.tmp/JMS_Provisiong_A.wsdl [ Produce_Message_ptt::Produce_Message(Request) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
; nested exception is:
ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Die Nachricht konnte aufgrund von folgender Fehlerbedingung nicht in die Queue gestellt werden:.
Weitere Informationen hierzu finden Sie in der Log-Datei.
means?
Where can i find the logs?

This is most likely caused by a nonexistent or misconfigured queue.
For a JMS adapter, make sure your AQ queue/topic is set up as JMSType. Make sure you've spelled everything correctly.
To find the logs for ESB go to:
$ORACLE_HOME/j2ee/oc4j_soa/log/oc4j see log.xml
For BPEL go to
$ORACLE_HOME/bpel/domains/default/logs see domain.log
You may also find errors in the OPMN logs:
$ORACLE_HOME/opmn/logs
see default_group~oc4j_soa~default_group~1.log
You will have to turn up log levels to "FINE" or "FINER" for ESB or DEBUG for BPEL to get anything close to a meaningful message. For my most recent error on ESB the "FINER" setting yielded the following message for this error:
</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[ORABPEL-12166
ERRJMS_ENQUEUE_ERR.
Could not enqueue message due to the following error condition:.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:237)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:143)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:197)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:156)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:485)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:736)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.executeOperation(WSIFInvoker.java:497)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:430)
at oracle.tip.esb.server.common.wsif.WSIFInvoker.nextService(WSIFInvoker.java:447)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.nextService(OutboundAdapterService.java:184)
at oracle.tip.esb.server.service.impl.outadapter.OutboundAdapterService.processBusinessEvent(OutboundAdapterService.java:112)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatchNonRoutingService(InitialEventDispatcher.java:106)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:85)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:105)
at oracle.tip.esb.server.service.EsbRouterSubscription.onBusinessEvent(EsbRouterSubscription.java:273)
at oracle.tip.esb.server.dispatch.EventDispatcher.executeSubscription(EventDispatcher.java:138)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscription(InitialEventDispatcher.java:212)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.processSubscriptions(InitialEventDispatcher.java:197)
at oracle.tip.esb.server.dispatch.EventDispatcher.dispatchRoutingService(EventDispatcher.java:94)
at oracle.tip.esb.server.dispatch.InitialEventDispatcher.dispatch(InitialEventDispatcher.java:82)
at oracle.tip.esb.server.dispatch.BusinessEvent.raise(BusinessEvent.java:1416)
at oracle.tip.esb.utils.EventUtils.raiseBusinessEvent(EventUtils.java:69)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.processMessage(ESBListenerImpl.java:369)
at oracle.tip.esb.server.service.impl.inadapter.ESBListenerImpl.onMessage(ESBListenerImpl.java:295)
at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:293)
at oracle.tip.adapter.jms.inbound.JmsConsumer.doSend(JmsConsumer.java:571)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:507)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:353)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:274)
at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.UnsupportedOperationException: publish is called without a valid Topic
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1252)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:215)
... 34 more
Hope that helps. See the SOA admin guide for help with setting log levels:
Here's where you can find all App Server books for SOA Suite:
http://download-west.oracle.com/docs/cd/B31017_01/nav/docindex.htm
Peace,
G.

Having multiple service operations in a single JMS adapter best practice

Hi All,
I am using JDeveloper and SOA Suite 11.1.1.6. I need to read from multiple JMS Topics and transform and enhance the messages through the Mediator and then persist into Database.
My question is
What is the best practice to consume from multiple topics, Should I configure separate JMS adapter for each of the Topic destination
OR
have a single JMS adapter with multiple operations by manually changing the JMS adapter wsdl and jca file?
I find cannot have
Please suggest.
Thanks in advance
Edited by: user5108636 on 15/05/2013 11:36

Hi Vijay,
did you actually test this? When I finish creating a DBAdapter, there is a operation present. Then when I click edit again on the DBAdapter, and I create another select, when I finish only the first operation is gone, and I can only see the one I've created via the last edit.
I dont understand your reply. Can I have two operations, each one with select underneath, in the same adapter?
Edited by: user13604541 on Jan 30, 2012 11:19 AM

Calling Foreign JMS in SOA Suite 11g JMS Adapter

Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
Robert

Please refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman

Invoking Jms Adapter from BPEL with enque stoped

Hi guys, I have an issue.
In my BPEL flowI have an invoke activity which has a jms adapter as a partner link.
The thing is that if you stop the enque in the DB, your flow in BPEL continues like nothing happened. It just passes the payload to the jms adapter. From it's point of view is asynchronous , but I want to make sure that the payload is in the queue before I continue the flow.
Any ideas?

Hi Oracler,
I don't understand what you mean by XML schema inline? Where do you define that in a JMS adapter ? Can you be more specfic when you say Try including both the elements(TEXT_LOB , TEXT_VC ) in the schema? I don't have those elements in my schema at all. I have tried the opaque option I still get the same Translator NULL error.
Please anyone help....

Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
Thnaks

Hi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban.

JMS Adapter enqueue - batch commits

Similar Messages

Maybe you are looking for