Musings of a Trained Monkey: Tag bea

Running BEA WebLogic Server on OS X...

Steve Longdo — Sun, 29 Apr 2007 19:31:00 +0000

People have trying installs of BEA WLS on OS X out for awhile. I remember installing WLS 9.2 back in 2005. I recently ran across a blog entry about installing WLS 10.0. I’m still using a PPC Mac with not nearly enough RAM, so I thought I would try to see how the 10.0 performance would be compared to my 9.2 experience.

Surprisingly 10.0 is much slower to start up. I appreciate that OS X and Apple’s JVM aren’t a supported platform, but still it took almost 7 minutes for the MedRec sample domain to start up! Under 9.2 it was only 2 minutes. Back when I installed 9.2 Apple’s JVM was 1.5 and I have 1.6 running now.

I wanted to do a fair comparison, but apparently installing 10.0 with Apple’s 1.6 JVM overwrites the PointBase configuration such that 9.2 won’t even start up the MedRec sample domain (incompatible serial uids for javax.xml.namespace.QName if anyone cares). Also Apple says that uninstalling their 1.6 beta is a bad idea?!? I’m sure I could probably clean it up and get it running, but that would exceed my ten minute or so attention span for working on Java stuff at home.

Tomcat 5.5/Java 5 and SSL...

Steve Longdo — Mon, 12 Dec 2005 20:30:00 +0000

I ran into a puzzling situation trying to setup Yale's CAS and the Spring Framework/Acegi contacts sample application on my workstation. I had CAS deployed on Tomcat 5.5 and the Acegi sample application deployed on BEA WebLogic 9.0, both running under Sun's JDK 1.5.0_06. I kept getting errors like:

Your CAS credentials were rejected.

Reason: HTTPS hostname wrong: <localhost> should be <127.0.0.1>

I couldn't figure this out because the server.xml for Tomcat included both the keystoreFile and truststoreFile parameters for the SSL connection. The JVM JRE cacerts file included self-signed certs for both the BEA server and the Tomcat server which should be picked up system wide whether or not I specifically include it in the server.xml file. I am not sure why but putting the following option on the Tomcat command line solved the problem:

-Djavax.net.ssl.trustStore="C:\Program Files\Java\jre1.5.0_06\lib\security\cacerts"

You can also see from this that it is a Windows workstation... I am documenting this for the benefit of other programmers and Google (which doesn't have much of anything about this particular problem).