You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by Glen Daniels <gl...@thoughtcraft.com> on 2009/10/08 18:57:59 UTC
Timeouts building Rampart 1.5?
Hi folks:
Before voting on the 1.5 release, I checked out the branch and did a mvn
clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
first time, and at "custom scenario 4" the second time.
Is anyone else seeing the build hanging? I'd like to confirm this isn't a
problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
Thanks,
--Glen
Re: Timeouts building Rampart 1.5?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Axis2 1.5.1 is not released yet, but the vote [1] is on now. Download/maven
repo info is there.
regards,
Nandana
[1] - http://markmail.org/message/4l7luhabkympe2p3
On Thu, Oct 8, 2009 at 7:38 PM, Thuman, Bernard H <Bernie.Thuman@vangent.com
> wrote:
> Sorry if I should have seen this somewhere, but where can I get access
> to 1.5.1 of axis2?
>
> -----Original Message-----
> From: Nandana Mihindukulasooriya [mailto:nandana.cse@gmail.com]
> Sent: Thursday, October 08, 2009 1:36 PM
> To: rampart-dev@ws.apache.org
> Subject: Re: Timeouts building Rampart 1.5?
>
> Hi Glen,
> I tried with 1.5 and build works fine, but with 1.5.1 it seems
> to
> hang sometimes. Will check little more and update.
>
> regards,
> Nandana
>
> On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
>
> > Hi folks:
> >
> > Before voting on the 1.5 release, I checked out the branch and did a
> mvn
> > clean install... it hung hard at "Testing WS-Sec: custom scenario 3"
> the
> > first time, and at "custom scenario 4" the second time.
> >
> > Is anyone else seeing the build hanging? I'd like to confirm this
> isn't a
> > problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
> >
> > Thanks,
> > --Glen
> >
>
>
RE: Timeouts building Rampart 1.5?
Posted by "Thuman, Bernard H" <Be...@vangent.com>.
Sorry if I should have seen this somewhere, but where can I get access
to 1.5.1 of axis2?
-----Original Message-----
From: Nandana Mihindukulasooriya [mailto:nandana.cse@gmail.com]
Sent: Thursday, October 08, 2009 1:36 PM
To: rampart-dev@ws.apache.org
Subject: Re: Timeouts building Rampart 1.5?
Hi Glen,
I tried with 1.5 and build works fine, but with 1.5.1 it seems
to
hang sometimes. Will check little more and update.
regards,
Nandana
On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
wrote:
> Hi folks:
>
> Before voting on the 1.5 release, I checked out the branch and did a
mvn
> clean install... it hung hard at "Testing WS-Sec: custom scenario 3"
the
> first time, and at "custom scenario 4" the second time.
>
> Is anyone else seeing the build hanging? I'd like to confirm this
isn't a
> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>
> Thanks,
> --Glen
>
Re: Timeouts building Rampart 1.5?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Dennis,
Rampart "org.apache.rampart:rampart-integration" module has
a dependency to "org.apache.axis2:axis2-transport-tcp" module from commons
transport and we are waiting for transports 1.0 release [1] which will
happen soon.
thanks,
Nandana
[1] - http://markmail.org/message/k5dvkwctv6hxxhzm
On Sat, Nov 7, 2009 at 3:59 AM, Dennis Sosnoski <dm...@sosnoski.com> wrote:
> Now that Axis2 1.5.1 is out, is Rampart 1.5 back on track for release?
>
> Thanks,
>
> - Dennis
>
>
>
> Glen Daniels wrote:
>
>> Thanks Nandana.
>>
>> OK, I got Rampart 1.5 building successfully with Axis2 1.5, but I still
>> see
>> the lockups happening when I try 1.5.1. So I'll take a look at this to
>> see
>> what's happening and delay the 1.5.1 release until it's resolved.
>>
>> --Glen
>>
>> Nandana Mihindukulasooriya wrote:
>>
>>
>>> Hi Glen, It seems that it is a SAML2 token test that is failing.
>>> After
>>> introduction of SAML2 tests you have to endorse some jars to run these
>>> tests. It is mentioned in the README file.
>>>
>>> "Test cases written for SAML 2.0 support requires endorsing the JDK's
>>> default JAXP implementation with Xerces(
>>> http://xerces.apache.org/mirrors.cgi#binary) and Xalan(
>>> http://xml.apache.org/xalan-j/downloads.html#latest-release). So before
>>> building Rampart from the source distribution, you need to copy
>>> resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar and
>>> xml-apis-x.x.x.jar from the Xerces binary distribution and
>>> xalan-x.x.x.jar
>>> from the xalan binary distribution to the endorsed directory. If you are
>>> using Sun JDK, endorsed directory is located at
>>> $JAVA_HOME/jre/lib/endorsed."
>>>
>>> Most proelly this should be the reason for above failure. (BTW, do you
>>> know
>>> a better way to handle this situation when we require some jars to be
>>> endorsed to run tests). I wish I could help to figure out the timeout
>>> issue
>>> but unfortunately I am working for an assignment deadline :(.
>>>
>>> regards,
>>> Nandana
>>>
>>> On Thu, Oct 8, 2009 at 11:10 PM, Glen Daniels <gl...@thoughtcraft.com>
>>> wrote:
>>>
>>>
>>>
>>>> Hi Nandana:
>>>>
>>>> Ok, I continued to have problems, so I ended up blowing away my m2
>>>> repository, then building the transports trunk, then building Rampart
>>>> again.
>>>> Now I'm seeing failures. Example:
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------------------
>>>> Test set: org.apache.rahas.RahasSAML2TokenCertForHoKTest
>>>>
>>>>
>>>> -------------------------------------------------------------------------------
>>>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.36 sec
>>>> <<< FAI
>>>> LURE!
>>>> testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) Time
>>>> elapsed:
>>>> 5.36
>>>> sec <<< FAILURE!
>>>> junit.framework.AssertionFailedError: unknown
>>>> at junit.framework.Assert.fail(Assert.java:47)
>>>> at org.apache.rahas.TestClient.testRequest(TestClient.java:117)
>>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>> at
>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>>> java:39)
>>>> at
>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>>> sorImpl.java:25)
>>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>>> at junit.framework.TestCase.runTest(TestCase.java:164)
>>>> at junit.framework.TestCase.runBare(TestCase.java:130)
>>>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>>>> at junit.framework.TestResult.runProtected(TestResult.java:124)
>>>> at junit.framework.TestResult.run(TestResult.java:109)
>>>>
>>>> There are four of them, and again this is with a clean build and clean
>>>> repository.
>>>>
>>>> Could this be a Windows / Linux thing? I'm running Win XP, Java
>>>> 1.5_0_15.
>>>>
>>>> --Glen
>>>>
>>>> Nandana Mihindukulasooriya wrote:
>>>>
>>>>
>>>>> Hi Glen,
>>>>> I tried with 1.5 and build works fine, but with 1.5.1 it seems
>>>>>
>>>>>
>>>> to
>>>>
>>>>
>>>>> hang sometimes. Will check little more and update.
>>>>>
>>>>> regards,
>>>>> Nandana
>>>>>
>>>>> On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
>>>>>
>>>>>
>>>> wrote:
>>>>
>>>>
>>>>> Hi folks:
>>>>>>
>>>>>> Before voting on the 1.5 release, I checked out the branch and did a
>>>>>> mvn
>>>>>> clean install... it hung hard at "Testing WS-Sec: custom scenario 3"
>>>>>> the
>>>>>> first time, and at "custom scenario 4" the second time.
>>>>>>
>>>>>> Is anyone else seeing the build hanging? I'd like to confirm this
>>>>>> isn't
>>>>>>
>>>>>>
>>>>> a
>>>>
>>>>
>>>>> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>>>>>>
>>>>>> Thanks,
>>>>>> --Glen
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>
>
Re: Timeouts building Rampart 1.5?
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
Now that Axis2 1.5.1 is out, is Rampart 1.5 back on track for release?
Thanks,
- Dennis
Glen Daniels wrote:
> Thanks Nandana.
>
> OK, I got Rampart 1.5 building successfully with Axis2 1.5, but I still see
> the lockups happening when I try 1.5.1. So I'll take a look at this to see
> what's happening and delay the 1.5.1 release until it's resolved.
>
> --Glen
>
> Nandana Mihindukulasooriya wrote:
>
>> Hi Glen, It seems that it is a SAML2 token test that is failing. After
>> introduction of SAML2 tests you have to endorse some jars to run these
>> tests. It is mentioned in the README file.
>>
>> "Test cases written for SAML 2.0 support requires endorsing the JDK's
>> default JAXP implementation with Xerces(
>> http://xerces.apache.org/mirrors.cgi#binary) and Xalan(
>> http://xml.apache.org/xalan-j/downloads.html#latest-release). So before
>> building Rampart from the source distribution, you need to copy
>> resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar and
>> xml-apis-x.x.x.jar from the Xerces binary distribution and xalan-x.x.x.jar
>> from the xalan binary distribution to the endorsed directory. If you are
>> using Sun JDK, endorsed directory is located at
>> $JAVA_HOME/jre/lib/endorsed."
>>
>> Most proelly this should be the reason for above failure. (BTW, do you know
>> a better way to handle this situation when we require some jars to be
>> endorsed to run tests). I wish I could help to figure out the timeout issue
>> but unfortunately I am working for an assignment deadline :(.
>>
>> regards,
>> Nandana
>>
>> On Thu, Oct 8, 2009 at 11:10 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
>>
>>
>>> Hi Nandana:
>>>
>>> Ok, I continued to have problems, so I ended up blowing away my m2
>>> repository, then building the transports trunk, then building Rampart
>>> again.
>>> Now I'm seeing failures. Example:
>>>
>>>
>>> -------------------------------------------------------------------------------
>>> Test set: org.apache.rahas.RahasSAML2TokenCertForHoKTest
>>>
>>> -------------------------------------------------------------------------------
>>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.36 sec
>>> <<< FAI
>>> LURE!
>>> testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) Time elapsed:
>>> 5.36
>>> sec <<< FAILURE!
>>> junit.framework.AssertionFailedError: unknown
>>> at junit.framework.Assert.fail(Assert.java:47)
>>> at org.apache.rahas.TestClient.testRequest(TestClient.java:117)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>>> java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>>> sorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at junit.framework.TestCase.runTest(TestCase.java:164)
>>> at junit.framework.TestCase.runBare(TestCase.java:130)
>>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>>> at junit.framework.TestResult.runProtected(TestResult.java:124)
>>> at junit.framework.TestResult.run(TestResult.java:109)
>>>
>>> There are four of them, and again this is with a clean build and clean
>>> repository.
>>>
>>> Could this be a Windows / Linux thing? I'm running Win XP, Java 1.5_0_15.
>>>
>>> --Glen
>>>
>>> Nandana Mihindukulasooriya wrote:
>>>
>>>> Hi Glen,
>>>> I tried with 1.5 and build works fine, but with 1.5.1 it seems
>>>>
>>> to
>>>
>>>> hang sometimes. Will check little more and update.
>>>>
>>>> regards,
>>>> Nandana
>>>>
>>>> On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
>>>>
>>> wrote:
>>>
>>>>> Hi folks:
>>>>>
>>>>> Before voting on the 1.5 release, I checked out the branch and did a mvn
>>>>> clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
>>>>> first time, and at "custom scenario 4" the second time.
>>>>>
>>>>> Is anyone else seeing the build hanging? I'd like to confirm this isn't
>>>>>
>>> a
>>>
>>>>> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>>>>>
>>>>> Thanks,
>>>>> --Glen
>>>>>
>>>>>
>
>
Re: Timeouts building Rampart 1.5?
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Thanks Nandana.
OK, I got Rampart 1.5 building successfully with Axis2 1.5, but I still see
the lockups happening when I try 1.5.1. So I'll take a look at this to see
what's happening and delay the 1.5.1 release until it's resolved.
--Glen
Nandana Mihindukulasooriya wrote:
> Hi Glen, It seems that it is a SAML2 token test that is failing. After
> introduction of SAML2 tests you have to endorse some jars to run these
> tests. It is mentioned in the README file.
>
> "Test cases written for SAML 2.0 support requires endorsing the JDK's
> default JAXP implementation with Xerces(
> http://xerces.apache.org/mirrors.cgi#binary) and Xalan(
> http://xml.apache.org/xalan-j/downloads.html#latest-release). So before
> building Rampart from the source distribution, you need to copy
> resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar and
> xml-apis-x.x.x.jar from the Xerces binary distribution and xalan-x.x.x.jar
> from the xalan binary distribution to the endorsed directory. If you are
> using Sun JDK, endorsed directory is located at
> $JAVA_HOME/jre/lib/endorsed."
>
> Most proelly this should be the reason for above failure. (BTW, do you know
> a better way to handle this situation when we require some jars to be
> endorsed to run tests). I wish I could help to figure out the timeout issue
> but unfortunately I am working for an assignment deadline :(.
>
> regards,
> Nandana
>
> On Thu, Oct 8, 2009 at 11:10 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
>
>> Hi Nandana:
>>
>> Ok, I continued to have problems, so I ended up blowing away my m2
>> repository, then building the transports trunk, then building Rampart
>> again.
>> Now I'm seeing failures. Example:
>>
>>
>> -------------------------------------------------------------------------------
>> Test set: org.apache.rahas.RahasSAML2TokenCertForHoKTest
>>
>> -------------------------------------------------------------------------------
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.36 sec
>> <<< FAI
>> LURE!
>> testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) Time elapsed:
>> 5.36
>> sec <<< FAILURE!
>> junit.framework.AssertionFailedError: unknown
>> at junit.framework.Assert.fail(Assert.java:47)
>> at org.apache.rahas.TestClient.testRequest(TestClient.java:117)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> java:39)
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
>> sorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:585)
>> at junit.framework.TestCase.runTest(TestCase.java:164)
>> at junit.framework.TestCase.runBare(TestCase.java:130)
>> at junit.framework.TestResult$1.protect(TestResult.java:106)
>> at junit.framework.TestResult.runProtected(TestResult.java:124)
>> at junit.framework.TestResult.run(TestResult.java:109)
>>
>> There are four of them, and again this is with a clean build and clean
>> repository.
>>
>> Could this be a Windows / Linux thing? I'm running Win XP, Java 1.5_0_15.
>>
>> --Glen
>>
>> Nandana Mihindukulasooriya wrote:
>>> Hi Glen,
>>> I tried with 1.5 and build works fine, but with 1.5.1 it seems
>> to
>>> hang sometimes. Will check little more and update.
>>>
>>> regards,
>>> Nandana
>>>
>>> On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
>> wrote:
>>>> Hi folks:
>>>>
>>>> Before voting on the 1.5 release, I checked out the branch and did a mvn
>>>> clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
>>>> first time, and at "custom scenario 4" the second time.
>>>>
>>>> Is anyone else seeing the build hanging? I'd like to confirm this isn't
>> a
>>>> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>>>>
>>>> Thanks,
>>>> --Glen
>>>>
>
Re: Timeouts building Rampart 1.5?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Glen, It seems that it is a SAML2 token test that is failing. After
introduction of SAML2 tests you have to endorse some jars to run these
tests. It is mentioned in the README file.
"Test cases written for SAML 2.0 support requires endorsing the JDK's
default JAXP implementation with Xerces(
http://xerces.apache.org/mirrors.cgi#binary) and Xalan(
http://xml.apache.org/xalan-j/downloads.html#latest-release). So before
building Rampart from the source distribution, you need to copy
resolver-x.x.x.jar, serializer-x.x.x.jar, xercesImpl-x.x.x.jar and
xml-apis-x.x.x.jar from the Xerces binary distribution and xalan-x.x.x.jar
from the xalan binary distribution to the endorsed directory. If you are
using Sun JDK, endorsed directory is located at
$JAVA_HOME/jre/lib/endorsed."
Most proelly this should be the reason for above failure. (BTW, do you know
a better way to handle this situation when we require some jars to be
endorsed to run tests). I wish I could help to figure out the timeout issue
but unfortunately I am working for an assignment deadline :(.
regards,
Nandana
On Thu, Oct 8, 2009 at 11:10 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi Nandana:
>
> Ok, I continued to have problems, so I ended up blowing away my m2
> repository, then building the transports trunk, then building Rampart
> again.
> Now I'm seeing failures. Example:
>
>
> -------------------------------------------------------------------------------
> Test set: org.apache.rahas.RahasSAML2TokenCertForHoKTest
>
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.36 sec
> <<< FAI
> LURE!
> testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) Time elapsed:
> 5.36
> sec <<< FAILURE!
> junit.framework.AssertionFailedError: unknown
> at junit.framework.Assert.fail(Assert.java:47)
> at org.apache.rahas.TestClient.testRequest(TestClient.java:117)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at junit.framework.TestCase.runTest(TestCase.java:164)
> at junit.framework.TestCase.runBare(TestCase.java:130)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
>
> There are four of them, and again this is with a clean build and clean
> repository.
>
> Could this be a Windows / Linux thing? I'm running Win XP, Java 1.5_0_15.
>
> --Glen
>
> Nandana Mihindukulasooriya wrote:
> > Hi Glen,
> > I tried with 1.5 and build works fine, but with 1.5.1 it seems
> to
> > hang sometimes. Will check little more and update.
> >
> > regards,
> > Nandana
> >
> > On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com>
> wrote:
> >
> >> Hi folks:
> >>
> >> Before voting on the 1.5 release, I checked out the branch and did a mvn
> >> clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
> >> first time, and at "custom scenario 4" the second time.
> >>
> >> Is anyone else seeing the build hanging? I'd like to confirm this isn't
> a
> >> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
> >>
> >> Thanks,
> >> --Glen
> >>
> >
>
Re: Timeouts building Rampart 1.5?
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Nandana:
Ok, I continued to have problems, so I ended up blowing away my m2
repository, then building the transports trunk, then building Rampart again.
Now I'm seeing failures. Example:
-------------------------------------------------------------------------------
Test set: org.apache.rahas.RahasSAML2TokenCertForHoKTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.36 sec <<< FAI
LURE!
testRequest(org.apache.rahas.RahasSAML2TokenCertForHoKTest) Time elapsed: 5.36
sec <<< FAILURE!
junit.framework.AssertionFailedError: unknown
at junit.framework.Assert.fail(Assert.java:47)
at org.apache.rahas.TestClient.testRequest(TestClient.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
There are four of them, and again this is with a clean build and clean
repository.
Could this be a Windows / Linux thing? I'm running Win XP, Java 1.5_0_15.
--Glen
Nandana Mihindukulasooriya wrote:
> Hi Glen,
> I tried with 1.5 and build works fine, but with 1.5.1 it seems to
> hang sometimes. Will check little more and update.
>
> regards,
> Nandana
>
> On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
>
>> Hi folks:
>>
>> Before voting on the 1.5 release, I checked out the branch and did a mvn
>> clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
>> first time, and at "custom scenario 4" the second time.
>>
>> Is anyone else seeing the build hanging? I'd like to confirm this isn't a
>> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>>
>> Thanks,
>> --Glen
>>
>
Re: Timeouts building Rampart 1.5?
Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
Hi Glen,
I tried with 1.5 and build works fine, but with 1.5.1 it seems to
hang sometimes. Will check little more and update.
regards,
Nandana
On Thu, Oct 8, 2009 at 6:57 PM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> Hi folks:
>
> Before voting on the 1.5 release, I checked out the branch and did a mvn
> clean install... it hung hard at "Testing WS-Sec: custom scenario 3" the
> first time, and at "custom scenario 4" the second time.
>
> Is anyone else seeing the build hanging? I'd like to confirm this isn't a
> problem with either Axis2 1.5 or Axis2 1.5.1 if at all possible.
>
> Thanks,
> --Glen
>