1 Reply Latest reply on Jun 20, 2008 3:25 AM by Ron Sigal

    EJB3.0 Slower when using Jboss Serialization

    Sebastien Degardin Newbie

      Hi All,

      I'm developing and EJB3.0 application, using remote Call from client (java SE).

      When I switch the EJB 3 Invoker to use Jboss Serialization, it seems to be slower. (about 200ms for a remote call that takes 150ms with default config).

      I only update the jboss-service.xml file located in /server/default/deploy/ejb3.deployer/META-INF

      Here is the config of my invoker ::

       <mbean code="org.jboss.remoting.transport.Connector"
       name="jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3">
       <depends>jboss.aop:service=AspectDeployer</depends>
       <attribute name="InvokerLocator">socket://${jboss.bind.address}:3873/?serializationtype=jboss</attribute>
       <attribute name="Configuration">
       <handlers>
       <handler subsystem="AOP">org.jboss.aspects.remoting.AOPRemotingInvocationHandler</handler>
       </handlers>
       </attribute>
       </mbean>
      


      Tks.

        • 1. Re: EJB3.0 Slower when using Jboss Serialization
          Ron Sigal Master

          Well, it looks like your configuration is correct.

          Our experience in Remoting with our performance tests is that the socket transport is considerably faster with JBossSerialization than with ordinary java serialization, but there are no guarantees. It's certainly possible that the situation is reversed, depending on the circumstances. I really don't know enough about JBossSerialization to say more than that.

          By the way, if you're doing EJB3 calls sequentially, you might take a look at JBREM-877 "New Socket Connection is being Created for Every Client Request to the Server" at http://jira.jboss.com/jira/browse/JBREM-877. Depending on your calling patthen, it might help you speed things up.