Home » Archive

Articles in the Glassfish Category

Clustering, Debian, Featured, Glassfish, How-to, Java »

[14 Mar 2011 | No Comment | ]

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

Clustering, Featured, Glassfish, Headline, Java, Shell »

[3 Mar 2010 | 3 Comments | ]

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 …

Clustering, Featured, Glassfish, Headline, How-to, Java »

[29 Dec 2009 | One Comment | ]

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

Apache, Bugs, Debian, Featured, Glassfish, Headline, How-to, Java, Linux, Shell, Tuning »

[28 Sep 2009 | No Comment | ]

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 …

Clustering, Glassfish, How-to, Java, Newbie »

[28 May 2009 | One Comment | ]

Why you should do that? All this ports, by default, are allocated dynamically and if you want to use a firewall between your client and JMS broker then you should have static ports assigned. Another solution is to tunnel through httpjms and httpsjms protocol but this are slow. In the next article I will show you how to assign static ports to this JMS service in Glassfish. To show you the all ports what need for JMS I just “ripped” the following table from SUN Site: http://docs.sun.com/app/docs/doc/820-4916/gcuhq?a=view

Share …