[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
Ovidiu Feodorov (JIRA)
jira-events at lists.jboss.org
Tue Feb 20 11:36:35 EST 2007
Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
-------------------------------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-861
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-861
Project: JBoss Messaging
Issue Type: Feature Request
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Fix For: 1.2.0.GA
Tim:
wrt our discussion about OOM errors in HTTP tests, I notice the service container is currently using the BlockingCallbackStore:
String params =
"/?" +
marshallers +
"serializationtype=" + serializationType + "&" +
dataType +
"socket.check_connection=false&" +
"clientLeasePeriod=" + clientLeasePeriod + "&" +
"callbackStore=org.jboss.remoting.callback.BlockingCallbackStore&" +
"clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&" +
"serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper&" +
"NumberOfRetries=1&" +
"NumberOfCallRetries=2&" +
"callbackErrorsAllowed=1&" +
"onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool";
but the remoting-service.xml is using the standard callback store:
<attribute name="leasePeriod">10000</attribute>
<attribute name="callbackStore">org.jboss.remoting.callback.CallbackStore</attribute>
<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
--
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
More information about the jboss-jira
mailing list