[
https://issues.apache.org/jira/browse/AXIS2-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12480794
]
Rich Scheuerle commented on AXIS2-2323:
---------------------------------------
Hi Glenn,
I agree that the testcases need to be scrubbed to remove excessive
System.out.printlns.
As far as the "JAXBBlock is consumed" issue, this indicates that something
consumed the block between the time that it was created and HTTPSender code.
Running with debug should tell us exactly what code is messing with the
JAXBBlock and causing it to be consumed.
I am surprised that this test is failing..it didn't fail before. Did you (or
someone else) add debug code to print out the messsage ? Printing out the
message will cause the block to be consumed.
I am busy today on a several issues...I can look into the problem later this
week.
Thanks,
Rich
> JAXWS build problems
> --------------------
>
> Key: AXIS2-2323
> URL: https://issues.apache.org/jira/browse/AXIS2-2323
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Environment: Windows XP, JDK 1.5.0_07, Maven 2.0.5
> Reporter: Glen Daniels
> Assigned To: Rich Scheuerle
> Priority: Critical
> Attachments: org.apache.axis2.jaxws.framework.JAXWSTest.txt, out.txt
>
>
> The main issue here is that JAXWS just won't build for me. I'm currently
> getting out of memory errors (even after adjusting my heap size with
> MAVEN_OPTS and JAVA_OPTS), and will attach the failed test report file here.
> This is when doing "mvn clean install" from the Axis2 root. If I try "mvn
> clean install" from the JAXWS directory, I get all kinds of class not found
> problems for dependencies like junit and axiom... no clue what's going on
> there, but I'll also attach the build output for that.
> I know the continuum build seems to be working, so I'm open to the idea that
> this might be a problem with my environment, but Nick told me that similar
> things may be happening for others, hence this JIRA. I'd very much
> appreciate any help you can offer in fixing or debugging the probem.
> A secondary issue here is that the JAXWS build is HUGELY verbose, including a
> long stretch of binary output to the screen which causes my machine to beep
> constantly during the build. I also suspect that displaying all of this
> stuff is slowing the build way down. Needless to say this is kind of
> sub-optimal :), so can we please turn all of this output off by default? As
> mentioned, I'm operating with a clean build and no adjustments to properties
> files.
> Thanks!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
