[jboss-dev] jboss-minimal-tests problem

[Jaroslaw Kijanowski]

The server log is wrong (this happend after my modifications). The original one is as follows:

2006-10-16 06:53:36,015 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.0.4.GA_CP01 (build: CVSTag=https://svn.jboss.org/repos/jbossas/tags/JBoss_4_0_4_GA_CP01 date=200610090734)] Started in 1s:621ms
2006-10-16 06:53:36,033 DEBUG [org.jboss.naming.NamingService] Error writing response to /127.0.0.1
java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1639)
        at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1548)
        at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1146)
        at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1100)
        at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1241)
        at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)
        at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1355)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
        at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:281)
        at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:477)
        at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:148)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
        at java.lang.Thread.run(Thread.java:534)



JK> Hello,
JK>  during the testsuite run, there is always (in head, jboss4,
JK>  jboss 3.2.7) one error during the jboss-minimal-tests:
JK> This can be found in the server.log:

JK> 2006-10-12 17:58:35,109 DEBUG
JK> [org.jboss.naming.NamingService] Error writing response to
JK> /127.0.0.1
JK> java.net.SocketException: Software caused connection abort: socket write error
JK>         at java.net.SocketOutputStream.socketWrite0(Native Method)
JK>         at
JK> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
JK>         at
JK> java.net.SocketOutputStream.write(SocketOutputStream.java:136)
JK>         at
JK> java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1676)
 
JK>  For some AS versions, this error prevents the testsuite to continue,
JK>  for some not.

JK>  This error occurs in the following section:
JK>  jboss\naming\src\main\org\jnp\server\Main.java

JK> private class BootstrapRequestHandler implements Runnable
JK>    {
JK>    .
JK>    .
JK>    .
JK>    OutputStream os = socket.getOutputStream();
JK>    ObjectOutputStream out = new ObjectOutputStream(os);
JK>    out.writeObject(serverStub); <- this cause the Exception
JK>    out.close();
JK>    .
JK>    .

JK>  I can eliminate this, by replacing BOTH lines:

JK>    ObjectOutputStream out = new ObjectOutputStream(os);
JK>    out.writeObject(serverStub); <- this cause the Exception

JK>  with
JK>    os.write(123);

JK> This makes the test running fine, but it's nonsense. Or does it mean,
JK> that this part of code isn't needed anymore?

JK> Can anybody tell me, where the written object is received? I couldn't find
JK> an appropriate code. Only this:

JK> jboss\naming\src\main\org\jnp\interfaces\NamingContext.java

JK> static Naming getServer(String host, int port, Hashtable serverEnv)
JK>       throws NamingException
JK>    {
JK>    .
JK>    .
JK>    .
JK>          // Get stub from naming server
JK>          BufferedInputStream bis = new
JK> BufferedInputStream(s.getInputStream());
JK>          ObjectInputStream in = new ObjectInputStream(bis);
JK>          MarshalledObject stub = (MarshalledObject) in.readObject();
JK>          server = (Naming) stub.get();
         
JK>          s.close();
JK>    .
JK>    .
JK>    .

JK> But this method is never called during the minimal-tests.

JK> Any ideas?

JK> -- 
JK> Best regards,
JK>  Jarek
JK> mailto:jaroslaw.kijanowski at jboss.com

JK> _______________________________________________
JK> jboss-development mailing list
JK> jboss-development at lists.jboss.org
JK> https://lists.jboss.org/mailman/listinfo/jboss-development