SOA JMS Adapter JCA Properites Issues

Hi,
we are using JMS adapter in a BPEL process for polling on a JMS queue which has Destinationname= "Queue1".
After deploying the composite we are changing JCA property Destinationname="Queue2" through SOA EM console.
It is working fine as expected,but when we restart the SOA server,then agian the Destinationname is pointing to "Queue1".
This is not expected functionality. Seems like a bug. . We have to change the settings every time the server is bounced.
Any Suggestions on this would be appreciated.
Regards,
Sudhakar.M

Hi Arun,
We have implemented minimumDelayBetweenMessages property in SOA Dev standalone environment.it is working AS excepted.
But when test this in Cluster environment it is not working as expected. then using oracle JCA documents we i found some other properties need to set
<property name="adapter.jms.receive.threads">1</property>
<property name="clusterGroupId">myBpelCluster</property>
<property name="clusterAcrossSubnet">false</property>
can you explain what is each property do,
what is the clusterGroupId value ? can we put any value or name of the SOA cluster.
what is the value we need to set for clusterAcrossSubnet?? how to decide .
Any help would be appreciate.
Regards,
Sudhakar.M

Similar Messages

Restrict SOA JMS Adapter dequeue frequency

Hi,
we are reading messages from third party JMS queues in the BPEL Process using JMS Adapter in the Composite. Sometimes because of more load on the JMS queue ie around 40 records per second we are facing load issues. BPEL is able to read close to 40 records per second from the queue and calls the Oracle Agile 9.3.2 Web services but the Agile web services are not able to handle such heavy load.
We want to throttle the JMS Adapter and limit the number of messages we dequeue.
What properties in JMS Adapter need to configured to control the dequeue rate.
Here is .jca file of the JMS adpater
<adapter-config name="ReadFAQueue" adapter="Jms Adapter" wsdlLocation="ReadFAQueue.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/C3FAQueueCF" UIJmsProvider="THIRDPARTY" adapterRef=""/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<property name="DestinationName" value="zzqmsbw1.queue.bw.fa"/>
<property name="UseMessageListener" value="false"/>
<property name="PayloadType" value="TextMessage"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
Regards,
Sudhakar.M

Hi All,
Finally I got Answer from SR.
Here is the link which explain frequency set..http://sudhakarsoa.blogspot.com/2011/03/how-to-set-delay-between-jmsaq-quque.html

OCEP JMS Adapter implement InboundMessageConverter issue

Hello,
I'm new to OCEP. I have a JMS adapter receiving Weblogic JMS message. JMS Message is a TextMessage, so the default MapMessage can't convert it. I need to write my own converter which implement InboundMessageConvert. Eclipse compiles just fine, but when deploying into a runtime OCEP environment, I get an error saying that my custom converter class does not implement InboundMessageConverter which I did. Did anyone encounter this issue and how to get around it?
I also tried the sample code provided in Developer Guide and it doesn't work. My code bellow is a sample to by pass the deployment issue..
package com.converter;
import com.bea.wlevs.adapters.jms.api.InboundMessageConverter;
import com.bea.wlevs.adapters.jms.api.MessageConverterException;
import javax.jms.JMSException;
import javax.jms.Message;
import java.util.List;
public class MyMessageConverter
implements InboundMessageConverter
public MyMessageConverter(){
super();
public List convert(Message message) throws MessageConverterException, JMSException
return null;
--- error message when deploy to runtime environment ---
<Mar 22, 2010 10:30:57 AM PDT> <Error> <Deployment> <BEA-2045010> <The application context "FilteringEvent" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.IllegalArgumentException: converter-bean com.converter.MyMessageConverter does not implement InboundMessageConverter
at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

Hi,
I have included the following two lines into the Manifest file, but this action has not fixed the problem:
com.bea.wlevs.adapters.jms;version="11.1.1.4_0",
com.bea.wlevs.adapters.jms.api;version="11.1.1.4_0"
My EPN file is as shown:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:osgi="http://www.springframework.org/schema/osgi"
xmlns:wlevs="http://www.bea.com/ns/wlevs/spring"
xmlns:jdbc="http://www.oracle.com/ns/ocep/jdbc"
xmlns:spatial="http://www.oracle.com/ns/ocep/spatial"
xmlns:application="http://www.bea.com/ns/wlevs/config/application"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://www.bea.com/ns/wlevs/spring
http://www.bea.com/ns/wlevs/spring/spring-wlevs-v11_1_1_3.xsd
http://www.oracle.com/ns/ocep/jdbc
http://www.oracle.com/ns/ocep/jdbc/ocep-jdbc.xsd
http://www.oracle.com/ns/ocep/spatial
http://www.oracle.com/ns/ocep/spatial/ocep-spatial.xsd
http://www.bea.com/ns/wlevs/config/application
http://www.bea.com/ns/wlevs/config/application/wlevs_application_config.xsd">
     <bean id="myConverter" class="com.bea.wlevs.adapter.example.jmsclient.JMSClient"/>
     <wlevs:adapter id="jmsInbound" provider="jms-inbound">
          <wlevs:instance-property name="converterBean" ref="myConverter"/>
     </wlevs:adapter>
     <application:jms-adapter>
<application:name>jmsInbound</application:name>
<application:jndi-provider-url>t3://localhost:9002</application:jndi-provider-url>
<application:destination-jndi-name>Queue1</application:destination-jndi-name>
<application:user>wlevs</application:user>
<application:password>123456</application:password>
<application:work-manager>JettyWorkManager</application:work-manager>
<application:concurrent-consumers>1</application:concurrent-consumers>
<application:session-transacted>false</application:session-transacted>
</application:jms-adapter>
<wlevs:event-type-repository>
The error showned by Eclipse is:
Multiple annotations found at this line:
     - cvc-complex-type.2.4.c: The matching wildcard is strict, but no declaration can be found for element 'application:jms-adapter'.
     - schema_reference.4: Failed to read schema document 'http://www.bea.com/ns/wlevs/config/application/
     wlevs_application_config.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the
     document is not <xsd:schema>.
Thanks!
Edited by: 899693 on 15-dic-2011 2:48

Receiver JMS Adapter Content Conversion issue

Scenario :
R/3 -->XI -->MQ(XML2Plain)
Hi
We are using Receiver JMS Adapter to send the Message from XI to MQ.
The XML has to be converted to plain file. And Content conversion is
being done.
With the new development, the message type defined consist of 8 fields
with fixed length. The XML message goes successfully from XI to MQ
without any content conversion. But once simple content conversion is
being done for Receiver JMS adapter, even though the message is
received but its empty (without any data records). The adapter
monitoring everything seems fine and it gives the status that message
converted to binary and the message is delivered to MQ. Though on
checking the messages there is no data records.
Below is my content conversion configuration done in Module tab. Kindly
revert back what can be the problem as have done exactly the same way
as described in Content Conversion How to Guide for receiver JMS.
localejbs/AF_Modules/MessageTransformBean Local Enterprise Bean XML2Plain
localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
localejbs/SAP XI JMS Adapter/SendBinarytoXIJMSService Local Enterprise Bean exit
XML2Plain Transform.Class com.sap.aii.messaging.adapter.Conversion
XML2Plain TransformContentType text/plain;charset=utf-8
XML2Plain xml.addHeaderLine 0
XML2Plain xml.addHeaderLine SimpleXML2Plain
XML2Plain xml.fieldFixedLengths 8,10,10,20,40,40,8,8
XML2Plain xml.fixedLengthTooShortHandling Cut
regards.
santosh.

Hi,
check localejbs/SAP XI JMS Adapter/ConvertMessageToBinary Local Enterprise Bean convert_XI2Bin
this is not CallJMSService.
And also check the receiver Structure, if it is falt structure its ok, else
see the below link if it has the complex structure , how to handle..
See the below links
/people/alessandro.guarneri/blog/2006/01/04/jms-sender-adapter-handling-too-short-lines
/people/william.li/blog/2006/11/13/how-to-use-saps-webas-j2ees-jms-queue-in-exchange-infrastructure
content conversion
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f02d12a7-0201-0010-5780-8bfc7d12f891
Regards
Chilla..

Throttling using JMS Adapter poller threads

Hi,
We are trying to realize the throttling using JMS Adapter poller threads mechanism
I came across this http://docs.oracle.com/cd/E14571_01/core.1111/e10108/adapters.htm (15.5 Oracle SOA JMS Adapter Tuning )
adapter.jms.receive.threads
Here is my configuration. I tried both the options listed below but none works for me.
option 1 - here property is of type string
<service name="JMSDelayMsgRead" ui:wsdlLocation="JMSDelayMsgRead.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/jms/JMSDelayMessage/JMSDelayMessage/JMSDelayMsgRead#wsdl.interface(Consume_Message_ptt)"/>
<binding.jca config="JMSDelayMsgRead_jms.jca">
<property name="adapter.jms.receive.threads" type="xs:string" many="false">4</property>
</binding.jca>
</service>
option 2 - Here property is of type integer
<service name="JMSDelayMsgRead" ui:wsdlLocation="JMSDelayMsgRead.wsdl">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/jms/JMSDelayMessage/JMSDelayMessage/JMSDelayMsgRead#wsdl.interface(Consume_Message_ptt)"/>
<binding.jca config="JMSDelayMsgRead_jms.jca">
<property name="adapter.jms.receive.threads" type="xs:integer" many="true" override="may">4</property>
</binding.jca>
</service>
I tried minimumDelayBetweenMessages parameter for throttling (which is based on time delay) and it works as expected but poller threads mechansim is more suitable for my situation.
Here is my environment details
I'm on SOA 11.1.1.4
JMS Adapter consuming from a Topic (IBM MQ)
Durable Subscription
Can any one help me get throttling using poller threads working?
Please let me know if you need further details about my configuration / logs etc.
I posted this in two other forums but didn't get any responses on them so posting it here. I apologize for the repetition of this post in multiple forums.
Thanks & Regards
shashi

Hi Raks,
Check this note for JNDI configuration..
802754
"If a 3rd party JMS provider should be used then usually the "Name of JNDI initial context factory" must be adjusted. I.e. com.sap.engine.services.jndi.InitialContextFactoryImpl must be replaced by some.other.vendor.jms.jndi.InitialContextFactory In addition it is necessary to deploy the jar that contains the some.other.vendor.jms.jndi.InitialContextFactory with the aii_af_jmsproviderlib.sda SDA file. In addition, you must extend the server/provider.xml deployment descriptor in the relevant way. Refer to Chapter 11 of the XI 3.0 Configuration Guide for more information"
You need to find out class "Name of JNDI initial context factory" for tibco as mentoned in the note and deploy the corresponding JAR file.
Also check this link for JNDI configuration parameters in the JMs adapter..
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Regards
Anand

JMS adapter could not receive message from Tibco EMS topic

I'm trying to consume message from tibco EMS topic using Oracle SOA JMS adapter. Can anyone please let me know the steps to do this. Appreciate your help.
Thanks,
SB

Increase Log level for cube.activation to debug and check the logs by stopping & starting the activation agent(I mean Retire and activate the process) .. It should give a clue on what's happening..

JMS Adapter - SOA Suite 11g

Hi,
We are facing a weird issue while configuring JMS adapter for a queue sits on a remote Weblogic JMS Server.
- Configured adapter in a BPEL process and provided JNDI name 'eis/wls/Queue'
- Configured outbound connection pool with remote server url/user id/pass
- added the same jndi name properties in soa/connectors/JMSadapter.rar/weblogic-ra.xml
When we test the service, the following error is thrown:
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. PublishToJms:JmsAdpWrite [ Produce_Message_ptt::Produce_Message(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Please help...
Regards,
AP

Hi,
We have re-deployed JMS adapter after changing weblogic-ra.xml as per the product documentation. Now getting a different exception..
java.lang.Exception: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Produce_Message' failed due to: ERRJMS_PROVIDER_ERR. ERRJMS_PROVIDER_ERR. Unable to produce message due to JMS provider internal error. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:570) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:597) at com.sun.el.parser.AstValue.invoke(AstValue.java:157) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at
Any thoughts on this ?
Regards,
AP

JMS Adapter Config issues with Plan.xml

Hi All,
I'm learning how to configure JMS Resources in WLS to use within a JMS adapter in my application. My approach so far has been :
1. Configure Outbound Connection in JMS Adapter : eis/wls/Queue. I used the weblogic.jms.XAConnectionFactory as the Connection Factory.
2. Create Queue within SOAJMSModule : jms/MyQueue and target - soa managed server.
Updated the JMSAdapter.rar deployment and restarted the SOA server as well as the JMS module.
3. Create JMS Adapter within JDeveloper to use jms/MyQueue as the destination and eis/wls/Queue as the JNDI source.
On deployment and running, I see this following error. Apologies it is a bit difficult to trawl through. I did have a look in the Plan.xml and it definitely has an entry for this Adapter and the jndi-name. Any other approach?
Oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:575) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:381) at oracle.sysman.emas.view.wsmgt.WSView.invokeOperation(WSView.java:298) 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:597) at com.sun.el.parser.AstValue.invoke(Unknown Source) at com.sun.el.MethodExpressionImpl.invoke(Unknown Source) at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53) at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1256) at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:102) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent$1.run(ContextSwitchingComponent.java:92) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent._processPhase(ContextSwitchingComponent.java:361) at oracle.adf.view.rich.component.fragment.ContextSwitchingComponent.broadcast(ContextSwitchingComponent.java:96) at oracle.adf.view.rich.component.fragment.UIXInclude.broadcast(UIXInclude.java:96) at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:765) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:305) at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emSDK.license.LicenseFilter.doFilter(LicenseFilter.java:101) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271) at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177) at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.wls.filter.SSOSessionSynchronizationFilter.doFilter(SSOSessionSynchronizationFilter.java:276) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.AuditServletFilter.doFilter(AuditServletFilter.java:179) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:203) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.model.targetauth.EMLangPrefFilter.doFilter(EMLangPrefFilter.java:158) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.core.app.perf.PerfFilter.doFilter(PerfFilter.java:141) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:542) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111) at java.security.AccessController.doPrivileged(Native Method) at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313) at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413) at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94) at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161) at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(Unknown Source) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120) at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source) at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source) at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) Caused by: oracle.sysman.emSDK.webservices.wsdlapi.SoapTestException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:260) at oracle.sysman.emSDK.webservices.wsdlparser.OperationInfoImpl.invokeWithDispatch(OperationInfoImpl.java:992) at oracle.sysman.emas.model.wsmgt.PortName.invokeOperation(PortName.java:729) at oracle.sysman.emas.model.wsmgt.WSTestModel.invokeOperation(WSTestModel.java:569) ... 81 more Caused by: javax.xml.ws.soap.SOAPFaultException: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PostException' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. ExceptionManagement:JMSPostException [ PostException_ptt::PostException(body) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/wls/Queue'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/wls/Queue. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. at oracle.j2ee.ws.client.jaxws.DispatchImpl.throwJAXWSSoapFaultException(DispatchImpl.java:1012) at oracle.j2ee.ws.client.jaxws.DispatchImpl.invoke(DispatchImpl.java:803) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.synchronousInvocationWithRetry(OracleDispatchImpl.java:235) at oracle.j2ee.ws.client.jaxws.OracleDispatchImpl.invoke(OracleDispatchImpl.java:106) at oracle.sysman.emSDK.webservices.wsdlapi.dispatch.DispatchUtil.invoke(DispatchUtil.java:256) ... 84 more
The deployment plan reads as follows :
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>connectors</application-name>
<variable-definition>
<variable>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<value>eis/wls/Queue</value>
</variable>
<variable>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<value>weblogic.jms.XAConnectionFactory</value>
</variable>
</variable-definition>
<module-override>
<module-name>JmsAdapter.rar</module-name>
<module-type>rar</module-type>
<module-descriptor external="false">
<root-element>weblogic-connector</root-element>
<uri>META-INF/weblogic-ra.xml</uri>
<variable-assignment>
<name>ConnectionInstance_eis/wls/Queue_JNDIName_13401799388390</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/jndi-name</xpath>
<origin>planbased</origin>
</variable-assignment>
<variable-assignment>
<name>ConfigProperty_ConnectionFactoryLocation_Value_13401801874110</name>
<xpath>/weblogic-connector/outbound-resource-adapter/connection-definition-group/[connection-factory-interface="oracle.tip.adapter.jms.IJmsConnectionFactory"]/connection-instance/[jndi-name="eis/wls/Queue"]/connection-properties/properties/property/[name="ConnectionFactoryLocation"]/value</xpath>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>connector</root-element>
<uri>META-INF/ra.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>E:\oracle\product\middleware\11.1.1\soa_11.1\soa\connectors\plan</config-root>
</deployment-plan>
Thanks
JB
Edited by: 939260 on Jun 20, 2012 5:13 AM

Hi JB,
Please follow the below steps from beginning...
1. Create the JMS Server in the Admin Console, the target server for the same should be the soa server
2. create new JMS Module.
3. Create new Connection factory in resources, give your JNDI names, the target servers should be the admin and the soa.
4. create new queue, give the JNDI names, the target server should be the JMS Server which you have created in the step 1 above.
5. Now go to deployments, slect the JMS adapter, click update, and say redeploy with the location of JMS-plan.xml given below...
6. Now inside the composite while configuring the JMS adapter, select the queue which you have created above.
If you have followed the abpve steps correctly, you should not face any problem.
Hope this helps,
N

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

Accessing JMS UDD deployed on OSB cluster from a composite JMS adapter deployed on soa cluster

Our environment setup
Single domain with three clusters
osb_cluster.soa_cluster and bam_cluster
osb_cluster: osb_server1 and osb_server2
wlsbJMSServer_auto_1: targetted to osb_server1
wlsbJMSServer_auto_2: targetted to osb_server2
osb_subdeployment1:targetted to wlsbJMSServer_auto_1 and wlsbJMSServer_auto_2 JMS servers
osb_subdeployment1 has JMS UDD queue jms/wlsb/queue
soa_cluster: soa_server1 and soa_server2
There is a BPEL composite deployed to soa_cluster. It has JMS adapter trying to read messages from jms/wlsb/queue
JCA JMSAdapter is deployed to osb,soa clusters and Admin server
ConnectionFactory is targetted to soa and osb clusters (osb_cluster and soa_cluster)
We have bounced soa and osb servers(not admin) after jms changes.
soa log says
JMSAdapter Composite1l JmsDDEndpoint_onFailure: Unable to resolve 'jms.wlsb.queue. Resolved 'jms'
Can we access JMS destinations deployed on one cluster from different cluster?
If yes, how can we do that ? do we need to modify BPEL JCA file to indicate destination is on another cluster?
Thanks,
Praveen

Anybody has faced similar issue?

SOA Suite 11g - dynamic JNDI destination JMS adapter

hi there soa suite users,
im currently using oracle soa suite 11g,
my use case having a bpel process processing something
and then route the result to several queue.
like this:
jms/adminduk/queue/mks1
jms/adminduk/queue/pdg1,
etc...
so the destination name can be build dynamically in the bpel,
and i stored in a string variable "destName".
(im using WLS 10.3 jms)
now i need to invoke a jms adapter service with produce operation,
but the queue destination needs to be using the variable "destName".
i already tried using assigning to property "jca.jms.JMSDestinationName"
in the invoke activity.
<invoke ...>
<bpelx:inputProperty name="jca.jms.JMSDestinationName"
variable="destName"/>
</invoke>
but it seems not working, and im getting this error:
Caused by: com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault}
parts: {{
summary=<summary>Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation
'SendSinkBioWniFromDaerahResponse' failed du
e to: ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution.
</summary>
,detail=<detail>[JMSExceptions:045103]While trying to find a topic or a queue we could not find the specific JMSServer
requested. The linked
exception may contain more information about the reason for failure.</detail>
,code=<code>null</code>
this is a basic use case of jms interoperability,
anyone have answers to this ??
thank you :)

Hi,
If someone is looking to dynamically set the JMSqueue name here is the solution.
in the Invoke activity set "jca.jms.JMSDestinationName"
value to "JMSHeaderVariable"
set the type to "input"
in the JMSHeaderVariable set the queue name dynamically.
and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.

Passing dynamic jndi destination to jms adapter in SOA Suite

hi i post this thread in SOA Suite category,
but havent got any answer yet,
maybe someone in weblogic jms community here have an answer :)
im interfacing Weblogic JMS 10.3 with SOA Suite 11gR1 BPEL/JMS Adapter,
and i need to pass a dynamic destination jndi to message producing adapter in the orchestration process.
details here:
Re: SOA Suite 11g - dynamic JNDI destination JMS adapter

Hi,
If someone is looking to dynamically set the JMSqueue name here is the solution.
in the Invoke activity set "jca.jms.JMSDestinationName"
value to "JMSHeaderVariable"
set the type to "input"
in the JMSHeaderVariable set the queue name dynamically.
and in the JMSadapter give any valid queue name, still the message will be routed to the queue which you have set in the invoke adapter.

PI 7.11 JMS adapter using JNDI weblogic server issue

Hi SAP experts,
I have a scenario to integrate to a application using JMS adapters. we use SAP PI 7.11 version.
We have deployed JMS drivers successfully and We face issue here to connect to weblogic server
We are using JMS adapter using JNDI to connect to weblogic server version 10.3.
Can anyone help with the exact format to be used in JMS properties table and additional parameters table in JMS communication channel. Your quick help will be appreciated.
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error looking up destination: AccrualDetailsQueue for profile: ConnectionProfile of channel: CC_SND_JMS on node: 3010950 having object id: 673696a9fe8c39fdab32213f0930afb3: javax.naming.NameNotFoundException: Unable to resolve 'AccrualDetailsQueue'. Resolved ''<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createDestination(JndiConnectorImpl.java:168)<br

Hi Padmini,
Refer to the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/content.htm
It was very helpful to me, for configuring the additional parameters in the communication Channel JMS.
I leave you some screenshots of the settings that I did.
I seize the opportunity to ask you, where do I can get the drivers (.Jar) for Weblogic?
Regards.
Rodrigo.

Correlation issue in JMS adapter - SYNC/ASYNC scenario without BPM

Hi,
I am working on a SYNC/ASYNC scenario with JMS adapter without using BPM. My scenario is SOAP<>PI>JMS. I configured the interface as below:
1. SOAP Sender channel
2. JMS Receiver Channel writing to Queue A.
     Module used:      a. RequestOneWayBean
               b. WaitResponseBean
     Correlation Settings:
               a. Set JMS Correlation ID to "XI Message ID"
               b. Store JMS CorrelationID of request (Checked)
               c. Set JMS Property to "JMS Correlation Id"
               d. Value = "XI MEssage ID"
3. JMS Sender channel reading from queue B ( I am exporting the message from queue A and importing into queue B)
     Module used:      a. NotifyResponseBean
     Correlation Settings:
               a. Set XI MEssage Id to "GUID"
               b. Set XI Conversation ID to "Stored JMS COrrelationID of Request"
I can see the cid in the message from queue A. But I observed thhat the header format of the message in Queue A is "MQSTR".
ISSUE:
1. While writing the message to queue A, below adapter log details(part b) concerned me:
     a. Message '8747a7c2-2b06-11df-8055-005056a70ed6' successfully processed by channel
     b. Could not create acknowledgements for message '8747a7c2-2b06-11df-8055-005056a70ed6'
I am not sure why I am receiving the message that " could not create acknowledgements"
2. While reading the message from the sender channel,I consistently get the error message as below:
     a. XI message ID corresponding to JMS message with ID 'ID:414d51205341504449442e514d202020c67b954b20005602'
          will be created as a new GUID with value '21bca916-424f-41f6-3347-c71090392b58'
     b. Error while processing message '21bca916-424f-41f6-3347-c71090392b58'; detailed error description:
          com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
          found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
Below are the blogs which I have already gone through:
1. JMS Synchronous Scenario without BPM - Correlation Settings and Transactional JMS Session
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/b028f6f6-7da5-2a10-19bd-cf322cf5ae7b
2. Note: 1086303
3. Sync / Async Bridge without BPM
In the note, they mentioned something about header being "MQRFH2". BUt in our case, the header is "MSSTR". Not sure whether it makes any difference.
Please help.
Edited by: GP on Mar 9, 2010 4:24 AM

Hi,
detailed error description:
com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: found no correlation ID: RecoverableException:
found no correlation ID at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:105) ...
This error would generally arose when there are multiple messages, got stuck in the outbound queue. Try to stop both the sender and receiver JMS comunication channels and clear both the inbound and outbound queues.
Once all the messages in the queue are cleraed, try posting the message again.
Regards,
Swetha.

Jms adapter issue

PI 7.31 is getting issue while connecting to Webshere MQ version 6.0.2.10.
The error in JMS sender communication channel is - "Error connecting due to missing class com.ibm.mq.jms.MQQueueConnectionFactory. Please ensure all resources are present in JMS provider library : com.sap.aii.adapter.lib.sda"
Few weeks back, MQ jar files were deployed by Basis.
I have attached jar file content. Do we have to deploy different jar files,the jar files are of websphere mq 6.0.2.10.
They were deployed on com.sap.aii.adapter.lib.sda
rgds

Hi ,
Go through below links once.
Receiver JMS Adapter Communication channel Error
JMS inbound and outbound queue
Regards
Venkat

SOA JMS Adapter JCA Properites Issues

Similar Messages

Maybe you are looking for