Administering AQ JMS objects in JNDI

I had used several JMS providers before like MQ and Tibco but I'm new to Oracle AQ.
I'm trying to write a JMS client program which lookups a connection factory and a destination from a JNDI context, and then create a session and publish JMS messages.
However, I cannot find a way to register JMS objects in JNDI. The sample programs provided by Oracle use a JMS session to create destination objects, which means they're not portable to other messaging system.
Questions:
1. Is there a way to administrate JMS objects in JNDI context in version 8.1.7?
2. I did search the forum and it seems like looking up JMS objects from JNDI is available on Oracle 9i. Is that true? And what administration tool am I supposed to use?
Thanks,
Andy

Hi,
I am not sure with OSB. I never seen the face of it. But when you say you are not able to see the subscriber in the table then you cannot consume the message.
Can quickly create AQJMS adapter service in bpel and select your topic and deploy the service in SOA server. Once it deploy go to the aq$my_topic1_s check if you able to see or not. And also try de-queue a message from the same topic.
I am using JMS Transport for Proxy Service and i have enabled the durable subscriber option as well. Please tell me how the entries in the subscribers table gets added.
You no need to do any thing. Just deploy your service and after that you should able to see record in the table. If record is not created then connection is not established between Topic and your service.
I have doubt with the endpoints only
jms://localhost:8011/aqjms.XATopicConnectionFactory/AqTopic
Your JNDI name for connection factories given as aqjms/XATopicConnectionFactory and here its aqjms.XATopicConnectionFactory. Can you check it.
Apart of this everthing looks same. Try above and let us know it.
Regards,
Tarak.
Edited by: Tarak on Nov 1, 2012 3:36 PM

Similar Messages

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

XI to IBM Websphere Default JMS Provider with JNDI

Hello everybody!
We face a problem with connecting SAP XI to IBM WebSphere Default JMS Provider (need to send a message from XI to WebSphere JMS and receive the response).
We have the following versions installed:
 SAP XI: 7.0 SP8 , Sun JDK 1.4.2
 IBM WebSphere: IBM WebSphere Application Server ND, 6.0.2.17, J2RE 1.4.2 IBM
We cannot set the JMS adapter of SAP XI for conecting with IBM WebSphere Default JMS Provider. The Communication Channel has erroneous state (at runtime) and the Communication Channel Monitoring tool displays the error message as described below (under "Variant 1" and "Variant 2" sub-headings) depending on the settings performed.
For connecting, the following JMS-provider settings were used at IBM WebSphere side:
 JMS Providers: Default Messaging Provider
 Queue Connection Factories: name:QueueConnectionFactory, jndi:jms/QueueConnectionFactory, provider: Default Messaging Provider
 Queues: name Queue, jndi: jms/Queue, provider: Default Messaging Provider
The XI communication channel (and associated JMS-adapter) was set as Variants 1 and 2 show. Settings for both cases and received error messages were the following:
Variant 1.
 Adapter type: JMS
 Type: Receiver
 JMS Provider: Access JMS Provider with JNDI (Java Naming and Directory Interface)
 JNDI Lookup Name of QueueConnectionFactory: jms/QueueConnectionFactory
 JNDI Lookup Name of JMS Queue: jms/Queue
 Name of JNDI Initial Context Factory: com.sap.engine.services.jndi.InitialContextFactoryImpl
 JNDI Server Address: iiop://WEBSPHERE.HOST:2809/
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state and the following error message is written:
 "Error during channel initialization; exception trace: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of jms/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)"
Variant 2
 The same settings as in Variant 1 above, were used and additionally the following settings were done:
 - Name of JNDI Initial Context Factory: com.ibm.websphere.naming.WsnInitialContextFactory
 - The archive aii_af_jmsproviderlib.sda containing libraries required by WsInitialContextFactory, was deployed to the SAP WebAS where the XI is running. Those libraries were taken from WebSphere Application Server Pluggable Application Client installation package (described in the article "WebSphere Application Server Pluggable Application Client" located at http://www-128.ibm.com/developerworks/websphere/library/techarticles/0409_bhogal/0409_bhogal.html)
 - Also, as it is recommended in the referred article, the files required by IBM's iiop protocol (ibmext.jar ibmorb.jar ibmorbapi.jar) were put to the folder jre/lib/endorsed of the server(Sun JVM 1.4.2 is used by SAP WebAS / XI).
 As the result, the Communication Channel Monitoring displays that the channel has erroneous state as well and the following error message is written:
 "No adapter registered for this channel"
We have not found the recommended solution either in SDN forums or in Internet in general. Is it yet possible to connect SAP XI to IBM WebSphere Default JMS Provider having mentioned product versioning? If yes, what settings have to be performed?

IBM Websphere Default JMS Provider which is installed alongwith the application server is nothing but a scaled down version of the IBM WebSphere MQSeries. you should be able to connect to it with the same settings that can be used for a separate MQSeries server connectivity from XI.

Storing of JMS ConnectionFactory in JNDI works Intermittently

I am saving my JMX ConnectionFactory (currently using an ActiveMQConnectionFactory) using JNDI. I am doing this so that the JMS server can be changed by simply replacing the stored ConnectionFactory object in JNDI all my applications can be switched to a new JMS server. My JNDI is currently backed by and LDAP Server (OpenDS). This all seems to work just fine, most of the time. I am running multiple applications on multiple oc4j servers on multiple computers and they all can get the correct ConnectionFactory and connect to the messaging system. My problem is that I am exposing properties from this JNDI server using JMX. When I invoke a method from the MBean browser in the OC4J Application Server Control that tries to access the Connection Factory through JNDI, I get an error that the object returned could not be cast to a ConnectionFactory. All of my other code seems to work. In fact, when I run standalone test code I can call the exact same method directly and it works. I just appears to happen when called through I assume and JMX invoke. What am I missing? Thanks for any light you can shed on this problem.

Yes, it is a separate application running under the same instance of the JVM (the OC4J container). I agree that the class is probably not being recognized by the classloader for the "OC4j Application Server Control" application, but can't figure out how to successfully include the relevant jar in the classpath of this classloader. Because of this I am not able to verify this correct nor fix the problem. I am wading through the Oracle documentation now to try and figure out where the jar belongs and if I need to change any configuration files.

JMS Objects in ObjectMessage is reference or copy? (WL 7.0)

          Hello All,
          I need to pass the of the message processing application specific status back
          to the client. I would not prefer to use the db for this status communication.
          Is thre any other way? I was thinking of using some objects provided JMS (wl 7.0)
          passes the objects by reference. Let me know if there are any other ways to pass
          the status back to the clients.
          Can message ackowledge can be made use of, in anyway?
          Your help is appreciated.
          Santhosh.


Hi Santhosh!
          Object messages are pass by value of necessity, as the JMS contract
          is that they must remain unchanged. (Things would get pretty
          tricky if they could not be.) But wait! This
          does not preclude passing an RMI reference to a
          remote object in an JMS object message. The
          distinction is that the RMI reference remains unchanged, so
          the message itself is unchanged. This ability is not standard
          JMS, and will not likely work with other JMS vendors.
          If you want to pass a reference in a J2EE standard way, the EJB spec
          provides the concept of serializable "handles"...
          Tom, BEA
          Santhosh Kumar wrote:
          > Hello All,
          >
          > I need to pass the of the message processing application specific status back
          > to the client. I would not prefer to use the db for this status communication.
          > Is thre any other way? I was thinking of using some objects provided JMS (wl 7.0)
          > passes the objects by reference. Let me know if there are any other ways to pass
          > the status back to the clients.
          >
          > Can message ackowledge can be made use of, in anyway?
          >
          > Your help is appreciated.
          >
          > Santhosh.

Runtime binding of JMS object(Queue, COnnection Factory)

I want to knwo whether runtime binding the JMS Objects(Connection Factory & Destinations)
is possible in WebLogic server?
According to Weblogic it only binds JMS Object at the startup of the server using
a Startup class?
Thanks a million

Destinations can be created dynamically.
check:
http://edocs.bea.com/wls/docs61/jms/implement.html#1189112
viswa
"Rakesh Jaiswal" <[email protected]> wrote:
>
I want to knwo whether runtime binding the JMS Objects(Connection Factory
& Destinations)
is possible in WebLogic server?
According to Weblogic it only binds JMS Object at the startup of the server
using
a Startup class?
Thanks a million

Clustering objects in jndi

Hi all,
I am building a solution using weblogic version 6.1sp1.
I am needing to share an object around a set of clusters to tell each cluster
about the services in the other clusters.
The first solution I thought of was to create a javax.naming.Reference to bind
into each of the clusters' JNDI tree and have it replicated throughout the tree.
After reading about the behavior of these types of objects, I am not sure how
to proceed.
It appears from the docs that if the server that bound the object into jndi goes
down the object will be unbound from all of the other servers in the cluster.
Please inform if my interpretation of the docs was incorrect.
The solution I am working for now is to not replicate the objects, and to create
a startup class for all of the servers, when they come up they will create and
bind their own versions.
Also, if anyone has another solution to this problem please reply ...

Your solution sounds right. Don't forget to set REPLICATE_BINDINGS to 'false' :
http://e-docs.bea.com/wls/docs61/javadocs/weblogic/jndi/WLContext.html
Chris Humphrey <[email protected]> wrote:
Hi all,
I am building a solution using weblogic version 6.1sp1.
I am needing to share an object around a set of clusters to tell each cluster
about the services in the other clusters.
The first solution I thought of was to create a javax.naming.Reference to bind
into each of the clusters' JNDI tree and have it replicated throughout the tree.
After reading about the behavior of these types of objects, I am not sure how
to proceed.
It appears from the docs that if the server that bound the object into jndi goes
down the object will be unbound from all of the other servers in the cluster.
Please inform if my interpretation of the docs was incorrect.
The solution I am working for now is to not replicate the objects, and to create
a startup class for all of the servers, when they come up they will create and
bind their own versions.
Also, if anyone has another solution to this problem please reply ...--
Dimitri

Help|| Is there any tool available to register Oracle datasource objects into JNDI

Is there any tool available to register Oracle datasource objects into JNDI.If so please tell me where can I download.
Thanks
shiva

I'd like to know the answer to this also.
I just started reading about JNDI 2 days ago and have never used it. I'd like to use DataSource in my application with JNDI. If I can use the database as my JNDI "server", then I'd prefer to do that instead of having a seperate external server.

Transform JMS objects to XML in ESB

All,
Is there a possibility of converting the JMS objects into XML using adapter services in ESB?
Thanks,
M.Rajesh

Rajesh,
If it is Text message(payload) then you can do that,
but for Java objects i never came across any thing?

Unable to bind object in JNDI tree.

While I try to bind a simple object in JNDI tree I get the following error.
I have not used any cluster .
Server : Web Logic 8.1 SP 6
Jdk version 1.4.2 comes along with bea weblogic 8.1 sp 6
Javax.naming.communicationException[
Root exception is java.rmi.unmarshalException:
Error unmarshalling arguments; nested exception is :
Java.lang.ClassNotFoundException: com.examples.person : This error could indicate that a compound was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on a server that is part of a cluster is also deployed on all other member of that cluster.

Is this somehow being called from the parameterless constructor?
You sometimes have to wrap bits of code with in designer checks to stop em running.
In c# that would be:
if (!DesignerProperties.GetIsInDesignMode(this))
// do your stuff only at runtime
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML

Unable to register object in JNDI tree

While I try to bind a simple object in JNDI tree I get the following error.
I have not used any cluster .
Server : Web Logic 8.1 SP 6
Javax.naming.communicationException[
Root exception is java.rmi.unmarshalException:
Error unmarshalling arguments; nested exception is :
Java.lang.ClassNotFoundException: com.examples.person : This error could indicate that a compound was deployed on a cluster member but not other members of that cluster. Make sure that any component deployed on a server that is part of a cluster is also deployed on a server that is part of a cluster is also deployed on all other member of that cluster.
-------------------------------

Is this somehow being called from the parameterless constructor?
You sometimes have to wrap bits of code with in designer checks to stop em running.
In c# that would be:
if (!DesignerProperties.GetIsInDesignMode(this))
// do your stuff only at runtime
Please don't forget to upvote posts which you like and mark those which answer your question.
My latest Technet article - Dynamic XAML

How to bind an object to JNDI tree in iAS?

Hi all,
When I try to bind a string object to jndi tree, the following exception
occurs:
javax.naming.NamingException: Unable to get object instance from reference.
Roo
t exception is javax.naming.NamingException: Can't bind instance of class
java.lang.String
at com.netscape.server.jndi.RootContext.bindCtx(Unknown Source)
at com.netscape.server.jndi.RootContext.rebind(Unknown Source)
at com.netscape.server.jndi.RootContext.rebind(Unknown Source)
at javax.naming.InitialContext.rebind(InitialContext.java:385)
at jsp.APPS.bmx.test2._jspService(test2.java:76)
at jsp.APPS.bmx.test2.service(test2.java:42)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
Source)
The code fragment is:
Context ctx = new InitialContext();
String str = "hell,every one!";
ctx.rebind("abc", str);
Can anyone give some help? Thanks in advance.
Johnson

To bind an object into the JNDI tree check the documentation here:
http://e-docs.bea.com/wls/docs81/jndi/jndi.html#475702
If this is to be used by all your applications that you deploy on the server check out the startup/shutdown class documentation here:
http://edocs.bea.com/wls/docs81/ConsoleHelp/startup_shutdown.html
Cheers
IV

Some JMS objects do not show up in JNDI tree

Hello friends. I have a situation where some of my JMS Queues do not show up in
the JNDI tree. Other Queues / Topics show up fine. I cannot find any difference
in the interface that tells me what my cause this to happen. Any insight would
be appreciated.
brian

are you using a cluster? if so check the multicast to see if its working
right.
Where are you looking up the JNDI tree? in the console or are you checking
the JNDI tree via weblogic.Admin LIST command? the LIST command may be a
better way to see it for sure.
sree
"Brian" <[email protected]> wrote in message
news:40b74519$1@mktnews1...
>
Hello friends. I have a situation where some of my JMS Queues do not showup in
the JNDI tree. Other Queues / Topics show up fine. I cannot find anydifference
in the interface that tells me what my cause this to happen. Any insightwould
be appreciated.
brian

JMS Properties in JNDI Directory

We are starting to use Message-Driven-Beans within our WLS 8 environment. My responsibility
is for WebSphere MQ and JMS. Currently our JMS usage has been such that that the
connection_factory information is stored in a central LDAP directory and administered
by the WebSphere MQ team. The queue objects are administered by the application
teams and kept locally. We would like to keep this concept also when using MDBs
in WLS. Looking at the configuration I cannot see how I could define two seperate
JNDI (initial_context) references - one for the queue object and a different one
for the connection_factory.
Any ideas?
Thanks in advance,
Martin
PS: Using MQ as transport for JMS is mandatory!

If your program is in an executeable jar file then add the following in the manifest
class-path: junk.jar
junk.jar has
pjb/props/myconfig.properties file
To access the properties in junk from your executable jar file in your class, do the following
Locale eng = Locale.ENGLISH;
String myvalue = java.util.ResourceBundle.getBundle("pjb.props.myconfig",eng).getString("greeting");That should work
Or if you not using an executable jar file just set your CLASSPATH to the directory where that junk.jar is.
java -cp c:\myjavalib\stash\ <-----Assmuing junk.jar is in thereJava dynamically reads jar files.

Error while using webmethod JMS provider with JNDI

Hi,
I am using webmethod JMS provider (not SAP JMS) with JNDI to connect to webmethod with XI. Central J2EE adapter engine is used and the comm chaneel is configured in with appropriate Provider JNDI Server address, initial context factory, Name of queue connection factory etc.
While activated the adapter short log shows: Adapter has not provided any status information about this channel"
In the detailed log following error message is displayed: "Obtained connection factory: null#"
#1.5 #001A4BAC31000052000001520000152200045090BF28DACA#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001530000152200045090BF28DB65#1214482519514#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Looking up connection factory under name NAIP_XIQueueConnectionFactory#
#1.5 #001A4BAC31000052000001540000152200045090BF28E42E#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Obtained connection factory: null#
#1.5 #001A4BAC31000052000001550000152200045090BF28E4B3#1214482519516#com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl##com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001560000152200045090BF28E528#1214482519516#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC31000052000001570000152200045090BF28E5A9#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Info##Java###Sucessfully executed CF invocations for connection factory object: for profile: #2#<null>#ConnectionProfile of channel: CC_RCV_JMS_SAPJNDIon node: 3010950 having object id: e4413a5265a436459e271d5e0dd4859b#
#1.5 #001A4BAC31000052000001580000152200045090BF28E64E#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.executeConnectionFactoryInvocations()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC31000052000001590000152200045090BF28E6CA#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015A0000152200045090BF28E741#1214482519517#com.sap.aii.adapter.jms.core.common.StringUtils##com.sap.aii.adapter.jms.core.common.StringUtils.isBlank(String str)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Entering method#
#1.5 #001A4BAC310000520000015B0000152200045090BF28E7C3#1214482519517#com.sap.aii.adapter.jms.core.connector.ConnectorImpl##com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Debug##Plain###Creating connection...#
#1.5 #001A4BAC310000520000015C0000152200045090BF28EB51#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Warning##Java###Catching #1#java.lang.NullPointerException
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.buildConnection(ConnectorImpl.java:198)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.doConnect(ConnectorImpl.java:166)
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.doConnect(JndiConnectorImpl.java:186)
at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.connect(ConnectorImpl.java:151)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.doStart(ChannelImpl.java:235)
at com.sap.aii.adapter.jms.core.channel.ChannelImpl.start(ChannelImpl.java:154)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.doAddUpdateChannel(AdapterImpl.java:404)
at com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(AdapterImpl.java:376)
at com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl$1.run(ChannelLifecycleCallbackImpl.java:51)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
#1.5 #001A4BAC310000520000015D0000152200045090BF28EC6A#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Error##Plain###[[ChannelName:CC_RCV_JMS_SAPJNDI,ChannelId: e4413a5265a436459e271d5e0dd4859b]] Error adding/updating channel.#
#1.5 #001A4BAC310000520000015E0000152200045090BF28ECF8#1214482519518#com.sap.aii.adapter.jms.core.channel.AdapterImpl##com.sap.aii.adapter.jms.core.channel.AdapterImpl.addOrReplaceChannel(Channel cpaChannel)#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC310000520000015F0000152200045090BF28ED76#1214482519519#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl##com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded().run()#J2EE_GUEST#0##n/a##8b16bd50437911ddc9f2001a4bac3100#SAPEngine_Application_Thread[impl:3]_16##0#0#Path##Plain###Exiting method#
#1.5 #001A4BAC3100005F000000660000152200045090BF65478A#1214482523474#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl#sap.com/com.sap.xi.mdt#com.sap.aii.adapter.jms.core.channel.ChannelLifecycleCallbackImpl.channelAdded(Channel channel)#AAAAAAAAA#108##n/a##002ee500437911dd99cf001a4bac3100#SAPEngine_Application_Thread[impl:3]_29##0#0#Path##Plain###Exiting method#
Please let me know anyone has come accross the problem or has idea how to solve it. Thanks.

Hi,
Ask ur basis admin to restart JMS adpater From Vis administrator and try again to activate the comm channel.
Hope this will solve ur problem and once again check connection fatcory and Queue name provided by Webmethod admin.
Regards,
Srini

Administering AQ JMS objects in JNDI

Similar Messages

Maybe you are looking for