Using XI with native netweaver JMS provider

I have configured an XI interface to use the provided netweaver JMS service provider.
The interface takes and IDoc and posts it to the JMS queue, however, when the target application goes to retrieve the message off of the queue, it is in the format of a binary message.
My question is how do I control the format of the message? (I need to set the MessageType field in the JMS header to type TextMessage).
Do I do this in the Integration Builder, communication channel page?
I notice that this page has check boxs for "Set Additional JMS parameters or Replace Default Settings" and "Use Adapter-Specific message Attributes" is this where I would add the property?
Any info would be appreciated!

Hi,
This Blog from Michal will help you in setting the Adapter specific Message attributes - this speaks about File based scenario but it will help you to get a hang of how to set the Adapter specific Message attributes
/people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14
After reading the blog go through this :
http://help.sap.com/saphelp_nw04/helpdata/en/43/03612cdecc6e76e10000000a422035/content.htm
and on this page:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
Hope this helps,
Karthik

Similar Messages

JMS : Using SUN MQUEUE as a JMS Provider

Hi guys,
I'm having quite some trouble in configuring a JMS scenario...
I'm using SUN MQueue as a JMS Provider. I've installed the respective drivers, imq.jar, fscontext.jar and jms.jar.
I had no trouble in deploying this drivers on the SDM.
Now, after creating a receiver JMS communication channel, I get the following error on the RWB:
Error during channel initialization; exception trace: java.lang.NoSuchMethodException: com.sun.messaging.QueueConnectionFactory.(java.lang.String)
at java.lang.Class.getConstructor0(Class.java:1937)
at java.lang.Class.getConstructor(Class.java:1027)
at com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerJMSSender.java:474)
I've searched XI logs, in order of getting some light on the subject...This was what I've got:
#com.sap.aii.af.service.jms.WorkerJMSSender.init(WorkerHandler moduleHandler, Object para)#J2EE_GUEST#0####975a11b0c58b11dbce6700145e1855ec#SAPEngine_Application_Thread[impl:3]_19##0#0#Error##Java###Unable to create the QueueConnectionFactory due to #1#SUNMQUEUE_IP:SUNMQUEUE_Port#
My question is what is #1#....
I've read a few forum threads, but none of them can clarify my error....
I've tried the same scenario using Business Connector...Of course, in BC I had to create 2 JAVA services, one for sending and another for receiving messages...there was no problem with this, I did managed to send JMS Messages to SUN MQUEUE...
Can anyone give a hint....anything...?

Hi,
This is something related to JMS Adapter configuration settings and security ...
please check .. all your settings..
<i>This is the SonicMQ implementation of the QueueConnectionFactory.
A JMS client, in this case the adapter, uses a QueueConnectionFactory object to generate QueueConnection objects of a JMS provider.
The default value for SonicMQ 3.0 is progress.message.jclient.QueueConnectionFactory</i>
See also..below links
http://help.sap.com/saphelp_nw04/helpdata/en/c1/739c4186c2a409e10000000a155106/content.htm
Installation problem: Central Instance 6.40 Oracle on Linux 32
Regards
Chilla..

I would like make my iphone 4S simfree in order to use it with my current service provider. I don`t know where to ask it; and need help. Thank you.

Hello everyone.
I`m a apple user from Turkey. Lately I have bought an iphone 4S in U.S.A and brought it back to my country. My problem is I can`t use it with my local service provider; because I can`t activate my iphone 4S with the sim kart which I have.
I need help; and asking you what can I do ?
Thank you all for your attention.

Actually I had a friend of me to buy it for me. When I got the iphone 4s there were a At&t sim kart in it already.
I can make it unlocked for free ?
Thank you both for your attention.

How to use IBM MQ as a JMS Provider?

Chapter 8.2 on session pools in the 1.0.2 spec seems to make no real mention
          of transansactions. If not could you point exactly where? What steps would
          one use to cause a foreign messaging-server to infect an async message
          with a JTA transaction using Chapter 8.2 session pools?
          Chapter 8.3 describes the XA libraries, which are not related to session pools.
          The general community feeling on Chapter 8.2 SessionPools is that in almost all
          cases they are
          inferior to MDBs. To make it worse, they are not a required part of the J2EE
          spec. Their
          only real advantage is that they can pool access to a single topic subscription.
          Nice, but hardly
          worth the trouble. Just brainstorming here, but the elegant solution here
          seems simple: extend
          the JMS spec to allow multiple consumers on a single subscription. This would
          also nicely solve
          one MDB/topic problem, as even with SessionPools, there is no way to have MDBs
          on multiple
          servers share a single subscription...
          I don't think the spec states that SessionPools should run on a client. I'm
          fairly sure
          that SessionPools were intended to be a server-side entity. The numerous
          repetitions stating
          that the MessageListener runs on the app server and that the app server controls
          the threads seems to support
          this. It is an extension past Chapter 8.2 to get them to work off-server.
          (Albeit potentially a nice one, if
          one is absolutely determined to use these things instead of MDBs.)
          Maciej Szefler wrote:
          > I've noticed that BEA maintains that this is a shortcoming in the JMS
          > spec -- particularly that there is no way to integrate XA messages from
          > other JMS implementations into Weblogic without the vendor implementing
          > propriatary Weblogic interfaces, I quote your FAQ:
          >
          > "The only reason this works for WebLogic Server JMS is that we have defined
          > a WebLogic Server extension interface that has a method to associate a
          > message with a transaction. This interface, MDBTransaction, is defined in
          > news://newsgroups.bea.com/[email protected]. It has one method,
          > associateTransaction(), that takes a javax.jms.Message parameter. This
          > message must be associated with the transaction. We are hoping that other
          > JMS vendors interested in integrating with WebLogic Server will implement
          > this interface. "
          >
          > "Another approach called source managed transactions, would be for there to
          > be an API to tell the JMS provider to start a transaction on your behalf
          > before delivering the message to an asynchronous consumer. This API doesn't
          > exist in J2EE either. Even if there were such a provision, few non-WLS JMS
          > providers can begin and drive such a transaction by themselves."
          >
          > I would like to know where it is that you guys came up with this novel (and
          > incorrect) position. The JMS API to do this exists, it is called ASF (JMS
          > spec chapter 8) and if WebLogic implemented it correctly then there would be
          > no problem driving XA MDBs using MQseries. The fact of the matter is that
          > Weblogic 6.1 server is simply not JMS compliant in this respect. The 6.1 JMS
          > implementation does not expose the ASF correctly (it relies on the client
          > using a special ServerSesisonPool implementation), nor does the MDB
          > container use the ASF (which I guess is understandable since it isn't
          > implemented correctly). The question is, is Weblogic 7.0 Server going to use
          > ASF to drive MDBs and is the Weblogic 7.0 JMS implemetation going to
          > correctly expose the ASF to advanced clients that may wish to use it?
          >
          > -Maciej Szefler
          > FiveSight Technologies Inc.
          >
          > "Tom Barnes" <[email protected]> wrote in message
          > news:[email protected]...
          > > Clarification. See in-line.
          > >
          > > Tom Barnes wrote:
          > >
          > > > Hi Steve,
          > > >
          > > > This request comes up numerous times in this newsgroup. Since
          > > > the FAQ isn't quite up to date, here is the cut-and-paste response:
          > > >
          > > > Resources:
          > > > Resource Library/White-Papers/WebLogic Server section on dev2dev site:
          > > >
          > http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          > > > jmsproviders.doc, jmsmdb.doc, jmsjta.doc
          > > >
          > > > Code Library/Code Samples/WebLogic Server section on dev2dev site:
          > > > "WebLogic MQSeries JMS Support"
          > > > wlsmqseries.zip
          > > >
          > > > Code Library/Alpha Code/WebLogic Server section on dev2dev site:
          > > > "Sample JMSBridge For WebLogic 6.0"
          > > > JMSBridge60.zip
          > > >
          > >
          > > The above is 6.0 sample code that has nothing to do the below 6.1 alpha
          > bridge, and
          > > was not developed by anyone on the JMS team. The location for the 6.1
          > information is:
          > >
          > > Resource Library/Guides and Tutorials
          > > "Introducing WebLogic Messaging Bridge"
          > > MessagingBridge61.zip
          > >
          > > (see
          > >
          > http://dev2dev.bea.com/resourcelibrary/guidestutorials/technicalguides.jsp?h
          > ighlight=guidestutorials)
          > >
          > >
          > >
          > > >
          > > > The 6.1 MDB can be driven directly by standard JMS implementations -
          > but
          > > > not transactionally by vendors that do not implement the
          > > > weblogic.jms.extensions.MDBTransaction interface. Such vendors
          > > > (including MQSeries) can be made transactional by using a messaging
          > bridge
          > > > to synchronously forward MQSeries messages into WL queues that in turn
          > > > drive the MDB. The 7.0 MDB will be able to be driven transactionally
          > > > by non-WL vendors.
          > > >
          > > > The messaging bridge works with JMS implementations that implement
          > > > the standard J2EE JMS API. This bridge is available as alpha code
          > > > for 6.1, will be fully supported in 6.1SP3 (due out in June?), and is
          > also
          > > > part of 7.0 (currently released in beta).
          > > >
          > > > Tom
          > > >
          > > > steve chen wrote:
          > > >
          > > > > We like to use IBM MQ as our message provider, use Message Driven
          > Bean (Weblogic
          > > > > 6.1) as the consumer. How do we configure WLS so it uses IBM MQ
          > instead of WLS
          > > > > built in JMS as the provider?
          > > > >
          > > > > Thanks
          > >

Using Weblogic MDB to consume message using a XA transaction with third party JMS Provider

          I understood from the WebLogic documentation that we can invoke a third party JMS
          using its XA interface from within a MDB where transaction-type is Container and
          trans-attribute is Required. Also we will need to specify its XAConnection factory
          name as connection-factory-jndi name. It that sufficient ?? Or do i need to set
          up some other attributes also ??.


          Hi Neeru,
          I understand u were able to solve this issue.
          I am using similar kind of configuration but instead of tibco i am using Webmethods.
          Could u please let me know what did u do to solve the problem?
          -thanks and regards.
          Praveen
          "Neeru Munjal" <[email protected]> wrote:
          >
          >Hi Rob,
          >I used the same whitepaper and tried to use TIBCO JMS with Weblogic server),
          >I
          >started with MDB example specified in Weblogic 7.0 release in examples/ejb20/message
          >and modified it to use trans-attribute as Required. Also I used connection
          >factory
          >which supports XA, but my MDB does not get called.
          >
          >Thanks & Regards
          >Neeru
          >
          >Rob Woollen <[email protected]> wrote:
          >>Here's a white paper about integrating 3rd party JMS providers with
          >WLS:
          >>
          >>http://dev2dev.bea.com/resourcelibrary/whitepapersdetail.jsp?highlight=whitepapers&filePath=components%2Fdev2dev%2Fresourcelibrary%2Fwhitepapers%2Fwp_jmsproviders.htm
          >>
          >>-- Rob
          >>
          >>Neeru Munjal wrote:
          >>> I understood from the WebLogic documentation that we can invoke a
          >third
          >>party JMS
          >>> using its XA interface from within a MDB where transaction-type is
          >>Container and
          >>> trans-attribute is Required. Also we will need to specify its XAConnection
          >>factory
          >>> name as connection-factory-jndi name. It that sufficient ?? Or do
          >i
          >>need to set
          >>> up some other attributes also ??.
          >>>
          >>
          >

Deploy project using Jdeveloper with native library (dll)

hi
i need to deploy project using Jdeveloper but the generated jar dose not include native library dll file .

it is ok now
using deployment in properties of project and add new file group of type dependency analysis

Can i buy a ipad 2 3g in the US that is not tied to Verizon or AT&T so that i can use it with a UK 3G provider?

Any help appreciated.

The AT&T 3G iPads are not tied to them - you don't need to activate the AT&T sim or sign up for a contract with them, just swap in a local micro-sim when you get back here. The Verizon models are CDMA based so they don't use sim cards - so they won't be any good here in the UK as we don't use CDMA.

Using RS with SAP Netweaver - Timeout during allocate /CPIC 'ThSAPCMRCV'

Hi All,
I am trying to connect to a remote SAP BI server from my local SQL server 2005 Reporting Services. I was able to view all info objects in the query builder but when I try to drill down and view members / drag and drop to create a query / preview the RS report, I get the following error ,
u201CError occurred retrieving child nodes - error occurred when starting the parser - timeout during allocate: /CPIC-CALL 'ThSAPCMRCV' u201D.
I have SAP front end and business explorer installed on my system. We also have the latest patches on SAP BI server.
I tried changing the timeout value but dint help.
Any help is appreciated.
Many Thanks,
Chitra

Hi
I think you should post this in basis and security forum.
Cheers
Chanda

MDB behavior with Foreign JMS Provider

          I am experiencing some MDB behavior which I do not quite understand. I would appreciate
          if someone could tell me what might be happening.
          An application on WebLogic 8.1 SP1 (also tried it with SP2) has MDB's which listen
          on a MQ Queue. If I put a large XML message on the MQ Queue (say around 600 KB),
          the onMessage execution is very random, For the large messages only 1 MDB gets
          invoked and the other messages just sit on the MQ Queue. Even though I have defined
          an weblogic execute queue for the MDB's and they have 15 threads allocated.
          The other messages get picked up after the first one gets completed. The problem
          is the whole transaction (which is XA) can take a while (upto 10 minutes). This
          is not intended, but for some reason it takes that long.
          Also, while monitoring the MDB execute queues, I noticed that none of the threads
          from that queue are performing the work and a thread dump shows that the weblogic.ejb20.internal.JMSPoller
          thread has invoked the MDB and is currently waiting for the database to finish
          some processing.
          When the message size is smaller, the MDB's fire concurrently and are executed
          on the MDB execute queue.
          Thanks,
          Ketan.


When we're using MDBs against a foreign JMS provider with XA, the EJB
          container tries to reduce the number of threads that are blocked waiting for
          a message. You should see lots of threads working when there are lots of
          messages on the queue, a few threads (or only one) working when the queue is
          empty or nearly so, and there should be some ramp-up and ramp-down time in
          between. It sounds like the ramp-up takes longer in your case because
          receiving the very first message takes a long time.
          If this behavior is causing big problems for you, you might want to contact
          product support and file an enhancement request.
          greg
          "Ketan" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Here is some more information regarding this issue.
          >
          > When I place sufficiently large messages (such that the parsing and
          processing
          > of these messages takes longer than it does for normal size messages), I
          notice
          > the following behavior.
          >
          > Lets say I put 6 large messages on the MQ Queue. The server immediately
          picks
          > up 1 message and starts processing it. The other 5 messages are sitting on
          the
          > MQ Queue, while the MDB execute queue has all 15 idle threads.
          >
          > After the processing of the message is done, 2 messages get picked up.
          This time,
          > 1 thread in the MDB execute queue gets the message and the other is
          processed
          > by the JMSPoller thread. After these 2 messages are processed, 3 Messages
          get
          > picked up and this time 2 messages are on the MDB execute queue and 1 is
          processed
          > by the JMSPoller.
          >
          > So based on this the question is ..Is this the expected behavior? I was
          under
          > the impression that the poller would simply dispatch messages to the
          execute queue,
          > and as a result, I was expecting all the messages would get picked up from
          the
          > MQ queue pretty fast and would not have to wait for 1 or more MDB's to
          finish
          > processing.
          >
          > I would really appreciate any suggestions anyone may have for me.
          >
          > Again the environment is WLS 8.1 SP2, MQ 5.3
          >
          > thanks,
          > Ketan

Using external JMS provider

I am trying to use Tibco EMS as an external jms provider.
I created new factory (named TibcoFN) in JMSConnector service using visual administrator
Then I deployed and started it without any visible problem.
Then I created reference in a web.xml file of web application.
When I am calling lookup of initial context I always get naming exception.
What steps am I missing?
Piya

I am trying to use ActiveMQ as my external JMS provider and having a hard time doing so. I've deployed the activemq jar file in the JMS Connector service > library, and defined jms-factories.xml like:
<?xml version="1.0" encoding="UTF-8" ?>
<jms-factories>
<connection-factory>
    <factory-name>jms/ConnectionFactory</factory-name>
    <library-name>activemq</library-name>
    <context-factory-type>
      <link-factory-name>jmsfactory/default/QueueConnectionFactory</link-factory-name>
      <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
      <provider-url>sapvm-vc:61616</provider-url>
      <security-principal></security-principal>
      <security-credentials></security-credentials>
    </context-factory-type>
</connection-factory>
</jms-factories>
But I am getting the following error:
Application error occurred during request processing.
Details:   org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'exampleManagerContainer' defined in class path resource [integrationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoSuchMethodError: javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection;
Exception id: [005056AB07A0005B0000004100000614000449BF8461CFBE]
Any ideas, please???
thanks,

Connection with the JMS provider

Hello,
I'm trying to activate the JMS adapter (Using XI 3.0), the JMS provider is IBM WebSphere MQ, we have the following error :
"MQJMS2005: failed to create MQQueueManager for .."
We found a note regarding that error, note number 749743.
I have 2 questions :
1. Where can I see the trace file ?
2. Where will I set the user & Password ?
Any ideas ??????
Yaki

Hi Yaki,
from:
http://help.sap.com/saphelp_nw04/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm
JMS Queue User - User for accessing the JMS queue
JMS Queue Password - Password (with confirmation) for accessing the JMS queue
so the values maintained at MQ
Regards,
michal

Using Swiftmq as the third-party Jms provider in Weblogic11

Hi, I am using swiftmq as 3rd-party jms provider in wls, however when I am trying to deploy a MDB listening on the queue configed in swiftmq.rar (resource adapter) in wls, it warns that ***MDB is unable to connect to the JMS destination: myforeigndestination.
The Error was:
weblogic.jms.common.InvalidDestinationException: Foreign destination
, so do I need to configure a foreign connection factory and config the mdb to refers to this foreign connection factory? thx

Hi, I am using swiftmq as 3rd-party jms provider in wls, however when I am trying to deploy a MDB listening on the queue configed in swiftmq.rar (resource adapter) in wls, it warns that ***MDB is unable to connect to the JMS destination: myforeigndestination.
The Error was:
weblogic.jms.common.InvalidDestinationException: Foreign destination
, so do I need to configure a foreign connection factory and config the mdb to refers to this foreign connection factory? thx

Netweaver JMS issues

I have a stand alone enterprise java application (not an EJB) that currently runs on several servers (one application per server). This application allows us to do parellel processing for performance reasons. Another important distinction is that we use a JMS Point-to-Point model with multiple consumers receiving messages off a single queue. The application is basically a JMS asynchronous message consumer, meaning it implements the javax.jms.MessageListener interface so it has the onMessage method.
Currently I have been using JBoss 4.0 as our JMS Provider. I have had no issues for awhile now with multiple consumers receiving messages off a single queue. Recently, I have been asked to move to use Netweaver's JMS provider. I was successful in changing the configurations and sending and receiving messages using the Netweaver JMS provider. However, it appears that I cannot get multiple consumers to receive messages off a single queue. I can successfully launch off several of our applications on several servers all listening to the single queue and I can also put multiple messages into that single queue. However, it appears that only one message consumer can receive a message off the single queue at one time (all the other message consumers seem to wait until the one message is done processing).
Again, I changed the configurations back to JBoss and everything worked fine (I also did it for OpenJMS and it worked as well). My quess is that I either did not setup something correctly or I need to make some kind of administative or jms setting. Any help would be greatly appreciated.
Just a side note. If I poll for messages on the single queue instead of using the onMessage() method with multiple message consumers I am able to run parellel processes.

We are talking P2P with load balancing and scaling for throughput. Moving this to a pub/sub is a bad performance move as typically pub/sub is more time and resource intensive than P2P.
Just make sure that in your JNDI definition your queue has been marked as shareable. As the JMS spec goes it does not help if the provider side of the queue has the queue marked as not shared. As well if the app reading from the queue through the listener has it opened in exclusive mode all the others are waiting.
This means some investigation may be needed.
A) JNDI verify JMSDestination is defined as shareable
b) programming wise verify that putting the listener to the queue does not make the mode opened as exclusive.
Typically you would have implemented an MDB. You need to check the number of instances that you have defined for the MDB. As well you may define the same destination with multiple JNDI names and thus set different MDBs on the same queue (but same MDB class).
There is a world of solutions out there. Pick the one that works for you
Enjoy
Message was edited by: F.J. Brandelik
SAP's implementation of JMS persistence is through a Database. Make sure locking happens at the record level and not at the page level.

Connecting to a Remote JMS provider from MDB in jboss-4.0

Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>



<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>

<attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
java.naming.factory.url.pkgs=com.tibco.tibjms.naming
java.naming.provider.url=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)

Hi,
I am using Tibco as a remote JMS Provider. When the Tibco server is running on the same machine as JBoss-4.0, the Message Driven Bean deployed in Jboss is able to get the messages from the queue on Tibco server.
I have added the following configuration to jms-ds.xml file

<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name="jboss.mq:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">TIBCOJMSProvider</attribute>
<attribute name="ProviderAdapterClass">
org.jboss.jms.jndi.JNDIProviderAdapter
</attribute>



<attribute name="QueueFactoryRef">XAQueueConnectionFactory</attribute>

<attribute name="TopicFactoryRef">XATopicConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
java.naming.factory.url.pkgs=com.tibco.tibjms.naming
java.naming.provider.url=tibjmsnaming://TibcoHost:7222
</attribute>
</mbean>
Also following invoker proxy binding is added to standardjboss.xml & it is used in MDB's jboss.xml
<invoker-proxy-binding>
<name>my-mdb-invoker</name>
<invoker-mbean>does-not-matter</invoker-mbean>
<proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
<proxy-factory-config>
<JMSProviderAdapterJNDI>TIBCOJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<MinimumSize>1</MinimumSize>
<KeepAliveMillis>30000</KeepAliveMillis>
<MaximumSize>15</MaximumSize>
<MaxMessages>1</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
</invoker-proxy-binding>
But When I try to use Tibco server on some other machine it throws following exception. It actually tryies to connect to Tibco server on same machine.
javax.jms.JMSException: Failed to connect to the server at tcp://localhost:7222
at com.tibco.tibjms.TibjmsxLinkTcp._createSocket(TibjmsxLinkTcp.java:748)
at com.tibco.tibjms.TibjmsxLinkTcp.connect(TibjmsxLinkTcp.java:857)
at com.tibco.tibjms.TibjmsConnection._create(TibjmsConnection.java:611)
at com.tibco.tibjms.TibjmsConnection.<init>(TibjmsConnection.java:1769)
at com.tibco.tibjms.TibjmsQueueConnection.<init>(TibjmsQueueConnection.java:35)
at com.tibco.tibjms.TibjmsxCFImpl._createImpl(TibjmsxCFImpl.java:90)
at com.tibco.tibjms.TibjmsxCFImpl._createConnection(TibjmsxCFImpl.java:151)
at com.tibco.tibjms.TibjmsXAQueueConnectionFactory.createQueueConnection(TibjmsXAQueueConnectionFactory.java:140
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:152)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:237)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:164)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate(JMSContainerInvoker.java:545)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService(JMSContainerInvoker.java:767)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy45.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:170)
at org.jboss.ejb.MessageDrivenContainer.startService(MessageDrivenContainer.java:262)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy43.start(Unknown Source)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:394)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:891)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:416)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy19.start(Unknown Source)
at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:605)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:935)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:746)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:709)
at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:119)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:131)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:242)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:642)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)

Distributed destination with MQ as Foreign Provider

Hi
          Messages arrive in a set of clustered MQ Series Queues. MDBs process the messages (We use MQ as the Foreign JMS Provider). Can I set up a distributed destination (JMS Queues) in WebLogic and use those clustered MQ queues as the Foreign Provider ? I would like the MQ Series clustering to provide the redundancy/availability of the MQ Series system and the JMS distributed destination to provide high availability for the MDBs that are hosted in a set of clustered WebLogic server instances.
          Thanks

Hi          > Messages arrive in a set of clustered MQ Series
          > Queues. MDBs process the messages (We use MQ as the
          > Foreign JMS Provider). Can I set up a distributed
          > destination (JMS Queues) in WebLogic and use those
          > clustered MQ queues as the Foreign Provider ?
          No. WL distributed destinations consist only of a set of physical WL destinations. The WL distributed destination code does not support non-WL destinations.
          > I would
          > like the MQ Series clustering to provide the
          > redundancy/availability of the MQ Series system and
          > the JMS distributed destination to provide high
          > availability for the MDBs that are hosted in a set of
          > clustered WebLogic server instances.
          If MQ Series exposes its distributed destination via the standard JMS API, then the MDBs will automatically run as MQ distributed dest clients. This is a function of MQ, not WL -- WL MDBs simply use the standard JMS API of the vendor's supplied client to get their messages.
          But note that WL MDBs use a single connection per MDB pool/deployment. Some clustering implementations (MQ?) require using multiple connections...
          >
          > Thanks

Using XI with native netweaver JMS provider

Similar Messages

Maybe you are looking for