Lately I have been a spending significant amount of time analyzing issues coming from sailfin performance team and system testing team. One of them was particularly tricky. Testing team was running a test 24x7 on a 10 instance sailfin cluster with CLB etc.
Tomorrow (Wednesday) morning at 9.30am, me and Kristoffer talk about SailFin architecture. The Venue is Hall E 134. This session gives the details about the project architecture, features and roadmap.
One of my Sun collegues (Bobby) noticed that glassfish web server stops responding soon after the startup. The most interesting thing he found was that he can access the webserver using http://localhost:8080 where as accessing it using IP address (http://x.x.x.x:8080) wasnt working.
At Indian Institute of Science, a prestigious educational institution in Bangalore, year 2006 edition of the http://foss.in will be held. GlassFish will have significant presence this time (November 24, 25 and 26) also.
In a typical Java EE application, MDBs are used to listen to messages from the external systems and act as integration point between two systems. Wouldnt it be good, if that MDB become part of a composite application and thus leverage full capability of JBI also? The example composite application below explains how a BPEL app is accessed from MDB.
Each J2EE application server comes with their own JMS providers. For a developer, it is a good thing. He can write his jms apps and MDBs easily. But a production environment might be quite different. In many cases, people write a new J2EE application and use it with their existing software stack.
This is my first ever blog. I am basically a developer/engineer by profession (not a writer). So, please don't expect my blogs to be anywhere near an organized reading material.
Lets come to the topic.