This entry demonstrates how to connect a JMX custom program to the JMX agent in Java CAPS 5.1.3 or 6 application server.[Read More]
Tuesday Oct 06, 2009
Saturday May 30, 2009
There are many situations where it is very helpful to get a dump of all Java threads inside the application server. Sometimes the application server does not process messages as fast as it should be. This is caused by deadlocks, Java locks or threads waiting for resources (I/O or CPU). To identify the root cause of the issue the best way is to get a dozen of full thread dumps one after the other typically during 20 seconds.
This blog entry demonstrates how to get such a thread dump for a Java CAPS 5.1 application server remotely from a machine running the Java JDK 1.6.[Read More]
Friday Mar 27, 2009
The Java CAPS Repository Browser is a web application that you can browse the structure of the Java CAPS Repository. You can browse the projects and especially compare different versions of a given Java Collaboration.[Read More]
Sunday Dec 21, 2008
Java CAPS 6 includes the Glassfish Application server.
It is easy to migrate existing web applications from Tomcat to Glassfish.
By doing so, we eliminate the installation of Tomcat.
We can consolidate integration projects built with Java CAPS 6 and Web applications on the same runtimes.
The migration is easy for most of the Java code.
In my experience, the only issues are for a few specific configuration items.[Read More]
Friday Aug 01, 2008
The previous tip on JMX monitoring for JAVA CAPS 5.1 presented only sample scripts to monitor the Java Virtual Machine. The scripts presented here are for monitoring eInsight (the active BPEL instances) and eGate (the active JCD).
[Read More]
This blog copyright 2009 by Eric Lerognon