Receiver.java show how to use queue for point-to-point messaging in JMS, while Publisher.java and Subscriber.java show how to use topic for publish/subscribe messaging. The "Readme.txt" file (also on the Web) contains the commands to run various applications and the latest information about the code. Before attempting to run these applications, be sure to read the "install.txt" file and make the necessary
Http://localhost:8001/console the first time when landing need to deploy, will automatically refresh (without the words of their own manual brush), take Bootuser login.
Left domain structure--ipcdomain--service--The message delivery--JMS module to the right INTEROP-JMS point in the page refresh, display a lot of their own definition of the queue, find want to emp
Http://localhost:8001/console the first time to log in need of deploy, will automatically refresh (not if you manually brush it), take Bootuser login.
Left domain structure--ipcdomain--service--Messaging--JMS module right INTEROP-JMS point in the page refresh, display a lot of their defined queue, find the queue to cle
1. Developed a simple small program to monitor the operation of WebLogic, friends download to try, do not have to login console to know the health of the server, including the JVM, thread, JDBC, state JMS, etc., there is a simpler option, drop-down select " Warning ", directly see if there is waiting queue, JVM tense, connection pool leakage, connection pool wait
Monitor weblogic server, Very simple to use, weblogic monitoring, inspection, fault simple tool, monitorweblogic1. I developed a simple small program to monitor weblogic running conditions. You can download it and try it. You don't have to log on to the console to know the running status of the server, including jvm, t
();
}
}
}); Thread.Sleep (1000000); }
} Queue up with an Oracle block and see the data in the Queues table when Java is not started. After starting Java, the console correctly outputs the message, and writes the message again through the Oracle program block, discovering that the console is handling the message correctly. The JMS listener in Java is not processed immediately,
JMX:
Tomcat Edit tomcat_home/bin/catalina.sh Add the following lines at the beginning
Catalina_opts= "${catalina_opts}-djava.rmi.server.hostname=jmx_host" # Modify Jmx_hostCatalina_opts= "${catalina_opts}-djavax.management.builder.initial="Catalina_opts= "${catalina_opts}-dcom.sun.management.jmxremote=true"Catalina_opts= "${catalina_opts}-dcom.sun.management.jmxremote.port=jmx_port" # Modify the JMS portCatalina_opts= "${catalina_opts}-
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.