Why you choose SNMP when Glassfish have strong JMX support? I presume, the answer for all who use SNMP is (almost) the same: Because the architecture of current monitoring solution is not scalable enough, and I cannot load my monitoring servers with supplementary JAVA processes.

Share this post

Hide Bookmarks

This, probably, is a bug which was not spotted very often because is very obscure and the Debian guys moved very quick and fixed the problem. I know, I found a lot of bugs related to sun.jvm.hotspot.debugger.NoSuchSymbolException: Could not find symbol “gHotSpotVMTypeEntryTypeNameOffset”, but this is different. Usually was a problem of “striping symbols from libjvm.so”, but in my case wasn’t that. Also I found this error related to OpenJDK (I use Sun JDK) and the solution was to use -server flag to get the correct libjvm.so. Anyway it took me …

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