[JBoss JIRA] (WFLY-3900) Unable to inject EJB Context into CDI Interceptor
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3900?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3900:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1149644|https://bugzilla.redhat.com/show_bug.cgi?id=1149644] from POST to MODIFIED
> Unable to inject EJB Context into CDI Interceptor
> -------------------------------------------------
>
> Key: WFLY-3900
> URL: https://issues.jboss.org/browse/WFLY-3900
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 9.0.0.Alpha1
> Reporter: Brad Maxwell
> Assignee: Stuart Douglas
> Fix For: 9.0.0.Beta1
>
> Attachments: inject-ejb-context-into-cdi-interceptor.jar, server.log
>
>
> CDI Interceptor cannot inject EJB session context.
> If the Interceptor is changed to EJB interceptor by removing the @Interceptor on the interceptor and removing it from the beans.xml, and adding @Interceptors(...) to the EJB, then it is able to inject.
> See attached reproducer with source and log file.
> private @Resource SessionContext sessionContext;
> Caused by: javax.naming.NameNotFoundException: env/test.ServiceLoggedInterceptor/sessionContext -- service jboss.naming.context.java.comp.inject-ejb-context-into-cdi-interceptor.inject-ejb-context-into-cdi-interceptor.HelloEJB.env."test.ServiceLoggedInterceptor".sessionContext
> at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:202) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-9.0.0.Alpha1.jar:9.0.0.Alpha1]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51]
> at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_51]
> at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:185)
> ... 127 more
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (JGRP-1897) ENCRYPT might drop messages during key change
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1897?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1897:
--------------------------------
Why is this an issue ? It doesn't happen often and if it does happen, since unicast messages are retransmitted (e.g. in {{UNICAST3}}), we'll end up receiving a dropped unicast a few hundred milliseconds later, anyway.
> ENCRYPT might drop messages during key change
> ---------------------------------------------
>
> Key: JGRP-1897
> URL: https://issues.jboss.org/browse/JGRP-1897
> Project: JGroups
> Issue Type: Bug
> Reporter: Tero Leppikangas
> Assignee: Bela Ban
>
> ENCRYPT might drop some (unicast) messages encrypted with unknown key if the delivery of new view is delayed.
> This problem was noticed while doing some stress testing on the fix for JGRP-1893.
> When view changes, coordinator multicasts the new view after which is starts using new symmetric keys. If some node receives a message sent with the new key before the new view is received, the received message will be dropped since it cannot be decrypted.
> We thought of possible solutions to be.
> 1. Sender specific queue holding the messages received.
> 2. Starting to queue up messages until new view has been received
> I have implemented the second option which is quite straightforward, but it could lead into problems when receiving message with unknown key that is not related to coming view change.
> I wonder if there is another way to overcome this problem?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-4046) Container lifecycle event method invoked outside of extension observer method invocation
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-4046?page=com.atlassian.jira.plugin.... ]
Thomas Diesler commented on WFLY-4046:
--------------------------------------
To reproduce, build: https://github.com/tdiesler/wildfly-camel/tree/2.0
> Container lifecycle event method invoked outside of extension observer method invocation
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-4046
> URL: https://issues.jboss.org/browse/WFLY-4046
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 9.0.0.Alpha1
> Reporter: Thomas Diesler
> Assignee: Jozef Hartinger
> Fix For: 9.0.0.Beta1
>
>
> Cannot deploy war that uses camel-cdi
> This works in 8.1.0.Final
> {code}
> org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation.
> at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61)
> at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56)
> at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47)
> at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131)
> at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-4046) Container lifecycle event method invoked outside of extension observer method invocation
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4046?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-4046:
---------------------------------
Assignee: Jozef Hartinger (was: Stuart Douglas)
> Container lifecycle event method invoked outside of extension observer method invocation
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-4046
> URL: https://issues.jboss.org/browse/WFLY-4046
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 9.0.0.Alpha1
> Reporter: Thomas Diesler
> Assignee: Jozef Hartinger
> Fix For: 9.0.0.Beta1
>
>
> Cannot deploy war that uses camel-cdi
> This works in 8.1.0.Final
> {code}
> org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation.
> at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61)
> at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56)
> at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47)
> at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131)
> at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-4046) Container lifecycle event method invoked outside of extension observer method invocation
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-4046:
------------------------------------
Summary: Container lifecycle event method invoked outside of extension observer method invocation
Key: WFLY-4046
URL: https://issues.jboss.org/browse/WFLY-4046
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 9.0.0.Alpha1
Reporter: Thomas Diesler
Assignee: Stuart Douglas
Fix For: 9.0.0.Beta1
Cannot deploy war that uses camel-cdi
This works in 8.1.0.Final
{code}
org.jboss.weld.exceptions.IllegalStateException: WELD-000143: Container lifecycle event method invoked outside of extension observer method invocation.
at org.jboss.weld.bootstrap.events.ContainerEvent.checkWithinObserverNotification(ContainerEvent.java:61)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.getAnnotatedType(ProcessAnnotatedTypeImpl.java:56)
at org.apache.camel.cdi.internal.CamelContextConfig.configure(CamelContextConfig.java:47)
at org.apache.camel.cdi.internal.CamelContextBean.configureCamelContext(CamelContextBean.java:131)
at org.apache.camel.cdi.internal.CamelExtension.startConsumeBeans(CamelExtension.java:231)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month
[JBoss JIRA] (WFLY-1702) Investigate module wiring consistency at build time
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/WFLY-1702?page=com.atlassian.jira.plugin.... ]
Thomas Diesler resolved WFLY-1702.
----------------------------------
Resolution: Out of Date
Fix Version/s: (was: 9.0.0.Beta1)
Out of Date
> Investigate module wiring consistency at build time
> ---------------------------------------------------
>
> Key: WFLY-1702
> URL: https://issues.jboss.org/browse/WFLY-1702
> Project: WildFly
> Issue Type: Task
> Components: Build System
> Reporter: Thomas Diesler
>
> Due to the use of human wiring decisions it is possible that the initial modules wiring setup is incomplete/inconsistent. Various inconsistencies can occur
> * There are code paths in a module that require a class load for which there is no dependency defined
> * Modules define (stale) dependencies that are never used
> * Modules define dependencies that are inconsistent in the class space
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 1 month