[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: PortUtil - Hits Max Will Always Hand Out 65535

jcreynol do-not-reply at jboss.com
Fri Mar 7 23:20:33 EST 2008


Got it.  Need to step through that a little slower.  Thanks for the reply.  Before I post another thread, I see that the docs say Connector has a default "socketTimeout" of 60000, but the default jboss-service.xml -- at least the one that was packaged with the 4.2.0 and 4.2.2 that I have, has this set at 600000.  Beginning to think that's my issue and going to try a 60000 setting to see if that cleans things up a bit and more quickly frees up the WorkerThreads for re-use.

http://labs.jboss.com/jbossremoting/docs/guide/ch05.html#d0e2491

493        <attribute name="Configuration"> 
  | 494           <!-- Using the following <invoker> element instead of the InvokerLocator above because specific attributes needed. --> 
  | 495           <!-- If wanted to use any of the parameters below, can just add them as parameters to the url above if wanted use the InvokerLocator attribute. --> 
  | 496           <config> 
  | 497              <!-- Other than transport type and handler, none of these configurations are required (will just use defaults). --> 
  | 498              <invoker transport="socket"> 
  | 499                 <attribute name="dataType" isParam="true">invocation</attribute> 
  | 500                 <attribute name="marshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationMarshaller</attribute> 
  | 501                 <attribute name="unmarshaller" isParam="true">org.jboss.invocation.unified.marshall.InvocationUnMarshaller</attribute> 
  | 502                 <!-- This will be port on which the marshall loader port runs on.  --> 
  | 503                 <!-- <attribute name="loaderport" isParam="true">4447</attribute> --> 
  | 504                 <!-- The following are specific to socket invoker --> 
  | 505                 <!-- <attribute name="numAcceptThreads">1</attribute>--> 
  | 506                 <!-- <attribute name="maxPoolSize">303</attribute>--> 
  | 507                 <!-- <attribute name="clientMaxPoolSize" isParam="true">304</attribute>--> 
  | 508                 <attribute name="socketTimeout" isParam="true">600000</attribute> 
  | 

Should a Jira issue be created to modify the socketTimeout in jboss-service.xml that ships in the default distribution?  (or maybe the docs need to change?)

Thanks again for the speedy reply!

-John

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135033#4135033

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135033



More information about the jboss-dev-forums mailing list