January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9645) EJB lookup over HTTP times out connection after 60 seconds

by Stuart Douglas (JIRA)

Stuart Douglas created WFLY-9645: ------------------------------------ Summary: EJB lookup over HTTP times out connection after 60 seconds Key: WFLY-9645 URL: https://issues.jboss.org/browse/WFLY-9645 Project: WildFly Issue Type: Bug Components: EJB, IO, Naming Affects Versions: 11.0.0.Final Environment: I work with https://developer.jboss.org/people/jaikiran on https://developer.jboss.org/thread/276635 so my Wildfly 11 environment has this fix in it. Reporter: peter craddock Assignee: Stuart Douglas The code examples and trace logging can be found here https://developer.jboss.org/thread/276840 I have work round the problem but was asked to raise it for further investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9636) EJB lookup over HTTP times out connection after 60 seconds

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9636?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-9636: ------------------------------------ Assignee: Stuart Douglas > EJB lookup over HTTP times out connection after 60 seconds > ---------------------------------------------------------- > > Key: WFLY-9636 > URL: https://issues.jboss.org/browse/WFLY-9636 > Project: WildFly > Issue Type: Bug > Components: EJB, IO, Naming > Affects Versions: 11.0.0.Final > Environment: I work with https://developer.jboss.org/people/jaikiran on https://developer.jboss.org/thread/276635 so my Wildfly 11 environment has this fix in it. > Reporter: peter craddock > Assignee: Stuart Douglas > > The code examples and trace logging can be found here https://developer.jboss.org/thread/276840 > I have work round the problem but was asked to raise it for further investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[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)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9643) Getting Internal server error on exception if the rest service content type is "application/xml"

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9643?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-9643: ------------------------------------ Component/s: REST (was: Application Client) Priority: Major (was: Blocker) Assignee: Alessio Soldano (was: Stuart Douglas) > Getting Internal server error on exception if the rest service content type is "application/xml" > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9643 > URL: https://issues.jboss.org/browse/WFLY-9643 > Project: WildFly > Issue Type: Bug > Components: REST > Reporter: Gopal krishna > Assignee: Alessio Soldano > > We are getting Internal server error if any exception is thrown from spring interceptor when rest API header is set as "application/xml". This works if the rest API header is set as "application/json". > we didnt see this issue in jboss 7 and WAS -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[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)

6 years, 3 months

1
0
0 / 0

[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)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2018