5:17 a.m.
Hello,
during the testsuite run, there is always (in head, jboss4,
jboss 3.2.7) one error during the jboss-minimal-tests:
This can be found in the server.log:
2006-10-12 17:58:35,109 DEBUG [org.jboss.naming.NamingService] Error writing response to
/127.0.0.1
java.net.SocketException: Software caused connection abort: socket write error
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:1676)
For some AS versions, this error prevents the testsuite to continue,
for some not.
This error occurs in the following section:
jboss\naming\src\main\org\jnp\server\Main.java
private class BootstrapRequestHandler implements Runnable
{
.
.
.
OutputStream os = socket.getOutputStream();
ObjectOutputStream out = new ObjectOutputStream(os);
out.writeObject(serverStub); <- this cause the Exception
out.close();
.
.
I can eliminate this, by replacing BOTH lines:
ObjectOutputStream out = new ObjectOutputStream(os);
out.writeObject(serverStub); <- this cause the Exception
with
os.write(123);
This makes the test running fine, but it's nonsense. Or does it mean,
that this part of code isn't needed anymore?
Can anybody tell me, where the written object is received? I couldn't find
an appropriate code. Only this:
jboss\naming\src\main\org\jnp\interfaces\NamingContext.java
static Naming getServer(String host, int port, Hashtable serverEnv)
throws NamingException
{
.
.
.
// Get stub from naming server
BufferedInputStream bis = new BufferedInputStream(s.getInputStream());
ObjectInputStream in = new ObjectInputStream(bis);
MarshalledObject stub = (MarshalledObject) in.readObject();
server = (Naming) stub.get();
s.close();
.
.
.
But this method is never called during the minimal-tests.
Any ideas?
--
Best regards,
Jarek
mailto:jaroslaw.kijanowski@jboss.com
5:59 a.m.
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@jboss.com
JK> _______________________________________________
JK> jboss-development mailing list
JK> jboss-development(a)lists.jboss.org
JK> https://lists.jboss.org/mailman/listinfo/jboss-development
11:01 a.m.
The write of the stub is still used and is read by the
org.jnp.interfaces.NamingContext code you are showing. I need to see why
this is an issue with the minimal test. When you see a failure, its that
the server is not shutting down or what?
Jaroslaw Kijanowski wrote:
Hello,
during the testsuite run, there is always (in head, jboss4,
jboss 3.2.7) one error during the jboss-minimal-tests:
This can be found in the server.log:
2006-10-12 17:58:35,109 DEBUG [org.jboss.naming.NamingService] Error writing response to
/127.0.0.1
java.net.SocketException: Software caused connection abort: socket write error
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:1676)
For some AS versions, this error prevents the testsuite to continue,
for some not.
This error occurs in the following section:
jboss\naming\src\main\org\jnp\server\Main.java
private class BootstrapRequestHandler implements Runnable
{
.
.
.
OutputStream os = socket.getOutputStream();
ObjectOutputStream out = new ObjectOutputStream(os);
out.writeObject(serverStub); <- this cause the Exception
out.close();
.
.
I can eliminate this, by replacing BOTH lines:
ObjectOutputStream out = new ObjectOutputStream(os);
out.writeObject(serverStub); <- this cause the Exception
with
os.write(123);
This makes the test running fine, but it's nonsense. Or does it mean,
that this part of code isn't needed anymore?
Can anybody tell me, where the written object is received? I couldn't find
an appropriate code. Only this:
jboss\naming\src\main\org\jnp\interfaces\NamingContext.java
static Naming getServer(String host, int port, Hashtable serverEnv)
throws NamingException
{
.
.
.
// Get stub from naming server
BufferedInputStream bis = new BufferedInputStream(s.getInputStream());
ObjectInputStream in = new ObjectInputStream(bis);
MarshalledObject stub = (MarshalledObject) in.readObject();
server = (Naming) stub.get();
s.close();
.
.
.
But this method is never called during the minimal-tests.
Any ideas?
2:04 p.m.
New subject: Re[2]: jboss-minimal-tests problem
Right, the server is not shutting down properly:
[jkijanowski@dev02 testsuite]$ ./build.sh jboss-minimal-tests
Searching for build.xml ...
Buildfile: /home/jkijanowski/JBoss_4_0_4_GA_CP01/testsuite/build.xml
Overriding previous definition of reference to xdoclet.task.classpath
jboss-minimal-tests:
[server:start] Starting server "minimal" with command:
[server:start] /opt/j2sdk1.4.2_09/bin/java -cp
/home/jkijanowski/JBoss_4_0_4_GA_CP01/build/output/jboss-4.0.4.GA_CP01/bin/run.jar:/opt/j2sdk1.4.2_09/lib/tools.jar
org.jboss.Main -c minimal -b localhost
[copy] Copying 1 file to
/home/jkijanowski/JBoss_4_0_4_GA_CP01/build/output/jboss-4.0.4.GA_CP01/server/minimal/deploy
[echo] Minimal server started, stopping
[delete] Deleting:
/home/jkijanowski/JBoss_4_0_4_GA_CP01/build/output/jboss-4.0.4.GA_CP01/server/minimal/deploy/shutdown.sar
BUILD SUCCESSFUL
Total time: 19 seconds
Found server "minimal" still running; stopping it.
Shutting down server: minimal
++++++++++++++++++++++++++++++++++
I can reproduce the log with the "broken pipe" only in qa lab. When I
run the minimal test at home I get a log with
"java.net.SocketException: Software caused connection abort: socket
write error", as described in the first log.
The broken pipe is maybe a firewall issue. But what about "socket
write error"?
Can you reproduce this error?
The write of the stub is still used and is read by the
org.jnp.interfaces.NamingContext code you are showing. I need to see why
this is an issue with the minimal test. When you see a failure, its that
the server is not shutting down or what?
Jaroslaw Kijanowski wrote:
> Hello,
> during the testsuite run, there is always (in head, jboss4,
> jboss 3.2.7) one error during the jboss-minimal-tests:
> This can be found in the server.log:
>
> 2006-10-12 17:58:35,109 DEBUG [org.jboss.naming.NamingService]
> Error writing response to /127.0.0.1
> java.net.SocketException: Software caused connection abort: socket write error
> 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:1676)
>
> For some AS versions, this error prevents the testsuite to continue,
> for some not.
>
> This error occurs in the following section:
> jboss\naming\src\main\org\jnp\server\Main.java
>
> private class BootstrapRequestHandler implements Runnable
> {
> .
> .
> .
> OutputStream os = socket.getOutputStream();
> ObjectOutputStream out = new ObjectOutputStream(os);
> out.writeObject(serverStub); <- this cause the Exception
> out.close();
> .
> .
>
> I can eliminate this, by replacing BOTH lines:
>
> ObjectOutputStream out = new ObjectOutputStream(os);
> out.writeObject(serverStub); <- this cause the Exception
>
> with
> os.write(123);
>
> This makes the test running fine, but it's nonsense. Or does it mean,
> that this part of code isn't needed anymore?
>
> Can anybody tell me, where the written object is received? I couldn't find
> an appropriate code. Only this:
>
> jboss\naming\src\main\org\jnp\interfaces\NamingContext.java
>
> static Naming getServer(String host, int port, Hashtable serverEnv)
> throws NamingException
> {
> .
> .
> .
> // Get stub from naming server
> BufferedInputStream bis = new
> BufferedInputStream(s.getInputStream());
> ObjectInputStream in = new ObjectInputStream(bis);
> MarshalledObject stub = (MarshalledObject) in.readObject();
> server = (Naming) stub.get();
>
> s.close();
> .
> .
> .
>
> But this method is never called during the minimal-tests.
>
> Any ideas?
>
>
7157
days inactive
7157
days old
jboss-development@lists.jboss.org
3 comments
2 participants
participants (2)
-
Jaroslaw Kijanowski -
Scott M Stark