Non-fatal ERROR generated the first time a CBR router is inv

[ldimaggio]

I started seeing this problem with ESB 4.2 as built from svn on 20070611 - revision 12456.

It's non-fatal as the CBR works - and it's only seen once - the first a CBR is invoked.

ERROR [STDERR] line 7:0 no viable alternative at character '\r'

[kurtstam]

The newer version of JBoss Rules is more 'picky'. Try looking at the line
endings of your rules file.

--Kurt

[ldimaggio]

This is interesting.

My rules file looked fine - until I did an "od -a" on it and discovered that each line ended with "cr nl"

Creating a new file with "nl" line endings solved the problem - but...

I suddenly wondering if this is really a bug - shouldn't the rules file parser be able to handle cr/nl line endings without flagging an error?

[marklittle]

I think you're right. This just looks like a Windows versus Unix file issue. You should raise this with the Rules guys (MarkP is extremely good at following up on this sort of thing).

[tirelli]

All,

I tested this problem and the error does not show up in MR3 and trunk at revision #13299.

Can you please update and let me know if you still face the problem? I'm closing the ticket, but feel free to re-open it if it is the case.

http://jira.jboss.com/jira/browse/JBRULES-920

Also, on an unrelated topic, but maybe you can route the bellow info to the appropriate people, while reproducing the error I was looking at your DSL here:

http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/services/jbrules/src/main/resources/XPathLanguage.dsl

May I suggest a small change? MR3 and newer versions of the engine support "inline-evals", that for your use case may give you a bit improved performance. So, just move your evals to inside the pattern. Example:

when]xpathMatch "{xpath}"=msg : Message( type == MessageType.JBOSS_XML, eval( org.jboss.internal.soa.esb.services.routing.cbr.DslHelper.xmlContentMatches(msg, "{xpath}") ) )

Also, it may be interest to check the sequential execution mode that will be released in MR4 and v4 final, that is giving up to 350% perf improvement for stateless scenarios like yours.

And as a final note, :) if you want to eliminate some clutter from the DRL file when using the DSL mappings, like having your imports automatically added, DSL supports that. Just send me a message and I can help you with that: [e-mail].

[kurtstam]

Thanks,

I think I will take you up on your offer :). I like easy and I like fast.

--Kurt