Error publishing large payload in AQ JMS Adapter

Hi,
We are usign AQ JMS Adapter and we are publishing payload in AQ JMS Topic thorugh BPEL process.
Issue is, i'm not able to publish large payload ( xml file of size 4KB) to AQ JMS Topic through asynchronous BPEL process.
When i post the xml in the BPEL Control, i'm getting the follwoing message:
"Cannot find the specified instance". I have tried 3-4 times but getting same message all the time
However, i'm able to publish xml to JMS Topic with synchronous BPEL process.
Please let me know if there is a way to overcome this issue.
Thanks in advance

If the StreamPayload property does not exist, then the default value false is assumed.
<activation-spec className="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec">
<property name="QueueName" value="RAW_IN_QUEUE"/>
<property name="DatabaseSchema" value="SCOTT"/>
<property name="StreamPayload" value="true"/>
</activation-spec>
you can add <property name="StreamPayload" value="true"/>
to the .jca file but rememeber This property is applicable when processing Raw messages, XMLType messages, and ADT type messages for which a payload is specified though an ADT attribute.

Similar Messages

Java.lang.OutOfMemoryError: allocLargeObjectOrArray error for large payload

Our is an outbound flow where one FTP adapter picks the files and it calls a requester service, requester service calls the EBS and EBS calls the provider service, and finally file is getting written using the B2B.
Since last 4/5 days we are getting java.lang.OutOfMemoryError: allocLargeObjectOrArray.
We are getting this error when large payloads are being used for doing testing.
As per our understanding, when you have a tree of composite invocations (so A invokes B invokes C invokes D via flowN 100 times), none of the memory is released until they all complete.
1. Could you please let us know exactly when memory is released?
2. How to tune/optimize this?
Our flow is like:
SyncDisbursePaymentGetFtpAdapter --> CreateDisbursedPaymentEbizReqABCSImp l--> SyncDisbursePaymentRBTTEBS --> SyncDisbursedPaymentJPMC_CHKProvABCSImpl--> AIAB2BInterface --> Oracle B2B
<Dec 12, 2012 8:17:06 PM EST> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: javax.management.remote.rmi.RMIConnecti\
onImpl.invoke(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 667664.
javax.management.RuntimeErrorException: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 667664
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:858)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:869)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:838)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
Truncated. see log file for complete stacktrace
Caused By: java.lang.OutOfMemoryError: allocLargeObjectOrArray: [B, size 667664
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847)
at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1756)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1169)
Truncated. see log file for complete stacktrace
Do any one have any idea how to rectify this error as whole UAT environment has become down because of this issue.

Please find the required info:
1. Operating System--> LINUX
2. JVM (Sun or JRockit)-->JRockit
3. Domain info (production mode enabled?, log levels, number of servers in cluster, number of servers in a machine)-->
a) production mode enabled-->>Production mode is not enabled, we are going to enable it.
b)Log levels---There are many logs b2b, soa, bpel, integration, which log level do I need to do finest(32).
c) number of servers in cluster-->2
d) number of servers in a machine-->1
3. Payload info (size, xml/non-xml?,)
a) size-->more than 1 MB, and upto 25 MB
b)xml/non-xm--> xml
we are trying to do the changes as suggested by you and will update accordingly.

How to hanlde breaked large messages in sender JMS adapter

Hi,
I have been asked like 'how can we handle breaked large messages in sender JMS adapter?'and lets say I am getting some messages as it is and some are breaked into small segements for the mesaages that are large....
do we need to use module,if so is there any standard module that we can use to hanlde this type of scenarios?
thank you in advance.
babu

http://biemond.blogspot.com/2009/10/jms-request-reply-interaction-pattern.html
if you check the blog of edwin, see his comments at the bottom
there he gives a suggestion how to add the selector properties to filter on
and this one is maybe helpfull
http://blogs.oracle.com/adapters/2010/05/configuring_request-reply_in_jmsadapter.html

Sending Large size files through JMS adapter.

We want to receive files larger than 5MB via the JMS receiver adapter. The receiver side has WebSphere MQSeries version 5.3.12.
The channel we are using is SYSTEM.AUTO.SVRCONN.
I can see a MQJMS2007 error in RWB for the JMS adapter.
Does the XI JMS adapter have features to handle large files > 5MB?

Neogy
As far as my knowledge goes it supports MQSERVER. But I am not sure of AMQCLCHL.TAB. Also AMQCLCHL.TAB have some disadvantages when compared with MQSERVER.
http://www3.sympatico.ca/n.rieck/docs/mqseries_client_on_openvms.html
Also the primary inefficiency of this AMQCLCHL.TAB format is its size. When this file is managed by the queue manager (which is your only choice without using this perl module), it grows and never shrinks. When channels are deleted, the linked list pointers are modified so that the deleted entry is merely skipped, but it is not removed from the file.
http://aspn.activestate.com/ASPN/CodeDoc/MQSeries/MQSeries/Config/ChannelTable.html#Secrets%20of%20AMQCLCHL.TAB
When new entries are added, a deleted entry will be searched for and reused if found. If not, a new entry will be added to the end of the file. The size problem occurs if you ever create a very large channel table file, since that will effectively extend the file size permanently.
use of MQSERVER differs from AMQCLCHL.TAB only with respect to the exits. To learn more on this:
http://eai.ittoolbox.com/groups/technical-functional/mqseries-l/162315#
Regards,
---Satish

Payload level filter JMS Adapter with Queue - not filtering

Hi ,
I have created AQ Queue in my Database, Using JMS Adapter i am able consume and produce the messages. I want a filter condition, which is not happening.
The scenario is i have a field ImportInd in my XSD and i need to pick the message with ImportInd = 1, otherwise the message should lie on the queue.
Please help me in this,
Thanks,
Padmini

Trying to give you the counterparts I have in my working example.
In my case the queue is on a separate machine, and the BPEL is deployed on a separate machine. Cross-domain security config needs to be done for these machines to be able to talk.
In weblogic console: where BPEL is running.
under deployment jmsadapter -> Outbound Connections -> jndi name is jms/PRISMQueue -> ConnectionFactoryLocation Property is jms/SoaCF
where queue is configured.
Under JMS Module Connection Factory Name is SoaConnectionFactory which JNDI name is jms/SoaCF
Under JMS Module Queue Name SOAPostActivityStatusQueue which JNDI name is jms.SOAPostActivityStatusQueue
Services>Messaging>JMSModules>MyModule>SOAPostActivityStatusQueue>
JNDI name - jms.SOAPostActivityStatusQueue
Adapter in BPEL/Composite-
Destination - jms.SOAPostActivityStatusQueue
JNDI - jms/PRISMQueue
JCA:
<adapter-config name="PostResponseFromPCService" adapter="JMS Adapter" wsdlLocation="PostResponseFromPCService.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="jms/PRISMQueue" UIJmsProvider="WLSJMS" UIConnectionName="tacoma"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<property name="PayloadType" value="TextMessage"/>
<property name="UseMessageListener" value="false"/>
<property name="DestinationName" value="jms.SOAPostActivityStatusQueue"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
HTH.
Thanks!

Payload Streaming (for handling large payload) in Oracle JCA Adapter for AQ

Hi All-
Oracle Documentation indicates that it supports Payload Streaming in Oracle JCA Adapter for AQ. Link http://download.oracle.com/docs/cd/E14571_01/integration.1111/e10231/adptr_aq.htm#CBAIAABF
However when I tried configuring an AQ Adapter in Jdeveloper, I was not able to see the check box for enabling Payload Streaming.
Do we have to manually update the .jca file to add the property "EnableStreaming" in the AQ Adapter Activation Spec? Is it supported and is it going to work?
What is the Message Size limit that the AQ Adapter can handle?
Please let me know.
Thanks,
Dibya

If the StreamPayload property does not exist, then the default value false is assumed.
<activation-spec className="oracle.tip.adapter.aq.inbound.AQDequeueActivationSpec">
<property name="QueueName" value="RAW_IN_QUEUE"/>
<property name="DatabaseSchema" value="SCOTT"/>
<property name="StreamPayload" value="true"/>
</activation-spec>
you can add <property name="StreamPayload" value="true"/>
to the .jca file but rememeber This property is applicable when processing Raw messages, XMLType messages, and ADT type messages for which a payload is specified though an ADT attribute.

Error status in JMS adapter - sync / async brigde. Message processed ok

Hi guys
I'm having som trouble with my scenarion. I'm sending sync message from SAP backend to XI using proxy. From XI onwards to JMS adapter async (and the other way around for the response message).
This works OK. However i have a status error in my RWB on the JMS adapter. There is er red exclamation mark and a text saying:
Correlation ID 'XXX' of JMS request message 'ID:yyy' saved that correponds to XI message 'XXX'
How do I get my adapters in status green?
Kind regards
Martin

Hi Kai
Oh - OK
Settings are:
Receiver JMS channel:
Set JMSCorrelation to: XI Message ID (MessageID)
Store JMS CorrelationId of request: Mark
Sender JMS channel:
Set XI Message ID (MessageID) to: GUID (Recommended Value)
Set XI Conversation ID (ConversationID) To: Stored JMS CorrelationId of Request.
Kind regards
Martin

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....

Problem with calling AQ JMS Adapter with Asynchronous BPEL Process

I have a AQ JMS Adapter and i'm invoking the adapter in my BPEL process.
I'm passing an xml as payload to AQ JMS adapter. When i post the xml in the BPEL Control, i'm getting the follwoing message:
"Cannot find the specified instance". I have tried 3-4 times but getting same message all the time.
However, i'm able to publish xml to JMS Topic with synchronous BPEL process.
I want to use asynchronous BPLE process.
Please let me know if there is a way to overcome this issue.
Thanks in advance.
Thanx in Advance.

I am experiencing the exact same issue while configuring for Tibco EMS!!!
I have also checked the oc4j-xa.xml file etc and I am also unable to find any guidance on the steps required from XML config files through to adapter wizard entries!

Outbound JMS adapter with fx example

When I wire outbound jms adapter as a listener for the spreaderOut
<wlevs:stream id="spreaderOut" manageable="true">
<wlevs:listener ref="outboundJmsAdapter" />
</wlevs:stream>
I get a error in instantiation of the outbound jms adapter using the factory. Although a create instance method exists it gives me an error as follows:
     at java.lang.Thread.run(Thread.java:595)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'outboundJmsAdapter' defined in OSGi res[META-INF/spring/com.bea.wlrt.example.fx-context.xml|id=127|symName=fx]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: No matching factory method found: factory method 'createInstance'
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:448)
The adapter factory configuration is as defined in the adapter spring configuration.
<bean id="outboundJmsAdapter" class="com.bea.wlevs.example.jms.outbound.OutboundMessageAdapter" factory-method="createInstance">
          <constructor-arg value="sample.outbound" />
          <constructor-arg ref="wlsjmsQueueConnectionFactory"/>
          <constructor-arg value="JMSQueueConnectionFactory01" />
          <property name="destinationName">
               <value>JMSResponseQueue01</value>
          </property>
          <property name="messageType">
               <value>text</value>
          </property>
</bean>
How do I resolve this?

When I wire outbound jms adapter as a listener for the spreaderOut
<wlevs:stream id="spreaderOut" manageable="true">
<wlevs:listener ref="outboundJmsAdapter" />
</wlevs:stream>
I get a error in instantiation of the outbound jms adapter using the factory. Although a create instance method exists it gives me an error as follows:
     at java.lang.Thread.run(Thread.java:595)
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'outboundJmsAdapter' defined in OSGi res[META-INF/spring/com.bea.wlrt.example.fx-context.xml|id=127|symName=fx]: Instantiation of bean failed; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: No matching factory method found: factory method 'createInstance'
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:448)
The adapter factory configuration is as defined in the adapter spring configuration.
<bean id="outboundJmsAdapter" class="com.bea.wlevs.example.jms.outbound.OutboundMessageAdapter" factory-method="createInstance">
          <constructor-arg value="sample.outbound" />
          <constructor-arg ref="wlsjmsQueueConnectionFactory"/>
          <constructor-arg value="JMSQueueConnectionFactory01" />
          <property name="destinationName">
               <value>JMSResponseQueue01</value>
          </property>
          <property name="messageType">
               <value>text</value>
          </property>
</bean>
How do I resolve this?

JMS Adapter Error

Hi Experts,
               We are havingone problem in Sender JMS Adapter. From Sender (SeeBeyond) xml files are getting posted into Remote Queue in MQ, then it has been sent to Local Queue of MQ, and then finally from Local MQ Queue PI is picking up the data and sending it to SNC system.
               The problem lies in PI itself. While coming into PI, the value in the incoming payload where special characters(say, swedish character) are coming, are coming into PI as a garbage value. Whereas, in Sender (SeeBeyond), MQ and in PI Character set is ISO 8859_1. We have stopped the Sender JMS channel in PI, and checked the payload in MQ and in SeeBeyond, in both of the cases it's fine, only when coming into PI, data are getting corrupted.
                For this we have done some investigation like below,
1) We had changed the CCSID from 00819 (ISO 8859_1) to 1208 (UTF-8), 1200 (UTF 16), but no luck.
2) We had added th below mentioned modules into Sender JMS in Processing Sequence with the existing modules,
AF_Modules/MessageTransformBean                                              Local Enterprise Bean               ContentType
(ii) AF_Modules/TextCodepageConversionBean                                   Local Enterprise Bean               codepageConversion
But yet we are getting the same error in encoding in the payload while coming into PI.
Can anybody help me out with it, or probably let me know if I am missing something in my investigation.
//BR
Soumya

Hi Stefan,
             Sorry for the late reply. We were testing in different cases in PI, and here what I have found. In Sender JMS adapter we had put the module "AF_Modules/MessageTransformBean" with Module Key "Transform". And the configuration of this Module Key is as follows:-
Transform     Transform.ContentType      text/plain;charset="UTF-8"
And we changed the CCSID to 1208 (UTF-8). Now when we saw the payload in SXI_MONITOR in PI, we have found that the special character is being distorted whereas in View Sourse the payload is fine including special character also. That means there might be some display problem in SXI_MONITOR.
             Now, the Sender sends the data in XML iin ISO 8859-1nto MQ, MQ send the same as a string in PI, from PI it's going to SCM system (R/3, Supply Chain Management), where we could see ABAP.APPLICATION Error. We tested the interface in SCM system by running SPROXY and found that it's not able to recognise ISO 8859-1, since it's a Non-Unicode System, it will only understan UTF-8 and hence the error. Now manually we have changed the XML Header into UTF-8 and tested at SCM side, and this goes fine.
           So, we could see the changing of XML Header from ISO 8859-1 to UTF-8 would be running fine at receiver end (SCM). Since SCM is a Non-Unicode System, the XML header cannot be changed to UTF-8, is there any possibility in PI that we can change the XML Header from ISO 8859-1 to UTF-8.
           For your information, we are using Sender JMS adapter to receive the File from Sender and we are using Receiver XI adapter to post the file into SCM system.
What's your suggestion Stefan, how can we change the XML Header from ISO 8859-1 to UTF-8 in PI?
Many Thanks
Soumya

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.

Error - JMS Adapter in BPEL ..

We are trying to send the message to remote weblogic JMS Queue using JMS Adapter in BPEL, during that time we are getting the below error in our BPEL console, can anyone help us to solve this error?
Invoke_1 (faulted)
[2007/10/22 09:29:58] Faulted while invoking operation "Produce_Message" on provider "JMS_Demo".less
-<messages>
-<input>
-<Invoke_1_Produce_Message_InputVariable>
-<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="opaque">
<opaqueElement xmlns="http://xmlns.oracle.com/pcbpel/adapter/opaque/">
Hello WIPRO
</opaqueElement>
</part>
</Invoke_1_Produce_Message_InputVariable>
</input>
-<fault>
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>
null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_2/bpel/domains/default/tmp/.bpel_BPELProcess1_1.5_cb5d57e810459b549d857161eefb49f0.tmp/JMS_Demo.wsdl [ Produce_Message_ptt::Produce_Message(opaque) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
; nested exception is:
     ORABPEL-12167
ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
Please examine the log file to determine the problem.
</summary>
</part>
-<part name="detail">
<detail>
null
</detail>
</part>
</remoteFault>
</fault>
</messages>
[2007/10/22 09:29:58] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. More...
-<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
-<part name="code">
<code>
null
</code>
</part>
-<part name="summary">
<summary>
file:/C:/product/10.1.3.1/OracleAS_2/bpel/domains/default/tmp/.bpel_BPELProcess1_1.5_cb5d57e810459b549d857161eefb49f0.tmp/JMS_Demo.wsdl [ Produce_Message_ptt::Produce_Message(opaque) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
; nested exception is:
     ORABPEL-12167
ERRJMS_EMPTY_PAYLOAD.
Payload Record Element is unexpectedly empty [Caused by: Error in encoded stream, got 2].
Please examine the log file to determine the problem.
</summary>
</part>
-<part name="detail">
<detail>
null
</detail>
</part>
</remoteFault>

I got he same error but it's kind weird.
when I rebuild and deployed the jar,the error changes.
I have tested the remote jms queue and topic with java client. they are working fine.
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="summary"><summary>file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - WSIF JCA Execute of operation 'Produce_Message' failed due to: Adapter Framework unable to create outbound JCA connection.
file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor VIMConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file to determine the problem.
[Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
; nested exception is:
     ORABPEL-12511
Adapter Framework unable to create outbound JCA connection.
file:/home/bpel/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_Queue2Topic_v2007_12_10__37928_c62fd67a4741626244d92a80798b5d2c.tmp/OutTopicService.wsdl [ Produce_Message_ptt::Produce_Message(ExpenseRecord) ] - : The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12141
ERRJMS_CONN_FAC_NOT_FOUND.
Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor VIMConnectionFactory neither through JNDI nor instantiate it as a Java class [Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file to determine the problem.
[Caused by: Unable to resolve 'VIMConnectionFactory'. Resolved '']
Please examine the log file for any reasons. Enable DEBUG logging in the BPEL Console.
</summary>
</part><part name="detail"><detail>null</detail>
</part></remoteFault>
Message was edited by:
user593125
Message was edited by:
user593125

Error with JMS adapter

We are using a JMS adapter with XML input files and we are getting the following error:
:#1.#00144F80C55600310000001A00001BC700DD9B18A4E85181#1288983973313#com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer##com.sap.engine.messaging.impl.core.queue.consumer.SendConsumer.handleRetriesOnException(MessagingException, QueueMessage, MessageController)#J2EE_GUEST#223963##<applicationserver_hostname>_<SID>_623765##8bfba530dea111dfbf9b00144f80c556#MS Queue Worker [JMS_http://sap.com/xi/XI/SystemSend]##0#0#Error##Java###Transmitting the message to endpoint using connection failed, due to: .#3#JMS_http://sap.com/xi/XI/System#com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message over HTTP. Reason: java.io.IOException: Error writing to server#http://<hostname>:50000/sap/xi/engine?type=entry#
One that is interesting is that these errors are occurring on application servers only. Could it be that the Integration Server URL is not fully qualified. In the SLD it's just <hostname>, not <hostname>.test.com (as an example).
Any help is greatly appreciated.

Dear George,
Concerning the issue, in the Integration Engine please try increasing the value of the parameter :
   - icm/HTTP/max_request_size_KB
from the default size of 100MB to e.g., 2GB.
Kindly go through the following link :
- http://help.sap.com/saphelp_nwpi71/helpdata/en/58/108b02102344069e4a31758bc2c810/frameset.htm
for details.
Additionally, it is recommended to setup a large message queue,
i.e.,
add an entry and appropriate value (e.g., 20480 KB) for the TUNING parameter : 'EO_MSG_SIZE_LIMIT'
using
TCODE
   sxmb_adm
    Integration Engine Configuration
      Select Edit mode and Add the TUNING parameter
I Hope this helps.
Best Regards
Nishwanth

Error in reciever JMS adapter (SENARIO FILE - XI- JMS )

HI everyone,
My previous error is solved (Error in getting initialcontext). I have deployed the required jar files on server.
Thanks to you'll.
Now I am getting the following error in JMS adapter monitoring RECIEVER CHANNEL . NO DETAIL INFORMTION SET.
i AM USING IBM websphere MQ series for recieving JMS messages from XI.
I have made Queue manager,
Queue,
reciever channel.
and have also provided the following details in my communication channel in XI
QueueConnection FactoryJavaClass : com.ibm.mq.jms.MQQueueConnectionFactory
QueueJavaClass : com.ibm.mq.jms.MQQueue
Ip address or server name : <my ip address> since i have installed IBM JMS server on my system.
server port :1415
QueueManagerName :QM_apple
channel name : reciever_channel
jms Queue: Q1
character set id (ccsid): This I have not given , Idont know what to give here
Transport protocol :tcp/ip
Please guide me to go further , I am stucked at the error , No reciever details set. What should i do?

Hi Deepak ,
Please refer this forum post .. if this helps.
Reg:Receiver Mail Adapter
Regards,
srinivas

Error publishing large payload in AQ JMS Adapter

Similar Messages

Maybe you are looking for