Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-08 Thread Dushan Abeyruwan
Hi There was an issue at bamboo builder where 1 port (LDAP register port 10389) was blinded due some error thus, build #81-85 was failed. after rectifying the port bind issue,now #86 has build successfully. cheers Dushan On Sun, Jan 8, 2012 at 10:48 AM, Charith Wickramarachchi wrote: > > > On

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Charith Wickramarachchi
On Sun, Jan 8, 2012 at 10:00 AM, Afkham Azeez wrote: > > > On Sun, Jan 8, 2012 at 9:10 AM, Charith Wickramarachchi > wrote: > >> >> >> On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote: >> >>> The only way to reduce the possibility of this happening is to start >>> servers with random portOffs

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Afkham Azeez
On Sun, Jan 8, 2012 at 9:10 AM, Charith Wickramarachchi wrote: > > > On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote: > >> The only way to reduce the possibility of this happening is to start >> servers with random portOffsets. Even then there could be clashes. Can we >> stop the 3.2 build for

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Charith Wickramarachchi
On Sun, Jan 8, 2012 at 6:24 AM, Afkham Azeez wrote: > The only way to reduce the possibility of this happening is to start > servers with random portOffsets. Even then there could be clashes. Can we > stop the 3.2 build for the moment? > > 3.2.0 Build is running on a Remote machine using the Remo

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Afkham Azeez
The only way to reduce the possibility of this happening is to start servers with random portOffsets. Even then there could be clashes. Can we stop the 3.2 build for the moment? -- Afkham Azeez Sent from my phone On Jan 8, 2012 12:39 AM, "Harshana Martin" wrote: > Hi Azeez, > > On Sun, Jan 8, 20

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Harshana Martin
Hi Azeez, On Sun, Jan 8, 2012 at 12:30 AM, Afkham Azeez wrote: > There is another Carbon server running it seems. Yes. I think we need to think about this, since we have both trunk and 3.2.0 builds could go in parallel. Due to this, build was hanged for few hours and i had to cancel the job.

Re: [Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Afkham Azeez
There is another Carbon server running it seems. Caused by: java.net.BindException: Address already in use 07-Jan-2012 00:22:08 at sun.nio.ch.Net.bind(Native Method)07-Jan-2012 00:22:08 at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:126) On Sat, Jan 7, 2012

[Carbon-dev] [Bamboo-Build] WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 has FAILED. Change made by azeez.

2012-01-07 Thread Bamboo
--- WSO2 Carbon Trunk > WSO2 Carbon - Platform Trunk > #84 failed (rerun once). --- This build was manually triggered from the stage: Default Stage by BambooBuil