[jboss-jira] [JBoss JIRA] Commented: (JBREM-877) New Socket Connection is being Created for Every Client Request to the Server

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-877?page=comments#action_12400394 ] 
            
Ron Sigal commented on JBREM-877:
---------------------------------

I've added a new feature to org.jboss.remoting.Client which allows the destruction of a client invoker to be delayed by some number of microseconds.  The idea is to pick a delay long enough that the client invoker will still be around to be used by the next invocation on the same server.

The delay is turned off by default, but it can be turned on by setting the parameter client.INVOKER_DESTRUCTION_DELAY (actual value "invokerDestructionDelay" to a positive integer.  The value can be set either by

* adding "invokerDestructionDelay=xxx" to the InvokerLocator, or
* adding the value with key "invokerDestructionDelay" to the configuration map passed to the Client constructor.

For EJB3 clients, the value should be set in the Connection MBean in the file <JBOSS_HOME>/server/<config>/deploy/ejb3.deployer/META-INF/jboss-service.xml.

Unit tests: org.jboss.test.remoting.invoker.ClientInvokerDelayedDestructionTestCase

Also committed org.jboss.test.remoting.invoker.InvokerDestructionTest, which illustrates the cost of constantly recreating the client invoker.  Some results can be found in the related forum thread.

Waiting for results in hudson. 

> New Socket Connection is being Created for Every Client Request to the Server
> -----------------------------------------------------------------------------
>
>                 Key: JBREM-877
>                 URL: http://jira.jboss.com/jira/browse/JBREM-877
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.2.SP2
>         Environment: Linux  os , Pentium duo Processor with 3.6 Ghz clock Speed, 4GB Ram in this Postgresql Database also Running
>            Reporter: Kumarselvan Somasundaram
>         Assigned To: Ron Sigal
>            Priority: Critical
>             Fix For: 2.4.0.CR1 (Pinto)
>
>
> whenever  EJB3 client requests the Server new socket is being created. at the client side the socket connection pool is not being used. Hope there is some issue with the socket connection after getting response from the server,becoz of which the server side the connection is being closed. this increases the CPU utilization,
> The same code is running fine in jboss 4.0.4 with jboss remoting 1.4.0
> new remoting 2.2.2 SP4 only handling 1/4 of the load with high CPU utilization. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira