[jboss-jira] [JBoss JIRA] Commented: (JBAS-3417) SocketException during minimal tests

[Scott M Stark (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBAS-3417?page=comments#action_12376793 ] 
            
Scott M Stark commented on JBAS-3417:
-------------------------------------

The test is running fine:

jboss-minimal-tests:
[server:start] Starting server "minimal" with command:
[server:start] /usr/java/jdk1.5.0_11/bin/java -cp /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/bin/run.jar:/usr/java/jdk1.5.0_11/lib/tools.jar  org.jboss.Main -c minimal -b localhost
     [copy] Copying 1 file to /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/minimal/deploy
     [echo] Minimal server started, stopping
   [delete] Deleting: /home/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.Beta3/server/minimal/deploy/shutdown.sar

BUILD SUCCESSFUL
Total time: 18 seconds

this just seems to be noise from a incomplete request. The source of the access to the naming port needs to be tracked down.


> SocketException during minimal tests
> ------------------------------------
>
>                 Key: JBAS-3417
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3417
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-5.0.0.Beta1
>         Environment: win xp, fedora core 5
>            Reporter: Jaroslaw Kijanowski
>
> while running the first test of the testsuite (jboss-minimal-tests), get a java.net.SocketException.
> server.log:
> 2006-07-22 17:05:55,046 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
> 2006-07-22 17:05:55,046 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/D:/jboss3/jboss-head/build/output/jboss-5.0.0.Beta/server/minimal/conf/jboss-service.xml
> 2006-07-22 17:05:55,046 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [5.0.0.Beta (build: CVSTag=HEAD date=200607220701)] Started in 3s:359ms
> 2006-07-22 17:05:55,281 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)
> 	at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1585)
> 	at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:1167)
> 	at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1121)
> 	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1278)
> 	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1073)
> 	at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1392)
> 	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:294)
> 	at org.jnp.server.Main$BootstrapRequestHandler.run(Main.java:476)
> 	at org.jboss.util.threadpool.RunnableTaskWrapper.run(Unknown Source)
> 	at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
> 	at java.lang.Thread.run(Thread.java:595)

-- 
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