[JBoss JIRA] (WFLY-5778) org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
by triumf Yang (JIRA)
[ https://issues.jboss.org/browse/WFLY-5778?page=com.atlassian.jira.plugin.... ]
triumf Yang commented on WFLY-5778:
-----------------------------------
Internal Server Error
{
"outcome" => "failed",
"failure-description" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"TrEvents.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TrEvents.war\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: Exception List with 7 exceptions:
Exception 0 :
org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.jboss.solder.servlet.http.RequestParamProducer.request
at org.jboss.solder.servlet.http.RequestParamProducer.request(RequestParamProducer.java:0)
Possible dependencies:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.jboss.solder.servlet.http.CookieParamProducer.request
at org.jboss.solder.servlet.http.CookieParamProducer.request(CookieParamProducer.java:0)
Possible dependencies:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.jboss.solder.servlet.http.RedirectBuilderImpl.request
at org.jboss.solder.servlet.http.RedirectBuilderImpl.request(RedirectBuilderImpl.java:0)
Possible dependencies:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318: Cannot resolve an ambiguous dependency between:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.manager.BeanManagerImpl.resolve(BeanManagerImpl.java:1262)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedInjectionPoint(Validator.java:926)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:902)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:917)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedBean(Validator.java:879)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:138)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
at injection point [BackedAnnotatedField] @Inject private org.jboss.solder.servlet.http.HeaderParamProducer.request
at org.jboss.solder.servlet.http.HeaderParamProducer.request(HeaderParamProducer.java:0)
Possible dependencies:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:367)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:281)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:134)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318: Cannot resolve an ambiguous dependency between:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.manager.BeanManagerImpl.resolve(BeanManagerImpl.java:1262)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedInjectionPoint(Validator.java:926)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:902)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:917)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedBean(Validator.java:879)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:138)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception 0 :
org.jboss.weld.exceptions.AmbiguousResolutionException: WELD-001318: Cannot resolve an ambiguous dependency between:
- WELD%AbstractBuiltInBean%TrEvents.war/WEB-INF/lib/solder-impl-3.2.1.Final.jar%HttpServletRequest,
- Producer Method [HttpServletRequest] with qualifiers [@Any @Default] declared as [[BackedAnnotatedMethod] @Produces @Typed @RequestScoped protected org.jboss.solder.servlet.http.ImplicitHttpServletObjectsProducer.getHttpServletRequest()]
at org.jboss.weld.manager.BeanManagerImpl.resolve(BeanManagerImpl.java:1262)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedInjectionPoint(Validator.java:926)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:902)
at org.jboss.weld.bootstrap.Validator.reallyValidatePseudoScopedBean(Validator.java:917)
at org.jboss.weld.bootstrap.Validator.validatePseudoScopedBean(Validator.java:879)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:138)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:155)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:518)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:68)
at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:66)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
"}},
"rolled-back" => true
}
> org.jboss.weld.exceptions.DeploymentException: WELD-001409: Ambiguous dependencies for type HttpServletRequest with qualifiers @Default
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-5778
> URL: https://issues.jboss.org/browse/WFLY-5778
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 9.0.2.Final
> Reporter: triumf Yang
> Assignee: Stuart Douglas
> Priority: Blocker
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFCORE-950) Embedded server started non-modular use first passed --jboss-home value only
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-950?page=com.atlassian.jira.plugin... ]
Ken Wills commented on WFCORE-950:
----------------------------------
Note as part of this, a couple of other issues surfaced:
- Restarting with a new --jboss-home continued to reference some files / directories in the previous running instance's --jboss-home (Should be fixed in this change).
- The initial boot.log is always the one that continues to receive logging. (Fix in progress).
- ModuleLoader: once loaded with getBootModuleLoader() continue to reference the initial modules directory.
> Embedded server started non-modular use first passed --jboss-home value only
> ----------------------------------------------------------------------------
>
> Key: WFCORE-950
> URL: https://issues.jboss.org/browse/WFCORE-950
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 2.0.0.Beta4
> Reporter: Petr Kremensky
> Assignee: Ken Wills
> Fix For: 3.0.0.Alpha1
>
>
> First value passed as --jboss-home to embed server instance (must be an existing directory) is always used for modules lookup and server standard paths setup within single CLI session.
> # Use wrong directory on first try, use correct directory on second try, embedded instance still tries to boot from wrong directory
> {noformat}$ pwd
> /home/pkremens/workspace/jboss-eap-7.0/bin/client
> $ java -jar jboss-cli-client.jar
> [disconnected /] embed-server --jboss-home=/home/pkremens/workspace/jboss-eap-7.0/bin
> Cannot start embedded server: WFLYEMB0014: Cannot load module org.jboss.vfs from: local module loader @500e80c2 (finder: local module finder @75670fc4 (roots: /home/pkremens/workspace/jboss-eap-7.0/bin/modules)): org.jboss.vfs:main
> # server still tries to use /home/pkremens/workspace/jboss-eap-7.0/bin
> [disconnected /] embed-server --jboss-home=/home/pkremens/workspace/jboss-eap-7.0
> Cannot start embedded server: WFLYEMB0014: Cannot load module org.jboss.vfs from: local module loader @500e80c2 (finder: local module finder @75670fc4 (roots: /home/pkremens/workspace/jboss-eap-7.0/bin/modules)): org.jboss.vfs:main
> {noformat}
> # Try to manage multiple EAP distros
> {noformat}
> /home/pkremens/workspace2
> ├── eap1
> │ └── jboss-eap-7.0
> └── eap2
> └── jboss-eap-7.0
> $ java -jar jboss-cli-client.jar
> [disconnected /] embed-server --jboss-home=/home/pkremens/workspace2/eap1/jboss-eap-7.0 --server-config=eap1.xml --empty-config
> [standalone@embedded /] stop-embedded-server
> [disconnected /] embed-server --jboss-home=/home/pkremens/workspace2/eap2/jboss-eap-7.0 --server-config=eap2.xml --empty-config
> # jboss.server.*.dir point to eap1, but should point to eap2
> [standalone@embedded /] /path=*:read-attribute(name=path)
> ...
> "address" => [("path" => "jboss.server.log.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0
> "address" => [("path" => "jboss.server.data.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/data"
> "address" => [("path" => "jboss.server.base.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone"
> "address" => [("path" => "jboss.server.config.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/configuration"
> "address" => [("path" => "jboss.server.temp.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/tmp"
> "address" => [("path" => "jboss.controller.temp.dir")],
> "result" => "/home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/tmp"
> "address" => [("path" => "jboss.home.dir")],
> "result" => "/home/pkremens/workspace2/eap2/jboss-eap-7.0"
> ...
> # Both configuration files were created in eap1 directory
> $ find /home/pkremens/workspace2 | grep eap[12].xml
> /home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/configuration/eap2.xml
> /home/pkremens/workspace2/eap1/jboss-eap-7.0/standalone/configuration/eap1.xml
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (DROOLS-999) Replace mockito-all with mockito-core
by Petr Široký (JIRA)
Petr Široký created DROOLS-999:
----------------------------------
Summary: Replace mockito-all with mockito-core
Key: DROOLS-999
URL: https://issues.jboss.org/browse/DROOLS-999
Project: Drools
Issue Type: Enhancement
Reporter: Petr Široký
Assignee: Petr Široký
{{mockito-all}} is uberjar and disrupts Maven dependency management. It needs to be replaced by {{mockito-core}}. Following IP BOM versions will also ban {{mockito-all}} so the build will start failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (WFLY-5777) NPE when forming jgroups cluster
by Thiago Presa (JIRA)
Thiago Presa created WFLY-5777:
----------------------------------
Summary: NPE when forming jgroups cluster
Key: WFLY-5777
URL: https://issues.jboss.org/browse/WFLY-5777
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 10.0.0.CR4, 9.0.1.Final
Reporter: Thiago Presa
Assignee: Paul Ferraro
I just got this NPE when deploying a new application on my Wildfly 10 CR4 domain cluster.
JGRP000027: failed passing message up: java.lang.RuntimeException: java.lang.NullPointerException
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:689)
at org.jgroups.JChannel.up(JChannel.java:738)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1029)
at org.jgroups.protocols.FORK.up(FORK.java:133)
at org.jgroups.protocols.FRAG2.up(FRAG2.java:165)
at org.jgroups.protocols.FlowControl.up(FlowControl.java:394)
at org.jgroups.protocols.pbcast.GMS.installView(GMS.java:735)
at org.jgroups.protocols.pbcast.ParticipantGmsImpl.handleViewChange(ParticipantGmsImpl.java:140)
at org.jgroups.protocols.pbcast.GMS.up(GMS.java:925)
at org.jgroups.stack.Protocol.up(Protocol.java:412)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:294)
at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:474)
at org.jgroups.protocols.pbcast.NAKACK2.deliverBatch(NAKACK2.java:982)
at org.jgroups.protocols.pbcast.NAKACK2.removeAndPassUp(NAKACK2.java:912)
at org.jgroups.protocols.pbcast.NAKACK2.handleMessage(NAKACK2.java:846)
at org.jgroups.protocols.pbcast.NAKACK2.up(NAKACK2.java:618)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:155)
at org.jgroups.protocols.FD.up(FD.java:260)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:310)
at org.jgroups.protocols.MERGE3.up(MERGE3.java:285)
at org.jgroups.protocols.Discovery.up(Discovery.java:295)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1577)
at org.jgroups.protocols.TP$MyHandler.run(TP.java:1796)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at org.wildfly.clustering.server.group.ChannelNodeFactory.createNode(ChannelNodeFactory.java:55)
at org.wildfly.clustering.server.group.ChannelNodeFactory.createNode(ChannelNodeFactory.java:40)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.getNodes(ChannelCommandDispatcherFactory.java:207)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.getNodes(ChannelCommandDispatcherFactory.java:201)
at org.wildfly.clustering.server.dispatcher.ChannelCommandDispatcherFactory.viewAccepted(ChannelCommandDispatcherFactory.java:216)
at org.jgroups.blocks.MessageDispatcher.handleUpEvent(MessageDispatcher.java:605)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:686)
... 25 more
I have already stumbled upon this issue in Wildfly 9: https://developer.jboss.org/thread/265607
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (DROOLS-989) Saving/Restoring drools session prevents timer-related rules from firing
by David Weir (JIRA)
[ https://issues.jboss.org/browse/DROOLS-989?page=com.atlassian.jira.plugin... ]
David Weir updated DROOLS-989:
------------------------------
Attachment: DroolsTimerTest.java
Version without dependence on Stringify classes
> Saving/Restoring drools session prevents timer-related rules from firing
> ------------------------------------------------------------------------
>
> Key: DROOLS-989
> URL: https://issues.jboss.org/browse/DROOLS-989
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: David Weir
> Assignee: Mario Fusco
> Priority: Blocker
> Attachments: DroolsTimerTest.java, DroolsTimerTest.java, DroolsTimerTest.java, DroolsTimerTest.java
>
>
> Attached test case shows a timer-base rule firing. Then the session is saved and restored per the manual. When the trigger is inserted again, the rule does not fire.
> This is killing my system whenever I have to restart and restore the current sessions.
> The workaround is to create the session again from scratch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months
[JBoss JIRA] (DROOLS-989) Saving/Restoring drools session prevents timer-related rules from firing
by David Weir (JIRA)
[ https://issues.jboss.org/browse/DROOLS-989?page=com.atlassian.jira.plugin... ]
David Weir updated DROOLS-989:
------------------------------
Attachment: DroolsTimerTest.java
Updated to show fail properly when test runs.
> Saving/Restoring drools session prevents timer-related rules from firing
> ------------------------------------------------------------------------
>
> Key: DROOLS-989
> URL: https://issues.jboss.org/browse/DROOLS-989
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.3.0.Final
> Reporter: David Weir
> Assignee: Mario Fusco
> Priority: Blocker
> Attachments: DroolsTimerTest.java, DroolsTimerTest.java, DroolsTimerTest.java
>
>
> Attached test case shows a timer-base rule firing. Then the session is saved and restored per the manual. When the trigger is inserted again, the rule does not fire.
> This is killing my system whenever I have to restart and restore the current sessions.
> The workaround is to create the session again from scratch
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 7 months