axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Resolved] (AXIS2-5589) Allocate exception for servlet AxisServlet
Date Sat, 05 Aug 2017 17:33:02 GMT


Andreas Veithen resolved AXIS2-5589.
    Resolution: Incomplete

To identify the root cause of this type of issue, you would typically enable debug logging
and then look for the messages that indicate why the module failed to load. On application
servers, failures to load the addressing module are most often caused by class loader issues,
not by bugs in Axis2. If you find evidence that there is a bug in Axis2, please create a new
ticket with all the evidence. Please note that we use JIRA as a bug tracker, not a Q&A

> Allocate exception for servlet AxisServlet
> ------------------------------------------
>                 Key: AXIS2-5589
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: Addressing
>    Affects Versions: 1.6.1
>         Environment: Test and infuture Production
>            Reporter: Santhosh
>              Labels: Allocate, AxisServlet, exception, for, servlet
>   Original Estimate: 756h
>  Remaining Estimate: 756h
> Hi Team,
> We are facing below exception when we exposed our webservice using AXIS2.0 on ITP webserver(HP
product which runs on Tandem OS). This is the first time we are facing this exception for
this instance and Load is minimal , all of sudden 1 of the 4 instances went into this state
and all requests processed by this instance are errored out. Before this exception occurred
we were able to see proper response and test it properly. 
> I have collected all required logs during the time of issue. Please drop me a mail on
"" for more details. Request you to please look into this and
provide us with your observations.
> ================================================================================
> Fri, Jun 21, 21:04:45;$Y9MV;SEVERE;StandardWrapperValve#invoke;Allocate exception for
servlet AxisServlet
> org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available:
>         at org.apache.axis2.engine.AxisConfiguration.engageModule(
>         at org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(
>         at org.apache.axis2.deployment.DeploymentEngine.engageModules(
>         at org.apache.axis2.deployment.WarBasedAxisConfigurator.engageGlobalModules(
>         at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(
>         at org.apache.axis2.transport.http.AxisServlet.initConfigContext(
>         at org.apache.axis2.transport.http.AxisServlet.init(
>         at org.apache.catalina.core.StandardWrapper.initServlet(
>         at org.apache.catalina.core.StandardWrapper.loadServlet(
>         at org.apache.catalina.core.StandardWrapper.allocate(
>         at org.apache.catalina.core.StandardWrapperValve.invoke(
>         at org.apache.catalina.core.StandardContextValve.invoke(
>         at org.apache.catalina.core.StandardHostValve.invoke(
>         at org.apache.catalina.valves.ErrorReportValve.invoke(
>         at com.hp.tandem.nsjsp.valves.RequestTrackerValve.invoke(
>         at org.apache.catalina.core.StandardEngineValve.invoke(
>         at org.apache.catalina.connector.CoyoteAdapter.service(
>         at org.apache.coyote.http11.Http11Processor.process(
>         at com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(
>         at com.tandem.servlet.coyote.http11.NSJSPHttp11Processor.process(
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
>         at$
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message