Skip to main content
View by: Most Recent | Topic | Community | Webloggers   
Monthly Archives:    

Blogs by topic J2EE and user rampsarathy

• Accessibility • Ajax • Blogging • Business • Community 
• Databases • Deployment • Distributed • Eclipse • Education 
• EJB • Extreme Programming • Games • GlassFish • Grid 
• GUI • IDE • Instant Messaging • J2EE • J2ME 
• J2SE • Jakarta • JavaFX • JavaOne • Jini 
• JSP • JSR • JXTA • LDAP • Linux 
• Mobility • NetBeans • Open Source • OpenSolaris • OSGi 
• P2P • Patterns • Performance • Porting • Programming 
• Research • RMI • RSS Feeds • Search • Security 
• Servlets • Struts • Swing • Testing • Tools 
• Virtual Machine • Web Applications • Web Design • Web Development Tools • Web Services and XML 


J2EE

SailFin CAFE, like other converged application development frameworks has changed the converged application development paradigm. Having used CAFE APIs so far, if one thought that application development has never been so fast and so easy, things  just got better with v1 b28. Communications (conversation, conference, imconversation, imconference...) that were created by applications were...
on Apr 12, 2010
Converged (Http/SIP) applications gives users the flexibility of creating or accessing information about their communications (call/conferences/im ...) over the web. To make this possible a typical converged application would contain an entry point for all the Http requests, which is mostly an Http Servlet. This servlet would return back appropriate responses by accessing the corresponding...
on Jan 25, 2010
Overload protection feature has been part of earlier releases of SailFin, lets start by describing the what can be improved in the current implementation. The algorithm (in the earlier releases) for detecting an overload was based on the fact that if a certain number of continuous samples remain above the configured threshold then the system is overloaded. This was a simple and...
on Oct 28, 2009
  Lots of fixes have gone into SailFin 2.0, some of these fixes are related to functionality whereas others are to improve performance. The changes sometimes required creation of new user configurable properties in order to extract the optimal-performance/desired-behavior depending on the users deployment. This article tries to explain some of the properties/attributes that were introduced...
on Sep 2, 2009
High availability in SailFin can be achieved by deploying a cluster of instances and configuring the load balancer and the replication modules as per the user's needs. Apart from the basic configuration of these modules, SailFin (2.0) also allows users to separate the intra-cluster traffic (resulting from the load-balancer, replication and the group management service modules) from the external...
on Aug 26, 2009
Simple Stun Server in SailFin STUN (Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs), defined by RFC 3489) is a protocol that helps  devices (clients) behind a NAT firewall or router with routing of packets. The protocol helps devices to find out the type of NAT service (Full Cone, Restricted Cone, Port Restricted Cone and  Symmetric...
on Mar 9, 2009
Generic JMS RA 2.0 is available as an alpha version download today, we are working towards promoting it to a release. One of the main features in 2.0 is the ability to use JMS providers that do not support Chapter 8 (Asynchronous message delivery). The synchronous delivery mode (DeliveryType=Synchronous) can be used to integrate such JMS providers. An article is already available that shows how...
on Sep 19, 2008
Overload Protection in SailFin SailFin has been designed to provide a certain quality of service in terms of the response times, call rate, etc ..  These QoS parameters might be compromised if there is a sudden increase in the load (Calls per second) directed at SailFin or because of some additional load on the CPU on which SailFin is running.  It is important to protect the...
on Jul 25, 2008
Throughput, stress and longevity metrics of the SailFin SIP container depends on a few factors that can be controlled and configured by the end user, and getting the right size of the buffers used internally is one of them. Bulk of the work in processing a SIP message involves reading the message (bytes) out of the socket channel and parsing it to frame a valid SIP message. And in a typical IMS (...
on Jun 30, 2008
SailFin SIP container requires threads to do various tasks like process an incoming request, send a response, execute timers and initiate new requests with clients. The threads required to perform these tasks are obtained from thread pools which are specifically created and configured for the sip-service in SailFin. In other words, the worker threads used in SailFin SIP container are not obtained...
on Jun 27, 2008
In my earlier posts, i had written about the features and enhancements that were introduced in GlassFish V2 in the JMS area. In this post let us see how we can debug JMS related problems (if) in GlassFish. First, a little background on JMS integration in GlassFish V2. Open MQ is the default JMS provider that is bundled with GlassFish V2 and is the only JMS provider whose life cycle (start/stop)...
on Jun 24, 2008
Redelivery with WSMQ 6.0 Using Message redelivery in Generic JMS RA with WebSphere MQ 6.0 Reliable redelivery feature has been available since  generic ra 1.7. During message redeliveries, a new transaction is started by the container every time the MDB endpoint is invoked. Redelivery stratergies are implemented based on how this transaction is handled by the RA and when the state...
on May 14, 2007
Configure_GenericJMSRA_For_ActiveMQ The previous blog entries showed how JMS providers like Jboss Messaging and MantaRay could be used with GlassFish. ActiveMQ is also one such JMS provider http://activemq.apache.org/ , the following steps describe the configurations required to use ActiveMQ with GlassFish.  Install GlassFish V2 and ActiveMQ 4.1 GlassFish V2 : https://glassfish.dev....
on Mar 19, 2007
JMS Service Availability in GlassFish V2 JMS Service Availability in GlassFish V2  Availabilty is the proportion of time a system is in a functioning condition (Wikipedia). It is a vital requirement for any enterprise application.This article talks about how jms service availability can be guaranteed for applications deployed on GlassFish and SJSMQ.  GlassFish V2 allows...
on Feb 17, 2007
Configuring Generic JMS RA for inbound load balancing. In the last blog we saw how MantaRay peer to peer advantage can be leveraged by applications (using JMS) in GlassFish. One issue that was presented there was duplication of message processing by GlassFish clustered instances when consuming messages from a topic destination. Ideal production requirements can  be met, if one and...
on Jan 9, 2007
Distributed (JMS) messaging applications using GlassFish and MantaRay Distributed (JMS) messaging applications using GlassFish and MantaRay     Generic JMS RA (1.7) that is bundled with GlassFish V2 enables applications deployed on GlassFish to use almost any JMS 1.1 compliant message broker. This article talks about how applications (typically Message Driven Beans)...
on Jan 8, 2007
Integrating JBoss Messaging (1.0.1) with Glassfish V2 (Build 26) using Generic JMS RA (1.7) Generic JMS RA (1.7) that is bundled with Glassfish V2 enables applications deployed on Glassfish to use almost any JMS 1.1 compliant message broker. This article talks about how applications (typically Message Driven Beans) deployed in glassfish can use JBoss Messaging as the JMS provider using Generic...
on Dec 4, 2006