[JBoss JIRA] Created: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
10:36 a.m.
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
1:23 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Ovidiu Feodorov updated JBMESSAGING-861:
----------------------------------------
Fix Version/s: 1.2.1
(was: 1.2.0.GA)
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.1
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
11:31 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Ovidiu Feodorov updated JBMESSAGING-861:
----------------------------------------
Fix Version/s: Unscheduled
(was: 1.2.1)
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: Unscheduled
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
2:25 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Tim Fox updated JBMESSAGING-861:
--------------------------------
Assignee: (was: Ovidiu Feodorov)
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
Fix For: Unscheduled
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
6:09 a.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Tim Fox updated JBMESSAGING-861:
--------------------------------
Fix Version/s: 1.2.1.CR1
(was: Unscheduled)
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
Fix For: 1.2.1.CR1
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
4:19 a.m.
New subject: [JBoss JIRA] Assigned: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Sergey Koshcheyev reassigned JBMESSAGING-861:
---------------------------------------------
Assignee: Sergey Koshcheyev
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: Sergey Koshcheyev
Fix For: 1.4.0.CR1
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
8:57 a.m.
New subject: [JBoss JIRA] Resolved: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Sergey Koshcheyev resolved JBMESSAGING-861.
-------------------------------------------
Resolution: Done
Remoting configuration moved to src/etc/remoting-*-service.xml. ServiceContainer still
parses it manually though because it needs to create RemotingJMXWrapper out of it, not
Connector. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110533.
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: Sergey Koshcheyev
Fix For: 1.4.0.CR1
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
7:48 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-861) Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration
[ http://jira.jboss.com/jira/browse/JBMESSAGING-861?page=all ]
Tim Fox closed JBMESSAGING-861.
-------------------------------
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: Sergey Koshcheyev
Fix For: 1.4.0.CR1
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
6917
days inactive
7030
days old
7 comments
3 participants
participants (3)
-
Ovidiu Feodorov (JIRA) -
Sergey Koshcheyev (JIRA)
-
Tim Fox (JIRA)