Stoping JMS application graceful

Hi
I have one flat java JMS application starts with command line. Application is consumer of one queue and split messages in to many and finally insert into DataBase. Application also have two other threads.
Here I am struggling with problem how to graceful stop this application with out any lost or fail.
Currently I use �kill -9 pid� to stop this which is not proper.
Kapil

Hi,
The process for creating/deploying "application resource" type JMS Modules are different from the "system" type modules.
To create the module itself, users need to
1) use any standard XML editor/IDE using the JMS module schema (http://www.bea.com/ns/weblogic/weblogic-jms/1.0/weblogic-jms.xsd)
2) Use the WebLogic Admin console to create a "system resource" type module then copy/rename/edit the corresponding JMS module descriptor file (which gets created under DOMAIN/config/jms" dir) as needd and delete the corresponding "system resource" module using the Admin console abefore attempting to deploy the "application resource" module.
For more information on this topic, please look at :
http://e-docs.bea.com/wls/docs103/jms_admin/deployjms.html
PS: Please note that the use of "default" targeting is not a recommended best practice when its comes to JMS resource targeting as it can quickly become very complicated when there are more than one JMS Servers in the domain.
A list of best practice recommendations can be found at: (though this is listed under the context of Automatic Service Migration, it still applies to general JMS configuration process).
http://e-docs.bea.com/wls/docs103/cluster/service_migration.html#wp1067914
Hope this helps.

Similar Messages

Error while migrating JMS application from Weblogic8.1 to Weblogic10.3

Hi All,
I am migrating my JMS application from weblogic8.1 to 10.3. I'm able to publish and subscribe message from local weblogic server. But when i'm configuring ldap server in weblogic-ejb-jar.xml, while deploying the application itself i'm getting the below error. Same thing working fine in weblogic8.1.
For this am i need to use foreignjms?. If this is the case please let me know how to configure foreignjms in weblogic10.3 server.
below are the details i'm giving in weblogic-ejb-jar.xml:
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>3</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>evtTESTEH3Queue</destination-jndi-name>
<initial-context-factory>com.sun.jndi.ldap.LdapCtxFactory</initial-context-factory>
<provider-url>ldap://192.168.20.18:389/ou=mqseries,o=crimsonlogic.com</provider-url>
<connection-factory-jndi-name>ivtQCF</connection-factory-jndi-name>
</message-driven-descriptor>
Error:
weblogic.application.ModuleException: Exception activating module: EJBModule(evtEJB.jar)
Unable to deploy EJB: JMSTESTEVTEventSubscriberMDBean from evtEJB.jar:
unable to find EndPointFinder for ldap://192.168.20.18:389/ou=mqseries,o=crimsonlogic.com
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
Truncated. see log file for complete stacktrace
java.lang.AssertionError: unable to find EndPointFinder for ldap://192.168.20.18:389/ou=mqseries,o=crimsonlogic.com
[email protected] on Mar 18, 2009 3:07 AM

Hello TomB,
Could you elaborate a bit on your explanation? I'm having the same problem as talk2srujan. I currently have an application which works fine in weblogic81 and, when migrated to weblogic103, fails at deployment time. The error I get is: unable to find EndPointFinder for tibjmsnaming://host:port
We didn't have to register any foreign servers in weblogic81, should I do this in weblogic103?
Could you also give a pointer to the known bug you mentioned?
Thanks in advance,
Rudra

How to configure the JMS application in WSAD 5.0

hi
i need to configure an JMS application in WSAD 5, but while configuring the application i am checked with intial context exception. but i have configured the jndi in the server. but i cant able to run the application.
can anybody help me like how to configure the JMS application in WSAD (can we configure it without MQ simulator if yes i need the steps)
thanks in advance

Hi,
did you check the WebSphere documentation or ask a question on an IBM forum?
Frank

Help needed to run a JMS application on WSAD

Hello everybody,
I�m trying to execute a JMS application which calls a QueueConnectionFactory and a Queue by JNDI lookup.
I had configured these queues & Connection Factory at the server configuration for the JMS Server & these are being displayed while the server is starting up that these names had been binded.until here it�s ok.
But the problem comes when I try to us my JMS program with configurations as websphere 5.1 application client.\
The error is being displayed as :
com.ibm.websphere.naming.CannotInstantiateObjectException: Exception occurred while the JNDI NamingManager was processing a javax.naming.Reference object.
[Root exception is java.lang.Exception: De-reference of JMS provider's Reference failed - check provider is on classpath]
WSCL0100E: Exception received: java.lang.reflect.InvocationTargetException
If any body can check this out please help.
best regards,
Raju Cherukuri.

Hi,
I am facing the same issue. Also regarding the resolution posted in this thread, to add the MQ jars in the classpath, do I still have to do if I am using the embedded JMS and not MQ.
Cosmo can you pls explain what are the steps to do, for whatever you've suggested.
Regards,
Hari

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.

How to create the jms application in eclipse3.5 ide

Any body please help me to create the jms application in eclipse3.5.....i am new to this jms technology ........pls help
me regarding this

What kind of help are you expecting here? I would expect that your first stop is a good book on JMS technology, an perhaps a visit to the Eclipse website to read up how to do JEE development using it.
Lack of knowledge is a problem you can easily fix yourself and must fix yourself. But perhaps you would like some book suggestions?

Testing simple JMS application

I have written a very simple JMS application.
I am trying to get it to run with the SUN App Server 8. I accepted the default values when installing the server. I have the app server up and running. The following code is suppose to create the Session:
Context context = new InitialContext();
ConnectionFactory connectionFactory =
(ConnectionFactory)context.lookup("ConnectionFactory");
Connection connection = connectionFactory.createConnection();
session = connection.createSession(false, Session.AUTO_ACKNOWLEDGE);
I ave tried to run this from both the command line and from JBuilder. I have include the J2EE.jar in the classpath. I get the following error.
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
I know that I can set properties for the InitialContext constructor, but is this required? If so, what would the properties be for the default server?

Looks like you're missing the initial context factory class which is:
java.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory
But I believe Sun recommends not settting it directly. You should include appserv-rt.jar in your classpath. That jar file has a file called jndi.properties which specifies the above property I just mentioned. Open it up and take a look for yourself.

ConnectionRunTimeException problem on JMS Application

Hi guys i am developing a JMS application based on durable publish/subscribe model on
netbeans 5.0 running Sun Java App Server 8.0 .I have defined a Connector resource of
resource type TopicConnectionFactory and a Destination resource of resource type Topic ,and registered
both of them with the app server.First i created both of these resources using the JMS Resource wizard, and configured
them both in the web app descriptor(web.xml) and sun web app descriptor(sun-web.xml) but when i try to run the PublishingHandler Servlet
i gives me a ConnectionRuntimeException.I deleted both of these resource,logged in to the app server
and created them afresh on the Admin Server Console.The creation was successful but when i restart the app server and try to run my application
i still get that ConnectionRuntimeException.
Now i don't know how can i configure my application to run,because i have tried all possible configurations.Anyone knowledgeable
about this, plz help me.
Here are snippets from app descriptors and the servlet class
Web Application Descriptor(web.xml)
<resource-ref>
        <res-ref-name>jms/sanparksConnectionFactory</res-ref-name>
        <res-type>javax.jms.TopicConnectionFactory</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
        <res-ref-name>jms/sanparksTopics</res-ref-name>
        <res-type>javax.jms.Topic</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Sun Web Application Descriptor(sun-web.xml)
<resource-ref>
    <res-ref-name>jms/sanparksConnectionFactory</res-ref-name>
    <jndi-name>jms/sanparksConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
    <res-ref-name>jms/sanparksTopics</res-ref-name>
    <jndi-name>jms/sanparksTopics</jndi-name>
</resource-ref>
Servlet Source Code(PublishingHandler.java)
package com.mcebo.sanparks.mediator;
import java.io.*;
import java.net.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.jms.*;
import javax.naming.*;
//User Defined packages
import com.klaas.sanparks.beans.TopicBean;
import com.mcebo.sanparks.accesslayer.XMLDBProcessor;
public class PublishingHandler extends HttpServlet
     TopicConnectionFactory factory = null;
     TopicConnection connection = null;
     TopicSession session = null;
     Topic topic = null;
     TopicBean sanparkTopic = new TopicBean();
     TopicPublisher publisher = null;
    XMLDBProcessor dbAcces = new XMLDBProcessor();
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        response.setContentType("text/html;charset=UTF-8");
        PrintWriter out = response.getWriter();
        String title = request.getParameter("title");
        String category = request.getParameter("category");
        String body = request.getParameter("body");
        String keyWord = request.getParameter("keyword");
        if((!title.equals(null)) && (!category.equals(null))&&(!body.equals(null))&& (!keyWord.equals(null)))
                sanparkTopic.setTitle(title);
                sanparkTopic.setCategory(category);
                sanparkTopic.setBody(body);
                sanparkTopic.setKeyWord(keyWord);
        try
               Context initContext = new InitialContext();
              package com.mcebo.sanparks.mediator;
import java.io.*;
import java.net.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.jms.*;
import javax.naming.*;
//User Defined packages
import com.klaas.sanparks.beans.TopicBean;
import com.mcebo.sanparks.accesslayer.XMLDBProcessor;
public class PublishingHandler extends HttpServlet
     TopicConnectionFactory factory = null;
     TopicConnection connection = null;
     TopicSession session = null;
     Topic topic = null;
     TopicBean sanparkTopic = new TopicBean();
     TopicPublisher publisher = null;
    XMLDBProcessor dbAcces = new XMLDBProcessor();
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        response.setContentType("text/html;charset=UTF-8");
        PrintWriter out = response.getWriter();
        String title = request.getParameter("title");
        String category = request.getParameter("category");
        String body = request.getParameter("body");
        String keyWord = request.getParameter("keyword");
        if((!title.equals(null)) && (!category.equals(null))&&(!body.equals(null))&& (!keyWord.equals(null)))
                sanparkTopic.setTitle(title);
                sanparkTopic.setCategory(category);
                sanparkTopic.setBody(body);
                sanparkTopic.setKeyWord(keyWord);
        try
                Context initContext = new InitialContext();
               // Context envContext = (Context)initContext.lookup("java:comp/env");
            //factory = (TopicConnectionFactory)envContext.lookup("jms/sanparksConnectionFactory");
               //topic = (Topic) envContext.lookup("jms/sanparksTopics");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               factory = (TopicConnectionFactory)initContext.lookup("jms/sanparksConnectionFactory");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               connection = factory.createTopicConnection();
               session = connection.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
               publisher = session.createPublisher(topic);
               ObjectMessage message = session.createObjectMessage();
               message.setObject(sanparkTopic);
               message.setStringProperty("Category",sanparkTopic.getCategory());
               publisher.publish(message);
               out.println("Message Published"+ sanparkTopic.getCategory());
               out.close();
        catch(Exception ex)
                ex.printStackTrace();
    // <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on the left to edit the code.">
    /** Handles the HTTP <code>GET</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Handles the HTTP <code>POST</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doPost(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Returns a short description of the servlet.
    public String getServletInfo()
        return "Short description";
    // </editor-fold>
               factory = (TopicConnectionFactory)initContext.lookup("jms/sanparksConnectionFactory");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               connection = factory.createTopicConnection();
               session = connection.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
               publisher = session.createPublisher(topic);
               ObjectMessage message = session.createObjectMessage();
               message.setObject(sanparkTopic);
               message.setStringProperty("Category",sanparkTopic.getCategory());
               publisher.publish(message);
               out.println("Message Published"+ sanparkTopic.getCategory());
               out.close();
        catch(Exception ex)
                ex.printStackTrace();
    // <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on the left to edit the code.">
    /** Handles the HTTP <code>GET</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Handles the HTTP <code>POST</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doPost(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Returns a short description of the servlet.
    public String getServletInfo()
        return "Short description";
    // </editor-fold>
}

Hi guys i am developing a JMS application based on durable publish/subscribe model on
netbeans 5.0 running Sun Java App Server 8.0 .I have defined a Connector resource of
resource type TopicConnectionFactory and a Destination resource of resource type Topic ,and registered
both of them with the app server.First i created both of these resources using the JMS Resource wizard, and configured
them both in the web app descriptor(web.xml) and sun web app descriptor(sun-web.xml) but when i try to run the PublishingHandler Servlet
i gives me a ConnectionRuntimeException.I deleted both of these resource,logged in to the app server
and created them afresh on the Admin Server Console.The creation was successful but when i restart the app server and try to run my application
i still get that ConnectionRuntimeException.
Now i don't know how can i configure my application to run,because i have tried all possible configurations.Anyone knowledgeable
about this, plz help me.
Here are snippets from app descriptors and the servlet class
Web Application Descriptor(web.xml)
<resource-ref>
        <res-ref-name>jms/sanparksConnectionFactory</res-ref-name>
        <res-type>javax.jms.TopicConnectionFactory</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
<resource-ref>
        <res-ref-name>jms/sanparksTopics</res-ref-name>
        <res-type>javax.jms.Topic</res-type>
        <res-auth>Container</res-auth>
        <res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
Sun Web Application Descriptor(sun-web.xml)
<resource-ref>
    <res-ref-name>jms/sanparksConnectionFactory</res-ref-name>
    <jndi-name>jms/sanparksConnectionFactory</jndi-name>
</resource-ref>
<resource-ref>
    <res-ref-name>jms/sanparksTopics</res-ref-name>
    <jndi-name>jms/sanparksTopics</jndi-name>
</resource-ref>
Servlet Source Code(PublishingHandler.java)
package com.mcebo.sanparks.mediator;
import java.io.*;
import java.net.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.jms.*;
import javax.naming.*;
//User Defined packages
import com.klaas.sanparks.beans.TopicBean;
import com.mcebo.sanparks.accesslayer.XMLDBProcessor;
public class PublishingHandler extends HttpServlet
     TopicConnectionFactory factory = null;
     TopicConnection connection = null;
     TopicSession session = null;
     Topic topic = null;
     TopicBean sanparkTopic = new TopicBean();
     TopicPublisher publisher = null;
    XMLDBProcessor dbAcces = new XMLDBProcessor();
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        response.setContentType("text/html;charset=UTF-8");
        PrintWriter out = response.getWriter();
        String title = request.getParameter("title");
        String category = request.getParameter("category");
        String body = request.getParameter("body");
        String keyWord = request.getParameter("keyword");
        if((!title.equals(null)) && (!category.equals(null))&&(!body.equals(null))&& (!keyWord.equals(null)))
                sanparkTopic.setTitle(title);
                sanparkTopic.setCategory(category);
                sanparkTopic.setBody(body);
                sanparkTopic.setKeyWord(keyWord);
        try
               Context initContext = new InitialContext();
              package com.mcebo.sanparks.mediator;
import java.io.*;
import java.net.*;
import javax.servlet.*;
import javax.servlet.http.*;
import javax.jms.*;
import javax.naming.*;
//User Defined packages
import com.klaas.sanparks.beans.TopicBean;
import com.mcebo.sanparks.accesslayer.XMLDBProcessor;
public class PublishingHandler extends HttpServlet
     TopicConnectionFactory factory = null;
     TopicConnection connection = null;
     TopicSession session = null;
     Topic topic = null;
     TopicBean sanparkTopic = new TopicBean();
     TopicPublisher publisher = null;
    XMLDBProcessor dbAcces = new XMLDBProcessor();
    protected void processRequest(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        response.setContentType("text/html;charset=UTF-8");
        PrintWriter out = response.getWriter();
        String title = request.getParameter("title");
        String category = request.getParameter("category");
        String body = request.getParameter("body");
        String keyWord = request.getParameter("keyword");
        if((!title.equals(null)) && (!category.equals(null))&&(!body.equals(null))&& (!keyWord.equals(null)))
                sanparkTopic.setTitle(title);
                sanparkTopic.setCategory(category);
                sanparkTopic.setBody(body);
                sanparkTopic.setKeyWord(keyWord);
        try
                Context initContext = new InitialContext();
               // Context envContext = (Context)initContext.lookup("java:comp/env");
            //factory = (TopicConnectionFactory)envContext.lookup("jms/sanparksConnectionFactory");
               //topic = (Topic) envContext.lookup("jms/sanparksTopics");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               factory = (TopicConnectionFactory)initContext.lookup("jms/sanparksConnectionFactory");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               connection = factory.createTopicConnection();
               session = connection.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
               publisher = session.createPublisher(topic);
               ObjectMessage message = session.createObjectMessage();
               message.setObject(sanparkTopic);
               message.setStringProperty("Category",sanparkTopic.getCategory());
               publisher.publish(message);
               out.println("Message Published"+ sanparkTopic.getCategory());
               out.close();
        catch(Exception ex)
                ex.printStackTrace();
    // <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on the left to edit the code.">
    /** Handles the HTTP <code>GET</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Handles the HTTP <code>POST</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doPost(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Returns a short description of the servlet.
    public String getServletInfo()
        return "Short description";
    // </editor-fold>
               factory = (TopicConnectionFactory)initContext.lookup("jms/sanparksConnectionFactory");
               topic = (Topic) initContext.lookup("jms/sanparksTopics");
               connection = factory.createTopicConnection();
               session = connection.createTopicSession(false,Session.AUTO_ACKNOWLEDGE);
               publisher = session.createPublisher(topic);
               ObjectMessage message = session.createObjectMessage();
               message.setObject(sanparkTopic);
               message.setStringProperty("Category",sanparkTopic.getCategory());
               publisher.publish(message);
               out.println("Message Published"+ sanparkTopic.getCategory());
               out.close();
        catch(Exception ex)
                ex.printStackTrace();
    // <editor-fold defaultstate="collapsed" desc="HttpServlet methods. Click on the + sign on the left to edit the code.">
    /** Handles the HTTP <code>GET</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doGet(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Handles the HTTP <code>POST</code> method.
     * @param request servlet request
     * @param response servlet response
    protected void doPost(HttpServletRequest request, HttpServletResponse response)
    throws ServletException, IOException
        processRequest(request, response);
    /** Returns a short description of the servlet.
    public String getServletInfo()
        return "Short description";
    // </editor-fold>
}

Sample Websphere6 JMS application with default Messaging

Hi,
Where could I get the Sample Websphere6 JMS application with default messaging?.
Please post me a link
Thank you

I am trying to execute
SimpleQueueSender.java from jms tutorial but unforunately getting following
errors.
Errors-->
Queue name is MyQueue
JNDI lookup failed: javax.naming.CommunicationException:
java.rmi.MarshalException: CORBA MARSHAL 13
98079699 Maybe; nested exception is:
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge :
minor code: 139807969
9 completed: Maybe
org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : minor
code: 1398079699 comple
ted: Maybe
at
com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_value(CDRInputStream_
1_0.java:936)
at
com.sun.corba.ee.internal.iiop.CDRInputStream.read_value(CDRInputStream.java
:292)
at
com.sun.corba.ee.internal.corba.TCUtility.unmarshalIn(TCUtility.java:268)
at
com.sun.corba.ee.internal.corba.AnyImpl.read_value(AnyImpl.java:562)
at
com.sun.corba.ee.internal.iiop.CDRInputStream_1_0.read_any(CDRInputStream_1_
0.java:618)
at
com.sun.corba.ee.internal.iiop.CDRInputStream.read_any(CDRInputStream.java:2
63)
at
com.sun.corba.ee.internal.javax.rmi.CORBA.Util.readAny(Util.java:103)
at javax.rmi.CORBA.Util.readAny(Util.java:92)
at
org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Un
known Source)
at
com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:154)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at SimpleQueueSender.main(SimpleQueueSender.java:70)
I have all the setup required for running jms api examples & also tried all the tips mentioned here ,but still getting these errors . Any
help would be greatly appreciated.
Praveg

Quiting applications gracefully from within LV

Hello,
Attached is an example VI that can be used to open and close a third party application. It does this using the System Exec vi and the windows comand line 'tskill'. The VI will prompt the user to go back to the application and save any changes.
Is there an alternative comand line or method which will close the application gracefully, so it asks the user to save changes directly (the same as when the application is quit manually or it is closed by windows shutting down)?
I am using XP sp3 and LV 8.6 (not very familiar with Windows comand lines etc though).
Thanks,
Blue
Attachments:
Open close app from LV example.vi ‏24 KB

Hello smercurio thanks for that link, very welcome! i have spent the last couple of days searching for something like that with no success. It contains the building blocks to do what i need.
The comments below are so that hopefully some other nubie will come across the solution more easily than i did... (as search terms are easy once you know them - eg searching the forum for user32 and lvutil32 gives me no hits).
How to begin to interact and manipulate with third party applications and windows from a LabView VI.
The 'Call Library Function Node' alows LV to communicate with .dll (dynamic link library) files.
The Windows API .dll for interacting with desktop windows is called 'user32.dll'
Examples of LabView VIs calling user32.dll can be found in Lvutil32 at:
http://zone.ni.com/devzone/cda/epd/p/id/2556
The VIs in Lvutil32 use both user32.dll and lvutil32.dll.
User32.dll is part of Windows.
Lvutil32.dll is not part of windows and will need to be included with any VIs that call it.
For VIs using windows command lines to launch applications it is necessary to include the full path to the application. Obviously moving the application from the path will cause an error. Alternatively you can edit the 'Path' entry in Control Panel > System Properties > Advanced > Environmental Variables > System Variables > Path to include the path to the application to be launched. This will mean that only the name of the application executable is needed.
A great VI for experimenting sending simulated key strokes to the active application is Virtual Keyboard.vi posted at the link below by Peter (though you may need to reduce the 'Delay' input).
http://forums.ni.com/ni/board/message?board.id=270&message.id=839&query.id=2019#M839
Comments, additions and corrections welcomed.
Thanks again for the support, Blue

Running JMS application

Hi,
If you can answer following queries I shall be oblised.
1.What are the different JMS provider available in industry?
2.Is Application server needed to run JMS application?Do application servers provide MOM?
3.Can I use websphere as JMS provider? Do I have to use MQSeries(MOM)in that case?
4.What are the thing I need to configure in application server(e.g. websphere) and/or MOM(eg. MGSeries)to run JMS application(both pub/sub and p2p)?
Looking for your reply.
Thanx & Regards,
Joydeep

1.SOme of them are Progress's Sonic, Fiarano, IBM MQ Series, WEblogic JMS. For complete list , you can search the internet.
2.No application server is not needed. Most of the application server provide JMS eg Weblogic
3.You may have to use MQ Series. WEbsphere doesnt provide it as its part IMO
4.Configuration on most involve setting connection factories, Creating Topics and Queues. There may be performance settings which may vary with product. But this is also ||ar in most servers.
--Ashwani

Hosting jms application

hello,
i have developed a jms application, currently tht is running on my test server of websphere 5.0. But my production server setup demands hosting the application on apache 1.3.3
Can can one guide as how to host the jms application on apache server 1.3.3 or is there some other way out.

Apache 1.3.3 is a web server. I wasn't aware that you could host JMS applications on it (unless there is a MOD-JMS module)

Persisting a user id across an OSB JMS Application

I have an application that user's log in to. After logging in they call an OSB service which puts a message on a jms queue using an OSB business service. I have an OSB proxy service that is listening on the queue. It picks up the message off the queue and calls another service. I want to be able to pass along the userid from the original cookie through the jms flow until my end point where a database insert is made. Does anyone have any suggestions how best to persist the userid through the jms busness and proxy services. I've seen where you can pass the caller's subject in the transport detail section of the jms business service definition, but I'm not sure if that will work and how the proxy could get a hold of it on the other end. Any tips would be appreciated.
thanks,
Mike

I found the answer from a collegue. Here's one solution: Oracle Fusion Middleware Security: Identity Propagation using JMS Transport with Oracle Server Bus 11gR1 PS2

JMS & Application Server

hi,
I've a problem to connect to the application server of Sun from an application.
I don't know the initial context and the url provider :
Properties prop = new Properties();
prop.put (Context.INITIAL_CONTEXT_FACTORY, ??? );
prop.put(Context.PROVIDER_URL, ??? );
Context jndi = new InitialContext(prop);I looked for it but all I found didn't work.
Can anyone help me please ?

Hi,
This might be useful to you.
// Set initial context and URL properties
Properties env = new Properties();
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.cosnaming.CNCtxFactory");
env.put(Context.PROVIDER_URL,
"iiop://host_name:9010");
// Create initial context and lookup
Context initial = new InitialContext(env);
Object obj =
initial.lookup("java:comp/env/ejb/simple");
SimpleHome home = (SimpleHome)
PortableRemoteObject.narrow(obj,SimpleHome.class);
Look into this thread as well.
http://forum.java.sun.com/thread.jspa?messageID=413085
4
VJThanks for your answer. It doesn't help me very much.
I find always over ejb but never jms. I need to connect to application server to get the connection factory.
thanks for your help.
Lolo

JMS application without appclient and deploytool

I have a requirement to run a Java application which communicates using JMS. "appclient" should not be used. This application should be able to run as an independent java application. How to achieve this?
Further I do not see "deploytool" in the JES 2004Q2 version, do I need one at all? I guess there is no need to deploy an application for JMS to work. Is that assumption true?
What should jms_client.properties contain? Where can I find the detailed explanation for the file?
Thanks a lot for any help in anticipation.

Hello,
I try to do the same thing as you : not use the appclient command, but my application must be an independent java application.
I can run a java application which lookup connectionFactory & destination created in the S1AS admin console on my localhost. the code look like this:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
props.put(Context.PROVIDER_URL,"iiop://localhost:3700");
jndiContext = new InitialContext(props);
to run the application, the classpath must contains :
%J2EE_HOME%\lib\j2ee.jar
%J2EE_HOME%\lib\appserv-rt.jar
%J2EE_HOME%\lib\lib\appserv-admin.jar
%IMQ_HOME%\lib\imqjmsra.jar
don't forget to also put your java application class.
then you can run the application (I try with the simple J2EE 1.4 tutorial):
java SimpleProducer jms/Queue 3
It's works.
But, when I try to get connectionfactory and destination from a remote server, it's not works...
my code:
props.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.enterprise.naming.SerialInitContextFactory");
props.put(Context.PROVIDER_URL,"iiop://<myservername>:3700");
the port number is ok, and the app server and JMS service is running.
The jms/JupiterConnectionFactory (to get connection with the JMS service) and the jms/Queue (destination) exists on the remote server.
And when I run the application on my machine, I have this error:
Destination name is jms/Queue
JNDI API lookup failed: javax.naming.NameNotFoundException: JupiterConnectionFac
tory not found
javax.naming.NameNotFoundException: JupiterConnectionFactory not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.
java:185)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.ja
va:157)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.ja
va:161)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialCont
extProviderImpl.java:96)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie
._invoke(Unknown Source)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tchToServant(CorbaServerRequestDispatcherImpl.java:651)
at com.sun.corba.ee.impl.protocol.CorbaServerRequestDispatcherImpl.dispa
tch(CorbaServerRequestDispatcherImpl.java:190)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
Request(CorbaMessageMediatorImpl.java:1653)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:1513)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleInput(C
orbaMessageMediatorImpl.java:895)
at com.sun.corba.ee.impl.protocol.giopmsgheaders.RequestMessage_1_2.call
back(RequestMessage_1_2.java:172)
at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.handleRequest
(CorbaMessageMediatorImpl.java:668)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.dispatc
h(SocketOrChannelConnectionImpl.java:375)
at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.read(So
cketOrChannelConnectionImpl.java:284)
at com.sun.corba.ee.impl.transport.ReaderThreadImpl.doWork(ReaderThreadI
mpl.java:73)
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.
run(ThreadPoolImpl.java:382)
I don't understand, my objects really exists on the remove app server.
How to do this ?
I have another questions.
When you use the S1AP admin console to create JMS connectionFactory and Destination, where these objects are physically stored ?
Because, when you use the Sun MQ broker admin console, you don't see the connectionFactory and destination that you create in S1AP admin console (but only the physical destination).
And when you choose, in the MQ admin console, to use the com.sun.jndi.fscontext.RefFSContextFactory JNDI service properties to store your objects, you can see a .bindings file in your directory (file:///tmp if you choose this for example) which contains connectionFactory and destination objects.
Someone can help me too ?
Thanks.

Stoping JMS application graceful

Similar Messages

Maybe you are looking for