I have several clusters with Glassfish 2.1.1 in a BIG virtual environment and all worked fine … until I add new processors to this clusters. After upgrade, I started to have problems with HttpSession replication. Starting debugging JXTA, Shoal and the Web Container didn’t help at all. Until I found this page Memory Replication & Multi-threaded Concurrent Access to HttpSessions. My applications was doing multi-thread concurrent access some times (Ajax) and this was the root cause of all lost sessions. I modified sun-web.xml from my application, accordingly with the …

After upgrading to the latest version of Debian squeeze/sid, I was not able to use the networking in java.
If you get:
[2/16/10 10:39 AM] Exception occurred:
java.net.SocketException: Network is unreachable
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)

Share this post

…

For some reasons the asupgrade tool from Sun Glassfish doesn’t work if you want to upgrade your Glassfish from 2.1 to 2.1.1. The upgrade method what I will present you in the next post, probably, is not recommended by SUN, but it will work in most cases (clustered or not). Just follow this steps:

Share this post

Hide Bookmarks

A lot of people are not satisfied by the default Java Logging (JUL) in Glassfish. Also, myself I encountered some problems on clustered environments where we should have one single log and not one log for each instance. Trying to change the logging system in Glassfish it looks to be almost impossible , but I found a very interesting project java.util.logging to log4j Bridge and the sky become more clear for Glassfish logging. Jul to Log4J Bridge are part of log4J project and is very useful when you …

Initially, DBAppender for Log4j was introduced in version 1.3 of Log4j, but this version was ABANDONED by Apache team. DBAppender is very useful when we want to send our log on a JNDI resource and not on standard JDBC or file. If you need just logging in a database for your application, then you should use JDBCAppender. If you want to log on a JNDI or Database Connection Pool the DBAppender is for you. In this post I will show you how to get, compile and quick test the DBAppender.

Share …