We are having a very strange (and intermittent) issue with some of our camel routes.
We are in the process of upgrading to a more up-to-date version but are still on camel 2.10.7 and running on java 1.6. I have looked through the forums and tickets but haven't found anything that looks like it could cause this issue. What appears to be occurring is this: * An XML document is received from a JMS queue (as a text message) o The xml is correctly formatted and is what we expect to see * It is then routed through an XSLT transformation (to strip off excess namespacing) * 99% of the time this works, but very occasionally we get Xpath errors when we go onto the next step * We were able to do a heap dump of a system that was having this problem, when we dug through the dump we were able to analyze an instance of the failure (same exchangeId) o It turns out that when the issue occurs the enclosing tags (document root) have disappeared rendering the document un-xpathable Since this works nearly all of the time and there is nothing special about the failing documents we suspect it could be a threading or race condition in the XSLT processing. Are there any known issues that might be related? This route is running in a relatively large and busy camel application that makes heavy use of XSLT transforms. We believe similar issues have occurred in other instances but haven't debugged to this level so that is just a hunch. I have included some details below, let me know if there is more I should include. I still have the heap/thread dump if there is anything else that might be worth digging into. Thanks for any help or advise, Sam Hendley Jms Timeout message (notice it has xml header and wrapping of EncryptionKeyFlow) [cid:image001.png@01CFD7FC.D4F23FD0] <?xml version="1.0" encoding="UTF-8"?> <EncryptionKeyFlow xmlns="http://www.example.com/messages";> <transactionId>2193-49984781-keymanager-1411163761368-126275</transactionId> <responseQueue>orch.encryptionkey.encryptionkeyTimeout.queue</responseQueue> .... <status>FAIL</status> <substatus>timeout</substatus> <statusMessages>Request timed out while waiting for response(s).</statusMessages> </EncryptionKeyFlow> Camel Body (stripped off top and bottom elements) [cid:image002.png@01CFD7FC.D4F23FD0] <transactionId>2193-49984781-keymanager-1411163761368-126275</transactionId> <responseQueue>orch.encryptionkey.encryptionkeyTimeout.queue</responseQueue> ... <status>FAIL</status> <substatus>timeout</substatus> <statusMessages>Request timed out while waiting for response(s).</statusMessages> Route: from(JMS_encryptionkeyTimeout).routeId(JMS_encryptionkeyTimeout) .log(LoggingLevel.INFO, "Timed out waiting for encryptionkey response") .choice() .when(isInBodyNullOrEmpty) .to(SEDA_encryptionkeyOrchDead) .otherwise() .to(DIRECT_processBackToClient) .end(); // Called from several places - when a response needs to be sent back to the client from(DIRECT_processBackToClient).routeId(DIRECT_processBackToClient) .setHeader(HDR_JMS_CORRELATION_ID).xpath("//*[local-name()='transactionId']", String.class) .to(XSLT_toAPIResponsePreprocessing) .choice() // New response type may be added later .when().xpath("not(/*[local-name()='responseQueue'])") .log(LoggingLevel.ERROR, "Unable to format encryptionkey response") .to(SEDA_encryptionkeyOrchDead) .otherwise() .recipientList().simple(JMS_RESPONSE_QUEUE) .end(); XSLT that is probably at fault: <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform";> <xsl:output standalone="yes" omit-xml-declaration="yes" /> <xsl:template match="processing-instruction()"> <xsl:copy><xsl:apply-templates/></xsl:copy> </xsl:template> <xsl:template match="*"> <xsl:element name="{local-name()}"><xsl:apply-templates select="@*|node()"/></xsl:element> </xsl:template> <xsl:template match="@*"> <xsl:attribute name="{local-name()}"><xsl:value-of select="."/></xsl:attribute> </xsl:template> </xsl:stylesheet>
