But as I have mentioned earlier we are using the JSR
calls and only one file we are loading. So directly we
are not loading the RuleBase class.
The rough code is provided below : Pls let me know
whether we can do something abt this.

RuleServiceProviderManager.registerRuleServiceProvider(

                        RULE_SERVICE_PROVIDER,
                        RuleServiceProviderImpl.class
);

RuleServiceProvider ruleServiceProvider =
RuleServiceProviderManager.getRuleServiceProvider(
RULE_SERVICE_PROVIDER );
ruleAdministrator =
ruleServiceProvider.getRuleAdministrator( );

// load the rules and register them
LocalRuleExecutionSetProvider ruleSetProvider =
ruleAdministrator.getLocalRuleExecutionSetProvider(
null );

InputStream rules =
this.getClass().getResourceAsStream( "Rules.java.drl"
);

RuleExecutionSet ruleExecutionSet =
ruleSetProvider.createRuleExecutionSet( rules, null );
                
ruleAdministrator.registerRuleExecutionSet(
"Rules.java.drl", ruleExecutionSet, null );
        
RuleRuntime ruleRuntime =
ruleServiceProvider.getRuleRuntime( );
statelessRuleSession = ( StatelessRuleSession )
ruleRuntime.createRuleSession("Rules.java.drl",null,
RuleRuntime.STATELESS_SESSION_TYPE );

List outList = statelessRuleSession.executeRules(
inList );

- Praveena

--- Michael Neale <[EMAIL PROTECTED]> wrote:

> hmmm... the only time I have seen that is if I was
> doing something silly
> with an iterator... as this is at startup, I can
> only imagine there is some
> sort of timing that is effecting classloaders. If
> its sporadic, its probably
> just bad luck. It looks like you are loading all
> your rulebases on startup
> then? I guess you could make them lazily load and
> that may not happen.
> 
> 
> On 4/27/06, christy praveen <[EMAIL PROTECTED]>
> wrote:
> >
> > Hello,
> >
> > In our application we have a wrapper over Drools.
> > We use the JSR calls to load and execute rules for
> > using Drools.
> >
> > One of the client for oour application is a JBOSS.
> > Sporadically we have some problem in starting the
> > application. From the log file we find the error
> is
> > owing to "org.drools.smf.FactoryException:
> > java.util.ConcurrentModificationException"
> > Attached is the error log file.
> > Could you kindly let me know what could be the
> reason
> > ?
> >
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Reply via email to