Error in evaluating correlation query

Question

Hi,
I am using 10.1.3.3.1 MLR#14 Patch (upgrade from 10.1.3.1). I have created a process where in I've created correlation sets. Basically, I am placing an Order XML on JMS queue (invoking JMS adapter) and the next activity is 'Receive' activity which is polling similar JMS queue for Order response. I have set up correlation between these two activities with the Order Id as the key. The process works fine sometimes and many a times it gets stuck while polling the JMS queue for response messages. I checked the log file and got the following error
<2008-11-28 11:38:32,467> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": [com.collaxa.cube.engine.delivery.DeliveryCorrelationException: Failed to evaluate correlation query.
Failed to evaluate the correlationAlias query "/ns2:ServiceBusinessMessage/ns2:Info/ns2:Attribute[ns2:Name='OrderId']/ns2:Value" on the element "oracle.xml.parser.v2.XMLElement@84f299"
Please check your BPEL/WSDL source to make sure that property alias is defined correctly.
ORABPEL-03813
Failed to evaluate correlation query.
Failed to evaluate the correlationAlias query "/ns2:ServiceBusinessMessage/ns2:Info/ns2:Attribute[ns2:Name='OrderId']/ns2:Value" on the element "oracle.xml.parser.v2.XMLElement@84f299"
Please check your BPEL/WSDL source to make sure that property alias is defined correctly.
I am getting the above error each time my process stucks while polling for the response messages. Also, this scenario I cannot re-produce at will as the process works fine in some cases while gets stuck for the remaining. Has anybody faced similar error? Is there any resolution as I could not find any help related to this error.
Thanks in advance.
Edited by: user2023115 on 28-Nov-2008 07:52

Answer 1

There should be. Try putting the table name in quotes - some DBMS use single quotes, some use double quotes. For example say the table name has a space in it. Try something like:
select * from 'a funny table';
or
select * from "a funny table";   (Actually, I think I'd try this one first...)
Failing this, you have two choices: change the name of the table, or dump Access and go with a real DBMS - which you will probibly want to do anyway because it will only be a matter of time before you start hitting a performance wall. Access is particularly bad if you have more than one process making a connection to it at a time. Interms of alternatives, there are a couple really good open-source products out there, as well as no-cost versions of Oracle and SQL-Server.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps