[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Burr Sutter updated JBESB-2084: ------------------------------- Attachment: ABusiness_rules_service.zip Drop into your quickstarts directory, unzip ant deploy ant runtest -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Jaroslaw Kijanowski commented on JBESB-2084: -------------------------------------------- You haven't added the decision tables to your esb archive, modify build.xml and change *.xls to decisionTables/*.xls Moreover your Priority_Rules DT has a wrong import statement (wrong packages), should be: org.jboss.soa.esb.message.Message, org.jboss.soa.esb.message.format.MessageType, org.jboss.soa.esb.samples.quickstart.businessrules.dvdstore.OrderHeader, org.jboss.soa.esb.samples.quickstart.businessrules.dvdstore.Customer Finally your last rule looks invalid, remove it and run the test again, should work fine now. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Burr Sutter commented on JBESB-2084: ------------------------------------ So, I've spent some more time testing this. I was also using groovy & other dynamic languages at the same time and if you have a script error then that shows up in the server console. In the case of a .drl or .xls error then you just receive the warning due to a OneWay mep like below. 15:25:46,252 WARN [ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/q uickstart_Business_Rules_Request_ESB/>, <wsa:ReferenceProperties jbossesb:java.n aming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <snipped> I wasn't trying to test the "missing" .xls, I actually had that in the right location in my version, I must have been half-way through changing that when I uploaded the example. However, I know I had syntax type of errors in my .xls and I don't see errors in the console nor server.log file. Upon further testing, the same is true of a .drl. For instance, just take quickstart business_rules_service, modify the MyBusinessRules.drl to include "STUFF HAPPENS" in an obviously bad place, redeploy and runtest. No errors about the bogus syntax in the .drl. Perhaps this is a debug level logging issue with IR5 and the default configuration. In the case of business_rules_service with a bad MyBusinessRules.drl, I just receive the following in the server.log 2008-10-01 15:41:08,994 INFO [STDOUT] { Updated customer status to 60} 2008-10-01 15:41:09,031 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_Business_Rules_Request_ESB/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: 3c1ee0c6-f384-476f-ae19-59f565611022 RelatesTo: jms:correlationID#3c1ee0c6-f384-476f-ae19-59f565611022 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Burr Sutter commented on JBESB-2084: ------------------------------------ OK. So the only way to see the syntax error in the .drl (or .xls) is to have DEBUG level logging on for the container and then look in server.log. It doesn't show up on the console but I do find the following in my server.log of the .org ESB Server which has DEBUG turned on: 2008-10-01 17:06:15,293 DEBUG [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://127.0.0.1:1099/queue/quickstart_Business_Rules_Request_ESB/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : 127.0.0.1:1099/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: fae35550-980d-4fcd-8940-fc68f978a393 RelatesTo: jms:correlationID#fae35550-980d-4fcd-8940-fc68f978a393 ] org.jboss.soa.esb.actions.ActionProcessingException: [12,0]: unknown:12:0 mismatched token: [@101,395:399='BOGUS',<7>,12:0]; at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:105) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:485) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:369) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.jboss.internal.soa.esb.services.rules.RuleServiceException: [12,0]: unknown:12:0 mismatched token: [@101,395:399='BOGUS',<7>,12:0]; at org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseHelper.getNewRuleBaseWithPackage(DroolsRuleBaseHelper.java:272) at org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseHelper.createRuleBaseFromRuleFiles(DroolsRuleBaseHelper.java:134) at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.getRuleBaseForFileBasedRules(DroolsRuleService.java:479) at org.jboss.internal.soa.esb.services.rules.DroolsRuleService.executeStatelessRules(DroolsRuleService.java:126) at org.jboss.internal.soa.esb.services.rules.RuleServiceCallHelper.executeRulesService(RuleServiceCallHelper.java:137) at org.jboss.soa.esb.actions.BusinessRulesProcessor.executeRulesService(BusinessRulesProcessor.java:121) at org.jboss.soa.esb.actions.BusinessRulesProcessor.process(BusinessRulesProcessor.java:97) ... 6 more Caused by: org.drools.rule.InvalidRulePackage: [12,0]: unknown:12:0 mismatched token: [@101,395:399='BOGUS',<7>,12:0]; at org.drools.rule.Package.checkValidity(Package.java:424) at org.drools.common.AbstractRuleBase.addPackage(AbstractRuleBase.java:394) at org.jboss.internal.soa.esb.services.rules.DroolsRuleBaseHelper.getNewRuleBaseWithPackage(DroolsRuleBaseHelper.java:267) ... 12 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Kevin Conner commented on JBESB-2084: ------------------------------------- I believe the platform took an explicit decision to limit the logging level in both servers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBESB-2084?page=com.atlassian.jira.plu... ] Mark Little commented on JBESB-2084: ------------------------------------ As J and Kev mentioned, we already agreed to turn down the logging level for this release. We won't consider another change until the next one at least. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira