You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/10/02 17:50:41 UTC
Jenkins build is still unstable: Synapse - Trunk #5278
See <https://builds.apache.org/job/Synapse%20-%20Trunk/changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Jenkins build is back to stable : Synapse - Trunk #5281
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Synapse%20-%20Trunk/5281/changes>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Jenkins build is still unstable: Synapse - Trunk #5280
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Synapse%20-%20Trunk/5280/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Jenkins build is still unstable: Synapse - Trunk #5279
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/Synapse%20-%20Trunk/5279/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: Jenkins build is still unstable: Synapse - Trunk #5278
Posted by Ravi Undupitiya <ra...@gmail.com>.
Fixed with r1763120 and build succeeded. But I recall an issue where not
setting SO_REUSEADDR (related to how OS's share sockets) would cause a
similar issue in HTTP core when consecutively binding to a port. So I have
triggered another build to make sure it's not a cleanup issue related to
consecutive builds.
On 3 October 2016 at 11:40, Isuru Udana <is...@gmail.com> wrote:
>
>
> On Mon, Oct 3, 2016 at 11:21 AM, Ravi Undupitiya <
> ravi.undupitiya@gmail.com> wrote:
>
>> Do we have shell access to the build servers to see if some service is
>> using 61616?
>>
>> I had a look at the integration tests and the base classes seem to be
>> handling cleanup of ActiveMQ just fine. This code is also untouched for a
>> while.
>>
>> Since we are not seeing any issues in a local build, shall we use a non
>> standard ActiveMQ port in integration tests?
>>
> +1
>
>>
>>
>>
>> On 3 October 2016 at 06:29, Isuru Udana <is...@gmail.com> wrote:
>>
>>> Sample 250 and 251 integration tests are failing in jenkins. I can build
>>> locally without an issue.
>>>
>>> This is due to a port binding issue for ActiveMQ in jenkins server.
>>>
>>>
>>>
>>> Sample 250: JMS to HTTP
>>> =======================
>>> 2016-10-02 17:41:39,989 [-] [main] ERROR ActiveMQController There was an error starting JMS broker: 0
>>> java.io.IOException: Failed to bind to server socket: tcp://localhost:61616 due to: java.net.BindException: Address already in use
>>> at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
>>>
>>> ........
>>>
>>>
>>> ........
>>>
>>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
>>> Caused by: java.net.BindException: Address already in use
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Sun, Oct 2, 2016 at 11:20 PM, Apache Jenkins Server <
>>> jenkins@builds.apache.org> wrote:
>>>
>>>> See <https://builds.apache.org/job/Synapse%20-%20Trunk/changes>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> *Isuru Udana*
>>> Technical Lead
>>>
>>>
>>>
>>>
>>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
>>> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
>>> <http://mytecheye.blogspot.com/>*
>>>
>>>
>>>
>>>
>>
>
>
> --
> *Isuru Udana*
> Technical Lead
>
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
> <http://mytecheye.blogspot.com/>*
>
>
>
>
Re: Jenkins build is still unstable: Synapse - Trunk #5278
Posted by Isuru Udana <is...@gmail.com>.
On Mon, Oct 3, 2016 at 11:21 AM, Ravi Undupitiya <ra...@gmail.com>
wrote:
> Do we have shell access to the build servers to see if some service is
> using 61616?
>
> I had a look at the integration tests and the base classes seem to be
> handling cleanup of ActiveMQ just fine. This code is also untouched for a
> while.
>
> Since we are not seeing any issues in a local build, shall we use a non
> standard ActiveMQ port in integration tests?
>
+1
>
>
>
> On 3 October 2016 at 06:29, Isuru Udana <is...@gmail.com> wrote:
>
>> Sample 250 and 251 integration tests are failing in jenkins. I can build
>> locally without an issue.
>>
>> This is due to a port binding issue for ActiveMQ in jenkins server.
>>
>>
>>
>> Sample 250: JMS to HTTP
>> =======================
>> 2016-10-02 17:41:39,989 [-] [main] ERROR ActiveMQController There was an error starting JMS broker: 0
>> java.io.IOException: Failed to bind to server socket: tcp://localhost:61616 due to: java.net.BindException: Address already in use
>> at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
>>
>> ........
>>
>>
>> ........
>>
>> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
>> Caused by: java.net.BindException: Address already in use
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sun, Oct 2, 2016 at 11:20 PM, Apache Jenkins Server <
>> jenkins@builds.apache.org> wrote:
>>
>>> See <https://builds.apache.org/job/Synapse%20-%20Trunk/changes>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>>
>> --
>> *Isuru Udana*
>> Technical Lead
>>
>>
>>
>>
>> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
>> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
>> <http://mytecheye.blogspot.com/>*
>>
>>
>>
>>
>
--
*Isuru Udana*
Technical Lead
*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
<is...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*
Re: Jenkins build is still unstable: Synapse - Trunk #5278
Posted by Ravi Undupitiya <ra...@gmail.com>.
Do we have shell access to the build servers to see if some service is
using 61616?
I had a look at the integration tests and the base classes seem to be
handling cleanup of ActiveMQ just fine. This code is also untouched for a
while.
Since we are not seeing any issues in a local build, shall we use a non
standard ActiveMQ port in integration tests?
On 3 October 2016 at 06:29, Isuru Udana <is...@gmail.com> wrote:
> Sample 250 and 251 integration tests are failing in jenkins. I can build
> locally without an issue.
>
> This is due to a port binding issue for ActiveMQ in jenkins server.
>
>
>
> Sample 250: JMS to HTTP
> =======================
> 2016-10-02 17:41:39,989 [-] [main] ERROR ActiveMQController There was an error starting JMS broker: 0
> java.io.IOException: Failed to bind to server socket: tcp://localhost:61616 due to: java.net.BindException: Address already in use
> at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
>
> ........
>
>
> ........
>
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
> Caused by: java.net.BindException: Address already in use
>
>
>
>
>
>
>
>
>
> On Sun, Oct 2, 2016 at 11:20 PM, Apache Jenkins Server <
> jenkins@builds.apache.org> wrote:
>
>> See <https://builds.apache.org/job/Synapse%20-%20Trunk/changes>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
>
> --
> *Isuru Udana*
> Technical Lead
>
>
>
>
> *; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
> <is...@gmail.com> blog: http://mytecheye.blogspot.com/
> <http://mytecheye.blogspot.com/>*
>
>
>
>
Re: Jenkins build is still unstable: Synapse - Trunk #5278
Posted by Isuru Udana <is...@gmail.com>.
Sample 250 and 251 integration tests are failing in jenkins. I can build
locally without an issue.
This is due to a port binding issue for ActiveMQ in jenkins server.
Sample 250: JMS to HTTP
=======================
2016-10-02 17:41:39,989 [-] [main] ERROR ActiveMQController There was
an error starting JMS broker: 0
java.io.IOException: Failed to bind to server socket:
tcp://localhost:61616 due to: java.net.BindException: Address already
in use
at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:33)
........
........
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)
Caused by: java.net.BindException: Address already in use
On Sun, Oct 2, 2016 at 11:20 PM, Apache Jenkins Server <
jenkins@builds.apache.org> wrote:
> See <https://builds.apache.org/job/Synapse%20-%20Trunk/changes>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
*Isuru Udana*
Technical Lead
*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
<is...@gmail.com> blog: http://mytecheye.blogspot.com/
<http://mytecheye.blogspot.com/>*