[JBoss JIRA] (DROOLS-5021) ClassCastException thrown when deserializing components of a Generic command
by Karel Suta (Jira)
[ https://issues.redhat.com/browse/DROOLS-5021?page=com.atlassian.jira.plug... ]
Karel Suta commented on DROOLS-5021:
------------------------------------
[~northgorky]
Hello, I have tried locally the sources from KieIssueDemo.tbz, but I wasn't able to reproduce the issue.
Can you please describe what environment and configuration do you use? What application server (Tomcat 9 ?), what is your JDK, what Kie server version did you use (7.29.0.Final ?), what system properties did you set when starting the application server.
Can you please also provide the kjar or Maven project which I could use to build it? I have tried to build using gradle from your attachment but it failed (I am not much familiar with using gradle).
> ClassCastException thrown when deserializing components of a Generic command
> ----------------------------------------------------------------------------
>
> Key: DROOLS-5021
> URL: https://issues.redhat.com/browse/DROOLS-5021
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 7.29.0.Final, 7.33.0.Final
> Reporter: Steve Davidson
> Assignee: Maciej Swiderski
> Priority: Major
> Attachments: DroolsKieContainerCommandServiceImplLine60.png, JSONMarshallerLine328.WrongSelected.png, KieIssueDemo.tbz, KieIssueDemo.tbz, KieRun.log
>
>
> When attempting to send a Generic Data object in an Insert Command to be added to the Rule Agenda, the server fails to deserialize the Insert Command with the following;
> Feb 6 11:09:30 thor jetty[21143]: Feb 06, 2020 11:09:30 AM org.kie.server.services.drools.DroolsKieContainerCommandServiceImpl callContainer
> Feb 6 11:09:30 thor jetty[21143]: SEVERE: Error calling container 'JUnit Test: kie-server'
> Feb 6 11:09:30 thor jetty[21143]: java.lang.ClassCastException: class java.util.LinkedHashMap cannot be cast to class org.kie.api.command.Command (java.util.LinkedHashMap is in module java.base of loader 'bootstrap'; org.kie.api.command.Command is in unnamed module of loader org.eclipse.jetty.webapp.WebAppClassLoader @51bd8b5c)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.kie.server.services.drools.DroolsKieContainerCommandServiceImpl.callContainer(DroolsKieContainerCommandServiceImpl.java:60)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.kie.server.remote.rest.drools.CommandResource.manageContainer(CommandResource.java:91)
> Feb 6 11:09:30 thor jetty[21143]: #011at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> Feb 6 11:09:30 thor jetty[21143]: #011at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> Feb 6 11:09:30 thor jetty[21143]: #011at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Feb 6 11:09:30 thor jetty[21143]: #011at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:140)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:443)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:233)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:139)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:358)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:142)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:219)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
> Feb 6 11:09:30 thor jetty[21143]: #011at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHolder$NotAsyncServlet.service(ServletHolder.java:1401)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:760)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:226)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.kie.server.services.impl.security.web.CaptureHttpRequestFilter.doFilter(CaptureHttpRequestFilter.java:42)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1596)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:501)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1592)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1296)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1562)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:186)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1211)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:221)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.Server.handle(Server.java:500)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:386)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:562)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:378)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:270)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:388)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806)
> Feb 6 11:09:30 thor jetty[21143]: #011at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938)
> Feb 6 11:09:30 thor jetty[21143]: #011at java.base/java.lang.Thread.run(Thread.java:834)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5313) Upgrading Drools Version from 6.2.0.Final to 7.31.0.Final
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5313?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-5313.
---------------------------------
Resolution: Incomplete Description
Rules "giving wrong results" we can't help you with, without first seeing the rules, seeing how they're fired, and being given a test case where if executed in 6.2 it gives one result, and in 7.31 it gives another.
Please provide a complete reproducer and open another jira attaching your reproducer there.
> Upgrading Drools Version from 6.2.0.Final to 7.31.0.Final
> ---------------------------------------------------------
>
> Key: DROOLS-5313
> URL: https://issues.redhat.com/browse/DROOLS-5313
> Project: Drools
> Issue Type: Quality Risk
> Components: core engine
> Reporter: Anuj Khare
> Assignee: Mario Fusco
> Priority: Blocker
>
> I am trying to upgrade below jars from 6.2.0.Final to 7.31.0.Final. Below are the issues am facing: 1. With 6.2.0.Final it takes 8 mins to compile all the rules, where as with 7.31.0.Final it takes nearly 40 mins 2. Some of the rules give wrong results when compiled with 7.31.0.Final
> Can some one help if and what needs to be taken care while upgrading drools jars. Jars am trying to upgrade are:
> org.drools.drools-compiler
> org.kie.kie-api
> org.jbpm.jbpm-flow
> org.jbpm.jbmpm-bpmn2
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5313) Upgrading Drools Version from 6.2.0.Final to 7.31.0.Final
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5313?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5313:
--------------------------------
Sprint: 2020 Week 19-21 (from May 4)
> Upgrading Drools Version from 6.2.0.Final to 7.31.0.Final
> ---------------------------------------------------------
>
> Key: DROOLS-5313
> URL: https://issues.redhat.com/browse/DROOLS-5313
> Project: Drools
> Issue Type: Quality Risk
> Components: core engine
> Reporter: Anuj Khare
> Assignee: Mario Fusco
> Priority: Blocker
>
> I am trying to upgrade below jars from 6.2.0.Final to 7.31.0.Final. Below are the issues am facing: 1. With 6.2.0.Final it takes 8 mins to compile all the rules, where as with 7.31.0.Final it takes nearly 40 mins 2. Some of the rules give wrong results when compiled with 7.31.0.Final
> Can some one help if and what needs to be taken care while upgrading drools jars. Jars am trying to upgrade are:
> org.drools.drools-compiler
> org.kie.kie-api
> org.jbpm.jbpm-flow
> org.jbpm.jbmpm-bpmn2
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5310) java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5310?page=com.atlassian.jira.plug... ]
Mario Fusco resolved DROOLS-5310.
---------------------------------
Resolution: Explained
The ProjectClassLoader in now in org.drools.reflective.classloader package ( see https://github.com/kiegroup/drools/blob/master/drools-core-reflective/src... ) while the stack trace that you pasted refers to the package it had in version 6.x. I'm afraid you're mixing different versions of drools in your classpath, please check it.
> java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-5310
> URL: https://issues.redhat.com/browse/DROOLS-5310
> Project: Drools
> Issue Type: Bug
> Reporter: Balasubramanyam Nandula
> Assignee: Mario Fusco
> Priority: Major
> Labels: Hybris6.4.0.72RHDM7.4
>
> SAP Hybris Platform Version: 6.4.0.7 | RHDM7.4 Libraries used as client for Rules Rest API
> JDK Version used in Hybris - 1.8
> When integrating RHDM7.4 libraries for SAP Hybris e-commerce solution we got the following exception on server start up. Libraries modified are provided in step to reproduce section
> *+Runtime Server reported issue+*
> (...) INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | ERROR [BatchSelfHealingItemsRunner] [PoolableThread] Problems executing de.hybris.platform.directpersistence.selfhealing.impl.DefaultSelfHealingService$BatchSelfHealingItemsScheduledRunnable@6cf2a843 : org.drools.core.common.ProjectClassLoader.storeClasses(Ljava/util/Map;)V
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses(Ljava/util/Map;)V
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieModuleKieProject.init(KieModuleKieProject.java:66)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:269)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:238)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:187)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.init.impl.DefaultRuleEngineKieModuleSwapper.createKieModule(DefaultRuleEngineKieModuleSwapper.java:279)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.init.impl.DefaultRuleEngineBootstrap.startup(DefaultRuleEngineBootstrap.java:73)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.lambda$1(OnTenantStartupProcessor.java:111)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at java.util.ArrayList.forEach(ArrayList.java:1257)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.activateRulesModules(OnTenantStartupProcessor.java:111)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.processOnTenantStartup(OnTenantStartupProcessor.java:79)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor$DefaultRuleEngineTenantListener.afterTenantStartUp(OnTenantStartupProcessor.java:276)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.lambda$0(AbstractTenant.java:912)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.ClassLoaderUtils.executeWithWebClassLoaderParentIfNeeded(ClassLoaderUtils.java:34)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.executeStartupNotifyIfNecessary(AbstractTenant.java:898)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.executeInitsIfNecessary(AbstractTenant.java:1390)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.assureTenantStarted(Registry.java:667)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateTenant(Registry.java:708)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.setCurrentTenant(Registry.java:555)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateMasterTenant(Registry.java:615)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateMasterTenantAndFailIfAlreadySet(Registry.java:603)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.util.threadpool.ThreadPool.setTenant(ThreadPool.java:79)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.util.threadpool.PoolableThread.internalRun(PoolableThread.java:206)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.threadregistry.RegistrableThread.run(RegistrableThread.java:135)
> (...)"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5310) java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5310?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5310:
--------------------------------
Sprint: 2020 Week 19-21 (from May 4)
> java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-5310
> URL: https://issues.redhat.com/browse/DROOLS-5310
> Project: Drools
> Issue Type: Bug
> Reporter: Balasubramanyam Nandula
> Assignee: Mario Fusco
> Priority: Major
> Labels: Hybris6.4.0.72RHDM7.4
>
> SAP Hybris Platform Version: 6.4.0.7 | RHDM7.4 Libraries used as client for Rules Rest API
> JDK Version used in Hybris - 1.8
> When integrating RHDM7.4 libraries for SAP Hybris e-commerce solution we got the following exception on server start up. Libraries modified are provided in step to reproduce section
> *+Runtime Server reported issue+*
> (...) INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | ERROR [BatchSelfHealingItemsRunner] [PoolableThread] Problems executing de.hybris.platform.directpersistence.selfhealing.impl.DefaultSelfHealingService$BatchSelfHealingItemsScheduledRunnable@6cf2a843 : org.drools.core.common.ProjectClassLoader.storeClasses(Ljava/util/Map;)V
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | java.lang.NoSuchMethodError: org.drools.core.common.ProjectClassLoader.storeClasses(Ljava/util/Map;)V
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieModuleKieProject.init(KieModuleKieProject.java:66)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:269)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:238)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildAll(KieBuilderImpl.java:187)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.init.impl.DefaultRuleEngineKieModuleSwapper.createKieModule(DefaultRuleEngineKieModuleSwapper.java:279)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.init.impl.DefaultRuleEngineBootstrap.startup(DefaultRuleEngineBootstrap.java:73)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.lambda$1(OnTenantStartupProcessor.java:111)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at java.util.ArrayList.forEach(ArrayList.java:1257)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.activateRulesModules(OnTenantStartupProcessor.java:111)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor.processOnTenantStartup(OnTenantStartupProcessor.java:79)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.ruleengine.event.OnTenantStartupProcessor$DefaultRuleEngineTenantListener.afterTenantStartUp(OnTenantStartupProcessor.java:276)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.lambda$0(AbstractTenant.java:912)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.ClassLoaderUtils.executeWithWebClassLoaderParentIfNeeded(ClassLoaderUtils.java:34)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.executeStartupNotifyIfNecessary(AbstractTenant.java:898)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.AbstractTenant.executeInitsIfNecessary(AbstractTenant.java:1390)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.assureTenantStarted(Registry.java:667)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateTenant(Registry.java:708)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.setCurrentTenant(Registry.java:555)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateMasterTenant(Registry.java:615)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.Registry.activateMasterTenantAndFailIfAlreadySet(Registry.java:603)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.util.threadpool.ThreadPool.setTenant(ThreadPool.java:79)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.util.threadpool.PoolableThread.internalRun(PoolableThread.java:206)
> INFO | jvm 1 | main | 2020/05/09 22:21:47.953 | at de.hybris.platform.core.threadregistry.RegistrableThread.run(RegistrableThread.java:135)
> (...)"
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13457) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13457?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet updated WFLY-13457:
-------------------------------------
Summary: Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS (was: [GSS](7.3.z) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS)
> Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
> -----------------------------------------------------------------
>
> Key: WFLY-13457
> URL: https://issues.redhat.com/browse/WFLY-13457
> Project: WildFly
> Issue Type: Bug
> Components: JCA, JMS
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
> When using JMSContext JMSProducers are only closed when JMSContext is closed which never happens in a life time of an application since that would negates any benefits of having JCA pool.
> This could be easily observed when examining memory dump. It is possible to see a large accumulation of JMSProducer objects in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13457) [GSS](7.3.z) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13457?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet moved JBEAP-19470 to WFLY-13457:
--------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13457 (was: JBEAP-19470)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JCA
JMS
(was: Generic JMS RA)
> [GSS](7.3.z) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
> ------------------------------------------------------------------------------
>
> Key: WFLY-13457
> URL: https://issues.redhat.com/browse/WFLY-13457
> Project: WildFly
> Issue Type: Bug
> Components: JCA, JMS
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
>
> There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
> When using JMSContext JMSProducers are only closed when JMSContext is closed which never happens in a life time of an application since that would negates any benefits of having JCA pool.
> This could be easily observed when examining memory dump. It is possible to see a large accumulation of JMSProducer objects in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13456) Readme for microprofile-openapi QS is WildFly specific and does not work for EAP
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13456?page=com.atlassian.jira.plugi... ]
Eduardo Martins updated WFLY-13456:
-----------------------------------
Description:
The QS is included in EAP XP Quickstarts ZIP, but its instructions are WildFly specific.
(1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc.
was:
The QS is included in EAP XP 1.0.0.GA-CR1 Quickstarts ZIP, but its instructions are WildFly specific.
(1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc.
(2) Starting the server with unsupported method "mvn wildfly:run &". Please use standard section {{Start the JBoss EAP Standalone Server}} or use a similar steps to start the server. The same applies for {{mvn wildfly:execute-commands}}, {{mvn wildfly:shutdown -Dwildfly.reload=true}} and {{mvn wildfly:shutdown}} commands.
(3) When trying the WF commands with EAP XP1 server, they fail:
{code}
[nziakova@laptop microprofile-openapi]$ export JBOSS_HOME
[nziakova@laptop microprofile-openapi]$ mvn wildfly:run &
...
[ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run (default-cli) on project microprofile-openapi-quickstart: Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run failed: Failure to find org.wildfly:wildfly-dist:zip:7.3.1.GA-redhat-SNAPSHOT
{code}
(4) When trying standard server start, the QS works fine without the step {{Add support for MicroProfile OpenAPI by adding the requisite extension and subsystem.}} - is it needed for EAP?
{code}
EAP_HOME/bin/standalone.sh -c standalone-microprofile.xml
{code}
> Readme for microprofile-openapi QS is WildFly specific and does not work for EAP
> --------------------------------------------------------------------------------
>
> Key: WFLY-13456
> URL: https://issues.redhat.com/browse/WFLY-13456
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 19.1.0.Final
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Blocker
>
> The QS is included in EAP XP Quickstarts ZIP, but its instructions are WildFly specific.
> (1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13456) Readme for microprofile-openapi QS is WildFly specific and does not work for EAP
by Eduardo Martins (Jira)
[ https://issues.redhat.com/browse/WFLY-13456?page=com.atlassian.jira.plugi... ]
Eduardo Martins moved JBEAP-19466 to WFLY-13456:
------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13456 (was: JBEAP-19466)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Quickstarts
(was: Quickstarts)
Affects Version/s: 19.1.0.Final
(was: EAP-XP-1.0.0.GA-CR1)
> Readme for microprofile-openapi QS is WildFly specific and does not work for EAP
> --------------------------------------------------------------------------------
>
> Key: WFLY-13456
> URL: https://issues.redhat.com/browse/WFLY-13456
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Affects Versions: 19.1.0.Final
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Blocker
>
> The QS is included in EAP XP 1.0.0.GA-CR1 Quickstarts ZIP, but its instructions are WildFly specific.
> (1) Use of WildFly instead of EAP on several places, e.g. title "Using MicroProfile OpenAPI in WildFly", introduction "This guide demonstrate how to use the MicroProfile OpenAPI functionality in WildFly" etc.
> (2) Starting the server with unsupported method "mvn wildfly:run &". Please use standard section {{Start the JBoss EAP Standalone Server}} or use a similar steps to start the server. The same applies for {{mvn wildfly:execute-commands}}, {{mvn wildfly:shutdown -Dwildfly.reload=true}} and {{mvn wildfly:shutdown}} commands.
> (3) When trying the WF commands with EAP XP1 server, they fail:
> {code}
> [nziakova@laptop microprofile-openapi]$ export JBOSS_HOME
> [nziakova@laptop microprofile-openapi]$ mvn wildfly:run &
> ...
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run (default-cli) on project microprofile-openapi-quickstart: Execution default-cli of goal org.wildfly.plugins:wildfly-maven-plugin:2.0.0.Final:run failed: Failure to find org.wildfly:wildfly-dist:zip:7.3.1.GA-redhat-SNAPSHOT
> {code}
> (4) When trying standard server start, the QS works fine without the step {{Add support for MicroProfile OpenAPI by adding the requisite extension and subsystem.}} - is it needed for EAP?
> {code}
> EAP_HOME/bin/standalone.sh -c standalone-microprofile.xml
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months