[esb-issues] [JBoss JIRA] Closed: (JBESB-1593) Tidy up qa classpaths

[Kevin Conner (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBESB-1593?page=all ]

Kevin Conner closed JBESB-1593.
-------------------------------

    Resolution: Done

Fixed in revision 18827.

> Tidy up qa classpaths
> ---------------------
>
>                 Key: JBESB-1593
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1593
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Testing
>    Affects Versions: 4.2.1 CP1
>            Reporter: Kevin Conner
>         Assigned To: Kevin Conner
>             Fix For: 4.2.1 CP2
>
>
> The CI builds have been failing recently because of classpath issues.
> The linux build was locking up because of a mismatch between the client remoting classes and the server remoting classes.  The test which locked could change, suggesting a race, but the stacktrace was always the same
>      [java]     [junit] "main" prio=1 tid=0x08615068 nid=0x4dec runnable [0xbf8b7000..0xbf8b8228]
>      [java]     [junit]         at java.net.SocketInputStream.socketRead0(Native Method)
>      [java]     [junit]         at java.net.SocketInputStream.read(SocketInputStream.java:129)
>      [java]     [junit]         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
>      [java]     [junit]         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
>      [java]     [junit]         - locked <0x854f7778> (a java.io.BufferedInputStream)
>      [java]     [junit]         at java.io.FilterInputStream.read(FilterInputStream.java:66)
>      [java]     [junit]         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.readVersion(MicroSocketClientInvoker.java:986)
>      [java]     [junit]         at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:572)
>      [java]     [junit]         at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:353)
>      [java]     [junit]         at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
>      [java]     [junit]         at org.jboss.remoting.Client.invoke(Client.java:1550)
>      [java]     [junit]         at org.jboss.remoting.Client.addCallbackListener(Client.java:1619)
>      [java]     [junit]         at org.jboss.remoting.Client.addListener(Client.java:913)
>      [java]     [junit]         at org.jboss.jms.client.remoting.JMSRemotingConnection.addInvokerCallbackHandler(JMSRemotingConnection.java:226)
>      [java]     [junit]         at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:301)
>      [java]     [junit]         at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:154)
> The windows qa tests have not been running because the command line used to start them was too long.  The result of this was that windows would fail to fork the junit process from the build.

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