You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Willem Jiang <ni...@iona.com> on 2007/03/02 11:00:34 UTC
System test failed with http2 module
Hi Eoghan,
I tried to run the Systest with http2 module today.
I found the org.apache.cxf.systest.ws.address.NonDecoupledTest and the
org.apache.cxf.systest.ws.address.MAPTest can't pass.
I digged the error and found the server will get the below exception
when the client called greeter.greetMeOneWay("implicit_oneway1");
Eoghan Can you help me to have a look at this?
Maybe I broke something in the http2 module.
BTW, I put the stack trace and svn diff of the pom.xml on the mail.
Cheers,
Willem.
Mar 2, 2007 3:36:17 PM
org.apache.cxf.transport.http.AbstractHTTPDestination flushHeaders
WARNING: Response object is null
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
INFO: retrieving MAPs from context property
javax.xml.ws.addressing.context.inbound
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
WARNING: WS-Addressing - failed to retrieve Message Addressing
Properties from context
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.MAPAggregator getMAPs
INFO: MAPs retrieved from message null
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
INFO: retrieving MAPs from context property
javax.xml.ws.addressing.context.outbound
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
WARNING: WS-Addressing - failed to retrieve Message Addressing
Properties from context
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
INFO: retrieving MAPs from context property
javax.xml.ws.addressing.context.outbound
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
WARNING: WS-Addressing - failed to retrieve Message Addressing
Properties from context
Mar 2, 2007 3:36:17 PM
org.apache.cxf.transport.http.AbstractHTTPDestination flushHeaders
WARNING: Response object is null
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
rebaseResponse
WARNING: SERVER_TRANSPORT_REBASE_FAILURE_MSG
org.apache.cxf.interceptor.Fault: Could not write to XMLStreamWriter.
at
org.apache.cxf.interceptor.StaxOutInterceptor.handleMessage(StaxOutInterceptor.java:95)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:168)
at
org.apache.cxf.interceptor.MessageSenderInterceptor.handleMessage(MessageSenderInterceptor.java:57)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:168)
at
org.apache.cxf.ws.addressing.ContextUtils.rebaseResponse(ContextUtils.java:353)
at
org.apache.cxf.ws.addressing.MAPAggregator.mediate(MAPAggregator.java:243)
at
org.apache.cxf.ws.addressing.MAPAggregator.handleMessage(MAPAggregator.java:96)
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:168)
at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:64)
at
org.apache.cxf.transport.http.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:206)
at
org.apache.cxf.transport.http.JettyHTTPDestination.doService(JettyHTTPDestination.java:176)
at
org.apache.cxf.transport.http.JettyHTTPDestination$2.handle(JettyHTTPDestination.java:121)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:690)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:191)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:710)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: com.ctc.wstx.exc.WstxIOException: Response object is null
at
com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1681)
at com.ctc.wstx.sw.BaseStreamWriter.close(BaseStreamWriter.java:288)
at
org.apache.cxf.interceptor.StaxOutInterceptor.handleMessage(StaxOutInterceptor.java:84)
... 22 more
Caused by: java.io.IOException: Response object is null
at
org.apache.cxf.transport.http.AbstractHTTPDestination.flushHeaders(AbstractHTTPDestination.java:321)
at
org.apache.cxf.transport.http.AbstractHTTPDestination$WrappedOutputStream.doFlush(AbstractHTTPDestination.java:373)
at
org.apache.cxf.io.AbstractCachedOutputStream.flush(AbstractCachedOutputStream.java:97)
at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:99)
at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:184)
at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:165)
at
com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1679)
... 24 more
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
INFO: retrieving MAPs from context property
javax.xml.ws.addressing.context.inbound
Mar 2, 2007 3:36:17 PM org.apache.cxf.ws.addressing.ContextUtils
retrieveMAPs
INFO: current MAPs [MessageId:
urn:uuid:ed7c03c7-ff83-484e-a019-2d9901543f2a, Action: , To:
http://localhost:9008/SoapContext/SoapPort, ReplyTo:
http://www.w3.org/2005/08/addressing/none]
Here is the svn diff which changes the systest to use http2 module.
Index: rt/ws/rm/pom.xml
===================================================================
--- rt/ws/rm/pom.xml (revision 513577)
+++ rt/ws/rm/pom.xml (working copy)
@@ -89,7 +89,7 @@
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-transports-http</artifactId>
+ <artifactId>cxf-rt-transports-http2</artifactId>
<version>${project.version}</version>
<scope>test</scope>
</dependency>
Index: rt/bindings/http/pom.xml
===================================================================
--- rt/bindings/http/pom.xml (revision 513577)
+++ rt/bindings/http/pom.xml (working copy)
@@ -55,7 +55,7 @@
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-transports-http</artifactId>
+ <artifactId>cxf-rt-transports-http2</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
Index: systests/pom.xml
===================================================================
--- systests/pom.xml (revision 513577)
+++ systests/pom.xml (working copy)
@@ -112,7 +112,7 @@
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-transports-http</artifactId>
+ <artifactId>cxf-rt-transports-http2</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
Index: integration/jca/pom.xml
===================================================================
--- integration/jca/pom.xml (revision 513577)
+++ integration/jca/pom.xml (working copy)
@@ -88,7 +88,7 @@
<dependency>
<groupId>org.apache.cxf</groupId>
- <artifactId>cxf-rt-transports-http</artifactId>
+ <artifactId>cxf-rt-transports-http2</artifactId>
<version>${project.version}</version>
</dependency>
Re: Maven upgrade OutOfMemory exception
Posted by ja...@mail.ooc.nf.ca.
Try setting the MAVEN_OPTS environment variable to the following (or higher maybe...):
export MAVEN_OPTS=-Xmx512M
Cheers,
Jon
On Fri, Mar 02, 2007 at 11:46:57AM -0000, O'Callaghan, Sean wrote:
> Hi,
>
> Since upgrading to Maven 2.0.5, CXF fails to compile a clean build.
> It runs out of memory when compiling the testutils classes.
> Is there any flag/switch I can set in Maven config to workaround this?
> This is on windows using jdk1.5.0_06
>
> Thanks,
>
> Seán.
>
> Compiling 1197 source files to C:\CXF\trunk\testutils\target\classes
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> Failure executing javac, but could not parse the error:
>
>
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
Re: Maven upgrade OutOfMemory exception
Posted by Daniel Kulp <da...@iona.com>.
The MAVEN_OPTS=-Xmx512M would probably do it.
However, you might also want to try a newer JDK. I haven't had an issue
with 1.5.0_11, but I'm also on Linux.
We probably could fork the compile in testutils. It's quite large so it
may be a good idea. I think we had a problem with the forked javac on
one of the platforms (OSX?), but that was a long time ago. We'd have to
test it a bit first.
Dan
On Friday 02 March 2007 06:46, O'Callaghan, Sean wrote:
> Hi,
>
> Since upgrading to Maven 2.0.5, CXF fails to compile a clean build.
> It runs out of memory when compiling the testutils classes.
> Is there any flag/switch I can set in Maven config to workaround this?
> This is on windows using jdk1.5.0_06
>
> Thanks,
>
> Seán.
>
> Compiling 1197 source files to C:\CXF\trunk\testutils\target\classes
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Compilation failure
>
> Failure executing javac, but could not parse the error:
>
>
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
Maven upgrade OutOfMemory exception
Posted by "O'Callaghan, Sean" <se...@iona.com>.
Hi,
Since upgrading to Maven 2.0.5, CXF fails to compile a clean build.
It runs out of memory when compiling the testutils classes.
Is there any flag/switch I can set in Maven config to workaround this?
This is on windows using jdk1.5.0_06
Thanks,
Seán.
Compiling 1197 source files to C:\CXF\trunk\testutils\target\classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure
Failure executing javac, but could not parse the error:
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError: Java heap space