Without JMS Providers??

Can I write my own Queue application and run it in a app server using the required jar files (jms.jar and jndi.jar ) without using any specific JMS providers.

What app server are you using? JBoss, WebSphere, WebLogic, Sun One etc all have JMS implementations.
If you're using a servlet container (e.g. Tomcat) then you'll need to use a third party JMS Provider such as ActiveMQ. Some JMS Providers (such as activemq) allow you to embed them in your web app, so you don't need to install and start a separate server.

Similar Messages

Dead message queue - DLQ for foreign JMS providers

Is there a way to configure Error-queue or 'Dead message/letter queue' in MDB listening to foreign JMS provider like JBoss? (Automatic routing of failed messages to error-queue after specified retries to preserve JMS messages)
          I did all the docs from BEA and it doesn't cover this DLQ for foreign JMS providers :). For Weblogic JMS service, DLQ can be configured in the config.xml. But for <ForeignJMSServer> there is no way to configure dead-queue.
          Could some please validate this before I start coding this piece in the application instead of appserver configuration.
          JMS provider is Tibco and JMS destinations are pre-defined and can't/doesn't need to be created
          Thanks in advance.

Interesting idea! But no, there's no facility for redirecting failed foreign provider messages to a DLQ. This is a feature normally supplied by the foreign provider itself.
          Some foreign providers, in addition to WebLogic 9.0 JMS, provide a "redelivery count" property in the message. If the foreign provider provides no automatic DLQ capability, you might be able to leverage this property to have your MDB application code automatically forward messages with high redelivery counts to the DLQ.
          Tom

How to invoke the mdb without jms client

Hi,
I have a requirment in that I want to invoke the message driven bean without jms client.
ejb 2.1 support this but I don't know how.
if any one have an idea pl reply this.
thanks

Ino I did not mean invoke MDB without sending a message, but I want to say invoking the mdb by some other like jaxm client or soap client.
if u have any idea pl tell me.
thanks
manish

Using foreign JMS providers with wls

does anybody have a clou, where i can find that article, i think it's
          by steve felts on using foreign JMS providers with wls? i think the
          link on dev2dev is broken?


The new article is called "Using Foreign JMS Providers with WLS" and it's
          here:
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          greg
          "leopld goess" <[email protected]> wrote in message
          news:[email protected]..
          > does anybody have a clou, where i can find that article, i think it's
          > by steve felts on using foreign JMS providers with wls? i think the
          > link on dev2dev is broken?

Integrating JMS providers with JBoss

Hi.
I am trying to integrate a foreign JMS provider to JBoss. I looked at the docs and all - and even managed to deploy an mbean that puts the factories and queues into the jndi - after which anyone who does a lookup() on it is capable of using the foreign provider.
However, trying to put an MDB - it doesn't work anymore. the MDB does not register itself on the destination it's supposed to - and therefore never receives the messages. The documentation is not very clear about how to do all that - does anyone have any experience with that?
Thanks, Nimo.

Hi Nimo,
Many of the most popular JMS providers (such as ArjunaMS, SonicMQ and FioranoMQ) provide various integration facilities with JBoss. I just did a Google site search and found information on all of the above how to integrate those providers with JBoss:
ArjunaMS Google search was:
site:www.arjuna.com jboss
Best hit:
http://www.arjuna.com/products/jboss/
SonicMQ Google search was:
site:www.sonicsoftware.com jboss
Best hit:
http://www.sonicsoftware.com/cgi-bin/sonic.cgi/dx_results.w?subcategory=23
FioranoMQ Google search was:
site:www.fiorano.com jboss
Best hit:
http://www.fiorano.com/downloads/fmq/FMQFaqs.pdf (pg 73 provides refers to JBoss integration information in a "Developer's Guide" - I guess this must be in a download of the product?)
Hope this helps you!
Cheers,
Tom Jenkinson
Arjuna Technologies Limited

Whitepaper on foreign JMS providers

The white paper that I posted a little while ago on integrating WLS 7.0 with
          foreign JMS providers is now available on the "dev2dev" website. You can use
          this link:
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          and click on "Using foreign JMS providers with JMS".
          And you can also use this:
          ftp://edownload:[email protected]/pub/downloads/jmsproviders.pdf
          greg


The white paper that I posted a little while ago on integrating WLS 7.0 with
          foreign JMS providers is now available on the "dev2dev" website. You can use
          this link:
          http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
          and click on "Using foreign JMS providers with JMS".
          And you can also use this:
          ftp://edownload:[email protected]/pub/downloads/jmsproviders.pdf
          greg

Foreign JMS Providers with WebLogic Server does not close connection

          Hello All,
          We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
          WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
          context factory to bind MQ.
          We found a number of LDAP connections are getting opened by JNDIMapper, but it's
          not getting closed.
          Can some one give some clue to this ?
          Also any suggestion to serve the current purpose is welcome.
          Thanks,
          Sudarson


What version are you using? "wlsmqseries.zip" does enlisting of MQ JMS
          sessions in XA transactions, but WLS 8.1 does that for you out of the box.
          If you're using 8.1, it would be better to use the new 8.1 features for
          foreign JMS providers.
          A place to start is the "Using WebLogic JMS with EJBs and Servlets" section
          of the JMS programming documentation for 8.1, and there have been many other
          posts on this newsgroup with details. (There also appear to be quite a few
          customers using this feature in their own systems, judging from the number
          of posts.)
          greg
          "sudarson" <[email protected]> wrote in message
          news:40bf05ea$1@mktnews1...
          >
          > Reposting the message. Awaiting response from newsgroup or BEA
          > Thanks,
          > Sudarson
          > "sudarson" <[email protected]> wrote:
          > >
          > >Hello All,
          > >
          > >We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for
          integrating
          > >WebLogic Server with MQ so that we can incorporate XA transactions. We
          > >use LDAP
          > >context factory to bind MQ.
          > >
          > >We found a number of LDAP connections are getting opened by JNDIMapper,
          > >but it's
          > >not getting closed.
          > >
          > >Can some one give some clue to this ?
          > >
          > >Also any suggestion to serve the current purpose is welcome.
          > >
          > >Thanks,
          > >Sudarson
          >

Integrate third party JMS providers with sunone 8

Hi,
I am trying to integrate a JMS provider, FioranoMQ with Sunone Application server (version 8). I have defined an external queue connection factory using the administration console. But I am not able to deploy the EJB as the exception in server.log says that queue connection factory does not exist.
Here is the stack trace of the exception
[com.sun.enterprise.connectors.ConnectorRuntimeException: jms_MyQcfis not created yet!]|#]
[#|2004-01-06T15:43:55.312-0800|SEVERE|j2ee-appserver1.4|javax.enterprise.system.container.ejb.mdb|_ThreadID=11;|com.sun.enterprise.connectors.ConnectorRuntimeException
com.sun.enterprise.connectors.ConnectorRuntimeException: jms_MyQcfis not created yet!
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.setValuesFromConfiguration(ActiveJmsResourceAdapter.java:316)
     at com.sun.enterprise.connectors.system.ActiveJmsResourceAdapter.updateMDBRuntimeInfo(ActiveJmsResourceAdapter.java:259)
     at com.sun.enterprise.connectors.inflow.ConnectorMessageBeanClient.setup(ConnectorMessageBeanClient.java:139)
     at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:189)
     at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:196)
     at com.sun.enterprise.server.AbstractLoader.loadEjbs(AbstractLoader.java:464)
     at com.sun.enterprise.server.ApplicationLoader.load(ApplicationLoader.java:129)
     at com.sun.enterprise.server.TomcatApplicationLoader.load(TomcatApplicationLoader.java:96)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:205)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:156)
     at com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:466)
In case I again try to create the jms_myqcf , it says that resource already exists.
The resource reference defined in the xml files are
Sun application client.xml
=====================
<sun-application-client>
<resource-ref>
<res-ref-name>jms_myqcf</res-ref-name>
<jndi-name>jms_myqcf</jndi-name>
<default-resource-principal>
<name></name>
<password></password>
</default-resource-principal>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>jms_MyQueue</resource-env-ref-name>
<jndi-name>jms_MyQueue</jndi-name>
</resource-env-ref>
</sun-application-client>
Sun EJB JAR.XML
===============
<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
<ejb-name>SimpleMessageEJB</ejb-name>
<jndi-name>jms_MyQueue</jndi-name>
<mdb-connection-factory>
<jndi-name>jms_myqcf</jndi-name>
</mdb-connection-factory>
</ejb>
</enterprise-beans>
</sun-ejb-jar>
Do you have any idea why this exception is thrown?
James

You are right that I am using j2ee 1.4 final release.
I donot know much about connector 1.5 resource adapter and donot have one. Is there no other way that i can integrate an external JMS provider with sunone?
I intend to do the following.
- define the connection factory object & destination object in the external JNDI or any JNDI of sunone so that the applications can lookup these objects.
- Now i want to deploy a MDB which creates connection using the conn factory and listens for messages on destination defined in the jndi in the first step.
Thats all i want to do. Do you know which is the easier and best approach to do that?

Transaction with third party JMS providers and ejb

          I am using a container managed stateless session bean to send messages to an ibm
          mqseries running on the same computer. The EJB is deployed on weblogic 7.0. It
          seems that sending JMS messages do not participate in the transaction and that
          I have to call queueSession.commit() explicity every time. However, receiving
          messages via Message Driven Beans in a transaction is not a problem. Any clue
          how to resolve this or what is happening?


To do this today, you'd have to get the "XAResource" object from your JMS
          provider's XASession object, and register it with JTA. I know this has come
          up before, and you should be able to find more about this on the newsgroup.
          Basically, every time you send a message, you need to do something like
          this:
          import javax.jms.*;
          import javax.transaction.*;
          XASession xaSession; // This is your vendor's XASession object
          XAResource xaResource = xaSession.getXAResource();
          Transaction tran = weblogic.transaction.TxHelper.getTransaction();
          tran.enlistResource(xaResource);
          // Now send your message!
          You need to call "enlistResource" every time you send a message, or it won't
          work.
          WebLogic Server 8.1 will be able to do this automatically as long as you're
          inside an EJB or a servlet.
          greg
          "raj" <[email protected]> wrote in message
          news:[email protected]..
          >
          > I am using a container managed stateless session bean to send messages to
          an ibm
          > mqseries running on the same computer. The EJB is deployed on weblogic
          7.0. It
          > seems that sending JMS messages do not participate in the transaction and
          that
          > I have to call queueSession.commit() explicity every time. However,
          receiving
          > messages via Message Driven Beans in a transaction is not a problem. Any
          clue
          > how to resolve this or what is happening?

Choosing between Platform default and Other JMS Providers

Hi,
I'm new to JMS and trying to find what are scenarios when default J2EE platform JMS Provider is not enough and we need to go with other options like ActiveMQ. What extra services ActiveMQ provides that lacks in platform default provider.
thanks

I would rather say, evaluate your requirement against platform default(Server default) and ActiveMQ. If your default provider full fills the requirements; use the default one.

ERROR: An event session cannot be started without any providers?

I was trying to get the storport provider that Yong
posted and I get the above error despite checking to ensure the log mode is FILE.
Not sure if the provider names are case sensitive, changing the provider name from Microsoft-Windows-Storport to Microsoft-Windows-StorPort didn't help either.
Suggestions?
Thanks!

Since iOS 5 has not been released yet, it's interesting you say you've already downloaded it. Trash the file you downloaded and wait for the official release. It will probably drop around 10:00 California time.

JNDIMapper Problem (Foreign JMS Providers with WebLogic Server does not close connection )

          Hello All,
          We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
          WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
          context factory to bind MQ.
          We found a number of LDAP connections are getting opened by JNDIMapper, but it's
          not getting closed.
          Can some one give some clue to this ?
          Also any suggestion to serve the current purpose is welcome.
          Thanks, Sudarson


          Hello All,
          We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
          WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
          context factory to bind MQ.
          We found a number of LDAP connections are getting opened by JNDIMapper, but it's
          not getting closed.
          Can some one give some clue to this ?
          Also any suggestion to serve the current purpose is welcome.
          Thanks, Sudarson

Foreign JMS vs. Remote MDB

Hi,
          I have a JMS scenario that I'm hoping to get some input on. The system architecture is as follows:
          One WebLogic 8.1 SP5 domain with a JMS server
          One WebLogic 9.2 MP1 domain with no JMS server
          We'd like to consume a JMS message that's sitting on a queue in the 8.1 domain by code running on the 9.2 domain.
          Without configuring a JMS server in the 9.2 domain (which we'd like to avoid), the two obvious options are:
          1. An MDB running on the 9.2 server that connects to a queue on the 8.1 server
          2. An MDB running on the 9.2 server that connects to a foreign JMS server locally which in turn is linked to the 8.1's JMS server
          Does anyone have any suggestions, experience from this or a similar scenario?
          The main areas that I'd be interested in are:
          - Inter domain compatability
          - Any problems with Transactions, XA
          Many thanks,
          Eoin

Hi,
          I think your approach is fine - inter-version compatibility is supported for both JMS and XA. You'll need to ensure that all 9.1 and 8.1 WL domain names are unique, ditto for all 8.1 WL server names, 8.1 WL store names, plus 8.1 JMS server names (even across different domains).
          "1" and "2" are essentially the same in that "Foreign JMS" is simply a mapping from the local JNDI naming service to a remote JMS service . "2" tends to be preferable as it can simplify administration once configured. For more information, see the "Integrating Remote JMS Providers" FAQ linked off of this page: "http://edocs.bea.com/wls/docs92/messaging.html".
          FYI There are advantages in using 9.x and later JMS - not only does it have a broader set of features, but it also has more sophisticated message management (use the console to pause/resume dests, view individual messages, etc), and significantly higher performance. Also, 9.x MDBs do a better job of connecting to remote 9.x distributed destinations than 8.1 MDBs - as they automatically ensure that all component destinations get serviced.
          Tom

TIBCO consumer, WebLogic JMS, reconnecting

We're currently running TIBCO 7.2 processes with WebLogic 7 as the JMS and DB connection factory.
          When using weblogic.jar to access JMS, we have discovered that TIBCO seems to loose connection entirely if a JMS server node dies, even when using distributed queues.
          We have implemented the 'forward-delay' option to process messages from queues without an active consumer, in the event of a physical node failure. When this occurs however, TIBCO will not automatically reconnect.
          Does anyone know of a work-around or whether or not this is resolved with the WL 9 releast of weblogic.jar?
          The issue is that the entry point to TIBCO processes is to listen on a queue. Once the connection is broken, the component stops listening for messages.

Hi Uday,
The best option depends on your use case.
A messaging bridge is usually only appropriate when you want to store-and-forward from a local destination to a remote destination, instead of directly sending to the remote destination. Store-and-forward is helpful when you still want to be able to produce a message even when the remote destination is unavailable.
SAF Agents are a store and forward solution, just like bridges, but are only designed to only work with WebLogic JMS destinations.
For links to WebLogic Messaging white-papers, blog posts, samples, and documentation, click Enterprise Grid Messaging on the [url http://www.oracle.com/technetwork/middleware/weblogic/overview/index.html]Oracle WebLogic Product Page.
Specifically, see the [url http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm#JMSPG553]Integrating Remote JMS Providers FAQ, which should help you choose between WebLogic's various JMS integration options.
Hope this helps,
Tom

Mule, Weblogic and MQ JMS : deadlock problem

Dear Oracle community,
We are hosting our Mule ESB (3.1) application on a Weblogic 10.3 (11g) server and are using IBM Websphere MQ's JMS solution (with libraries version 7.0.1.7).
The problem we are facing is that JMS connections are created by one of Weblogic's worker (thread) and the close() method for those connections are not necessarily called by the same thread.
This is bad because from what I know this behavior is undefined from JMS specification
(see http://docs.oracle.com/cd/E15051_01/wls/docs103/jms/design_best_practices.html#wp1061413 ) and it is a blocker issue in our case because this lead to a deadlock.
Do someone has any idea how to enforce the fact that the same thread do create and close the connection through Weblogic and/or Mule configuration (without re-implementing the connector) ?
Thanks in advance for your help,
Best regards,
Y.
PS : I've already posted this question on Mule ESB's forum : http://forum.mulesoft.org/mulesoft/topics/mule_weblogic_and_mq_jms_deadlock_problem
Edited by: user7428803 on May 14, 2012 2:26 PM

I hope you found a solution by now, but as an FYI:
* The JMS specification specifically requires that JMS providers support the ability to call connection.close() and session.close() from an arbitrary thread even when another thread is making calls on these objects. It furthermore goes into some detail about the expected behavior of these calls. The best practices link you cited alludes to this: "The JMS Specification states that multi-threading a session, producer, consumer, or message method results in undefined behavior +except when calling close().+"
* Depending on your use case, you may not need to use Mule to integrate MQ with WebLogic. WebLogic supports a variety of options for integrating MQ directly without the use of third party tooling. See http://download.oracle.com/docs/cd/E17904_01/web.1111/e13727/interop.htm .
Tom

Without JMS Providers??

Similar Messages

Maybe you are looking for