[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:
------------------------------
Labels: resource-adapter (was: )
> 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
> Labels: resource-adapter
>
> # 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
[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
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
{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
--
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:
------------------------------
Priority: Minor (was: Major)
> 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
> {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
--
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)
Jiri Danek created WFLY-13880:
---------------------------------
Summary: 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
# 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
{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
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13877) [Regression] java.lang.IllegalArgumentException: invalid null LoadStoreParameter
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFLY-13877?page=com.atlassian.jira.plugi... ]
Martin Choma commented on WFLY-13877:
-------------------------------------
Seems as test issue.
We used to have this in our test. {{.truststorePath("whatever")}} was workaround for issue in creaper library.
{code}
// truststorePath has to be filled because of bug in creaper https://github.com/wildfly-extras/creaper/issues/110
httpsRealmBuilder.truststorePath("whatever").truststoreProvider("PKCS11").truststorePassword(getPKCS11StorePassword());
{code}
Apparently since WF 21 {{truststorePath("whatever")}} starts to make problem. When I remove it (what is possible now in creaper library) test works correctly.
{code}
httpsRealmBuilder.truststoreProvider("PKCS11").truststorePassword(getPKCS11StorePassword());
{code}
Are you able to find issue which was changing this behaviour?
> [Regression] java.lang.IllegalArgumentException: invalid null LoadStoreParameter
> --------------------------------------------------------------------------------
>
> Key: WFLY-13877
> URL: https://issues.redhat.com/browse/WFLY-13877
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Major
>
> We started to experience new failure in existing FIPS tests. It is legacy security subsystem configured in FIPS mode and authenticating Undertow.
> It is not related to new version of JDK. I can confirm same tests and JDK pass with WF20, but is not passing on WF21.
> {code}
> 15:48:29,224 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.core.management.security.realm.HttpsRealm.trust-manager: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.HttpsRealm.trust-manager: Failed to start service
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter
> at jdk.crypto.cryptoki/sun.security.pkcs11.P11KeyStore.engineLoad(P11KeyStore.java:821)
> at java.base/java.security.KeyStore.load(KeyStore.java:1513)
> at org.jboss.as.domain-management@13.0.0.Beta5//org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:116)
> at org.jboss.as.domain-management@13.0.0.Beta5//org.jboss.as.domain.management.security.FileTrustManagerService.start(FileTrustManagerService.java:137)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> 15:48:29,236 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}}
> 15:48:29,241 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0190: Step handler org.jboss.as.controller.RestartParentResourceHandlerBase$1@235f68cb for operation add at address [
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm"),
> ("authentication" => "truststore")
> ] failed -- org.jboss.as.controller.registry.Resource$NoSuchResourceException: WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]' not found [ "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"HttpsRealm\")
> ]' not found" ]: org.jboss.as.controller.registry.Resource$NoSuchResourceException: WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]' not found [ "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"HttpsRealm\")
> ]' not found" ]
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.requireChild(OperationContextImpl.java:1274)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:945)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:916)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:890)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:884)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.RestartParentResourceHandlerBase$1$1.handleRollback(RestartParentResourceHandlerBase.java:84)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1567)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1539)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1521)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1478)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1461)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1325)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:877)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:757)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.elytron-private@1.13.0.CR4//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.elytron-private@1.13.0.CR4//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller(a)13.0.0.Beta5//org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOpTests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.513 sec <<< FAILURE! - in com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase
> com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase Time elapsed: 6.509 sec <<< ERROR!
> org.wildfly.extras.creaper.core.CommandFailedException: Operation {"operation" => "composite","address" => [],"steps" => [{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm")]},{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm"),("server-identity" => "ssl")],"keystore-password" => "pass123+","keystore-provider" => "PKCS11"},{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm"),("authentication" => "truststore")],"keystore-password" => "pass123+","keystore-path" => "whatever","keystore-provider" => "PKCS11"}]} failed: {"outcome" => "failed","result" => {"step-1" => {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}},"rolled-back" => true},"step-2" => {"outcome" => "failed","rolled-back" => true},"step-3" => {"outcome" => "failed","rolled-back" => true}},"failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}}}},"rolled-back" => true}
> at org.wildfly.extras.creaper.core.online.AutomaticErrorHandlingForCommands.commandFailedWithMessage(AutomaticErrorHandlingForCommands.java:138)
> at org.wildfly.extras.creaper.core.online.AutomaticErrorHandlingForCommands.execute(AutomaticErrorHandlingForCommands.java:60)
> at org.wildfly.extras.creaper.core.online.operations.Operations.batch(Operations.java:167)
> at org.wildfly.extras.creaper.commands.undertow.AddHttpsSecurityRealm.apply(AddHttpsSecurityRealm.java:82)
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.apply(OnlineManagementClientImpl.java:136)
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.apply(OnlineManagementClientImpl.java:125)
> at com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase.setupServer(HttpsUndertowTestCase.java:213)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13877) [Regression] java.lang.IllegalArgumentException: invalid null LoadStoreParameter
by Martin Choma (Jira)
[ https://issues.redhat.com/browse/WFLY-13877?page=com.atlassian.jira.plugi... ]
Martin Choma updated WFLY-13877:
--------------------------------
Priority: Major (was: Critical)
> [Regression] java.lang.IllegalArgumentException: invalid null LoadStoreParameter
> --------------------------------------------------------------------------------
>
> Key: WFLY-13877
> URL: https://issues.redhat.com/browse/WFLY-13877
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 21.0.0.Beta1
> Reporter: Martin Choma
> Assignee: Darran Lofthouse
> Priority: Major
>
> We started to experience new failure in existing FIPS tests. It is legacy security subsystem configured in FIPS mode and authenticating Undertow.
> It is not related to new version of JDK. I can confirm same tests and JDK pass with WF20, but is not passing on WF21.
> {code}
> 15:48:29,224 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service org.wildfly.core.management.security.realm.HttpsRealm.trust-manager: org.jboss.msc.service.StartException in service org.wildfly.core.management.security.realm.HttpsRealm.trust-manager: Failed to start service
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter
> at jdk.crypto.cryptoki/sun.security.pkcs11.P11KeyStore.engineLoad(P11KeyStore.java:821)
> at java.base/java.security.KeyStore.load(KeyStore.java:1513)
> at org.jboss.as.domain-management@13.0.0.Beta5//org.jboss.as.domain.management.security.FileKeystore.load(FileKeystore.java:116)
> at org.jboss.as.domain-management@13.0.0.Beta5//org.jboss.as.domain.management.security.FileTrustManagerService.start(FileTrustManagerService.java:137)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> ... 6 more
> 15:48:29,236 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}}
> 15:48:29,241 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0190: Step handler org.jboss.as.controller.RestartParentResourceHandlerBase$1@235f68cb for operation add at address [
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm"),
> ("authentication" => "truststore")
> ] failed -- org.jboss.as.controller.registry.Resource$NoSuchResourceException: WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]' not found [ "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"HttpsRealm\")
> ]' not found" ]: org.jboss.as.controller.registry.Resource$NoSuchResourceException: WFLYCTL0216: Management resource '[
> ("core-service" => "management"),
> ("security-realm" => "HttpsRealm")
> ]' not found [ "WFLYCTL0216: Management resource '[
> (\"core-service\" => \"management\"),
> (\"security-realm\" => \"HttpsRealm\")
> ]' not found" ]
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.requireChild(OperationContextImpl.java:1274)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:945)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:916)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:890)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.readResource(OperationContextImpl.java:884)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.RestartParentResourceHandlerBase$1$1.handleRollback(RestartParentResourceHandlerBase.java:84)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$RollbackDelegatingResultHandler.handleResult(AbstractOperationContext.java:1567)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.invokeResultHandler(AbstractOperationContext.java:1539)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1521)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1478)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1461)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1325)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:877)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:757)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1413)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:431)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:248)
> at org.wildfly.security.elytron-private@1.13.0.CR4//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:304)
> at org.wildfly.security.elytron-private@1.13.0.CR4//org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:248)
> at org.jboss.as.controller@13.0.0.Beta5//org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:240)
> at org.jboss.as.controller(a)13.0.0.Beta5//org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOpTests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.513 sec <<< FAILURE! - in com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase
> com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase Time elapsed: 6.509 sec <<< ERROR!
> org.wildfly.extras.creaper.core.CommandFailedException: Operation {"operation" => "composite","address" => [],"steps" => [{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm")]},{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm"),("server-identity" => "ssl")],"keystore-password" => "pass123+","keystore-provider" => "PKCS11"},{"operation" => "add","address" => [("core-service" => "management"),("security-realm" => "HttpsRealm"),("authentication" => "truststore")],"keystore-password" => "pass123+","keystore-path" => "whatever","keystore-provider" => "PKCS11"}]} failed: {"outcome" => "failed","result" => {"step-1" => {"outcome" => "failed","failure-description" => {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}},"rolled-back" => true},"step-2" => {"outcome" => "failed","rolled-back" => true},"step-3" => {"outcome" => "failed","rolled-back" => true}},"failure-description" => {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"org.wildfly.core.management.security.realm.HttpsRealm.trust-manager" => "Failed to start service
> Caused by: java.lang.IllegalArgumentException: invalid null LoadStoreParameter"}}}},"rolled-back" => true}
> at org.wildfly.extras.creaper.core.online.AutomaticErrorHandlingForCommands.commandFailedWithMessage(AutomaticErrorHandlingForCommands.java:138)
> at org.wildfly.extras.creaper.core.online.AutomaticErrorHandlingForCommands.execute(AutomaticErrorHandlingForCommands.java:60)
> at org.wildfly.extras.creaper.core.online.operations.Operations.batch(Operations.java:167)
> at org.wildfly.extras.creaper.commands.undertow.AddHttpsSecurityRealm.apply(AddHttpsSecurityRealm.java:82)
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.apply(OnlineManagementClientImpl.java:136)
> at org.wildfly.extras.creaper.core.online.OnlineManagementClientImpl.apply(OnlineManagementClientImpl.java:125)
> at com.redhat.eap.qe.fips.standalone.HttpsUndertowTestCase.setupServer(HttpsUndertowTestCase.java:213)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13879) Upgrade Mojarra to 2.3.14.SP01
by Farah Juma (Jira)
[ https://issues.redhat.com/browse/WFLY-13879?page=com.atlassian.jira.plugi... ]
Farah Juma updated WFLY-13879:
------------------------------
Description: We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest upstream bug fixes. We should also backport the upstream fix for WFLY-12677. (was: We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest bug fixes. We should also backport the upstream fix for WFLY-12677.)
> Upgrade Mojarra to 2.3.14.SP01
> ------------------------------
>
> Key: WFLY-13879
> URL: https://issues.redhat.com/browse/WFLY-13879
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JSF
> Reporter: Farah Juma
> Assignee: Farah Juma
> Priority: Major
>
> We should upgrade from Mojarra 2.3.9 to 2.3.14 to incorporate the latest upstream bug fixes. We should also backport the upstream fix for WFLY-12677.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months