[jira] [Created] (ARTEMIS-2283) Bad WARN messages: AMQ222211: Storage is back to stable now...
Emmanuel Hugonnet created ARTEMIS-2283:
--
Summary: Bad WARN messages: AMQ11: Storage is back to stable
now...
Key: ARTEMIS-2283
URL: https://issues.apache.org/jira/browse/ARTEMIS-2283
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.7.0
Reporter: Emmanuel Hugonnet
There are unwanted WARN messages:
|{color:#00}13:47:48,158 INFO [org.jboss.as] (Controller Boot Thread)
WFLYSRV0025: WildFly Full 15.0.0.Alpha1-SNAPSHOT (WildFly Core 7.0.0.Alpha4)
started in 8017ms - Started 495 of 723 services (489 services are lazy, passive
or on-demand){color}|
|{color:#00}13:47:50,235 WARN [org.apache.activemq.artemis.core.server]
(Thread-0
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
AMQ222183: Blocking message production on address 'jms.queue.InQueue'; size is
currently: 10,635,300 bytes; max-size-bytes on address: 10,485,760,
global-max-size is 10,635,300{color}|
|{color:#00}13:47:52,642 WARN [org.apache.activemq.artemis.core.server]
(Thread-4
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
|{color:#00}13:47:57,642 WARN [org.apache.activemq.artemis.core.server]
(Thread-15
(ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
|{color:#00}... {color}|
when server has configured {{global-max-memory-size}} and address-full-policy
to BLOCK. Once {{global-max-memory-size}} then starts to log above warnings
which with max-disk-usage. Which is not correct as no disk limitation was
reached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Deleted] (AMQCLI-11) Uploaded image for project: 'OpenNLP' OpenNLPOPENNLP-1242 19-88S. Poortman
[ https://issues.apache.org/jira/browse/AMQCLI-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon deleted AMQCLI-11: - > Uploaded image for project: 'OpenNLP' OpenNLPOPENNLP-1242 > 19-88S. Poortman > - > > Key: AMQCLI-11 > URL: https://issues.apache.org/jira/browse/AMQCLI-11 > Project: ActiveMQ CLI Tools > Issue Type: Bug >Reporter: Simon poortman >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (ARTEMIS-2284) Artemis 2.7.0 logs password for STOMP protocol in clear text in debug logs
Miroslav Novak created ARTEMIS-2284:
---
Summary: Artemis 2.7.0 logs password for STOMP protocol in clear
text in debug logs
Key: ARTEMIS-2284
URL: https://issues.apache.org/jira/browse/ARTEMIS-2284
Project: ActiveMQ Artemis
Issue Type: Bug
Components: Broker
Affects Versions: 2.7.0
Reporter: Miroslav Novak
If TRACE log is enabled for {{org.apache.activemq.artemis}} then StompProtoco
is logging password in clear text:
{code}
13:48:06,488 DEBUG [org.apache.commons.beanutils.BeanUtils] (ServerService
Thread Pool -- 86)
BeanUtils.populate(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516,
{needClientAuth=tru
e, trustStorePassword=hornetqexample, keyStorePassword=hornetqexample,
port=6445, sslEnabled=true, host=127.0.0.1,
trustStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-weekly-common-ssl/eap-t
estsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.truststore,
keyStorePath=/home/hudson/hudson_workspace/workspace/eap-7.x-messaging-week
ly-common-ssl/eap-testsuite/jboss-hornetq-testsuite/tests-eap7/src/test/resources/org/jboss/qa/hornetq/test/transportprotocols/hornetq.example.keystore})
...
13:48:06,488 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService
Thread Pool -- 86)
setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516,
trustStorePassword, horn
etqexample)
...
13:48:06,489 TRACE [org.apache.commons.beanutils.BeanUtils] (ServerService
Thread Pool -- 86)
setProperty(org.apache.activemq.artemis.core.protocol.stomp.StompProtocolManager@2aa25516,
keyStorePassword, hornet
qexample)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARTEMIS-2279) IllegalStateException: Cannot find binding
[
https://issues.apache.org/jira/browse/ARTEMIS-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16801693#comment-16801693
]
Sami Nieminen commented on ARTEMIS-2279:
Posted here:
http://activemq.2283324.n4.nabble.com/IllegalStateException-Cannot-find-binding-td4749734.html
> IllegalStateException: Cannot find binding
> --
>
> Key: ARTEMIS-2279
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2279
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.4
>Reporter: Sami Nieminen
>Priority: Major
>
> We have artemis master/slave configuration on production, currently version
> 2.6.4. We regularly experience the following errors:
> {code}
> 2019-03-15 22:50:45,970 WARN [org.apache.activemq.artemis.core.server]
> AMQ25: Sending unexpected exception to the client:
> java.lang.IllegalStateException: Cannot find binding
> f32e2087-8a3a-463f-972c-6bc3344a9fc3
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeMapping(SimpleAddressManager.java:221)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeBindingInternal(SimpleAddressManager.java:202)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeBinding(SimpleAddressManager.java:103)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.removeBinding(WildcardAddressManager.java:138)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.removeBinding(PostOfficeImpl.java:662)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deleteQueue(QueueImpl.java:1674)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1890)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1847)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1827)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.deleteQueue(ServerSessionImpl.java:836)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.slowPacketHandler(ServerSessionPacketHandler.java:395)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.onMessagePacket(ServerSessionPacketHandler.java:287)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.Actor.doTask(Actor.java:33)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_162]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_162]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.6.4.jar:2.6.4]
> {code}
> I didn't see these errors on single-server configuration. What could cause
> this error?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (ARTEMIS-2279) IllegalStateException: Cannot find binding
[
https://issues.apache.org/jira/browse/ARTEMIS-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sami Nieminen closed ARTEMIS-2279.
--
Resolution: Not A Bug
> IllegalStateException: Cannot find binding
> --
>
> Key: ARTEMIS-2279
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2279
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.6.4
>Reporter: Sami Nieminen
>Priority: Major
>
> We have artemis master/slave configuration on production, currently version
> 2.6.4. We regularly experience the following errors:
> {code}
> 2019-03-15 22:50:45,970 WARN [org.apache.activemq.artemis.core.server]
> AMQ25: Sending unexpected exception to the client:
> java.lang.IllegalStateException: Cannot find binding
> f32e2087-8a3a-463f-972c-6bc3344a9fc3
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeMapping(SimpleAddressManager.java:221)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeBindingInternal(SimpleAddressManager.java:202)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.SimpleAddressManager.removeBinding(SimpleAddressManager.java:103)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.WildcardAddressManager.removeBinding(WildcardAddressManager.java:138)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.removeBinding(PostOfficeImpl.java:662)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.QueueImpl.deleteQueue(QueueImpl.java:1674)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1890)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1847)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.destroyQueue(ActiveMQServerImpl.java:1827)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.deleteQueue(ServerSessionImpl.java:836)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.slowPacketHandler(ServerSessionPacketHandler.java:395)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.onMessagePacket(ServerSessionPacketHandler.java:287)
> [artemis-server-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.Actor.doTask(Actor.java:33)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
> [artemis-commons-2.6.4.jar:2.6.4]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [rt.jar:1.8.0_162]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [rt.jar:1.8.0_162]
> at
> org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
> [artemis-commons-2.6.4.jar:2.6.4]
> {code}
> I didn't see these errors on single-server configuration. What could cause
> this error?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (ARTEMIS-2282) QueueImpl.addTail NPEs during processing of a management message
[ https://issues.apache.org/jira/browse/ARTEMIS-2282?focusedWorklogId=218626&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-218626 ] ASF GitHub Bot logged work on ARTEMIS-2282: --- Author: ASF GitHub Bot Created on: 26/Mar/19 13:35 Start Date: 26/Mar/19 13:35 Worklog Time Spent: 10m Work Description: franz1981 commented on issue #2590: ARTEMIS-2282 QueueImpl::addTail of a management message could throw NPE URL: https://github.com/apache/activemq-artemis/pull/2590#issuecomment-476638141 @michaelandrepearce @k-wall I've added a test (not one of my most brilliant one I admit): it is always reproducing the issue, without needing any weird concurrent/non-deterministic behaviours :+1: This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 218626) Time Spent: 40m (was: 0.5h) > QueueImpl.addTail NPEs during processing of a management message > > > Key: ARTEMIS-2282 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2282 > Project: ActiveMQ Artemis > Issue Type: Bug >Affects Versions: 2.7.0 >Reporter: Keith Wall >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > We are in the process of upgrading to Artemis 2.7.0 > ([https://github.com/EnMasseProject/enmasse/pull/2493]). We notice the > following NPE showing in the Artemis logs following a run of our test-suite. > Our application sends management messages over AMQP (to activemq.management) > to control the Broker and we can see from the stack that it is the processing > of these messages that leads to the failure. > -Our test suite is passing and as far as we can tell, there is no functional > defect.- (Correction, we are seeing failures [updated :2019-03-25]), > Could this be related to the recent work of ARTEMIS-1710? > > 2019-03-22T21:42:15.150Z WARN [ProtonServerReceiverContext] null: > java.lang.NullPointerException > at > org.apache.activemq.artemis.core.server.impl.QueueImpl.addTail(QueueImpl.java:898) > at > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl.internalprocessReferences(RoutingContextImpl.java:138) > at > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl.processReferences(RoutingContextImpl.java:133) > at > org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl$2.done(PostOfficeImpl.java:1370) > at > org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:189) > at > org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:130) > at > org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.afterCompleteOperations(AbstractJournalStorageManager.java:323) > at org.apac2019-03-22T21:42:15.150Z WARN [ProtonServerReceiverContext] null: > java.lang.NullPointerException > at > org.apache.activemq.artemis.core.server.impl.QueueImpl.addTail(QueueImpl.java:898) > at > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl.internalprocessReferences(RoutingContextImpl.java:138) > iv at > org.apache.activemq.artemis.core.server.impl.RoutingContextImpl.processReferences(RoutingContextImpl.java:133) > at > org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl$2.done(PostOfficeImpl.java:1370) > at > org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:189) > at > org.apache.activemq.artemis.core.persistence.impl.journal.OperationContextImpl.executeOnCompletion(OperationContextImpl.java:130) > at > org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.afterCompleteOperations(AbstractJournalStorageManager.java:323) > emq.artemis.core.postoffice.impl.PostOfficeImpl.processRoute(PostOfficeImpl.java:1362) > at > org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:976) > at > org.apache.activemq.artemis.core.postoffice.impl.PostOfficeImpl.route(PostOfficeImpl.java:867) > at > org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.doSend(ServerSessionImpl.java:1972) > at > org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.handleManagementMessage(ServerSessionImpl.java:1857) > at > org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.send(ServerSessionImpl.java:1613) > at > org.apac
[jira] [Work logged] (ARTEMIS-2283) Bad WARN messages: AMQ222211: Storage is back to stable now...
[
https://issues.apache.org/jira/browse/ARTEMIS-2283?focusedWorklogId=218761&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-218761
]
ASF GitHub Bot logged work on ARTEMIS-2283:
---
Author: ASF GitHub Bot
Created on: 26/Mar/19 17:05
Start Date: 26/Mar/19 17:05
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #2591: ARTEMIS-2283
Bad WARN message "AMQ11: Storage is back to stable now"
URL: https://github.com/apache/activemq-artemis/pull/2591
LocalMonitor::under on PagingManagerImpl won't log anymore with a
warning message if the producers got unblocked
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 218761)
Time Spent: 10m
Remaining Estimate: 0h
> Bad WARN messages: AMQ11: Storage is back to stable now...
> --
>
> Key: ARTEMIS-2283
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2283
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.7.0
>Reporter: Emmanuel Hugonnet
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are unwanted WARN messages:
>
> |{color:#00}13:47:48,158 INFO [org.jboss.as] (Controller Boot Thread)
> WFLYSRV0025: WildFly Full 15.0.0.Alpha1-SNAPSHOT (WildFly Core 7.0.0.Alpha4)
> started in 8017ms - Started 495 of 723 services (489 services are lazy,
> passive or on-demand){color}|
> |{color:#00}13:47:50,235 WARN [org.apache.activemq.artemis.core.server]
> (Thread-0
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ222183: Blocking message production on address 'jms.queue.InQueue'; size
> is currently: 10,635,300 bytes; max-size-bytes on address: 10,485,760,
> global-max-size is 10,635,300{color}|
> |{color:#00}13:47:52,642 WARN [org.apache.activemq.artemis.core.server]
> (Thread-4
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#00}13:47:57,642 WARN [org.apache.activemq.artemis.core.server]
> (Thread-15
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#00}... {color}|
>
> when server has configured {{global-max-memory-size}} and address-full-policy
> to BLOCK. Once {{global-max-memory-size}} then starts to log above warnings
> which with max-disk-usage. Which is not correct as no disk limitation was
> reached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Work logged] (ARTEMIS-2283) Bad WARN messages: AMQ222211: Storage is back to stable now...
[
https://issues.apache.org/jira/browse/ARTEMIS-2283?focusedWorklogId=218804&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-218804
]
ASF GitHub Bot logged work on ARTEMIS-2283:
---
Author: ASF GitHub Bot
Created on: 26/Mar/19 18:05
Start Date: 26/Mar/19 18:05
Worklog Time Spent: 10m
Work Description: franz1981 commented on issue #2591: ARTEMIS-2283 Bad
WARN message "AMQ11: Storage is back to stable now"
URL: https://github.com/apache/activemq-artemis/pull/2591#issuecomment-476777451
@ehsavoie I've changed my mind: I have noticed that we already have some
test to cover things like log messages to I think tht is the right place to put
them :+1:
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 218804)
Time Spent: 20m (was: 10m)
> Bad WARN messages: AMQ11: Storage is back to stable now...
> --
>
> Key: ARTEMIS-2283
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2283
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
>Affects Versions: 2.7.0
>Reporter: Emmanuel Hugonnet
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are unwanted WARN messages:
>
> |{color:#00}13:47:48,158 INFO [org.jboss.as] (Controller Boot Thread)
> WFLYSRV0025: WildFly Full 15.0.0.Alpha1-SNAPSHOT (WildFly Core 7.0.0.Alpha4)
> started in 8017ms - Started 495 of 723 services (489 services are lazy,
> passive or on-demand){color}|
> |{color:#00}13:47:50,235 WARN [org.apache.activemq.artemis.core.server]
> (Thread-0
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ222183: Blocking message production on address 'jms.queue.InQueue'; size
> is currently: 10,635,300 bytes; max-size-bytes on address: 10,485,760,
> global-max-size is 10,635,300{color}|
> |{color:#00}13:47:52,642 WARN [org.apache.activemq.artemis.core.server]
> (Thread-4
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#00}13:47:57,642 WARN [org.apache.activemq.artemis.core.server]
> (Thread-15
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$5@371ff371))
> AMQ11: Storage is back to stable now, under max-disk-usage.{color}|
> |{color:#00}... {color}|
>
> when server has configured {{global-max-memory-size}} and address-full-policy
> to BLOCK. Once {{global-max-memory-size}} then starts to log above warnings
> which with max-disk-usage. Which is not correct as no disk limitation was
> reached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (ARTEMIS-2285) Sorting by user column in connections view not working
Sebastian T created ARTEMIS-2285: Summary: Sorting by user column in connections view not working Key: ARTEMIS-2285 URL: https://issues.apache.org/jira/browse/ARTEMIS-2285 Project: ActiveMQ Artemis Issue Type: Bug Components: Web Console Affects Versions: 2.7.0 Reporter: Sebastian T The connections view in the web console cannot be sorted by user, despite the users column header being clickable and showing sort direction indicator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work logged] (ARTEMIS-2285) Sorting by user column in connections view not working
[ https://issues.apache.org/jira/browse/ARTEMIS-2285?focusedWorklogId=218849&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-218849 ] ASF GitHub Bot logged work on ARTEMIS-2285: --- Author: ASF GitHub Bot Created on: 26/Mar/19 18:46 Start Date: 26/Mar/19 18:46 Worklog Time Spent: 10m Work Description: sebthom commented on pull request #2592: ARTEMIS-2285 Sorting by user column in connections view not working URL: https://github.com/apache/activemq-artemis/pull/2592 The value returned by ConnectionsView.getField(con, "users") currently returns a Set which does not implement the Comparable interface thus ActiveMQAbstractView#getComparator() always returns a comparator which evaluates to 0. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 218849) Time Spent: 10m Remaining Estimate: 0h > Sorting by user column in connections view not working > -- > > Key: ARTEMIS-2285 > URL: https://issues.apache.org/jira/browse/ARTEMIS-2285 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Web Console >Affects Versions: 2.7.0 >Reporter: Sebastian T >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > > The connections view in the web console cannot be sorted by user, despite the > users column header being clickable and showing sort direction indicator. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
