[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
by Kay J (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ]
Kay J commented on DROOLS-1537:
-------------------------------
I only want to load rules from a String, which I have to place in a drl file. No Maven or kjar involved, so the KieScanner isn't usable. What would be the proper way to do this? I can't rely on having the old kBase still. Is there any way to do this?
> Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-1537
> URL: https://issues.jboss.org/browse/DROOLS-1537
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.5.0.Final
> Reporter: Kay J
> Assignee: Mario Fusco
> Attachments: RestoreReproducer.java
>
>
> Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78
> Hello Drools users,
> I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic.
> I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1537:
-------------------------------------
Fix cherry-picked to branch 7.0.x by https://github.com/kiegroup/drools/commit/2d6e9fb88
> Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-1537
> URL: https://issues.jboss.org/browse/DROOLS-1537
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.5.0.Final
> Reporter: Kay J
> Assignee: Mario Fusco
> Attachments: RestoreReproducer.java
>
>
> Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78
> Hello Drools users,
> I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic.
> I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1537) Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1537?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1537:
-------------------------------------
Fixed by https://github.com/kiegroup/drools/commit/a1546a142a4645ad08e88bf1dfee090...
Regarding deserializing using a KieBase instance that is different from the one used for serialization this is also possible and works as expected ( as demonstrated by the test case I added here https://github.com/kiegroup/drools/blob/a1546a142a4645ad08e88bf1dfee090a5... ) provided that the 2 KieBases are identical.
This is indeed what you also did in your reproducer. What confused me is that you created 2 distinct kjars with same drls. Normally you don't do that: you have a single kjar and reload it from the maven repo when your app restarts. You do a newer version only if you change something, but in that case you need to use the KieScanner to trigger an incremental update of the KieBase in use.
> Scheduled activations are rescheduled as if new when unmarshalling session in Drools 6.5
> ----------------------------------------------------------------------------------------
>
> Key: DROOLS-1537
> URL: https://issues.jboss.org/browse/DROOLS-1537
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.5.0.Final
> Reporter: Kay J
> Assignee: Mario Fusco
> Attachments: RestoreReproducer.java
>
>
> Ticket representing question/bug from drools user group: https://groups.google.com/forum/#!topic/drools-usage/Gy3uhkh6J78
> Hello Drools users,
> I found an anomaly in Drools 6.5. I insert an Event, which triggers a rule with a timer after some time. For backup reasons I marshal the session inbetween to back it up and on unmarshal it later. However, after unmarshalling it, the scheduled activations are sometimes scheduled as if just inserted (e.g. 1min scheduling, with marshal/unmarshal after 25s results in the activation firing after 85 (25+60) seconds instead of actual 60s. I know this worked with Drools 5.6 consistently, but now it sometimes works, sometimes not, which is indeterministic.
> I created a test reproducing this behaviour, which has changing output whenever you execute it. What the example does: It create a scheduled activation, which should trigger after 20s. After 10s the session is marshalled, destroyed and unmarshalled into a new session. After another 10s it should finally trigger. (10s + 10s -> the 20s scheduled).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (DROOLS-1124) Unble to provision errors when creating KieContainor from KieServices in the Vert.X verticle
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1124?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-1124:
-------------------------------------
Can you please attach a small project reproducing this issue?
> Unble to provision errors when creating KieContainor from KieServices in the Vert.X verticle
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-1124
> URL: https://issues.jboss.org/browse/DROOLS-1124
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.4.0.CR2
> Environment: OS: MacOX and 10.10.5
> Vert.X: 3.2.1
> Reporter: xiaodong wang
> Assignee: Mario Fusco
>
> WARN Sisu - Error injecting: org.apache.maven.execution.DefaultMavenExecutionRequestPopulator
> com.google.inject.ProvisionException: Unable to provision, see the following errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was bound.
> while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator
> 1 error
> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1018)
> at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1044)
> at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
> at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:54)
> at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:113)
> at org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:122)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
> at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:46)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1066)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1009)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1059)
> at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1005)
> at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:82)
> at org.eclipse.sisu.plexus.LazyPlexusBean.getValue(LazyPlexusBean.java:51)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:263)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:249)
> at org.kie.scanner.embedder.PlexusComponentProvider.lookup(PlexusComponentProvider.java:42)
> at org.kie.scanner.embedder.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:119)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:90)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:81)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:75)
> at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:42)
> at org.kie.scanner.embedder.MavenProjectLoader.loadMavenProject(MavenProjectLoader.java:96)
> at org.kie.scanner.Aether.<init>(Aether.java:62)
> at org.kie.scanner.Aether.getAether(Aether.java:74)
> at org.kie.scanner.MavenRepository.getMavenRepository(MavenRepository.java:80)
> at org.kie.scanner.ArtifactResolver.<init>(ArtifactResolver.java:53)
> at org.kie.scanner.KieRepositoryScannerImpl.getArtifactResolver(KieRepositoryScannerImpl.java:102)
> at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:119)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:130)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:116)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:93)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:115)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:111)
> at com.cyngn.soothsayer.application.Server.init(Server.java:83)
> at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$163(DeploymentManager.java:427)
> at io.vertx.core.impl.ContextImpl.lambda$wrapTask$18(ContextImpl.java:335)
> at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> at java.lang.Thread.run(Thread.java:745)
> 14:22:39.388 [vert.x-eventloop-thread-1] ERROR o.kie.scanner.embedder.MavenEmbedder - Unable to build MavenEmbedder
> org.codehaus.plexus.component.repository.exception.ComponentLookupException: com.google.inject.ProvisionException: Unable to provision, see the following errors:
> 1) No implementation for org.apache.maven.repository.RepositorySystem was bound.
> while locating org.apache.maven.execution.DefaultMavenExecutionRequestPopulator
> at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule)
> at ClassRealm[maven, parent: ClassRealm[maven-parent, parent: null]] (via modules: org.eclipse.sisu.wire.WireModule -> org.eclipse.sisu.plexus.PlexusBindingModule)
> while locating org.apache.maven.execution.MavenExecutionRequestPopulator
> 1 error
> role: org.apache.maven.execution.MavenExecutionRequestPopulator
> roleHint:
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:267)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:255)
> at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:249)
> at org.kie.scanner.embedder.PlexusComponentProvider.lookup(PlexusComponentProvider.java:42)
> at org.kie.scanner.embedder.MavenEmbedder.buildMavenExecutionRequest(MavenEmbedder.java:119)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:90)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:81)
> at org.kie.scanner.embedder.MavenEmbedder.<init>(MavenEmbedder.java:75)
> at org.kie.scanner.embedder.MavenProjectLoader.parseMavenPom(MavenProjectLoader.java:42)
> at org.kie.scanner.embedder.MavenProjectLoader.loadMavenProject(MavenProjectLoader.java:96)
> at org.kie.scanner.Aether.<init>(Aether.java:62)
> at org.kie.scanner.Aether.getAether(Aether.java:74)
> at org.kie.scanner.MavenRepository.getMavenRepository(MavenRepository.java:80)
> at org.kie.scanner.ArtifactResolver.<init>(ArtifactResolver.java:53)
> at org.kie.scanner.KieRepositoryScannerImpl.getArtifactResolver(KieRepositoryScannerImpl.java:102)
> at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:119)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:130)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:116)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:93)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:115)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:111)
> at com.cyngn.soothsayer.application.Server.init(Server.java:83)
> at io.vertx.core.impl.DeploymentManager.lambda$doDeploy$163(DeploymentManager.java:427)
> at io.vertx.core.impl.ContextImpl.lambda$wrapTask$18(ContextImpl.java:335)
> at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357)
> at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (WFCORE-2480) CS tool, provide way to create empty credential store
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2480?page=com.atlassian.jira.plugi... ]
Yeray Borges reassigned WFCORE-2480:
------------------------------------
Assignee: Yeray Borges (was: Darran Lofthouse)
> CS tool, provide way to create empty credential store
> -----------------------------------------------------
>
> Key: WFCORE-2480
> URL: https://issues.jboss.org/browse/WFCORE-2480
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Martin Choma
> Assignee: Yeray Borges
> Labels: credential-store, wildfly-elytron-tool
>
> There is no way to create empty credential store. Curently credential store can be created only with adding alias as well.
> {code}
> java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --salt 12345678 --iteration 230 --summary
> {code}
> I would expect something like
> {code}
> java -jar wildfly-elytron-tool.jar credential-store --create --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years