[JBoss JIRA] (WFLY-9639) Messages are stuck in a Queue that is configured on HornetQ
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-9639?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reassigned WFLY-9639:
------------------------------------
Component/s: JMS
(was: Application Client)
Assignee: Jeff Mesnil (was: Stuart Douglas)
> Messages are stuck in a Queue that is configured on HornetQ
> -----------------------------------------------------------
>
> Key: WFLY-9639
> URL: https://issues.jboss.org/browse/WFLY-9639
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 9.x.x TBD
> Environment: RHEL 7.2, JDK 1.8_144
> Reporter: Rajendra Mallampati
> Assignee: Jeff Mesnil
>
> We use WildFly 9.0.2 for hosting our web application and it has both real time and batch processing components. One of the functions supported on the web includes uploading a file with a number of lines any where from 1 to 10K, If the file is valid (virus scan etc passed) it is parsed into that may messages and published to a queue. Each message will have two counters total number of messages that are published to the queue, and the message number.
> The consuming side is implemented using Spring DefaultMessageListenerContainer (DMLC) with a concurrency of 50 and maxConcurrency of 75. The listeners that implement MessageListener interface are integrated into DMLC. sometimes, if the producing side published 100 messages the consuming side only receiving 98 (per say) and gets stuck because two more messages should be in the Queue. Those two messages are not delivered and don't know where they are going. We tried even persistent Queues and the result is same (getting stuck).
> This is happening in production and any insight into this issue is highly appreciated.
> Here are the software details:
> App server : Wildfly 9.0.2
> HornetQ : 2.4.7
> JDK : 1_8_144
> If you need additional details I will be very glad to provide.
> Thanks
> Rajendra
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFCORE-3483) Deprecate PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3483?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-3483:
-------------------------------------
Summary: Deprecate PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException (was: Deprecated PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException)
> Deprecate PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3483
> URL: https://issues.jboss.org/browse/WFCORE-3483
> Project: WildFly Core
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Priority: Minor
>
> The management layer has some old code that uses throwing or catching of NoSuchElementException as a way to represent that a resource doesn't exist. Clean this out so we can more easily move to a cleaner set of exceptions.
> This work will consist of two aspects:
> 1) Code that's meant to catch Resource.NoSuchResourceException but instead catches its superclass NoSuchElementException will shift to catching the subclass. This will make the true intent of the code clearer.
> 2) The unused PathAddress.navigate and remove methods, which throw NoSuchElementException, will be deprecated. Using PathAddress to maneuver through a deep DMR node tree is not really how management works ever since we introduced the Resource class long long ago (hence these methods are unused.)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFCORE-3483) Deprecated PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-3483:
----------------------------------------
Summary: Deprecated PathAddress.navigate and remove, replace controller catches of NoSuchElementException with Resource.NoSuchResourceException
Key: WFCORE-3483
URL: https://issues.jboss.org/browse/WFCORE-3483
Project: WildFly Core
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
The management layer has some old code that uses throwing or catching of NoSuchElementException as a way to represent that a resource doesn't exist. Clean this out so we can more easily move to a cleaner set of exceptions.
This work will consist of two aspects:
1) Code that's meant to catch Resource.NoSuchResourceException but instead catches its superclass NoSuchElementException will shift to catching the subclass. This will make the true intent of the code clearer.
2) The unused PathAddress.navigate and remove methods, which throw NoSuchElementException, will be deprecated. Using PathAddress to maneuver through a deep DMR node tree is not really how management works ever since we introduced the Resource class long long ago (hence these methods are unused.)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month