[
https://issues.apache.org/jira/browse/AXIS2-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647753#action_12647753
]
martin voegeli commented on AXIS2-3791:
---------------------------------------
Hi Chris
I think the stack overflow is the result, not the cause.
Webshere suffers from some open source decease: IBM uses their own Axis
contribution as part of the websphere deployment too.
If the class-loader hierachie is incorrect, classes from your axis
distribution and the one in the WAS distro collide.
Usually you can fix the problem with the parent last strategy, but their
are not so rare cases, where this does not work (because of indirect
dependencies).
BEA/Oracle WLS solves this problem by moving their own version to the
com.bea namespace (very good strategy).
Therefore you have the following options:
- use the builtin web-service distro
- enable classloader tracing and check-out, if your class loader policy
setting are really working (it does not always)
- checkout your deployment: You may have some missing jar in your
web-deployment, that is found in a classloader higher up, but which is
not compatible with your version
hope it helps
martin
> Endlesloop in AxisServlet init (Websphere 6.1 deployment)
> ---------------------------------------------------------
>
> Key: AXIS2-3791
> URL: https://issues.apache.org/jira/browse/AXIS2-3791
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: transports
> Affects Versions: 1.3
> Environment: Solaris-10
> Websphere 6.1
> java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_13-b05
> 20071004)
> Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)
> IBM Java ORB build orb50-20070915 (SR6)
> XML build XSLT4J Java 2.7.9
> XML build IBM JAXP 1.3.7
> XML build XML4J 4.4.11
> Reporter: martin voegeli
> Assignee: Deepal Jayasinghe
> Priority: Minor
> Original Estimate: 0.17h
> Remaining Estimate: 0.17h
>
> Wrong usage of servlet init procedure leads to endlessloop, if container
> issues init method twice.
> =>
> http://java.sun.com/j2ee/1.4/docs/api/javax/servlet/GenericServlet.html#init(javax.servlet.ServletConfig)
>
> [5/7/08 14:55:37:535 MEST] 00000036 ServletWrappe E SRVE0100E: Did not
> realize init() exception thrown by servlet AxisServlet:
> java.lang.StackOverflowError
> at javax.servlet.GenericServlet.init(GenericServlet.java:256)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
> at javax.servlet.GenericServlet.init(GenericServlet.java:256)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:413)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:487)
> AxisServlet.java:
> public void init(ServletConfig config) throws ServletException {
> 413 super.init(config);
> try {
> this.servletConfig = config;
> ...
> GenericServlet.java
> public void init(ServletConfig config)
> throws ServletException
> {
> this.config = config;
> init();
> }
> AxisServlet.java:487:
> /**
> * Convenient method to re-initialize the ConfigurationContext
> *
> * @throws ServletException
> */
> public void init() throws ServletException {
> if (this.servletConfig != null) {
> 487 init(this.servletConfig);
> }
> }
> After reinstalling the websphere server, the issue was resolved. Seems, that
> WAS6.1 has some buggy state too. Maybe you can handover the issue to IBM ;-)
--
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]
