I am now building cleanly with 532452.
Thanks!

On 4/25/07, Simon Laws <[EMAIL PROTECTED]> wrote:

On 4/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
>
> ant elder wrote:
> > On 4/25/07, Simon Laws <[EMAIL PROTECTED]> wrote:
> >>
> >> On 4/25/07, Simon Laws <[EMAIL PROTECTED]> wrote:
> >> >
> >> >
> >> >
> >> > On 4/25/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> >> > >
> >> > > Simon Laws wrote:
> >> > > > On 4/24/07, Kevin Williams <[EMAIL PROTECTED]> wrote:
> >> > > >>
> >> > > >> Hi Sebastien,
> >> > > >> The test runs fines from /http-tomcat.
> >> > > >> --Kevin
> >> > > >>
> >> > > >> On 4/24/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]>
wrote:
> >> > > >> >
> >> > > >> > [snip]
> >> > > >> > Kevin Williams wrote:
> >> > > >> > > Now, I am getting the Connection refused error:
> >> > > >> > >
> >> > > >> > > INFO: Stopping Coyote HTTP/1.1 on http-8586
> >> > > >> > > Apr 24, 2007 12:31:07 PM
> >> org.apache.catalina.startup.Embeddedstart
> >> > > >> > > INFO: Starting tomcat server
> >> > > >> > > Apr 24, 2007 12:31:07 PM
> >> org.apache.catalina.core.StandardEngine
> >> > > >> start
> >> > > >> > > INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
> >> > > >> > > Apr 24, 2007 12:31:07 PM
> >> > > >> > > org.apache.catalina.startup.ContextConfigdefaultWebCon
> >> > > >> > > fig
> >> > > >> > > INFO: No default web.xml
> >> > > >> > > Apr 24, 2007 12:31:07 PM
> >> org.apache.coyote.http11.Http11Protocol
> >> > > >> init
> >> > > >> > > INFO: Initializing Coyote HTTP/1.1 on http-8586
> >> > > >> > > Apr 24, 2007 12:31:07 PM
> >> org.apache.coyote.http11.Http11Protocol
> >> > > >> start
> >> > > >> > > INFO: Starting Coyote HTTP/1.1 on http-8586
> >> > > >> > > Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time
> >> elapsed:
> >> > > >> 4.686sec
> >> > > >> > > <<< FA
> >> > > >> > > ILURE!
> >> > > >> > >
> >> > > >> testRequestSession(
> >> > > org.apache.tuscany.http.tomcat.TomcatServerTestCase
> >> > > >> )
> >> > > >> > > Time el
> >> > > >> > > apsed: 1.082 sec  <<< ERROR!
> >> > > >> > > java.net.ConnectException: Connection refused: connect
> >> > > >> > >        at java.net.PlainSocketImpl.socketConnect(Native
> >> Method)
> >> > > >> > >        at
> >> > > >> java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java :372)
> >> > > >> > >        at java.net.PlainSocketImpl.connectToAddress(
> >> > > >> PlainSocketImpl.java
> >> > > >> > > :233)
> >> > > >> > >        at
> >> java.net.PlainSocketImpl.connect(PlainSocketImpl.java
> >> :220)
> >> > > >> > >        at
> >> java.net.SocksSocketImpl.connect(SocksSocketImpl.java
> >> > > :378)
> >> > > >> > >        at java.net.Socket.connect(Socket.java:536)
> >> > > >> > >        at java.net.Socket.connect (Socket.java:486)
> >> > > >> > >        at java.net.Socket.<init>(Socket.java:394)
> >> > > >> > >        at java.net.Socket.<init>(Socket.java:207)
> >> > > >> > >        at
> >> > > >> > >
> >> > > >>
> >> org.apache.tuscany.http.tomcat.TomcatServerTestCase.testRequestSessio
> >> > > >> > > n(TomcatServerTestCase.java:87)
> >> > > >> > >        at sun.reflect.NativeMethodAccessorImpl.invoke0
> (Native
> >> > > >> Method)
> >> > > >> > >        at sun.reflect.NativeMethodAccessorImpl.invoke
> >> > > >> > > (NativeMethodAccessorImpl.
> >> > > >> > > java:64)
> >> > > >> > >        at sun.reflect.DelegatingMethodAccessorImpl.invoke
> >> > > >> > > (DelegatingMethodAcces
> >> > > >> > > sorImpl.java:43)
> >> > > >> > >
> >> > > >> >
> >> > > >> > Kevin,
> >> > > >> >
> >> > > >> > This one is interesting as it's an isolated Tomcat test
> >> case, not
> >> > > even
> >> > > >> > involving integration with the Web Service binding. I
suspect
> a
> >> > > timing
> >> > > >> > issue, where Tomcat is returning from the start method
before
> >> it's
> >> > > >> > actually ready to accept requests. I'm going to investigate
it
> >> but
> >> > > >> have
> >> > > >> > question: Are you able to reproduce this problem when
> >> running mvn
> >> > > from
> >> > > >> > the http-tomcat directory? or are you only running into it
> when
> >> > > >> building
> >> > > >> > the whole trunk?
> >> > > >> >
> >> > > >> > Thanks
> >> > > >> >
> >> > > >> > --
> >> > > >> > Jean-Sebastien
> >> > > >> >
> >> > > >> >
> >> > > >> >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > >> > To unsubscribe, e-mail:
[EMAIL PROTECTED]
> >> > > >> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >> > > >> >
> >> > > >> >
> >> > > >>
> >> > > > I checked out all of the java changes and my build doesn't work
> >> with
> >> > > the
> >> > > > switch to the NioProtocol connector in http-tomcat. I get
> >> "Connection
> >> > > > Refused" on the third test case, i.e. it seems to work twice
and
> >> then
> >> > > > fails.  I backed out to the previous vanilla connection and it
> >> gets
> >> > > > all the
> >> > > > way through the test.
> >> > > >
> >> > > > Simon
> >> > > >
> >> > >
> >> > > Simon, could you please try revision r532289?
> >> > >
> >> > > The following changes:
> >> > > http://svn.apache.org/viewvc?view=rev&revision=532289
> >> > > should help with these problems.
> >> > >
> >> > > With these changes, I am able to build on both Linux and Windows.
> >> > >
> >> > > --
> >> > > Jean-Sebastien
> >> > >
> >> > >
> >> > >
> >> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >> > >
> >> > > Thanks Jean_Sebastien, will do. I also have a fix for lockup
> >> problems
> >> > we've been seeing in the wsdl and databinding itests I'll check it
in
> >> when
> >> > I've tested against these latest change of yours.
> >> >
> >> > Regards
> >> >
> >> > Simon
> >>
> >>
> >>
> >> OK, I'm at r532305. I did a mvn clean and deleted sca from my local
> >> maven
> >> repository and I still get the exception I was seeing before with the
> >> NioProtocol piece in place.
> >>
> >> 25-Apr-2007 11:44:30 org.apache.coyote.http11.Http11NioProtocol init
> >> INFO: Initializing Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:30 org.apache.coyote.http11.Http11NioProtocol start
> >> INFO: Starting Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:32 org.apache.coyote.http11.Http11NioProtocoldestroy
> >> INFO: Stopping Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:32 org.apache.catalina.core.StandardEngine start
> >> INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
> >> 25-Apr-2007 11:44:32
> >> org.apache.catalina.startup.ContextConfigdefaultWebConfig
> >> INFO: No default web.xml
> >> 25-Apr-2007 11:44:32 org.apache.coyote.http11.Http11NioProtocol init
> >> INFO: Initializing Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:32 org.apache.coyote.http11.Http11NioProtocol start
> >> INFO: Starting Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:33 org.apache.catalina.core.StandardEngine start
> >> INFO: Starting Servlet Engine: Apache Tomcat/6.0.10
> >> 25-Apr-2007 11:44:33
> >> org.apache.catalina.startup.ContextConfigdefaultWebConfig
> >> INFO: No default web.xml
> >> 25-Apr-2007 11:44:33 org.apache.coyote.http11.Http11NioProtocoldestroy
> >> INFO: Stopping Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:34
org.apache.tomcat.util.net.NioEndpoint$Acceptorrun
> >> SEVERE: Socket accept failed
> >> java.nio.channels.AsynchronousCloseException
> >>         at java.nio.channels.spi.AbstractInterruptibleChannel.end
> >> (AbstractInterr
> >> uptibleChannel.java:213)
> >>         at sun.nio.ch.ServerSocketChannelImpl.accept(
> >> ServerSocketChannelImpl.jav
> >> a:169)
> >>         at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(
> >> NioEndpoint.java:
> >> 955)
> >>         at java.lang.Thread.run(Thread.java:797)
> >> 25-Apr-2007 11:44:34 org.apache.coyote.http11.Http11NioProtocol init
> >> INFO: Initializing Coyote HTTP/1.1 on http-8586
> >> 25-Apr-2007 11:44:35 org.apache.coyote.http11.Http11NioProtocol start
> >> INFO: Starting Coyote HTTP/1.1 on http-8586
> >> Tests run: 5, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 9.193
> >> sec
> >> <<< FA
> >> ILURE!
> >> testUnregisterMapping(
> org.apache.tuscany.http.tomcat.TomcatServerTestCase)
> >>
> >> Time
> >> elapsed: 1.242 sec  <<< ERROR!
> >> java.net.ConnectException: Connection refused: connect
> >>         at java.net.PlainSocketImpl.socketConnect(Native Method)
> >>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java
:372)
> >>         at
> >> java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java
> >> :233)
> >>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:220)
> >>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:378)
> >>         at java.net.Socket.connect(Socket.java:536)
> >>         at java.net.Socket.connect(Socket.java:486)
> >>         at java.net.Socket.<init>(Socket.java:394)
> >>         at java.net.Socket.<init>(Socket.java:207)
> >>         at
> >> org.apache.tuscany.http.tomcat.TomcatServerTestCase.testUnregisterMap
> >> ping(TomcatServerTestCase.java:88)
> >>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
> >>
> >> I'm just going off to repeat the process to make doubly sure.
> >>
> >> Simon
> >>
> >
> > I see similar problems. A lot of "
> > java.nio.channels.AsynchronousCloseException"s for various tests
> although
> > that doesn't seem to always cause the test to fail, and occasional "
> > java.net.ConnectException: Connection refused: connect" for various
> > tests.
> > TomcatServerTestCase nearly always fails with a ConnectException if i
> > build
> > from the top but building from within http-tomcat it mostly works, the
> > Axis2
> > binding occasionally fails when building from the top but so far
always
> > works when building from within binidng-ws-axis2, and the wsdl itests
> are
> > also failing intermittently.
> >
> >   ...ant
> >
>
> I made two more changes. First I switched back to the regular Tomcat
> Http11Protocol handler as the Nio-based one seems to cause problems in
> some environments. I also noticed that Tomcat does not check that its
> acceptor thread has actually terminated before returning from stop() and
> I think that this contributes to the address-in-use and
> connection-refused issues that we've been seeing, so I subclassed the
> Tomcat JioEndpoint to wait for the acceptor thread to terminate.
>
> Could you please try revision r532435 and see if it fixes these
> connection issues in your environment? Thanks.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> I got a complete and clean build with this change. I have now also
checked
in the axis fix (one liner in Axis2TargetInvoker) to stop some of the
itests
locking up and added the databinding itest back into the build.

Simon

Reply via email to