1 Reply Latest reply on Mar 9, 2009 8:48 PM by Ron Sigal

    Web Start Application Hang

    Christoph Kalsdorf Newbie

      Hi all,

      Short description of my issue:

      200 clients connecting to one Application Server (the server where Jboss is running)
      From time to time the users can not log on to the system anymore.
      Already logged on users can continue to work on the system
      If we restart the Jboss server new users can log on again until the next time this incident occurs.

      We figured out that using pooled (instead of jrmp) invoker for stateless-rmi-invoker should solve that problem. The thing is that the overall performance of the application was not acceptable after this change.

      Is there any Jboss configuration expert who could help setting the parameters proper?

      Thanks in advance for your effort

        • 1. Re: Web Start Application Hang
          Ron Sigal Master

          The pooled and rmi invokers are both legacy invokers and are not part of Remoting. The current default behavior for EJB2, EJB3, and JBossMessaging is to use an invoker based on Remoting. In particular:

          * EJB2 uses UnifiedInvoker (see "jboss:service=invoker,type=unified" in $JBOSS_HOME/server/$CONFIG/conf/jboss-service.xml)

          * EJB3 uses a variation of UnifiedInvoker (see "jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3" in $JBOSS_HOME/server/$CONFIG/deploy/ejb3.deployer/META-INF/jboss-service.xml)

          Once you're using a Remoting based invoker, based on the Remoting socket transport, you can increase the number of worker threads on the server side, which would increase the number of clients that can connect to the server, with the "maxPoolSize" parameter. The default value, by the way, is 300.

          For more information see Chapter 5 "Configuration" in the Remoting Guide:

          * http://www.jboss.org/jbossremoting/docs/guide/2.2/html/index.html for Remoting version 2.2.2.SP10, and

          * http://www.jboss.org/jbossremoting/docs/guide/2.5/html/index.html for version 2.5.0.SP2.