Standalone applications
Hi, In the System.exit(1) thread, I've read that some people was using some auto-executable files to start up some standalone applications, but I haven't been able to find some clear documentation about it. I've tried with the Sun J2EE tutorials and the J2EE spec but it does not get to the details. Is there any place where I can get more specific documentation? And Orion specific documentation? My problem is that I can move my web applications from one host to another very easily, but I have to modify each time the standalone application startup scripts, so I was wondering if there was a standard way to miminize it. I guess you have to use the java tag in the application.xml descriptor... but how do you execute the application, where do you specify properties like the classpath, -D properties... Thanks in advance, D.
Clusters, JMS, and standalone applications
Greetings. I am having difficulty with getting JMS working under Orion in a clustered environment. The general layout of the cluster is this, 1 (or more) Util machines, one of which is running the JMS server. -Run high-load utility programs that are listening on various Queues for new jobs (basically offline batch processes) 1 Load Balancer machine 2 (or more) Web/App Servers. Some applications will send messages to the Queues for execution offline by the listening utility programs. Initially when I tried to set this up, I tried to have the applications log into Queues in the cluster. This threw all kinds of weird exceptions, and also looked like I would have to have one instance of each utility program per running instance of Orion. So I tried moving all the Queues to the Utility server, and running the Utility programs from there. I set the jms.xml file (attached) to the IP address of the Util box. Unfortunately, the util apps are STILL not getting messages (which are sent by EJB's). No errors are getting thrown, so I suspect that the messages are being put on the local queues. If anyone has any examples of how to set this up, it would be greatly appreciated. Thanks, Steve ?xml version=1.0? !DOCTYPE jms-server PUBLIC Orion JMS server http://www.orionserver.com/dtds/jms-server.dtd; !-- jms-server port=9127 -- jms-server port=9127 xa-queue-connection-factory host=192.168.0.72 location=com.hrnexus.JMSFactory password=hrnexus username=user / !-- Queue bindings, these queues will be bound to their respective JNDI path for later retrieval -- queue name=RFP Release Queue location=com.hrnexus.RFPReleaseQueue host=192.168.0.72 password=hrnexus username=user descriptionRFP Processing/description /queue queue name=ImportJMSQueue location=com.hrnexus.ImportJMSQueue host=192.168.0.72 password=hrnexus username=user descriptionImporter Message Queue/description /queue queue name=CustomerSetupMessages location=com.hrnexus.CustSetupQueue host=192.168.0.72 password=hrnexus username=user descriptionCustomer Setup Information/description /queue !-- Topic bindings, these topic will be bound to their respective JNDI path for later retrieval -- !-- Not currently used topic name=Demo Topic location=jms/demoTopic descriptionA dummy topic/description /topic -- !-- path to the log-file where JMS-events/errors are stored -- log file path=../log/jms.log / /log /jms-server
Re: Clusters, JMS, and standalone applications
You should be able to keep one machine as JMS server and run different subscribers/publishers on different machines. This only gotcha is you can't run the subscribers as MessageListeners, I tried to run subscriber as a listener on different machine but some how the listener mode doesn't work. For subscribers instead of listener you have to use blocing method. i.e qsession.createReceiver().receive() method. You have to use this type of blocking subscribers. - Original Message - From: Stephen Davidson [EMAIL PROTECTED] To: Orion-Interest [EMAIL PROTECTED] Sent: Tuesday, September 25, 2001 3:08 PM Subject: Clusters, JMS, and standalone applications Greetings. I am having difficulty with getting JMS working under Orion in a clustered environment. The general layout of the cluster is this, 1 (or more) Util machines, one of which is running the JMS server. -Run high-load utility programs that are listening on various Queues for new jobs (basically offline batch processes) 1 Load Balancer machine 2 (or more) Web/App Servers. Some applications will send messages to the Queues for execution offline by the listening utility programs. Initially when I tried to set this up, I tried to have the applications log into Queues in the cluster. This threw all kinds of weird exceptions, and also looked like I would have to have one instance of each utility program per running instance of Orion. So I tried moving all the Queues to the Utility server, and running the Utility programs from there. I set the jms.xml file (attached) to the IP address of the Util box. Unfortunately, the util apps are STILL not getting messages (which are sent by EJB's). No errors are getting thrown, so I suspect that the messages are being put on the local queues. If anyone has any examples of how to set this up, it would be greatly appreciated. Thanks, Steve ?xml version=1.0? !DOCTYPE jms-server PUBLIC Orion JMS server http://www.orionserver.com/dtds/jms-server.dtd; !-- jms-server port=9127 -- jms-server port=9127 xa-queue-connection-factory host=192.168.0.72 location=com.hrnexus.JMSFactory password=hrnexus username=user / !-- Queue bindings, these queues will be bound to their respective JNDI path for later retrieval -- queue name=RFP Release Queue location=com.hrnexus.RFPReleaseQueue host=192.168.0.72 password=hrnexus username=user descriptionRFP Processing/description /queue queue name=ImportJMSQueue location=com.hrnexus.ImportJMSQueue host=192.168.0.72 password=hrnexus username=user descriptionImporter Message Queue/description /queue queue name=CustomerSetupMessages location=com.hrnexus.CustSetupQueue host=192.168.0.72 password=hrnexus username=user descriptionCustomer Setup Information/description /queue !-- Topic bindings, these topic will be bound to their respective JNDI path for later retrieval -- !-- Not currently used topic name=Demo Topic location=jms/demoTopic descriptionA dummy topic/description /topic -- !-- path to the log-file where JMS-events/errors are stored -- log file path=../log/jms.log / /log /jms-server
