[JBoss JIRA] (WFCORE-5136) NPE in ModelControllerMBeanHelper
by Ivo Studensky (Jira)
[ https://issues.redhat.com/browse/WFCORE-5136?page=com.atlassian.jira.plug... ]
Ivo Studensky updated WFCORE-5136:
----------------------------------
Labels: downstream_dependency regression (was: regression)
> NPE in ModelControllerMBeanHelper
> ---------------------------------
>
> Key: WFCORE-5136
> URL: https://issues.redhat.com/browse/WFCORE-5136
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Kabir Khan
> Priority: Blocker
> Labels: downstream_dependency, regression
>
> The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.
> {code}
> 15:50:42,596 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client
by Richard Achmatowicz (Jira)
[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ]
Richard Achmatowicz commented on WFLY-13871:
--------------------------------------------
Ok, i'll have look. Thanks for the feedback.
> Re-implement correct suspend/resume behaviour for EJB client
> ------------------------------------------------------------
>
> Key: WFLY-13871
> URL: https://issues.redhat.com/browse/WFLY-13871
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations.
> This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored.
> This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client
by Joerg Baesner (Jira)
[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ]
Joerg Baesner edited comment on WFLY-13871 at 9/17/20 7:11 AM:
---------------------------------------------------------------
[~rachmato], unfortunately the change of the PR does not resolve the issue...
> Re-implement correct suspend/resume behaviour for EJB client
> ------------------------------------------------------------
>
> Key: WFLY-13871
> URL: https://issues.redhat.com/browse/WFLY-13871
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations.
> This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored.
> This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5136) NPE in ModelControllerMBeanHelper
by Bartosz Spyrko-Smietanko (Jira)
[ https://issues.redhat.com/browse/WFCORE-5136?page=com.atlassian.jira.plug... ]
Bartosz Spyrko-Smietanko updated WFCORE-5136:
---------------------------------------------
Description:
The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.
{code}
15:50:42,596 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
{code}
was:
The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.
{code}
15:50:42,596 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
{code}
This is a regression against EAP 7.3.2, so setting priority to blocker for now.
> NPE in ModelControllerMBeanHelper
> ---------------------------------
>
> Key: WFCORE-5136
> URL: https://issues.redhat.com/browse/WFCORE-5136
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Kabir Khan
> Priority: Blocker
> Labels: regression
>
> The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.
> {code}
> 15:50:42,596 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5136) NPE in ModelControllerMBeanHelper
by Bartosz Spyrko-Smietanko (Jira)
[ https://issues.redhat.com/browse/WFCORE-5136?page=com.atlassian.jira.plug... ]
Bartosz Spyrko-Smietanko moved JBEAP-20208 to WFCORE-5136:
----------------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-5136 (was: JBEAP-20208)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JMX
(was: JMX)
Affects Version/s: (was: 7.3.3.CR1)
Fix Version/s: (was: 7.3.3.GA)
> NPE in ModelControllerMBeanHelper
> ---------------------------------
>
> Key: WFCORE-5136
> URL: https://issues.redhat.com/browse/WFCORE-5136
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX
> Reporter: Bartosz Spyrko-Smietanko
> Assignee: Kabir Khan
> Priority: Blocker
> Labels: regression
>
> The fix for JBEAP-19870 causes a NPE being thrown for some JMX calls.
> {code}
> 15:50:42,596 WARN [org.jboss.remotingjmx.protocol.v2.ServerCommon] (pool-13-thread-1) Unexpected internal error: java.lang.NullPointerException
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:556) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.invoke(ModelControllerMBeanHelper.java:487) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.invoke(ModelControllerMBeanServerPlugin.java:193) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:727) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.BlockingNotificationMBeanServer.invoke(BlockingNotificationMBeanServer.java:168) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.AuthorizingMBeanServer.invoke(AuthorizingMBeanServer.java:258) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerProxy$InvokeHandler.handle(ServerProxy.java:950)
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1$1.run(ServerCommon.java:153)
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:71) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor$1.run(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) [wildfly-elytron-auth-server-1.10.8.Final-redhat-00001.jar:1.10.8.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) [wildfly-controller-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.as.jmx.ServerInterceptorFactory$Interceptor.handleEvent(ServerInterceptorFactory.java:66) [wildfly-jmx-10.1.12.Final-redhat-00001.jar:10.1.12.Final-redhat-00001]
> at org.jboss.remotingjmx.protocol.v2.ServerCommon$MessageReciever$1.run(ServerCommon.java:149)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_265]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_265]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_265]
> {code}
> This is a regression against EAP 7.3.2, so setting priority to blocker for now.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (DROOLS-5649) [DMN XML] Signavio Profile - ZipFunction: parameter do not match
by Tommy Neubert (Jira)
Tommy Neubert created DROOLS-5649:
-------------------------------------
Summary: [DMN XML] Signavio Profile - ZipFunction: parameter do not match
Key: DROOLS-5649
URL: https://issues.redhat.com/browse/DROOLS-5649
Project: Drools
Issue Type: Bug
Reporter: Tommy Neubert
Assignee: Mario Fusco
h2. 1. Synopsis
In order to allow the execution of dmn.xml files exported by the Signavio Process Manager, the Signavio Profile ([https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio|h...]) contains all custom made functions.
The zip-function that is contained in this profile however expects its parameters in a different format then the Signavio Process Manager exports. This causes the parsing/execution of such dmn.xml files to fail. Customers have to manually adjust the xml file in order to get there executions running. This is both inconvenient and error prone and should be fixed.
h2. 2. Technical Details
As described above the parameters of the zip-function do not match
Signavio Process Manager Export:
{code:java}
zip(["name", "age"], [names, ages]){code}
Signavio Profiles expected parameters:
{code:java}
zip(["name", "age"], names, ages)
{code}
Codepointer:
[https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-signavio/s...]
h2. 3. Acceptance Criteria
# zip-function exported by the Signavio Process Manager should be executable without manual adjustments
# [backwards compatible]existing dmn.xml files (with manual adjustments) should still be exectuable
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13880) resource adapter logs plaintext JMS password at Warning level on connection error
by Jiri Danek (Jira)
[ https://issues.redhat.com/browse/WFLY-13880?page=com.atlassian.jira.plugi... ]
Jiri Danek updated WFLY-13880:
------------------------------
Description:
# start jms broker (AMQ 7 Broker, ActiveMQ Artemis based)
# start wildfly
# connect to the endpoint that causes JMS messages to be sent
# kill the broker
# observe following message in the log, containing {{user=example, pwd=example}}
{noformat}
14:24:51,513 WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (QpidJMS Connection Executor: ID:a340d7e7-a228-4730-b8ab-3bc7a1f66b41:1) Handling jms exception failure: JmsManagedConnection{mcf=org.jboss.resource.adapter.jms.JmsManagedConnectionFactory@1f572370, info=JmsConnectionRequestInfo{userName=example, password=example, clientID=null, transacted=false, acknowledgeMode=1, type=3}, user=example, pwd=example, isSetUp=true, isDestroyed=false, lock=org.jboss.resource.adapter.jms.ReentrantLock@317e1235[Unlocked], con=org.jboss.resource.adapter.jms.JmsConnectionSession@4b199ffd, session=class org.apache.qpid.jms.JmsSession@1532118793, xaSession=null, xaResource=null, xaTransacted=false, context=org.apache.qpid.jms.JmsContext@3fb9fa6a, xaContext=null}: org.apache.qpid.jms.exceptions.JmsConnectionFailedException: The JMS connection has failed: Transport connection remotely closed.
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:35)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:21)
at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)
at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1546)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1530)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1374)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.fireProviderException(AmqpProvider.java:1150)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.lambda$onTransportClosed$18(AmqpProvider.java:914)
at deployment.resource-adapter.rar//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at deployment.resource-adapter.rar//io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at deployment.resource-adapter.rar//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.qpid.jms.provider.exceptions.ProviderFailedException: Transport connection remotely closed.
... 7 more
{noformat}
I am not sure how important this is. In my experience, people dislike having their passwords spilled out in plaintext. On the other hand, I'd expect that a report about this will already exist somewhere, and I was unable to find it. So maybe it is not a production isssue for anyone.
Originally reported at https://github.com/amqphub/amqp-10-resource-adapter/issues/13
The log message comes from https://github.com/jms-ra/generic-jms-ra/blob/ece9e15843136023c26d3d0bd32...
was:
# start jms broker (AMQ 7 Broker, ActiveMQ Artemis based)
# start wildfly
# connect to the endpoint that causes JMS messages to be sent
# kill the broker
# observe following message in the log, containing {{user=example, pwd=example}}
{noformat}
14:24:51,513 WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (QpidJMS Connection Executor: ID:a340d7e7-a228-4730-b8ab-3bc7a1f66b41:1) Handling jms exception failure: JmsManagedConnection{mcf=org.jboss.resource.adapter.jms.JmsManagedConnectionFactory@1f572370, info=JmsConnectionRequestInfo{userName=example, password=example, clientID=null, transacted=false, acknowledgeMode=1, type=3}, user=example, pwd=example, isSetUp=true, isDestroyed=false, lock=org.jboss.resource.adapter.jms.ReentrantLock@317e1235[Unlocked], con=org.jboss.resource.adapter.jms.JmsConnectionSession@4b199ffd, session=class org.apache.qpid.jms.JmsSession@1532118793, xaSession=null, xaResource=null, xaTransacted=false, context=org.apache.qpid.jms.JmsContext@3fb9fa6a, xaContext=null}: org.apache.qpid.jms.exceptions.JmsConnectionFailedException: The JMS connection has failed: Transport connection remotely closed.
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:35)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:21)
at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)
at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1546)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1530)
at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1374)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.fireProviderException(AmqpProvider.java:1150)
at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.lambda$onTransportClosed$18(AmqpProvider.java:914)
at deployment.resource-adapter.rar//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
at deployment.resource-adapter.rar//io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at deployment.resource-adapter.rar//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.apache.qpid.jms.provider.exceptions.ProviderFailedException: Transport connection remotely closed.
... 7 more
{noformat}
I am not sure how important this is. In my experience, people dislike having their passwords spilled out in plaintext. On the other hand, I'd expect that a report about this will already exist somewhere, and I was unable to find it. So maybe it is not a production isssue for anyone.
Originally reported at https://github.com/amqphub/amqp-10-resource-adapter/issues/13
> resource adapter logs plaintext JMS password at Warning level on connection error
> ---------------------------------------------------------------------------------
>
> Key: WFLY-13880
> URL: https://issues.redhat.com/browse/WFLY-13880
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.0.Final
> Reporter: Jiri Danek
> Assignee: Emmanuel Hugonnet
> Priority: Minor
>
> # start jms broker (AMQ 7 Broker, ActiveMQ Artemis based)
> # start wildfly
> # connect to the endpoint that causes JMS messages to be sent
> # kill the broker
> # observe following message in the log, containing {{user=example, pwd=example}}
> {noformat}
> 14:24:51,513 WARN [org.jboss.resource.adapter.jms.JmsManagedConnection] (QpidJMS Connection Executor: ID:a340d7e7-a228-4730-b8ab-3bc7a1f66b41:1) Handling jms exception failure: JmsManagedConnection{mcf=org.jboss.resource.adapter.jms.JmsManagedConnectionFactory@1f572370, info=JmsConnectionRequestInfo{userName=example, password=example, clientID=null, transacted=false, acknowledgeMode=1, type=3}, user=example, pwd=example, isSetUp=true, isDestroyed=false, lock=org.jboss.resource.adapter.jms.ReentrantLock@317e1235[Unlocked], con=org.jboss.resource.adapter.jms.JmsConnectionSession@4b199ffd, session=class org.apache.qpid.jms.JmsSession@1532118793, xaSession=null, xaResource=null, xaTransacted=false, context=org.apache.qpid.jms.JmsContext@3fb9fa6a, xaContext=null}: org.apache.qpid.jms.exceptions.JmsConnectionFailedException: The JMS connection has failed: Transport connection remotely closed.
> at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:35)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.exceptions.ProviderFailedException.toJMSException(ProviderFailedException.java:21)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:80)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.exceptions.JmsExceptionSupport.create(JmsExceptionSupport.java:112)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onAsyncException(JmsConnection.java:1546)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onProviderException(JmsConnection.java:1530)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.JmsConnection.onConnectionFailure(JmsConnection.java:1374)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.fireProviderException(AmqpProvider.java:1150)
> at deployment.resource-adapter.rar//org.apache.qpid.jms.provider.amqp.AmqpProvider.lambda$onTransportClosed$18(AmqpProvider.java:914)
> at deployment.resource-adapter.rar//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
> at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
> at deployment.resource-adapter.rar//io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)
> at deployment.resource-adapter.rar//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
> at deployment.resource-adapter.rar//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.apache.qpid.jms.provider.exceptions.ProviderFailedException: Transport connection remotely closed.
> ... 7 more
> {noformat}
> I am not sure how important this is. In my experience, people dislike having their passwords spilled out in plaintext. On the other hand, I'd expect that a report about this will already exist somewhere, and I was unable to find it. So maybe it is not a production isssue for anyone.
> Originally reported at https://github.com/amqphub/amqp-10-resource-adapter/issues/13
> The log message comes from https://github.com/jms-ra/generic-jms-ra/blob/ece9e15843136023c26d3d0bd32...
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months