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

Similar Messages

Transaction on JMS using OpenMQ provider

Hi,
I'm struggling with the following problem:
I'm running jboss 4.2.3GA and I use OpenMQ as JMS provider
this is my jms configuration file:
<?xml version="1.0" encoding="UTF-8"?>
<connection-factories>

<mbean code="org.jboss.naming.ExternalContext"
name="jboss.jndi:service=ExternalContext,jndiName=mq">
     <use-java-context>true</use-java-context>
<attribute name="JndiName">mq</attribute>
<attribute name="Properties">
java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
java.naming.provider.url=file:///C:/Users/mbazzani/OpenMQ/var/mq/instances/imqbroker/fs370
</attribute>
<attribute name="RemoteAccess">true</attribute>
<attribute name="InitialContext">javax.naming.InitialContext</attribute>
</mbean>
     <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
          name="imq.provider:service=JMSProviderLoader,name=JMSProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
<attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
<attribute name="FactoryRef">jnp://127.0.0.1/mq/XAConnectionFactory</attribute>
<attribute name="QueueFactoryRef">jnp://127.0.0.1/mq/XAQueueConnectionFactory</attribute>
<attribute name="TopicFactoryRef">jnp://127.0.0.1/mq/NonXATopicConnectionFactory</attribute>
<attribute name="Properties">
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=localhost
java.naming.factory.url.pkgs=org.jnp.interfaces
</attribute>
</mbean>
<mbean code="org.jboss.naming.NamingAlias"
          name=":service=NamingAlias,fromName=queue/DLQ">
<attribute name="ToName">mq/DLQ</attribute>
<attribute name="FromName">queue/DLQ</attribute>
</mbean>
          <mbean code="org.jboss.naming.NamingAlias" name=":service=NamingAlias,fromName=jms/ConnectionFactory">
     <attribute name="ToName">mq/XAConnectionFactory</attribute>
     <attribute name="FromName">jms/ConnectionFactory</attribute>
          </mbean>
     <mbean code="org.jboss.naming.NamingAlias"
name=":service=NamingAlias,fromName=jms/QueueConnectionFactory">
     <attribute name="ToName">mq/XAQueueConnectionFactory</attribute>
     <attribute name="FromName">jms/QueueConnectionFactory</attribute>
     </mbean>
     <mbean code="org.jboss.naming.NamingAlias"
     name=":service=NamingAlias,fromName=jms/TopicConnectionFactory">
     <attribute name="ToName">mq/XATopicConnectionFactory</attribute>
     <attribute name="FromName">jms/TopicConnectionFactory</attribute>
     </mbean>




<mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
     name="jboss.mq:service=ServerSessionPoolMBean,name=StdJMSPool">
<depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
<attribute name="PoolName">StdJMSPool</attribute>
<attribute name="PoolFactoryClass">
org.jboss.jms.asf.StdServerSessionPoolFactory
</attribute>
</mbean>

<tx-connection-factory>
<jndi-name>JmsXA</jndi-name>
<xa-transaction/>
     <track-connection-by-tx/>
     <rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
<max-pool-size>20</max-pool-size>
<security-domain-and-application>JmsXARealm</security-domain-and-application>
</tx-connection-factory>
</connection-factories>
The problem is that the transaction is not honored and the Message is sent to the queue before the transaction complete.
Anyone know if it's a know issue if I missed something or something like that ?
here: http://dl.dropbox.com/u/175137/mmm.zip the Ejb/Ear project used for test
Obviously the connection factory in openMq are all XA
and I reviewed all the paths but I cannot figure out where the problem is
Thanks in advice
Edited by: user9007030 on 9-feb-2012 15.28

Solved
the problem was that I was binding directly using a naming alias without passing through the resource adapter

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

Need example of the use of AQ Streams with JMS and no JNDI

This question may be a stretch, but help me if you can.
I do not have Oracle Internet Directory, but I do have 10g database and queues created.
I would like to use plain JMS 1.1 wherever is that possible, but I understand that I will need to use Oracle AQjmsFactory to get to the connection and queue objects.
Does anyone has any examples on how to do this. When I use patches of examples that oracle provides I get NullPointerException.
Thank you,
Edmon

We started with the sample encoder and receiver available
here:
http://www.adobe.com/devnet/flashcom/articles/broadcast_receiver.html
Great article and sample apps!
We were broadcasting and receiving within an hour.
Then we integrated the necessary AS into our own custom
encoders and players.
Good luck!

SOAP to JMS using Sync/Async bridge - configuration confirmation needed

Hi group,
Since I'm experincing error in a scenario using sync/async bridge in jms adapter I really would like a confirmation on my configuration.
For a simple SOAP to JMS scenario is it then correct that all I need is;
1) 2 synchronous message interfaces, 1 inbound and 1 outbound
2) 1 Receiver determination
3) 1 Interface determination
4) 1 Receiver agreement (JMS adapter with module configuration)
5) 2 Sender agreements (in my case 1 soap and 1 JMS adapter - the later with module configuration).
6) The sender and receiver JMS adapters point to different MQ queues (request and response queues)
7) The sender agreement for the JMS adapter uses my synchronous, inbound message interface (isn't this really just a "dummy" to actually fetch data from response queue - meaning that the actual utilized business system/service, MI and namespace are unimportant, since the module will make the adapter notify the listening module in the receiver JMS adapter?)
Best Regards,
Daniel

Hi, thanks for your reply.
I'm familiar with the links provided. I believe everything is configured as it should be, but since I get error I would like to have my configuration confirmed. Neither the weblog (or SAP guide) are detailed enough to convince me 100% that my configuration is correct. Surely the problem could be on the MQ side, but before going into that, I want to be sure that its not on XI-side.
So I really would like confirmation on the steps/question that I wrote:-)
Best Regards,
Daniel

Use of setTimeToLive() method in JMS

Hi,
Can you please tell me the use of setTimeToLive method in JMS.
I have a code fragment like this:
QueueSender sender = queueSession.createSender(queue);
sender.setTimeToLive(60000);

As is said by the [API - doc|http://java.sun.com/products/jms/javadoc-102a/index.html] ,
It is the length of time in milliseconds from its dispatch time that a produced message should be retained by the message system.
In other words, there may be a scenario where a message sent by the QueueSender is not received by the receiver because of different cicumstances... In such case, the Message System waits for the TimeToLive milliseconds of time before the message is sent to the deadQueue.

When we should use JMS based proxy services and when JMS Adapter in OSB

Hi,
Can somebody explain me when we could go for JMS Adapter and when we should go for JMS based service in OSB?
The one scenerio i can think of is when my provider/consumer is using jms provider other than WLS jms provider we should use jms adapter.
Edited by: user12883209 on Jan 5, 2012 5:29 AM

I don't think there are clear guidelines available, however here is my view.
1) OSB 11gR1 is not certified with Oracle JMS Adapter. It is certified with Oracle FTP, Database, AQ and application adapters.
http://docs.oracle.com/cd/E21764_01/doc.1111/e15867/interop.htm#OSBAG1403
2) In addition of the Weblogic JMS, OSB can also integrate with following provider without using adapter.
- WebSphere MQ
- Tibco EMS
3) if you need to integrate JMS with BPEL Process or Oracle SOA suite composite, it has built in support for generic Oracle JMS adapter. Oracle generic JMS adapter can integrate with AQ JMS (JMS providers OJMS 8.1.7, 9.0.1.4, and 9.2), TIBCO JMS, IBM Websphere MQSeries (IBM MQSeries JMS 6.0), Weblogic JMS, Apache, and Active MQ
http://docs.oracle.com/cd/E14571_01/integration.1111/e10231/adptr_jms.htm
4) If you need to integrate OSB with Weblogic JMS, WebSphere MQ, Tbco EMS it does not need JMS adapter.
Hope this helps !!!
Jayesh Patel
http://jayesh-patel.blogspot.com/
http://www.yagnasys.com/

Use of Additional Parameters in JMS Adapter

Hi Frnds,
Can any one explain the use of Additional Parameters in JMS Adapter.
Regards,
Raj

HI,
To make additional settings or replace the default settings, enter the parameters and values in the table.
those are JMSMessageClass and JMS.Message.method.setStringProperty.
For more details.
http://help.sap.com/saphelp_nw04/helpdata/EN/10/b1b4c8575a6e47954ad63438d303e4/content.htm
Thanks.

Problem in accessing 2 certificates in smart card using Sun PKCS11 Provider

I have stored 2 certificates in iKey. To acess and use them in Java I am using Sun PKCS11 Provider.
The program is .
1. The keyStore.aliases() is returning 1 alias only(instead of 2).
2. Throwing following error when accessing the private key using
code: PrivateKey pvt = keyStore.getKey(alias, null);
Error Message Detail:
"KeyStoreException: invalid KeyStore state: found 2 private keys sharing CKA_ID 0x00"
at Sun .. P11KeyStore.getTokenObject(P11KeyStore.java:2135)
at ...P11KeyStore.engineGetKey(P11KeyStore.java:292

Did you look at this, Does it help you, Since no one has answered all day, and I will assume you searched for that error first, perhaps you could provide some more detail?
http://forum.java.sun.com/thread.jspa?threadID=5195275&tstart=15
Message was edited by:
mdares

How to retrieve public/ private from iKey token using Sun PKCS#11 provider

Dear all,
I'm trying to access one rainbow iKey 2032 token in Java 1.5 (Windows Environment) using Sun PKCS#11 provider. Token is stored with certificate. There is no problem to logging into the token using java.
     Provider p = new sun.security.pkcs11.SunPKCS11(configName);
     Security.addProvider(p);
     KeyStore ks = null;
     try{
          char[] pin = {'P','A','S','S','W','O','R','D'};
          ks = KeyStore.getInstance("pkcs11");
          ks.load(null,pin);
catch(Exception e) {}
Now I am wondering how to retrieve a public and private from token, so that I can encrypt and decrypt a plain text file. Could anyone give me a sample program for this?
Your help is very much appreciated!!

Hi Fred13
1. I have the same pkcs.cfg and get the following trace. Can you help me understand? Does this imply a bad dkck201.dll? I would really like to get this working for my implementation. tia.
lException in thread "main" java.security.ProviderException: Initialization failed
     at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:175)
     at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:76)
     at com.mkp.jce.chap1.ProviderDetail.main(ProviderDetail.java:38)
Caused by: sun.security.pkcs11.wrapper.PKCS11Exception: CKR_TOKEN_NOT_RECOGNIZED
     at sun.security.pkcs11.wrapper.PKCS11.C_GetTokenInfo(Native Method)
     at sun.security.pkcs11.Token.<init>(Token.java:105)
     at sun.security.pkcs11.SunPKCS11.initToken(SunPKCS11.java:555)
     at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:169)
2. (If I can be so indulgent of your time) Can you provide more information on cbp? I have done a search and there is little on it. It appears to be a new authentication framework tied in with sasl unique to 1.5. Any links for self education would be appreciated.

Unable to use Server UTIL to browse JMS destinations

Hello All,
I am using the following command to browse the destination in the Application server system,
java com.evermind.server.jms.JMSServerUtils -port 9129 -username oc4jadmin -password welcome1 browse jms/demoTopic
But it gives the following error (I have given the port number as 9129 as my OC4INSTANCE installed for ESB, BPEL has this port),
Oracle Containers for J2EE 10g (10.1.3.3.0) (build "070610.1800.23513"), OC4J JMS 1.1
javax.jms.JMSException: Unable to create a connection to "/0.0.0.0:9,129" as user "oc4jadmin".
at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1075)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1155)
at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:130)
at com.evermind.server.jms.EvermindConnectionFactory.unprivileged_createConnection(EvermindConnectionFactory.java:131)
at com.evermind.server.jms.EvermindConnectionFactory.access$000(EvermindConnectionFactory.java:45)
at com.evermind.server.jms.EvermindConnectionFactory$1.execute(EvermindConnectionFactory.java:114)
at com.evermind.server.jms.RemoteClientProxy.doSecureOp(RemoteClientProxy.java:94)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:111)
at com.evermind.server.jms.EvermindConnectionFactory.createConnection(EvermindConnectionFactory.java:102)
at com.evermind.server.jms.JMSServerUtils.internalScan(JMSServerUtils.java:665)
at com.evermind.server.jms.JMSServerUtils.scan(JMSServerUtils.java:640)
at com.evermind.server.jms.JMSServerUtils.main(JMSServerUtils.java:191)
Caused by: java.lang.NullPointerException
at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:152)
at com.evermind.server.jms.TCPJMSRemoteServer.initializeConnection(TCPJMSRemoteServer.java:110)
at com.evermind.server.jms.TCPJMSRemoteServer.<init>(TCPJMSRemoteServer.java:68)
at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:122)
... 9 more
Please let me know where is the issue ?
I am able to log onto application server using those credentials.
Thanks
Nags.

Hi Gurus,
I am facing similar problem as the first post in this thread.
I have created a file persistent queue called TRAINING_FILEPERSIST_QUEUE, and have inserted a message in it( verified using the JMX browser).
Here is the message it shows
<textmessage>
<header>
<JMSCorrelationID value="" />
<JMSDeliveryMode value="PERSISTENT" />
<JMSDestination value="Queue[TRAINING_FILEPERSIST_QUEUE]" />
<JMSExpiration value="0" />
<JMSMessageID value="ID:Oc4jJMS.Message.personal.6e320096:12287e016b3:-8000.1115" />
<JMSPriority value="4" />
<JMSRedelivered value="false" />
<JMSReplyTo value="null" />
<JMSTimestamp value="1247841141640" />
<JMSType value="" />
</header>
<properties>
<string key="JMSXConsumerTXID" value="" />
<int key="JMSXDeliveryCount" value="1" />
<string key="JMSXProducerTXID" value="" />
<long key="JMSXRcvTimestamp" value="1247844938531" />
<string key="JMSXUserID" value="oc4jadmin" />
<string key="JMS_OC4J_Type" value="textmessage" />
</properties>
<textbody>
<string value="Ponting,m,30
Waugh,m,30
Bradman,m,35
" />
</textbody>
</textmessage>
Now I am using the following command in the developer prompt to browse the queue:
java com.evermind.server.jms.JMSServerUtils -port 12602 -username oc4jadmin -password welcome1 browse TRAINING_FILEPERSIST_QUEUE
but it gives the following error
Oracle Containers for J2EE 10g (10.1.3.1.0) (build "061008.0900.00025"), OC4J J
MS 1.1
javax.jms.JMSException: TRAINING_FILEPERSIST_QUEUE: destination "Connection[Oc4j
JMS.Connection.personal.17685f93:122895c9c84:-8000.1]" is unknown in connection
"{2}".
at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1072)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1152)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1123)
at com.evermind.server.jms.JMSServerUtils.internalScan(JMSServerUtils.ja
va:672)
at com.evermind.server.jms.JMSServerUtils.scan(JMSServerUtils.java:640)
at com.evermind.server.jms.JMSServerUtils.main(JMSServerUtils.java:191)
Any idea what am I doing wrong.

Can BEA JMS C APIs be used to communicate with other JMS servers?

Hello,
          Can BEA JMS C APIs be used to communicate with other JMS servers?
          If yes, is it enough to download, compile the JMS C APIs, and link the C applications to the libraries (shared or static) produced?
          If not, can you point me to an open source framework that can be used to enable C applications to communicate with JMS servers?
          I have HP-UX server that has both C and Java compilers (Java 1.5).

The JMS C client is a pre-compiled library - we don't supply the source - so C applications link to it. If I recall correctly, there is an HP version. The C client library is actually thin layer that uses JNI to directly invoke a Java JMS client running in an embedded JVM.
          The library might work with other vendor's Java JMS clients, but BEA does not officially support this usage.
          Tom

ClassCastException in my WS over JMS using JAX-RPC in WLS 10.3...

Hi,
I am developing a WS over JMS using JAX-RPC in WLS 10.3 (I tried both WLS 10.3.0 and 10.3.1). And when WLS is trying to marshal the response, it throws "ClassCastException":
ava.lang.ClassCastException: org.tmforum.mtop.nrf.xsd.com.v1.EquipmentHolderEnumType cannot be cast to java.lang.String
at com.bea.staxb.runtime.internal.StringTypeConverter.print(StringTypeConverter.java:45)
at com.bea.staxb.runtime.internal.SimpleContentBeanMarshaller.print(SimpleContentBeanMarshaller.java:52)
at com.bea.staxb.runtime.internal.RuntimeBindingProperty.getLexical(RuntimeBindingProperty.java:154)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeCharData(PushMarshalResult.java:639)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:413)
at com.bea.staxb.runtime.internal.SimpleContentRuntimeBindingType.accept(SimpleContentRuntimeBindingType.java:46)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:400)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalType(PushMarshalResult.java:153)
at com.bea.staxb.runtime.internal.PushMarshalResult.visitProp(PushMarshalResult.java:631)
at com.bea.staxb.runtime.internal.PushMarshalResult.visit(PushMarshalResult.java:403)
at com.bea.staxb.runtime.internal.ByNameRuntimeBindingType.accept(ByNameRuntimeBindingType.java:89)
at com.bea.staxb.runtime.internal.PushMarshalResult.writeContents(PushMarshalResult.java:195)
at com.bea.staxb.runtime.internal.PushMarshalResult.marshalTopType(PushMarshalResult.java:96)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalBindingType(MarshallerImpl.java:302)
at com.bea.staxb.runtime.internal.MarshallerImpl.marshalElement(MarshallerImpl.java:383)
at weblogic.wsee.bind.runtime.internal.LiteralSerializerContext.marshalElement(LiteralSerializerContext.java:82)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.internalSerializeElement(BaseSerializerContext.java:197)
at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeElement(BaseSerializerContext.java:128)
at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:322)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:228)
at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:215)
at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:134)
at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:134)
at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:104)
at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:51)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:287)
at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:271)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:341)
at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:189)
at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80)
at weblogic.wsee.server.jms.JmsWebservicesMessageDispatcher.dispatchMessage(JmsWebservicesMessageDispatcher.java:175)
at weblogic.wsee.server.jms.JmsQueueListener.processMessage(JmsQueueListener.java:397)
at weblogic.wsee.server.jms.JmsQueueListener.onMessage(JmsQueueListener.java:392)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
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)
The "EquipmentHolderEnumType" is generated JAXB object (obviously it is not a String) from WSDL using WLS wsld generation. And here is how that Enum is defined in XSD:
<xsd:simpleType name="EquipmentHolderEnumType">
<xsd:annotation>
<xsd:documentation>
<p>Equipment holder type</p>
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="MINOR_EXT"/>
<xsd:enumeration value="rack"/>
<xsd:enumeration value="shelf"/>
<xsd:enumeration value="sub_shelf"/>
<xsd:enumeration value="slot"/>
<xsd:enumeration value="sub_slot"/>
<xsd:enumeration value="remote_unit"/>
<xsd:enumeration value="remote_slots"/>
</xsd:restriction>
</xsd:simpleType>
My question is why WLS is trying to cast the EnumType to String when marshalling it? How can I fix this exception?
Also, second question: my WS will take some time to get the response ready (1+ minute). I was using WLS console test client to test my WS. And the test client always got time out:
java.io.IOException: Request timed out
at weblogic.wsee.connection.transport.jms.JmsTransport.receive(JmsTransport.java:356)
at weblogic.testclient.WebServiceOperation.invokeJms(WebServiceOperation.java:463)
at weblogic.testclient.WebServiceOperation.addWeblogicHeadersAndInvoke(WebServiceOperation.java:382)
at weblogic.testclient.WebServiceOperation.invokeComplex(WebServiceOperation.java:305)
at weblogic.testclient.WebServiceOperation.invoke(WebServiceOperation.java:626)
How can I configure the WLS console test client so that I can increase teh timeout setting for the client?
Thank you very much!
Jian

Hi, pls how did you solve your problem exatly? Because I have similar problem without solution.
I have WSDL contract like:
<xs:element name="duration">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="durationType">
<xs:attribute name="days" type="xs:int" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<xs:simpleType name="durationType">
<xs:restriction base="xs:string">
<xs:enumeration value="PERIODIC"/>
<xs:enumeration value="PERPETUAL"/>
<xs:enumeration value="CREDIT_DAYS"/>
</xs:restriction>
</xs:simpleType>
And client site generated by WLS ant task "generate-from-wsdl" with "JAXRPC" option and when I use calling of this client and exeption was appeared:
FaultString [com.company.DurationType] FaultActor [null] Detail [<detail><java:string>java.lang.ClassCastException: com.company.DurationType</java:string></detail>];
Note: all other messages are correct.
thx

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

How to create a JMS queue linked to external (remote) JMS server?

Hello,
I'm trying to receive messages from a remote JMS queue. I found some information on the Internet on how to create an external JNDI resource (my remote JMS queue connection factory is bound to LDAP context on remote box). I was able to configure JNDI resource that points to remote queue connection factory, but I don't know what to do next.
How can I create a local JMS destination (queue) that will be the image of the remote queue? At least I'm guessing this is what needs to be done in order to deploy MDBs.
I would appreciate it if someone could tell me how to get this working. Maybe the steps I took were not in the right direction - the bottom line is that JMS queue and queue connection factory are deployed on a remote server, and I need to get messages sent to them on the local server. I'm using Sun App Server from J2EE 1.4.
Thank you,
Mark

Please refer to http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6377822, particularly the evaluation. Could your situation be the same too (i.e server ip address changing dynamically)? Also, which OS are you using and do you have any firewalls setup that prevents access to port 3700?

JMS : Using SUN MQUEUE as a JMS Provider

Similar Messages

Maybe you are looking for