October 2013 - jboss-jira - Jboss List Archives

[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.0.CR5 (was: 1.1.2.Final) > 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.0.CR5 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-76) Release Remoting JMX 1.1.2.Final

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/REMJMX-76?page=com.atlassian.jira.plugin.... ] Darran Lofthouse resolved REMJMX-76. ------------------------------------ Resolution: Done > Release Remoting JMX 1.1.2.Final > -------------------------------- > > Key: REMJMX-76 > URL: https://issues.jboss.org/browse/REMJMX-76 > Project: Remoting JMX > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.2.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2079) Update security realm <authorization /> to support multiple definitions.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-2079?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-2079: ----------------------------------- Fix Version/s: 9.0.0.CR1 (was: 8.0.0.CR1) > Update security realm <authorization /> to support multiple definitions. > ------------------------------------------------------------------------ > > Key: WFLY-2079 > URL: https://issues.jboss.org/browse/WFLY-2079 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management, Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.CR1 > > > Complex configuration could result in different methods being used for authentication, as a result we may also need to support multiple sources for loading group membership information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1721) AUTH and ENCRYPT protocols configured with plain text passwords

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1721?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1721: --------------------------- Fix Version/s: 3.5 > AUTH and ENCRYPT protocols configured with plain text passwords > --------------------------------------------------------------- > > Key: JGRP-1721 > URL: https://issues.jboss.org/browse/JGRP-1721 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Fix For: 3.5 > > > The following parameters of AUTH protocol are stored as plain text: > * keystore_password > The following parameters of ENCRYPT protocol are stored as plain text: > * store_password > * key_password > Example: > {code} > <ENCRYPT key_store_name="defaultStore.keystore" store_password="changeit" alias="myKey"/> > {code} > Requirements for storing passwords: https://docspace.corp.redhat.com/docs/DOC-131628 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-1722: --------------------------- Fix Version/s: 3.5 > Improve performance of ENCRYPT protocol > --------------------------------------- > > Key: JGRP-1722 > URL: https://issues.jboss.org/browse/JGRP-1722 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 3.4 > Reporter: Martin Gencur > Assignee: Bela Ban > Fix For: 3.5 > > > A stress tests with the following setup showed that performance (reads and writes/sec) is halved when ENCRYPT protocol is enabled: > Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on keys, 20 % writes, 80 % reads. > It would be great if we could improve the performance of ENCRYPT protocol. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2338) When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2338?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2338: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug 1020881|https://bugzilla.redhat.com/show_bug.cgi?id=1020881] I'm blocked by this issue in my testing I'm adding TestBlocker keyword. As server stucks for reload and shutdown in most of the cases this issue blocks my testing of the JDBC object store. > When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-2338 > URL: https://issues.jboss.org/browse/WFLY-2338 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Stefano Maestri > Attachments: 0001-patching-servicename-for-ds-dependency.patch > > > It should be the cause of https://bugzilla.redhat.com/show_bug.cgi?id=1020881 > It has the effects described in the BZ, i.e. can cause warnings or can entirely block the application server from stopping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2354) Webservice13 tck failures introduced by ejb3 and security change

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2354?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2354: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> made a comment on [bug 1021543|https://bugzilla.redhat.com/show_bug.cgi?id=1021543] PR : https://github.com/jbossas/jboss-eap/pull/583 > Webservice13 tck failures introduced by ejb3 and security change > ----------------------------------------------------------------- > > Key: WFLY-2354 > URL: https://issues.jboss.org/browse/WFLY-2354 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > There 2 tck regression failures under webserivice13 directory in EAP 6.2.0.ER6. > IT turns out the change[2] introduced this two failures: > [1]https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/TCK6-EA... > [2][2]https://github.com/jbossas/jboss-eap/commit/72d5cd3f96540519a9747579... > EAP 6.2.0.ER6 sever error message: > ------------------------------------------------------------------------------ > 18:32:00,338 ERROR [org.jboss.as.ejb3.invocation] (http-myserver.com/127.0.0.1:8080-1) JBAS014134: EJB Invocation failed on component WSEjbSingletonTest for method public java.lang.String com.sun.ts.tests.webservices13.ejb.annotations.WSEjbSingletonTest.HelloBean.bye(java.lang.String): javax.ejb.EJBException: java.lang.IllegalStateException: JBAS014485: EJB WSEjbSingletonTest is enabled for security but doesn't have a security domain set > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:189) [jboss-as-ejb3-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2354) Webservice13 tck failures introduced by ejb3 and security change

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2354?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2354: ----------------------------------------------- Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> changed the Status of [bug 1021543|https://bugzilla.redhat.com/show_bug.cgi?id=1021543] from NEW to ASSIGNED > Webservice13 tck failures introduced by ejb3 and security change > ----------------------------------------------------------------- > > Key: WFLY-2354 > URL: https://issues.jboss.org/browse/WFLY-2354 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > There 2 tck regression failures under webserivice13 directory in EAP 6.2.0.ER6. > IT turns out the change[2] introduced this two failures: > [1]https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/TCK6-EA... > [2][2]https://github.com/jbossas/jboss-eap/commit/72d5cd3f96540519a9747579... > EAP 6.2.0.ER6 sever error message: > ------------------------------------------------------------------------------ > 18:32:00,338 ERROR [org.jboss.as.ejb3.invocation] (http-myserver.com/127.0.0.1:8080-1) JBAS014134: EJB Invocation failed on component WSEjbSingletonTest for method public java.lang.String com.sun.ts.tests.webservices13.ejb.annotations.WSEjbSingletonTest.HelloBean.bye(java.lang.String): javax.ejb.EJBException: java.lang.IllegalStateException: JBAS014485: EJB WSEjbSingletonTest is enabled for security but doesn't have a security domain set > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:189) [jboss-as-ejb3-7.3.0.Final-redhat-SNAPSHOT.jar:7.3.0.Final-redhat-SNAPSHOT] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-76) Release Remoting JMX 1.1.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-76: -------------------------------------- Summary: Release Remoting JMX 1.1.2.Final Key: REMJMX-76 URL: https://issues.jboss.org/browse/REMJMX-76 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.2.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2338) When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2338?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2338: ----------------------------------------------- Ondrej Chaloupka <ochaloup(a)redhat.com> made a comment on [bug 1020881|https://bugzilla.redhat.com/show_bug.cgi?id=1020881] I found out that this happens not only with reload but as well when server is stopping. Which means that when the JDBC object store is configured and you stopped the server the server stucks and it has to be killed by 'kill -9' or similar way. This problem seems to me quite urgent. I can see that the issue is already solved for Wildfly then please check the process of the stopping the server as well. > When using a JDBC object store, the RecoveryManager service stop can occur after the datasource is already stopped > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-2338 > URL: https://issues.jboss.org/browse/WFLY-2338 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Stefano Maestri > Attachments: 0001-patching-servicename-for-ds-dependency.patch > > > It should be the cause of https://bugzilla.redhat.com/show_bug.cgi?id=1020881 > It has the effects described in the BZ, i.e. can cause warnings or can entirely block the application server from stopping -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2013