GlassFish lockups were Microsoft's fault

Just days after the official release of GlassFish V2 in September 2007, we migrated one of our production applications from JBoss 4 to GlassFish V2. I had been playing with GlassFish V1 and later V2 for many months and -really- liked the command line and web based admin console. Earlier I had been given the opportunity to make major changes to our application to port it over to Java EE 5 using features such as JSF, JPA, JAX-WS and EJB 3. I had also converted our proprietary JBoss JMX MBean service to a standard JCA resource adapter. The rollout of GlassFish V2 and the new version of our application went smoothly, and we lived happily ever after. Well, not quite. A few weeks later we experienced our first lockup.

[Read More]

Comments (2)