September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3888) Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created WFLY-3888: -------------------------------------- Summary: Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly Key: WFLY-3888 URL: https://issues.jboss.org/browse/WFLY-3888 Project: WildFly Issue Type: Enhancement Reporter: Wolf-Dieter Fink Assignee: Jason Greene All ERROR and WARN messages should show the full timer information, specially the customer timer-information. This will make it more easy to identify the exact timer in case of an EJB object has multiple timer instances active. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-121) Upgrade to Remoting JMX 2.0.1.CR1

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-121: --------------------------------------- Summary: Upgrade to Remoting JMX 2.0.1.CR1 Key: WFCORE-121 URL: https://issues.jboss.org/browse/WFCORE-121 Project: WildFly Core Issue Type: Component Upgrade Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.0.Alpha9 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-4) Allow for long method calls within the protocol.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-4?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-4: ---------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Allow for long method calls within the protocol. > ------------------------------------------------ > > Key: REMJMX-4 > URL: https://issues.jboss.org/browse/REMJMX-4 > Project: Remoting JMX > Issue Type: Task > Components: Connection, RPC > Reporter: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > Methods such as invoke could take a long time to return depending on what the MBean is actually doing. > This task is to build support for this into the protocol, 2 initial ideas are: - > 1 - Allow the client to 'ping' the server after a request has timed out and ask the server is this request still running, server side the we can track the correlation IDs of current requests an check it is still in-progress. > 2 - The server could periodically send a message to the client to say the message is still in progress, the client could cache these and on timing out check if one has been received recently and wait again if one has. > 3 - Any other suggestions? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-19) Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-19?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-19: ----------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Optimise server side notifications to eliminate serialization issue re different instances of same filter and hand back server side. > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: REMJMX-19 > URL: https://issues.jboss.org/browse/REMJMX-19 > Project: Remoting JMX > Issue Type: Task > Components: Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > The NotificationMBeanSupport class compares these items by identity so when different copies are received server side it breaks these comparisons. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-10) Internationalisation of log messages

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-10?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-10: ----------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Internationalisation of log messages > ------------------------------------ > > Key: REMJMX-10 > URL: https://issues.jboss.org/browse/REMJMX-10 > Project: Remoting JMX > Issue Type: Task > Reporter: Darran Lofthouse > Fix For: 2.0.1.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-8) Connection state notification suppport

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-8?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated REMJMX-8: ---------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Connection state notification suppport > -------------------------------------- > > Key: REMJMX-8 > URL: https://issues.jboss.org/browse/REMJMX-8 > Project: Remoting JMX > Issue Type: Task > Components: Connection, Notifications > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-81) Add http-remoting-jmx testing

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-81?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-81: ----------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Add http-remoting-jmx testing > ----------------------------- > > Key: REMJMX-81 > URL: https://issues.jboss.org/browse/REMJMX-81 > Project: Remoting JMX > Issue Type: Task > Components: Tests > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > Connecting over HTTP is now the default mode for WildFly yet we have no testing of this within the Remoting JMX project itself. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-85) Add support for remote:// remote+http:// and remote+https:// URI schemes

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-85?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated REMJMX-85: ----------------------------------- Fix Version/s: 2.0.1.CR2 (was: 2.0.1.CR1) > Add support for remote:// remote+http:// and remote+https:// URI schemes > ------------------------------------------------------------------------ > > Key: REMJMX-85 > URL: https://issues.jboss.org/browse/REMJMX-85 > Project: Remoting JMX > Issue Type: Enhancement > Components: Connection > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR2 > > > Remaining schemes should be deprecated. > Note: Drop the JMX from the scheme as it is redundant. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (REMJMX-89) Release Remoting JMX 2.0.1.CR1

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-89?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved REMJMX-89. ------------------------------------ Resolution: Done > Release Remoting JMX 2.0.1.CR1 > ------------------------------ > > Key: REMJMX-89 > URL: https://issues.jboss.org/browse/REMJMX-89 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 2.0.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-1885) bind_addr of 0.0.0.0 should throw an exception

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1885?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-1885. ---------------------------- Resolution: Done > bind_addr of 0.0.0.0 should throw an exception > ---------------------------------------------- > > Key: JGRP-1885 > URL: https://issues.jboss.org/browse/JGRP-1885 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5.1, 3.6 > > > Setting {{bind_addr}} to {{0.0.0.0}} breaks communication as there's no way to route a message to {{0.0.0.0:46677}}, beyond the local host. > SOLUTION: throw an exception when bind_addr is set to the wildcard address. This can be done in the code which checks {{@LocalAddress}}. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

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 September 2014