JMS in J2EE

I have tried to modify the JMS example in /jms/clientmdbentity folder and it works fine. But what I have tried to convert from Container-managed-persistence into Bean-managed-persistence bean and it does not work. And I really don't understand the error message, it says something like this: can not add another resources ....
I also tried a simple java class which access both database resource and jms resource and the error is similar, if anyone can help that would be great.
Thanks

I have to create new jdbc resource which used XA Datasource (PointbasePool) and it works OK now. I only doing this in order to have a better understanding the JMS. Thanks anyway.

Similar Messages

JMS & Tomcat & J2EE

hi all
I would like to run JMS with Tocmat 4.1.24. and SUN J2EE.
I encountered following problem.
three days .... I can't solve this problem.
there is a lot of this question in this forum. but no answer. so I try to again.
this is very important to me....sample code is basic sample in JMS tutorial.
personally, It's very important to me.
thanks in Advance.
following error ->
javax.naming.NameNotFoundException: Name QueueConnectionFactory is not bound in
this Context
at org.apache.naming.NamingContext.lookup(NamingContext.java:811)
at org.apache.naming.NamingContext.lookup(NamingContext.java:194)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.safeidentity.ps.auth.TestJMS.doGet(TestJMS.java:31)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:247)

it's all very well having Tomcat, but it's not JMS Server. You need to have a JMS Server running, which is what your application should be 'looking up'. Try the open source OpenJMS (http://openjms.sourceforge.net). Once the JMS server is running (which is what creates the JNDI context) you will then be able to find/bind to it.

Connecting JMS to J2EE Reference Implementation 1.3 beta

Is it possible to write JMS client talking with J2EE server without having in path j2ee.jar? Something like remote small client communicating with the server due JMS? Do I have to use some third party
software (I have swiftMQ in mind) for this? If somebody have configuration for swift bridge to J2EE
Refernce Implementation can you share it?

The JMS service provider that comes with J2EE SDK 1.3 is only a reference implementation of the JMS API.
In a real application system, one will be using a JMS service provider from some vendor. Preferably one that is certified to be J2EE compatible.
In fact, this is true as such for anything in j2ee.jar Through j2ee.jar, Sun provides a reference implementation of J2EE APIs with its J2EE SDK and in a real application one will not have j2ee.jar in the client or server classpath. Instead one will use jar files specific to the vendor that one has chosen.
Specifically about swiftMQ, as per Sun, it is not a J2EE licensee. swiftMQ is JMS 1.0.2 compliant. But it is not certified to be J2EE compatible.
Refer http://java.sun.com/products/jms/nonlicensedvendors.html for more details.

Small weblogic.jar for jms/j2ee clients of weblogic

          We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          I attempted to use the whitepaper document distributed by BEA for creating a smaller
          jar file, but it did not work. Has anyone else in the user community successfully
          created the jar file and if so could they give me some insight on how they did
          it.
          Thanks,
          Ashish


Hi Ashish,
          I've personally used the "URL" class loader option with success,
          and I know that several customers have also used this option, as
          well as the other options for years. Feel free to
          post more detail than "it did not work", and I may be able
          to help you out.
          Tom, BEA
          P.S. If 8.1 is an option, you may with to consider using the
          thin client jars it supplies.
          Ashish Bisarya wrote:
          > We are trying to create a smaller footprint for the ~38M weblogic.jar for distribution
          > to our client applications to use the JMS and J2EE features of Weblogic 7.0sp2.
          > I attempted to use the whitepaper document distributed by BEA for creating a smaller
          > jar file, but it did not work. Has anyone else in the user community successfully
          > created the jar file and if so could they give me some insight on how they did
          > it.
          >
          > Thanks,
          > Ashish

How to enable JMS to be J2EE Compliant from within JVM

I am wondering how I can use JMS in J2EE compliant mode from within the JVM via a Java stored procedure.
I know that I can set a property (i.e. oracle.jms.j2eeCompliant="true") at execution time, but was wondering how I can make the entire JVM J2EE compliant.

You cannot make the JVM J2EE compliant! However, you can use some J2EE APIs such as JMS, on top of J2SE.
See a basic use of JMS in Java stored procedure
http://otn.oracle.com/sample_code/tech/java/jsp/samples/jms/Readme.html
Note: the main purpose of JMS support within the database is to integrate with AQ.
Kuassi

Getting the below error while using the JMS server.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160064> <There was an error while making the initial connection to the JMS resource named EMSTopicFactoryNonXA from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory EMSTopicFactoryNonXA failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
<Sep 20, 2010 9:27:43 AM EDT> <Warning> <J2EE> <BEA-160082> <There was an error while making the initial connection to the JMS resource named com/lehman/fit/ice/agg2/TopicConnectionFactory from the EJB "Agg2BatchBean" inside application "Agg2". The server will attempt the connection again later. The error was javax.jms.JMSException: [J2EE:160048]JNDI lookup of the JMS connection factory com/lehman/fit/ice/agg2/TopicConnectionFactory failed: javax.naming.AuthenticationException: Not permitted: invalid name or password [Root exception is javax.jms.JMSSecurityException: invalid name or password]>
Note:-weblogic version 9.1sp0
Please suggest me how to resolve the above exception.

The pooled JMS session is enlisted in another transaction error

I have an MDB with pool size 2 deployed in weblogic 9.2.3(linux). I see the following error in server logs.
<May 27, 2009 7:32:26 AM CDT> <Error> <EJB> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: javax.jms.JMSException: [J2EE:160054]The pooled JMS session is enlisted in another transaction and may not be used elsewhere
The exception is : javax.jms.JMSException: [J2EE:160054]The pooled JMS session is enlisted in another transaction and may not be used elsewhere
     at weblogic.deployment.jms.JMSExceptions.getJMSException(JMSExceptions.java:22)
     at weblogic.deployment.jms.WrappedTransactionalSession.enlistInTransaction(WrappedTransactionalSession.java:196)
     at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:198)
     at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:297)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:517)
     at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:533)
     at java.lang.Thread.run(Thread.java:595)
>
any idea why this error is coming??

Looks it is like a bug, you can ask patch for from support.

Language support in JMS adapter with Oracle JDev 10.1.3.1

Hi,
I' using JDeveloper 10.1.3.1 with Oracle SOA Suite - ESB 10.1.3.1 in the following scenario:
1) Use Database adapter with "on insert" condition to read Student record with Chinese name (Unicode format) - ESB process
2) Use JMS adapter to push this data into "DemoTopic" as string - ESB process
3) Use Message Driven Bean's (EJB 3.0) "onMessage" method to fetch the data from JMS topic - J2EE app
4) Use JDBC executeUpdate to update this Chinese name into another database table - J2EE app
5) Finally, verify the updated Chinese name in ADF application - J2EE app
Prerequisites
1) The database charset on both sides of the flow is UTF8
2) The ADF application JSF page encoding is UTF8
3) The SOA Suite is installed on DB repository (UTF8 charset)
Result
1) The flow from Step 1-5 works.
2) But, the println of the JMS message (holding the Chinese name) gives "????" when checked with Wordpad (Unicode readable word processor)
3) Junk characters are inserted into the database
Please let me know where I'm going wrong. Also, let me know if I need to configure/set the character encoding in OC4J, or the JMS adapter and how.

Hi all,
This is been resolved by using the AL32UTF8 character set in the database. JMS adapter by default supports UTF-8. No setting/configuration needs to be done.

JMS queue question

Hi all,
I am using Weblogic Application Server and say I have 1000 messages in a JMS Queue say "Q1".
Q1. How are these messages picked up from the queues? i.e. by a thread etc.
Q2. If they are picked up by threads then who configures these threads? Are they default threads created by the Weblogic Application Server or are user-created threads?
Q3. Also, if 20 threads are involved in picking the messages from the queue and of them one thread snaps while picking the message then what will happen? and what will be the solution??
Thanks.

Q1/Q2*:
The answer to your question is "its provider specific".
You will need someone who explicitly works on weblogic to provide specifics so you may want to utilize a weblogic specific forum instead of a generic JMS forum
I'll try to answer this in very generic terms that should apply to all providers:
If you are receiving messages with an MDB: there is a thread pool associated with the resource adapter which plugs the JMS provider into the server. This is generally configured as part of the application server configuration. That pool dictates the maximum number of threads which can call the same MDB's at the same time.
If you are receiving messages with a Servlet: In this case, you are probably calling receive within the servlet. That will use the thread provide by the webstack which is executing the servlet
If you are receiving messages in an AppClient or Standalone provider: You are using your own thread if you call receive(), or a thread provided by the provider if you are calling onMessage()
In all cases, the provider may be allocating additional threads "beneath the covers" to process those messages.
Q3*:
I'm not quite sure what snaps means. Threads run until they exit. I'm going to guess that the question is "what if the MDB or code throws a RuntimeException". If you mean something different, please supply a more specific description of the error.
This one depends on what whether or not you are using transactions and how you are receiving those messages.
If you are using transactions in an MDB: the transaction will rollback and the message will be redelivered to another consumer.
In all other cases, it depends on the specifics (I was going to list them but it seems like to much work for a Friday afternoon).
If you are using a non-transacted or non-MDB method to retrieve the messages, let me know and I can tell you how, per the JMS and J2EE specs, it should work. I'll need to know acknowledge mode/transaction, type of client and if you are calling receive() or onMessage().
-- Linda

Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'

Hi
When executing import/export service through FSM we are getting below error on server console. Can someone please help us to resolve this.
<Nov 22, 2012 10:25:14 PM IST> <Error> <oracle.j2ee.ws.common.jaxws.JAXWSMessages> <BEA-000000> <[MessageID: uuid:3eac9f32-ad81-4d96-b5b2-18cf0fd887c0[migRequestId=300100015300332][migObjectId=300100015300326][]] Could not send async request message to the JMS queue.
java.security.PrivilegedActionException: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:373)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
at weblogic.security.Security.runAs(Security.java:61)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:51)
at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:56)
at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:365)
at oracle.j2ee.ws.server.jaxws.JMSChannel.getConnection(JMSChannel.java:468)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendMessage(JMSChannel.java:235)
at oracle.j2ee.ws.server.jaxws.JMSChannel.sendRequest(JMSChannel.java:199)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate$JMSMessageQueue.send(AsyncServiceRuntimeDelegate.java:170)
at oracle.j2ee.ws.server.jaxws.AsyncServiceRuntimeDelegate.pro
Caused By: javax.naming.NameNotFoundException: Unable to resolve 'oracle.j2ee.ws.server.async.DefaultRequestQueue'. Resolved 'oracle.j2ee.ws.server.async'; remaining name 'DefaultRequestQueue'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
FYI:
The "oracle.jrf.ws.async_template_11.1.1.jar" jar file required for JMS (oracle.j2ee.ws.server.async.) which is present in below directory path of weblogic standalone.
Edited by: user12820425 on Dec 2, 2012 11:56 PM

Are you using Standalone (or) Integrated WLS. It works only on Standalone WLS.
Also for these issues, please put this in Cross Pillar Integration Forum. Contact Ning.Dong

JMS with Eclipse

HI
I downloaded the example for JMS for J2EE 5. But I see these examples are developed in Netbeans... and the problem is particularly during compilation using ant... which depends on NetBeans. How do I proceed with running these examples in Eclipse?

could you describe the necessary changes in details? I met the same problem as yours. but connectionFactory or queue cannot be retrieved with " @Resource(mappedName = "jms/ConnectionFactory")". could you help me ?

AQ and JMS - Oracle XA exception when trying to read message

I'm trying to setup Oracle AQ as a foreign JMS provider. I've setup the DipsAQXAQueueConnectionFactory and DipsAQDestination in the JNDI of my weblogic server according to the sample posted by Eric Ma. This works ok and prints out the following on server startup....
          The arguments are :
          {JNDIServerPort=7001, QueueJndiName=AQJMSQueue, JNDIServer=localhost, AQueueName=DIPS_AQJMS_QUEUE, S
          erver=147.209.179.194, Port=15005, AQueueTableName=DIPS_AQJMS_TEXT, Instance=dev39, DriverType=oci8,
           MessageType=SYS.AQ$_JMS_TEXT_MESSAGE, FactoryJndiName=AQJMSConnectionFactory}
          The XA queue connection factory and queue is bound to the WLS JNDI Tree !
          My MDB ejb is configured as follows...
          * @ejbgen:message-driven default-transaction="Required"
          * ejb-name = FmcDispatch
          * destination-jndi-name = AQJMSQueue
          * destination-type = javax.jms.Queue
          * @ejbgen:foreign-jms-provider initial-context-factory="weblogic.jndi.WLInitialContextFactory" provider-url="t3://localhost:7001"
          * connection-factory-jndi-name="AQXAJMSConnectionFactory"
          public class FmcDispatch
          extends GenericMessageDrivenBean
          implements MessageDrivenBean, MessageListener
          The problem is, when the above EJB is deployed, I'm always getting the following exceptions...
          >
          <14/02/2006 11:21:03 AM EST> <Error> <EJB> <BEA-010079> <An error occurred while attempting to recei
          ve a message from JMS for processing by a message-driven bean: [EJB:010196]'javax.jms.JMSException:
          [J2EE:160049]An error occurred while registering the JMS connection with JTA: javax.transaction.Syst
          emException: start() failed on resource 'weblogic.ejb20.JMSConnectionPoller.FmcDispatch': XAER_RMERR
          : A resource manager error has occured in the transaction branch
          oracle.jdbc.xa.OracleXAException
          at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1184)
          at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
          The exception is : javax.jms.JMSException: [J2EE:160049]An error occurred while registering the JMS
          connection with JTA: javax.transaction.SystemException: start() failed on resource 'weblogic.ejb20.J
          MSConnectionPoller.FmcDispatch': XAER_RMERR : A resource manager error has occured in the transactio
          n branch
          oracle.jdbc.xa.OracleXAException
          at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1184)
          at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:311)
          at weblogic.deployment.jms.WrappedXAResource_oracle_jdbc_xa_client_OracleXAResource.start(Un
          known Source)
          at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1145)
          at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1077
          at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:240)
          at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.
          java:449)
          Any ideas?

Oracle home is pointing to wrong location.When we made the change to corrent location.Then we rebuilt the jar file started the managed server it is working fine.

JMS Performance/Design

Hi,
I am new to JMS and J2ee and I need some guidance, if anyone can help me plz.
I am building a new application where I might have a very large number of clients (hundred of thousands possibly) exchanging messages with a server and between them.
I was using sockets and serialization to handle that but it was ok for small number of users only.
so First I need a robust server that can handle a large number of users, since I have a limited budget I was thinking to use JBoss since it's open sourse and free, is this a good choice or is it better to get weblogic or websphere, etc..?
Every client who logs in can communicate to the server and exchange messages or (objects).
When a client wants to talk to another client, he does that through the server too of course.
I am thinking to use JMS (message beans) to exchange messages between the server and clients, or between the clients themselves (synchronously/asynchronously). I need to find what is the best implementation/design that will have the better performance and to avoid bottleneck on the server ?
should I create a message bean for each client on the server when he logs in to handle the communication between this client and the server and keep it until he logs out?
or should all clients subscribe to the same message bean (or service) on the server?
if the client starts a communication with another client, should I open a session for only the 2 of them? or the same bean they are subscribed to will handle that?
I was thinking to use publisher/subscriber but if there is a huge amount of trafic going on between these clients, how can the server handle all these requests quickly?

Hi,
Thank you for the reply.
I know that the system is not that easy, that's why I am looking for help :)
The software itself consists of client application and server side application, the comuunication part is similar to yahoo messenger, but a user can be behind a local server/firewall (mainly if it's a company) or use the public server .
the requirements are the following:
-The client side application is downloaded from the web-site of our company.
-The application communicates to our company's server for updates and other services (same way as window updates itself by contacting microsoft server).
-a corporate might decide to buy/download our server application in order to establish a local secure server rather than being on our public server.
-The client might be member of the local server of his company (behind a firewall of course) but he also still can communicate to our public server for updates.
(same way if you have a windows client part of a local server and he still can contact Microsoft for updates)
-A Client can search the local server or our server for other clients/users and add them to his friends list (like yahoo)
-The user will be notified (if he likes) when a friend goes online or offline
-The user can send/receive data from his friends. (the data is not big maybe maximum a couple hundred KB , the worse case is maybe 1/2 MB)
They told ma about JXTA and I am looking at it, any better ideas ?
Regards
George

Instance missing in BPEL console

Hi,
I have a process say "THIRD", it has database adapters and exception handling for each scope as well. In the case of any exception in "THIRD", the process calls the another process say "EMAIL" which is only meant for e-mail notification.
Now the situation:
When sometimes the process name "THIRD" is invoked from client(Oracle Apps/BES) first time in the morning and if any of the DB adapter throws exception, the instance of "EMAIL" is created and send the mail too. But if we try to find out the instance of "THIRD" which cause the problem is missing in BPEL Console.
Moreover, it happens only first time in the morning and doesn't happen everyday.
Thanks in advance.
---Janit

Is your BPEL deployed on OC4J?
Described property is here
<ORAHOME>\integration\orabpel\system\appserver\oc4j\j2ee\home\config\server.xml
restart OC4J. Check also BPEL domain parameter syncMaxWaitTime (From BPEL Console-> Manage BPEL Domain). syncMaxWaitTime should be less than transaction-config timeout. Otherwise it is not working properly.
<snip>
<?xml version="1.0"?>
<!DOCTYPE application-server PUBLIC "-//Oracle//DTD OC4J Application-server 9.04//EN" "http://xmlns.oracle.com/ias/dtds/application-server-9_04.dtd">
<application-server application-directory="../applications"
check-for-updates="false"
deployment-directory="../application-deployments"
connector-directory="../connectors"
>
     <rmi-config path="./rmi.xml" />
     <jms-config path="./jms.xml" />
     <j2ee-logging-config path="./j2ee-logging.xml" />
     <log>
          <file path="../log/server.log" />
     </log>
     <transaction-config timeout="60000" />
</snip>

Spring DefaultMessageListener, OC4J , AQ and XA

Greetings:
We are accessing our XA connection Factory through a JCA Resource Adaptor in order to read from a queue residing in AQ.
The difference is that we are using the SpringDefaultMessage Listener instead of a MessageDrivenBean
Each time the listener polls we get:
javax.jms.JMSException: Not supported in XA-backed session outside global transaction
Also, when we set the DML property "concurrentConsumers" to a value higher than one, we get this error:
javax.jms.JMSException: J2EE 1.4 does not allow multiple JMS sessions per connection
We have had this configuration working through the Oracle Filebased Resource Adaptor (OracleASjms) but the trouble started when we switched to AQ.
Any help would be appreciated.
We are using OC4J 10.1.3.4
Database 10.1.5
Spring 2.5.6
Edited by: user5390357 on Jan 13, 2009 11:47 AM

I am not familiar with Spring, but I can comment from the JMS standpoint:
Each time the listener polls we get:
javax.jms.JMSException: Not supported in XA-backed session outside global transactionThis is probably because Spring uses unmanaged threads that are not infected with the current transaction information. Starting OC4J with "-userThreads" might solve this problem.
Also, when we set the DML property "concurrentConsumers" to a value higher than one, we get this error:
javax.jms.JMSException: J2EE 1.4 does not allow multiple JMS sessions per connectionOracle JMS Connector aka generic Resource Adapter implements J2EE/JCA. Resource Adapter concept deals with different transaction resources such as JDBC and JMS. In JDBC, transaction context is a Connection. In JMS, it is a Session. As the greatest common denominator J2EE allows one transactional context per Connection. Which means for a JMS RA: at most one session per managed connection, which is aparently violated when you use "concurrentConsumers" > 1 (i.e. more than one concurrent session on the same connection). This is not different for OC4J JMS (OracleASjms), but you probably bypassed the resource adapted and used resource provider instead. You can do the same with AQ, make sure you use JDBC URL instead of datasource.
This is the example from my colleague Qiang:
<resource-provider name="ourAqXaResourceProvider" class="oracle.jms.OjmsContext">
<property name="url" value="jdbc:oracle:thin:@ourHost:1521:ourSid />
<property name="username" value="AQ_USER"></property>
<property name="password" value="password1"></property>
</resource-provider>
{code}

JMS in J2EE

Similar Messages

Maybe you are looking for