[jboss-svn-commits] JBL Code SVN: r36768 - labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info.

[jboss-svn-commits at lists.jboss.org]

Author: whitingjr
Date: 2011-03-02 05:42:34 -0500 (Wed, 02 Mar 2011)
New Revision: 36768

Modified:
   labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/benchmark-troubleshooting.txt
   labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/info-refreshing-eap-install-deployment-steps.txt
Log:
Added solutions to issues.
Updated eap refresh notes.

Modified: labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/benchmark-troubleshooting.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/benchmark-troubleshooting.txt	2011-03-02 10:38:47 UTC (rev 36767)
+++ labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/benchmark-troubleshooting.txt	2011-03-02 10:42:34 UTC (rev 36768)
@@ -3,20 +3,23 @@
 Controller errors:
 
 Message: Heartbeat failed for Agent X
+Solution:   Check the client machine has sufficient permission to open files of a sufficient quantity. ulimit -a  
 Solution:	Check satellite log file(s) for OutOfMemoryExceptions. The error will not necessarily be there but it can be the cause.
 Solution:   Synchronize the time on machines in SUT using NTP.
+Solution:   Increase the timeout is run.properties
 Solution:	Increment the value for the number of Client JVMs running on a single Node for the Location.
 Solution:	One possibility is the network is exhausted. A side effect will be sluggish console responsiveness.
-Solution:	Check the client machine has sufficient permission to open files of a sufficient quantity. ulimit -a	
 
 Message: Input rate distribution deviations do not exceed 20%
 Solution:   Increment the driver instances for a location.
 
 Satellite errors:
 
-Message: Connection failure has been detected: Did not receive data from server for .....
-Solution:
+Message in satellite log: WARNING Connection failure has been detected: Did not receive data from server for org.hornetq.core.remoting.impl.netty.NettyConnection
+Solution:   Configure the an increased client-failure-check-period on the connection factory in hornetq-jms.xml 
 
 Message: Cannot maintain pacing distribution
 Solution:	Increment driver thread count for interaction.
 
+Message: Timed out waiting for response when sending packet 43
+Solution: Increase the server to client timeout property connection-ttl. Or set it to -1
\ No newline at end of file

Modified: labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/info-refreshing-eap-install-deployment-steps.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/info-refreshing-eap-install-deployment-steps.txt	2011-03-02 10:38:47 UTC (rev 36767)
+++ labs/jbosstm/workspace/whitingjr/sandbox/batch-execution-SPEC-jms2007/info/info-refreshing-eap-install-deployment-steps.txt	2011-03-02 10:42:34 UTC (rev 36768)
@@ -13,6 +13,9 @@
 
 Place the .so file in the ./native/lib64 directory
 
+Start the server.
+Stop the server.
+
 Change hornetq-configuration
 
 jboss-5.1.0.Branch/server/production/conf/bindingservice.beans/META-INF/bindings-jboss-beans.xml