Hi,

Sometimes (rarely) we see the following Exception in the Stratos logs, while 
troubleshooting errors. Specifically, we’ve seen this in logs of runs where 
cartridges haven’t been started up at all or where terminated cartridges have 
not been recognised as inactive, both of which are pretty bad failure modes.

TID: [0] [STRATOS] [2015-11-26 04:01:18,962] ERROR 
{org.wso2.carbon.sts.STSDeploymentListener} -  Error occur while deploying 
wso2carbon-sts service for tenant 1
org.apache.axis2.phaseresolver.PhaseException: Did not find the desired phase 
'Transport' while deploying handler 'POXSecurityHandler'.
        at 
org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:75)
        at 
org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToFlow(PhaseResolver.java:68)
        at 
org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:104)
        at 
org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:110)
        at 
org.apache.axis2.description.AxisOperation.onEngage(AxisOperation.java:152)
        at 
org.apache.axis2.description.AxisDescription.engageModule(AxisDescription.java:478)
        at 
org.apache.axis2.description.AxisService.onEngage(AxisService.java:827)
...
        at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
        at 
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1653)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

I’ve found these references online: http://stackoverflow.com/a/22244408/1298153 
and http://mail.wso2.org/mailarchive/dev/2014-December/040486.html. This 
suggests adding <phase name="Transport”/> after the security phase. The Stratos 
axis2.xml config files do not contain this setting.

I’m not familiar with axis2, and what confuses me with this is that if it was a 
config issue, why does it only show up sporadically?

Can anyone shed some light on this exception? Is it safe to patch the xml file 
and add that “transport” thing? Should the patch be done? If so, which XML file 
should be patched?

Cheers,

Michiel

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to