search

javaee / metro-wsit

https://javaee.github.io/metro-wsit/
Other
9 stars 24 forks source link

WSSTUBE0025: Error in Verifying Security in the Inbound Message #1647

Open glassfishrobot opened 12 years ago

glassfishrobot commented 12 years ago

Security tests are failing with WSSTUBE0025: Error in Verifying Security in the Inbound Message.

Metro HA results: http://ejp-172x-150.in.oracle.com:85/results/summary/metro-ha.html#com.sun.dft.glassfish.metroha.secureconversation

Framework logs:

javax.xml.ws.WebServiceException: WSSTUBE0025: Error in Verifying Security in the Inbound Message. at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processClientResponsePacket(SecurityClientTube.java:439) at com.sun.xml.wss.jaxws.impl.SecurityClientTube.processResponse(SecurityClientTube.java:362) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:972) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:910) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:873) at com.sun.xml.ws.api.pipe.Fiber.run(Fiber.java:717) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: javax.xml.ws.soap.SOAPFaultException: Invalid Security Header at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:696) at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:714) ... 9 more Caused by: com.sun.xml.wss.impl.WssSoapFaultException: Invalid Security Header at com.sun.xml.wss.impl.SecurableSoapMessage.newSOAPFaultException(SecurableSoapMessage.java:349) at com.sun.xml.wss.jaxws.impl.SecurityTubeBase.getSOAPFaultException(SecurityTubeBase.java:710) ... 9 more

Environment

Glassfish 3.1.2 Patch2 , Metro 2.2.0-1

Affected Versions

[2.2]

glassfishrobot commented 12 years ago

Reported by arunkumar_s

glassfishrobot commented 12 years ago

nitkal said: Just to summarize the behavior, it appears that the original failure (on Jul 3) was due to a time-sync issue between the instances that caused the security error message in the server.log of instance109:

Caused by: com.sun.xml.ws.api.security.secconv.WSSecureConversationRuntimeException: The provided context token has expired

Once the instances were synced up and the test was re-run , in the failed case the server.log (for instance109) shows the output related to an unexpected behavior in RM (Message number [4]). This is the root cause of the error which is throwing up an error related to invalid security header in the client side ( a common error when the server cannot secure the policy due to another root cause - a bug fixed later in the trunk).

Also it appears that this RM issue is not consistent, since the test passes at times.

glassfishrobot commented 12 years ago

snajper said: To me it seems like duplicate of http://java.net/jira/browse/GLASSFISH-18170 which is an intermittent RM issue already present since metro 2.2.

glassfishrobot commented 12 years ago

nitkal said: Transferring to RM , since this is an existing RM issue

glassfishrobot commented 11 years ago

@mpotociar said: Assigning to Martin to reassign as appropriate since I no longer own the domain.

glassfishrobot commented 12 years ago

Was assigned to snajper

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA WSIT-1647