You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "William Walsh (JIRA)" <ji...@apache.org> on 2010/12/20 21:53:01 UTC
[jira] Created: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
[ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
------------------------------------------------------------------------------------------------------------------
Key: AXIS2-4910
URL: https://issues.apache.org/jira/browse/AXIS2-4910
Project: Axis2
Issue Type: Bug
Components: Tools
Affects Versions: 1.5.1
Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
Reporter: William Walsh
Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
{quote}
curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
INFO - [javac] 1 error
{quote}
And, we see this output for the generation of that related failing code:
{quote}
INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
By using the Process or the Compile command" splitlimit "option, or by setting"
http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
By using the Process or the Compile command" splitlimit "option, or by setting"
http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
{quote}
On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
* Further information on these symptoms
* Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977530#action_12977530 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
I've taken a brief look at the Axis2 codegen source and was wondering if anyone in the audience here could help validate my understanding or not. I'm currently of the opinion that the difference between the successful (always - WLS) and failing (sporadic - WAS) cases is due to the implementation of javax/xml/transform/TransformerFactory.class, which is different between the two cases. Does that seem likely? I'm basing this on the calls to TransformerFactory in org.apache.axis2.util.XSLTTemplateProcessor and a class loader trace shows it coming from $JAVA_HOME/jre/lib/xml.jar for WAS and for WLS it comes from the Sun rt.jar.
I'm going to have to open a PMR with IBM on this as it doesn't seem like an issue with Apache Axis2, but it always helps when working with IBM to be as specific as possible.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973903#action_12973903 ]
Andreas Veithen commented on AXIS2-4910:
----------------------------------------
I would say that this is definitely a bug in the IBM JRE. I guess that if you are using IBM's JRE, then this is because your target environment is an IBM product. If that is the case, then the most efficient way to solve this issue would be to open a PMR for that product.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993473#comment-12993473 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
Hi Stamatis, I have a PMR open with IBM and have given them a testcase where they have been able to recreate the failure, but sporadically; e.g. 1 failure out of 1 or 2 thousand runs. You should open a PMR with IBM to pursue this as it seems your symptoms are more consistent than my own and it might help IBM come up with a fix faster. So, no, there is no fix as far as I know at this time. (FP 7.0.0.13 means the WebSphere fix pack level, which IBM publishes about every 3 months. With that level is a JDK level, but that level can usually be upgraded/downgraded separately from WebSphere. This is an issue with the JDK levels at FP 11 & 13.)
Thanks,
William
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Resolved: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi resolved AXIS2-4910.
-------------------------------------------------
Resolution: Fixed
resolve the issue since it seems to be a problem with IBM jdk as pointed out by the last comment.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973933#action_12973933 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
Andreas, I think you're correct that an IBM PMR is likely in that I am working on a testcase and so far the ERR 0635 error only occurs with the IBM JDK (OK with Sun & NetWeaver). I'm still investigating and will update when I get the testcase complete. Currently the relationship between ERR 0635 and the compilation failure in our application is only tenuous; so, I'm hoping the test case will make that clear one way or the other and I'll know how to proceed. I could open a PMR now with IBM, but I'd rather know if the scope is just the ERR 0635 or related also to the compilation failure of the Stub code. Hope to update in the next day or two.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samisa Abeysinghe updated AXIS2-4910:
-------------------------------------
Component/s: (was: Tools)
codegen
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982148#action_12982148 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
To give an update:
I have a PMR open with IBM and they have been able to recreate the failure in their environment with my testcase and are recommending we upgrade from the JDK level at WAS FP 7.0.0.11 to FP 7.0.0.13 (either the whole WAS FP or just the JDK level should be fine) as there are a lot of XML and XSLT fixes in this newer level. While IBM were able to see two failures initially with the testcase I don't think they saw any after that and after I saw one failure with the testcase I didn't see any after hundreds/thousands more test runs. So, it is quite sporadic and its occurrence rate seems quite low too. So, we're going to do some testing with FP13 and IBM is doing some testing on their end; but, given its low frequency I don't think we'll have confidence of complete resolution for some weeks or months.
At this point it certainly doesn't appear to be an issue with Axis2; so, I think it makes the most sense to close this JIRA off and I can always provide further updates if there's anything more of interest.
Thanks
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Updated: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
William Walsh updated AXIS2-4910:
---------------------------------
Attachment: Axis2DocWebServiceTestBPO.wsdl
Hi, Here is the wsdl file associated with that particular error. We keep these WSDL files for our tests under source control, so it should be constant from build to build.
I'm going to try to setup a test case for this so I can iteratively run the code generation tool to see if I can recreate the failure.
Thanks,
William
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Stamatis Glykos (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993427#comment-12993427 ]
Stamatis Glykos commented on AXIS2-4910:
----------------------------------------
Hello,
It seems that I am facing the same problem.
In my ant script I call the "org.apache.axis2.tool.ant.AntCodegenTask" to generate the server and client side code.
But every time the compilation of produced files fails because some getter/ setter methods are missing.
My developing machine runs the followings:
java version "1.6.0"
Java(TM) SE Runtime Environment (build pwi3260sr8fp1-20100624_01(SR8 FP1))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr8ifx-20100609_59383 (JIT enabled, AOT enabled)
J9VM - 20100609_059383
JIT - r9_20100401_15339ifx2
GC - 20100308_AA)
JCL - 20100624_01
D:\OSVviews\DLS_main\dls\develop\build>javac -version
javac 1.6.0-internal
Since I cannot understand and couldnt find what "FP 7.0.0.13" means, can anyone tell me if that fix shall exist the JDK I use?
Thanks
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974784#action_12974784 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
The test case I created I ran on my machine for 500+ iterations without a failure, but when I ran it on the machine where it previously failed it failed on the 41st iteration. It's currently unclear if the ERR 0635 error (appears to occur in all cases, successful & unsuccessful) we see is related to the subsequent failure; but, certainly the code that gets generated is in error. It's treating the simpleMultiply service as if it's taking in a boolean instead of returning a float.
>From the log4j trace we can see in the successful case:
{quote}
[JavaFromWSDL] <bean anon="yes" mapperClass="ExtensionMapper" name="SimpleMultiplyResponse" nsprefix="ns1" nsuri="http://remote.testmodel.util.curam" ordered="yes" originalName="simpleMultiplyResponse" package="" skip-write="yes" unwrapped="yes">
[JavaFromWSDL] <property javaname="_return" minOccurs="0" name="return" nsuri="http://remote.testmodel.util.curam" primitive="yes" shorttypename="float" type="float"/>
[JavaFromWSDL] </bean>
{quote}
And in the unusccessful case:
{quote}
[JavaFromWSDL] <bean anon="yes" mapperClass="ExtensionMapper" name="SimpleMultiplyResponse" nsprefix="ns1" nsuri="http://remote.testmodel.util.curam" ordered="yes" originalName="simpleMultiplyResponse" package="" skip-write="yes" unwrapped="yes">
[JavaFromWSDL] <property javaname="Args0" minOccurs="0" name="args0" nsuri="http://remote.testmodel.util.curam" primitive="yes" shorttypename="boolean" type="boolean"/>
[JavaFromWSDL] </bean>
{quote}
I'll post the logs and other artifacts after the Christmas break.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973488#action_12973488 ]
Samisa Abeysinghe commented on AXIS2-4910:
------------------------------------------
Can you please provide the WSDL to help test and fix this.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "William Walsh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004276#comment-13004276 ]
William Walsh commented on AXIS2-4910:
--------------------------------------
Just wanted to follow-up with the information I got from IBM regarding ERR 0635:
The XSLT processor in the IBM JDK translates XSLT stylesheets in Java
classes, and for any particularly large template in those stylesheets,
its initial attempt at generating the method corresponding to that
template might exceed the JVM Specification's limit on the size of a
method. If this happens, the XSLT processor will split the method into
smaller methods, none of which exceeds the limit on the size of the
method.
If the user sets the 'split limit', this sets a maximum method size that
the processor uses internally prior to generating byte code. Using this
option generally improves performance. However, the option has to be
set on the TransformerFactory used to process the XSLT stylesheet, and
if that is happening through the Axis2 code, you have no way of
controlling that unless you modify the Axis2 code or unless the Axis2
code provides some mechanism that allows the user to supply
TransformerFactory settings to TransformerFactory it uses.
... the option is specific to IBM's
Java run-time environment. It can be set using the
TransformerFactory.setAttribute method. I found a value of 1500 worked
with the Axis2 stylesheets.
If they choose to, the Axis2 developers can set the attribute this way:
TransformerFactory tf = TransformerFactory.newInstance();
try {
tf.setAttribute(
"http://www.ibm.com/xmlns/prod/xltxe-j/split-limit",
Integer.valueOf(1500));
} catch (IllegalArgumentException iae) {
}
www
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] Commented: (AXIS2-4910) [ERR 0635] Sporadically from
org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using
generated code
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977537#action_12977537 ]
Andreas Veithen commented on AXIS2-4910:
----------------------------------------
Yes, IBM's JRE comes with a different XSLT implementation. Therefore, a potential workaround could be to add xalan.jar to the classpath, in order to use that as XSLT implementation instead of the default one from the JRE.
> [ERR 0635] Sporadically from org.apache.axis2.wsdl.WSDL2Code followed by failing compilations using generated code
> ------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4910
> URL: https://issues.apache.org/jira/browse/AXIS2-4910
> Project: Axis2
> Issue Type: Bug
> Components: codegen
> Affects Versions: 1.5.1
> Environment: Various OSes (Windows XP, UNIX flavors, etc). May be specific to IBM V6 JDK.
> Reporter: William Walsh
> Attachments: Axis2DocWebServiceTestBPO.wsdl
>
>
> Not sure if this is an Axis2 bug (would have used question category if it was available to me), but:
> We are invoking the Axis2 1.5.1 org.apache.axis2.wsdl.WSDL2Code tool via an Ant <java> task and we're seeing sporadic failures where something - e.g. one attribute out of several is not being included in the generated Stub code, or as below when a method was missing. When I say sporadic I'm guessing it's about 5 or 6 identified failures out of hundreds across our automated nightly Anthill builders and our ClearCase builders. This is using WSDL 1.1 input.
> I'm only considering the period of time in the last few months when this area of our tests/builds has been stable and I have no reason to believe these errors are our internal issues. Unfortunately, all these builders wipe out the environment after the failure (unless I take extraordinary action) and so I have only been able to do limited investigation. I've never seen the issue in my own development environments.
> In one of the most recent failures I see our test code failing compilation as below because it's referencing a class method that WSDL2Code did not generate:
> {quote}
> curam \ util \ test \ webservices \ Axis2WSConnectorTest.java: 268: can not find symbol INFO - [javac] symbol: method get_return () INFO - [javac] location: class wsconnector.Axis2DocWebServiceTestBPOStub.OppositeResponse
> INFO - [javac] assertFalse (oppositeResponse.get_return ()); INFO - [javac] ^ INFO - [javac] Note: Some input files use or override a deprecated API.
> INFO - [javac] Note: To learn more, use the-Xlint: deprecation recompile.
> INFO - [javac] 1 error
> {quote}
> And, we see this output for the generation of that related failing code:
> {quote}
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> INFO - [JavaFromWSDL] Warning: "[ERR 0635] generated a number of functions than the JVM method size limit and is automatically divided into smaller functions.
> By using the Process or the Compile command" splitlimit "option, or by setting"
> http://www.ibm.com/xmlns/prod/xltxe-j/split-limit "converter plant property, you can manually put the huge template into smaller templates."
> {quote}
> On this same builder another test ran immediately following this failure (same source, etc.) and did not fail. The failing build was using the IBM V6 JDK and the non-failing build was using the Sun V6 JDK. Based on a google search (only 10 hits found) the above directed me to this IBM site, which appears to identify xltxe-j as new functionality:
> http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.user.win32.60/user/xml/xslt_migrate.html
> At this point, with the limited data points I have I feel it's too early to say this is an Axis2 or an IBM JDK issue, but would appreciate it if anyone has:
> * Further information on these symptoms
> * Thoughts on how I might gather more data when using the Axis2 tool to get for information so I can pursue with IBM if that's appropriate.
> I admit that I have not yet spent the time pouring over Axis2 and related code, IBM support site, etc.; but, given our project timelines I needed to get this entered to see if there is any faspath to resolution. So, apologies for that.
--
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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org