You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Dennis Sosnoski <dm...@sosnoski.com> on 2011/03/11 05:15:43 UTC

Build problem

I've been having a problem in the build for the last several days. This
occurs in systest/jaxws:

FAILURE!
testJAXBObjectPAYLOAD(org.apache.cxf.systest.dispatch.DispatchClientServerTest) 
Time elapsed: 10.453 sec  <<< ERROR!
java.util.concurrent.TimeoutException: Timeout Exceeded
        at
org.apache.cxf.endpoint.ClientCallback.get(ClientCallback.java:166)
        at
org.apache.cxf.jaxws.JaxwsResponseCallback.get(JaxwsResponseCallback.java:54)
        at
org.apache.cxf.systest.dispatch.DispatchClientServerTest.testJAXBObjectPAYLOAD(DispatchClientServerTest.java:508)

I've dug into the code enough to see that the socket receive timeout is
being set on the connection, so I'm wondering if it's a problem with the
socket handling on my system. I'm running OpenSuse 11.3, and have tried
both Java 5 and 6.

Has anyone else encountered this problem? Or have any suggestions how to
handle it, aside from just disabling the test for my builds?

Thanks,

  - Dennis

-- 

Dennis M. Sosnoski
Java SOA and Web Services Consulting <http://www.sosnoski.com/consult.html>
Axis2/CXF/Metro SOA and Web Services Training
<http://www.sosnoski.com/training.html>
Web Services Jump-Start <http://www.sosnoski.com/jumpstart.html>

Re: Build problem

Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Looks like a gremlin. I checked out a clean copy of trunk and the build
now works without a problem.

Thanks,

  - Dennis


On 03/11/2011 06:06 PM, Daniel Kulp wrote:
> No idea.   I haven't seen that test fail.
>
> My only thought is to change the line above it:
> pol.setReceiveTimeout(100);
>
> and try various smaller and larger values.   Maybe it doesn't like such a low 
> timeout.  I don't really know.  :-(
>
> Dan
>
>
> On Thursday 10 March 2011 11:15:43 PM Dennis Sosnoski wrote:
>   
>> I've been having a problem in the build for the last several days. This
>> occurs in systest/jaxws:
>>
>> FAILURE!
>> testJAXBObjectPAYLOAD(org.apache.cxf.systest.dispatch.DispatchClientServerT
>> est) Time elapsed: 10.453 sec  <<< ERROR!
>> java.util.concurrent.TimeoutException: Timeout Exceeded
>>         at
>> org.apache.cxf.endpoint.ClientCallback.get(ClientCallback.java:166)
>>         at
>> org.apache.cxf.jaxws.JaxwsResponseCallback.get(JaxwsResponseCallback.java:5
>> 4) at
>> org.apache.cxf.systest.dispatch.DispatchClientServerTest.testJAXBObjectPAYL
>> OAD(DispatchClientServerTest.java:508)
>>
>> I've dug into the code enough to see that the socket receive timeout is
>> being set on the connection, so I'm wondering if it's a problem with the
>> socket handling on my system. I'm running OpenSuse 11.3, and have tried
>> both Java 5 and 6.
>>
>> Has anyone else encountered this problem? Or have any suggestions how to
>> handle it, aside from just disabling the test for my builds?
>>
>> Thanks,
>>
>>   - Dennis
>>     
>

Re: Build problem

Posted by Daniel Kulp <dk...@apache.org>.
No idea.   I haven't seen that test fail.

My only thought is to change the line above it:
pol.setReceiveTimeout(100);

and try various smaller and larger values.   Maybe it doesn't like such a low 
timeout.  I don't really know.  :-(

Dan


On Thursday 10 March 2011 11:15:43 PM Dennis Sosnoski wrote:
> I've been having a problem in the build for the last several days. This
> occurs in systest/jaxws:
> 
> FAILURE!
> testJAXBObjectPAYLOAD(org.apache.cxf.systest.dispatch.DispatchClientServerT
> est) Time elapsed: 10.453 sec  <<< ERROR!
> java.util.concurrent.TimeoutException: Timeout Exceeded
>         at
> org.apache.cxf.endpoint.ClientCallback.get(ClientCallback.java:166)
>         at
> org.apache.cxf.jaxws.JaxwsResponseCallback.get(JaxwsResponseCallback.java:5
> 4) at
> org.apache.cxf.systest.dispatch.DispatchClientServerTest.testJAXBObjectPAYL
> OAD(DispatchClientServerTest.java:508)
> 
> I've dug into the code enough to see that the socket receive timeout is
> being set on the connection, so I'm wondering if it's a problem with the
> socket handling on my system. I'm running OpenSuse 11.3, and have tried
> both Java 5 and 6.
> 
> Has anyone else encountered this problem? Or have any suggestions how to
> handle it, aside from just disabling the test for my builds?
> 
> Thanks,
> 
>   - Dennis

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog
Talend - http://www.talend.com