JMS: Standalone vs J2EE

Hello,
I am looking for comments/advice on implementing a JMS component as a standalone application versus a J2EE (message driven bean). Mainly in terms of experience or pros and cons of each technology. We are implementing the component from scratch and are curious about the performance consequences that people have encountered.
These JMS components can perform heavy database access, heavy file I/O, and/or heavy computation load. I am if the benefits of running a JMS client as a message driven bean in a J2EE container will outweigh any performance implications when executing many heavy weight tasks within the same JVM.
Thanks
Darryl

Darryl -
You may want to also post this question on the Oracle9iAS J2EE forum on OTN to reach a wider Java audience.
http://technet.oracle.com:89/cgi-bin/forumdisplay.cgi?action=topics&forum=Oracle9iAS+J2EE&number=99&DaysPrune=20&LastLogin=

Similar Messages

Classpath for JMS standalone client

Hi,
I observed some problem, when I try to start my JMS client application. If in classpath is oc4j.jar it works, but when I replace oc4j.jar with oc4jclient.jar doesn't
I notice the message:
Exception in thread "main" java.lang.NoClassDefFoundError: com/evermind/server/jms/EvermindXAConnectionFactory
at com.evermind.server.jms.ConnectInfo.getPass(ConnectInfo.java:98)
at com.evermind.server.jms.EvermindTopicConnectionFactory.createTopicCon
nection(EvermindTopicConnectionFactory.java:83)
at sapconnector.MaterialMoverClient.main(MaterialMoverClient.java:52)
the line no. 52 exactly means:
TopicConnection connection = factory.createTopicConnection();
What the OC4J client jar (oc4jclient.jar) is not enough for starting JMS standalone client?
regards
Krzysztof

Hi, thanks for the reply.
Well, I figured out that problem. It was my jar file. One of the jar file, which is imqjmsra.jar wasn't really the right one and that was giving me the problem. Well, at least that is working not, but I am having new problems.
Right, I have been trying to make this work for about three days now. The truth is that my standalone JMS does work, when it is running on the same machine where the J2EE Server is located, but I am trying to make my JMS standalone client to connect to J2EE server from different location. Now I am getting connection refused error. Well, I guess I will be keep trying util I get this working.

How to use JMS in a J2EE environment

Hello all,
I would like to find out how to use JMS in a J2EE environment. I use Borland Enterprise Server. Do I need to buy a message software to use JMS? How to use JMS with Message Driven bean?
Thanks a lot.
Best regards
Susan

If you don't want to buy you could try OpenJMS, a free JMS product (http://openjms.sourceforge.net/)
As for learning how to use JMS w/ MDBs, I would suggest grabbing a book on JMS. I found the OReilly book on JMS to be pretty helpful for me.

How to create a JMS standalone client with SAS PE8.2 ?

HI everyone,
I use Creator2.1 and I want to write a JMS standalone client that communicate through JMS with a webapp built with Creator.
My pb is that I dont know how to set up initialContext.
Hashtable env=new Hashtable();
env.put(Context.PROVIDER_URL, "mq://localhost:28676/jms");
env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
context = new InitialContext(env);
factory = (TopicConnectionFactory) context.lookup(factoryName);
For example this code doesnt work and I have the following exception when I try to run my client.
29 sept. 2006 10:31:03 com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl <init>
ATTENTION: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: localhost; port: 3700"
org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2257)
at com.sun.corba.ee.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2278)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:208)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:221)
at com.sun.corba.ee.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:104)
at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:146)
at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:286)
at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112)
at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69)
at com.sun.enterprise.naming.SerialContext.narrowProvider(SerialContext.java:89)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:128)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:288)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.orange.clara.Main.main(Main.java:59)
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:336)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:191)
... 12 more
Caused by: java.net.ConnectException: Connection refused: connect
at sun.nio.ch.Net.connect(Native Method)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464)
at java.nio.channels.SocketChannel.open(SocketChannel.java:146)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSocket(IIOPSSLSocketFactory.java:320)
... 13 more
Does anyone had already met this pb ?
Regards
R�gis

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?

BPM standalone and J2EE versions

What is the diffrence between BPM standalone and J2EE versions
and
What are the advantages of Using J2EE Version over standlone?
In configuration document it is mentioned that we need to deploy wlj2eedeployer.ear on weblogic server.
Why this deployment?
Thanks

Depending on your needs, the Engine can be deployed using two different implementation styles.
Standalone Oracle BPM Enterprise Engine
Oracle BPM can be deployed in a standalone environment running on a JVM. This is the original version of the Engine and has been around for 10 years.
The benefits of deploying processes to Enterprise Standalone are:
<li> It does not require an application server J2EE container to run. This means a lower cost of entry if you do not already own WebLogic or WebSphere J2EE application servers.
<li> It is simple to install and administer.
Enterprise Standalone uses a simple active/standby failover mechanism. When the active engine starts, it immediately registers in the Oracle BPM Directory that it is the primary engine. When the standby engine starts on another machine, it sees that another engine has already registered as the active server in the Oracle BPM Directory. Since the active engine is already up, the standby knows that it needs to ping the primary engine periodically to ensure it is still up. If the standby engine fails to get a response from the active engine, the standby notifies the Directory that it is now the active engine. When what was previously the active primary engine restarts, it notifies the Directory that it has restarted, sees that another server is now the primary and then starts as the secondary.
J2EE Application Server Oracle BPM Enterprise Engine
Oracle BPM Enterprise engines can also run on a J2EE application server within WebLogic and WebSphere containers.
Oracle BPM Engines running on a J2EE Application Server support active clustering. This means that as loads increase over time, new nodes can be added making the environment more scalable over time.
With the J2EE Application Server environment automatic failover is automatically provided across nodes.
Finally, in answer to your last question - the deployed wlj2eedeployer.ear is useful because this lets you stop and start the Engine and deploy projects from the simple (ok - somewhat simple) Oracle BPM Process Administrator tool.
Hope this helps,
Dan

JMS Standalone Application

I am Developing JMS Standalone Application And Using Sun App Server 8.1 The Following I Have Created
1. META-INF/application-client.xml
2. source/jms/SimpleQueueSender.java
3.source/jms/SimpleQueueReceiver.java
The Following Is The Code In application-client.xml
<application-client>
        <display-name>Simple JMS Standalone Application </display-name>
        <resource-ref>
                <description>Simple Queue SenderReceiver</description>
                <res-ref-name>jms/MyQCF</res-ref-name>
                <res-type>javax.jms.QueueConnectionFactory</res-type>
                <res-auth>Container</res-auth>
        </resource-ref>
        <resource-env-ref>
                <description>SQR</description>
                <resource-env-ref-name>jms/MyQueue</resource-env-ref-name>
                <resource-env-ref-type>javax.jms.Queue</resource-env-ref-type>
        </resource-env-ref>
</application-client>The Following Is The Code Used In SimpleQueueXXX(Either Sender Or Receiver )
queueConnectionFactory = (QueueConnectionFactory)
                jndiContext.lookup("java:comp/env/jms/MyQCF");
            queue = (Queue) jndiContext.lookup("java:comp/env/jms/MyQueue");when i run the the packaged jar file using appclient
the following error is generated
WARNING: ACC003: Application threw an exception.
javax.naming.InvalidNameException: Real JNDI name cannot be empty for jms/MyQCF
at com.sun.enterprise.naming.NamingManagerImpl.bindObjects(NamingManagerImpl.java:475)
at com.sun.enterprise.appclient.AppContainer.preInvoke(AppContainer.java:134)
at com.sun.enterprise.appclient.Main.<init>(Main.java:383)
at com.sun.enterprise.appclient.Main.main(Main.java:99)
Mar 9, 2006 7:16:40 PM com.sun.enterprise.appclient.Main <init>
WARNING: ACC010: Make sure the server port is not disabled and that you are looking up a valid name
Thanks In Advance , Please Help Me At The Earliest

Yaa , I Have Resolved It By Writing sun-application-client.xml but now i am getting some another error , can look into this why does this come
Mar 10, 2006 12:53:26 PM com.sun.enterprise.appclient.Main <init>
WARNING: ACC003: Application threw an exception.
java.lang.ClassNotFoundException:
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at com.sun.enterprise.appclient.Main.<init>(Main.java:388)
at com.sun.enterprise.appclient.Main.main(Main.java:99)
Thanks In Advance , Please Reply At The Earliest

JMS and Standalone vs J2EE

Hello,
I am looking for comments/advice on implementing a JMS component as a standalone application versus a J2EE (message driven bean). Mainly in terms of experience or pros and cons of each technology. We are implementing the component from scratch and are curious about the performance consequences that people have encountered.

Darryl -
You may want to also post this question on the Oracle9iAS J2EE forum on OTN to reach a wider Java audience.
http://technet.oracle.com:89/cgi-bin/forumdisplay.cgi?action=topics&forum=Oracle9iAS+J2EE&number=99&DaysPrune=20&LastLogin=

Standalone JMS client in J2EE 1.4 Beta

Hi,
I expected it should be possible to deploy an MD Bean and to send message to it from outside the server - using "runclient". It does not work for me. During "runclient" it can not find the queue - defined with "message-destination". Can anybody tell me - is it supposed to work this way?
I do runclient -client m01mclient.ear -name MDClient
I have .ear with application.xml and sun-j2ee-ri.xml and .jar in it with application-client.xml. Here are the descriptors:
application-client>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<?xml version="1.0" encoding="UTF-8"?>
<application-client version="1.4"
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd">
<display-name>MDClient</display-name>
<resource-ref>
<res-ref-name>jms/KnownConnectionFactory</res-ref-name>
<res-type>javax.jms.ConnectionFactory</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<message-destination-ref>
<message-destination-ref-name>jms/KnownQueue</message-destination-ref-name>
<message-destination-type>javax.jms.Queue</message-destination-type>
<message-destination-usage>Produces</message-destination-usage>
<message-destination-link>NameForKnownQueue</message-destination-link>
</message-destination-ref>
<message-destination>
<message-destination-name>NameForKnownQueue</message-destination-name>
</message-destination>
</application-client>
sun-j2ee-ri.xml>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE j2ee-ri-specific-information
PUBLIC "-//Sun Microsystems Inc.//DTD J2EE Reference Implementation 1.4//EN"
"http://localhost:8000/sun-j2ee-ri_1_4.dtd">
<j2ee-ri-specific-information>
<app-client>
<module-name>mdclient.jar</module-name>
<resource-ref>
<res-ref-name>jms/KnownConnectionFactory</res-ref-name>
<jndi-name>jms/QueueConnectionFactory</jndi-name>
<default-resource-principal>
<name>j2ee</name>
<password>j2ee</password>
</default-resource-principal>
</resource-ref>
<message-destination>
<message-destination-name>NameForKnownQueue</message-destination-name>
<jndi-name>jms/Queue</jndi-name>
</message-destination>
</app-client>
</j2ee-ri-specific-information>

Sorry for the false alarm. In fact it works fine with these same deployment descriptors.
But in the last J2EE Tech Tips the client is packaged much simpler.

Using JMS adapter with J2ee native queuing system

Hi there,
As far as I have understood J2EE contains it's own native queuing system (JMS). Since the J2EE is part of the WAS, shouldn't it be possible to somehow use XI's JMS adapter in conjunction with this native JMS?
I've tried to search many places in many ways, but haven't been able to find any info. Is it possible at all?
Hope, some of u guys can help out there:-)
Regards,
Daniel

Hi Keith,
It looks as if you are in the same situation.
We have this working very nicely now and I'm happy to share. In fact I was just granted wiki permissions so I can add the information there along with screen shots.
Informaiton on this configuration is very scattered but I imagine many people would find it useful for integrating with Mainframes without adding any complexity to the legacy environment. Let me come back to you with some more inormation, but for now you can get started with this:
Insert a module as the 3rd line in your Module Processing Sequence to use AF_Modules/MessageTransformBean and give it a key in order to associate with the parameters you will need to type in below. These parameters are very similar to normal XI File adapter parameters.
SAP Note 793922 has more info on the parameters... not the greatest reference I know.
Also this has some info...
http://help.sap.com/saphelp_nw04/Helpdata/EN/57/0b2c4142aef623e10000000a155106/content.htm
I'll try and get some screen shots up on the Wiki.

JMS Application on J2EE server

Hi,
How can I run a simple PTP client-server application of JMS on windows platform? I am using a machine running windows 98, on which I have installed JDK1.3 and J2SDKEE1.2.1. I use J2EE server to deploy EJBs and Servlets on localmachine. I want to use the same J2EE server (J2SDKEE1.2.1 for windows) for JMS applications also. Please help me.
Paras.

Sun's J2EE SDK 1.2.1 does not support JMS. In other words, it does not have a JMS provider.
You need to use Sun's J2EE SDK 1.3 to use the reference implementation of JMS API.
However, you could use JMS provider from other vendor and still use J2EE SDK 1.2.1 reference inplementation as your application server.

JMS-MQSeries without J2EE

Hi,
I tried to compile the SimpleTopicPublisher and SimpleTopicSubscriber from the following link. I used the javax.jms.jar and the jms.jar from sun.
http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/client.html#1027256
The code got compiled.
I had a queue in MQSeries, its sample queue called postcard.
When I tried running SimplePublisherTopic, the following exception was thrown:
<code>
D:\>java SimpleTopicPublisher postcard 1
Topic name is postcard
JNDI API lookup failed: javax.naming.NoInitialContextException: Need to specify
class name in environment or system property, or as an applet parameter, or in a
n application resource file: java.naming.factory.initial
javax.naming.NoInitialContextException: Need to specify class name in environmen
t or system property, or as an applet parameter, or in an application resource f
ile: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
43)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
a:283)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at SimpleTopicPublisher.main(SimpleTopicPublisher.java:60)
</code>
The program is J2EE server independent. The MQSeries for Win 2000 is used for JMS services.
Please help me in understanding the following :
1) How to get the JNDI server running and registering our topic there?
2) There was no reference of 'Topic' in MQSeries. There are only 'Queue'. If this is the case, how to create topics in MQSeries.
3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
4) MQSeries has a Java API. Is it a replacement/substitute for Sun JMS API? Which should we use to write a generic JMS code?
Thanks in advance,
Rajesh

I could solve some of the exceptions based on Steve's suggestions. I am giving below on how I solved.
"JNDI API lookup failed: javax.naming.NoInitialContextException: "
The SimpleTopicPublisher has set env property for InitialContext and expects our System's properties to specify the provider URL. I have added the property this way in code:
          try {
               // Identify service provider to use
               Hashtable env = new Hashtable(11);
               env.put(Context.INITIAL_CONTEXT_FACTORY,
                             "com.sun.jndi.fscontext.RefFSContextFactory");
               env.put(Context.PROVIDER_URL,
                             "file:/C:/Program Files/IBM/MQSeries/Java/lib");
               jndiContext = new InitialContext(env);
          } catch (NamingException e) {
                    System.out.println("Could not create JNDI API " +
                         "context: " + e.toString());
                    e.printStackTrace();
                    System.exit(1);
          }1) How to get the JNDI server running and registering our topic there?
Unlike RMI Naming server/registry, JNDI is a standard API for naming services. Hence it is not designed as a server listening on a port. I understand the File System based name space. The bindings of key-value is maintained in .bindings file in the place you specify as a PROVIDER_URL. Both publisher and subscriber has to refer this name space. This is how you start registering and retrieving MQ objects.
3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
Providers are vendors who have implemented javax.naming.Spi package. The default provider you get from Sun is one reference implementation. It is "com.sun.jndi.fscontext.RefFSContextFactory". There is no IBM MQSeries provider. The same "com.sun.jndi.fscontext.RefFSContextFactory" is only supplied with MQSeries also.
I don't know the answers for questions 2 and 4. I shall post it as soon as I understand.
Those of you who read this, if you find deviation from righteouness, please correct.
Thanks/Regards,
Rajesh

JMS Server without J2EE server?

Hi,
We're working on a relatively small application where a small amount of messaging would be beneficial. What I ideally need is a free reference implementation of the JMS spec which does not require a full J2EE server with ORB, etc all being started up. I was looking at what comes with the j2sdkee 1.3.1 but I can not see how to configure JNDI to use anything other than the naming service provided by the ORB.
If anybody can recommend an implementation available that might be of use that would be great.
Thanks,
Aoife

HI rajdeepdua,
ur comments:
>>It seems that all the vendors are trying to promote their products
well, i am NOT a SonicSoftware Marketing person.
>>If you need a free jms server the i think you should go for either openjms or joram
But i did lot of testing with Different JMS Server And i am convinces that Sonic MQ performs the best. Their DRA (Dynamic Routing architecture) is fantastic and performs absouletly bugless unlike its competitors.

Jms from sun j2ee to bea weblogic

Hy,
          is there a easy way to connect a JmsFactory from an j2ee sun server to a
          bea weblogic server?
          JMS API Tutorial shows an example for connecting two j2ee Server:
          j2eeadmin --addJmsFactory MyFactory queue -props
          url=corbaname:iiop:remoteserver:1050:#remoteserver
          Weblogic 7 seems to support iiop (on Port 7001?) but
          something is missing ... no connection could be made to send Messages
          from j2ee (sun) to weblogic server?
          Any hint?
          Best Regards,
          Holger


Hi Holger,
          The WL JMS client does not support iiop in 7.0,
          although it does in 8.1 (beta soon). Instead use t3, a much
          faster protocol, or, if you need to tunnel, use http.
          Note that BEA has a comprehensive white-paper on integrating
          "foreign" JMS providers on dev2dev.bea.com:
          "Using Foreign JMS Providers With WebLogic Server"
          Tom
          Holger von Rhein wrote:
          > Hy,
          >
          > is there a easy way to connect a JmsFactory from an j2ee sun server to a
          > bea weblogic server?
          >
          > JMS API Tutorial shows an example for connecting two j2ee Server:
          >
          > j2eeadmin --addJmsFactory MyFactory queue -props
          > url=corbaname:iiop:remoteserver:1050:#remoteserver
          >
          > Weblogic 7 seems to support iiop (on Port 7001?) but
          > something is missing ... no connection could be made to send Messages
          > from j2ee (sun) to weblogic server?
          >
          > Any hint?
          >
          >
          > Best Regards,
          >
          > Holger
          >

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

Regarding JMS standalone application client

Hi,
I m new to JMS.
I m using NetBeans IDE and would like to know how can i create connection factories and destinations either administratively or through JNDI.
Btw, i m writing a simple stand alone application client which has a queuesender and a queuereceiver.
Regards.

Hi,
I m using Jboss4.2.0GA...plz tell me how to create a connection factory and a destination queue......and then how to look them up via JNDI??
I m writing a simple stand alone application client with a sender and a receiver.
Regards,
Chowdary.

JMS: Standalone vs J2EE

Similar Messages

Maybe you are looking for