clif console runs out of memory at the end of a test
the following exception is repeated several times :
[java] Exception while serving classes
[java] java.net.SocketException: Connection reset by peer: socket write error
[java] at java.net.SocketOutputStream.socketWrite0(Native Method)
[java] at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) [java] at java.net.SocketOutputStream.write(SocketOutputStream.java:136) [java] at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) [java] at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) [java] at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) [java] at java.io.OutputStreamWriter.write(OutputStreamWriter.java:191)
[java] at
org.objectweb.clif.supervisor.lib.CodeServer$ClassServerRequest.run(CodeServer.java:173) [java] {0=initialized} [java] {0=starting} [java] {0=running} [java] {0=completed} [java] java.lang.OutOfMemoryError
The "out of memory" error occurs at the end of a test. The test is not so long (about an hour, I've benched for 4 - 5 hours without problems with previous versions of clif). When got an out of memory, the console becomes slow to refresh (cpu ramps up to 100% for a while before the console is redisplayed). Trying to see if it comes from my scenario.
-clif version : 0.2a4 (compiled 2004-aug-05) -the scenario which was executed was an own scenario, based on MTScenario, and emitting http queries built with the jakarta common http lib -OS : redhat linux with sun's JVM 1.4.2-b28 for injector and application server -console under windows 2000 with the same VM. -the problem is not application server dependent