Saturday January 21, 2006

How is SSL in Glassfish
The SSL (Secure Socket Layer) or TLS (Transport Layer Security) configuration is so simple and is readily available on Glassfish appserver.The latest version is TLS1.0 or SSL3.0.

The default server certificate installed and configured when the appserver is installed and domain is created. The default SSL port is 8181 unless changed during the installation. Once the installation is done, https://localhost:8181/ should work.

The SSL implementation in glassfish is JSSE (Java Secure Socket Extension) and certificate database is the java standard JKS format. The server certificate is a self signed RSA algorithm without any extensions. It is very usual that one generate a certificate request and get signed with a well known CA (Certificate Authority) certificate and import back into the certificate store (say keystore).

There is a simple page on commands and ant based targets for listing , generating, importing and exporting of certificates with keytool is available at handling certs.

...more to come... have a nice weekend!
Posted by Jagadesh Babu Munta ( Jan 21 2006, 12:55:13 AM PST ) Permalink Comments [5]

Monday January 09, 2006

Java process hang - getting stack traces
The other day, I was looking at a java process hang and here are the basic steps followed to get the jvm/native stack traces and core file for further debugging or investigation. I got the deadlock information in the stack!

Solaris platform
Get the entire process tree from your basic command process. Say ps -ef |egrep "java" . Then running ptree pid gives the all the related processes and see the exact process that you would like to have the stack.

Run the following to command to get the stack:
kill -QUIT pid or kill -3 pid

Observe the stack or other information such as deadlock in the console where the command started or connected log or a redirected file.

Use following command to get the native process stack:
pstack pid

To get the core file, use the command - gcore pid .

Windows Platform
Use ctrl+\ on the command window for getting the stack. Not sure if the process started at the background:-(

One of the helpful page, I found is at http://www.unixville.com/~moazam/stories/2004/05/18/debuggingHangsInTheJvm.html
Posted by Jagadesh Babu Munta ( Jan 09 2006, 12:58:22 PM PST ) Permalink Comments [19]