April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5403) CLONE - Adding modcluster via the CLI fails.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5403?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5403: ---------------------------------------------- Jean-frederic Clere <jclere(a)redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801] According Comment #19 and Comment #20 that is not a blocker. > CLONE - Adding modcluster via the CLI fails. > -------------------------------------------- > > Key: AS7-5403 > URL: https://issues.jboss.org/browse/AS7-5403 > Project: Application Server 7 > Issue Type: Bug > Components: CLI, Clustering > Affects Versions: 7.1.2.Final (EAP) > Reporter: Tom Fonteyne > Assignee: Radoslav Husar > Fix For: 8.0.0.Alpha1 > > > Adding modcluster via the CLI fails. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBMESSAGING-1944) When a message is rejected by a full destination the session.close() method has a 10 seconds delay before returning.

by Tom Ross (JIRA)

[ https://issues.jboss.org/browse/JBMESSAGING-1944?page=com.atlassian.jira.... ] Tom Ross resolved JBMESSAGING-1944. ----------------------------------- Fix Version/s: 1.4.8.SP10 (was: 1.4.8.SP9) Resolution: Done > When a message is rejected by a full destination the session.close() method has a 10 seconds delay before returning. > -------------------------------------------------------------------------------------------------------------------- > > Key: JBMESSAGING-1944 > URL: https://issues.jboss.org/browse/JBMESSAGING-1944 > Project: JBoss Messaging > Issue Type: Bug > Components: Messaging Core > Environment: JBoss EAP 5.x > Reporter: Tom Ross > Assignee: Tom Ross > Fix For: 1.4.8.SP10 > > > The session.close() method waits on the send() method to notify it that all message have been sent. This arrangement breaks when a none persistent message gets rejected by a full destination. In that case the close() method waits for 10 seconds before returning. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6972) JBAS014884: No operation named 'composite' exists at address

by Van Halbert (JIRA)

Van Halbert created AS7-6972: -------------------------------- Summary: JBAS014884: No operation named 'composite' exists at address Key: AS7-6972 URL: https://issues.jboss.org/browse/AS7-6972 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) Environment: RHEL 6, JDK 1.7 Reporter: Van Halbert Assignee: Brian Stansberry I'm using EAP 6.1 ER5, and trying to execute the following using CLI: /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default) /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}]) but I get the message: … "failure-description" => "JBAS014884: No operation named 'composite' exists at address [ … (see forum for full discussion) -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-717) Get JBoss Negotiation into Maven Central

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-717?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-717: -------------------------------------- Fix Version/s: Negotiation_2_2_4 (was: Negotiation_2_2_3) > Get JBoss Negotiation into Maven Central > ---------------------------------------- > > Key: SECURITY-717 > URL: https://issues.jboss.org/browse/SECURITY-717 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_4 > > > This will allow the JBoss Negotiation Toolkit to be removed from the project and instead moved to the quick starts making it much easier for end users to deploy and test. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-677) Remove JBoss Negotiation Toolkit

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-677?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-677: -------------------------------------- Fix Version/s: Negotiation_2_2_4 (was: Negotiation_2_2_3) > Remove JBoss Negotiation Toolkit > -------------------------------- > > Key: SECURITY-677 > URL: https://issues.jboss.org/browse/SECURITY-677 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_4 > > > JBoss Negotiation Toolkit is being moved to the quickstarts, so it does not need to be maintained in two different locations delete it from the Negotiation source tree. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-736) Tag and release JBoss Negotiation 2.2.3

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/SECURITY-736?page=com.atlassian.jira.plug... ] Darran Lofthouse resolved SECURITY-736. --------------------------------------- Resolution: Done > Tag and release JBoss Negotiation 2.2.3 > --------------------------------------- > > Key: SECURITY-736 > URL: https://issues.jboss.org/browse/SECURITY-736 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6770) Recovery manager service may not always use the correct orphan filters

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6770?page=com.atlassian.jira.plugin.s... ] jaikiran pai reopened AS7-6770: ------------------------------- Reopening to link the PR on github > Recovery manager service may not always use the correct orphan filters > ---------------------------------------------------------------------- > > Key: AS7-6770 > URL: https://issues.jboss.org/browse/AS7-6770 > Project: Application Server 7 > Issue Type: Bug > Components: Transactions > Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final) > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha1 > > > I've been looking into certain transaction recovery use cases (with EJB remote beans involved) and while investigating the issues, I noticed that the orphan filters being set in the JTAEnvironmentBean might not be available to the Recovery manager service. That's because the MSC service which sets up the transaction recovery manager service runs before the JTAEnvironmentBean is setup with the orphan filters, which actually happens in a separate MSC service (Arjuna tx manager service) which starts *after* the recovery manager MSC service. > (Sorry, don't have the code in front of me, else would have added the exact class names - will do so later). -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6971) Upgrade to JBoss Negotiation 2.2.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6971?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6971: ---------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 955555|https://bugzilla.redhat.com/show_bug.cgi?id=955555] from NEW to ASSIGNED > Upgrade to JBoss Negotiation 2.2.3 > ---------------------------------- > > Key: AS7-6971 > URL: https://issues.jboss.org/browse/AS7-6971 > Project: Application Server 7 > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-6971) Upgrade to JBoss Negotiation 2.2.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6971?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration updated AS7-6971: ----------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=955555 > Upgrade to JBoss Negotiation 2.2.3 > ---------------------------------- > > Key: AS7-6971 > URL: https://issues.jboss.org/browse/AS7-6971 > Project: Application Server 7 > Issue Type: Task > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.Alpha1 > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-736) Tag and release JBoss Negotiation 2.2.3

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-736?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-736: -------------------------------------------------- Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 955555|https://bugzilla.redhat.com/show_bug.cgi?id=955555] from NEW to ASSIGNED > Tag and release JBoss Negotiation 2.2.3 > --------------------------------------- > > Key: SECURITY-736 > URL: https://issues.jboss.org/browse/SECURITY-736 > Project: PicketBox > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Negotiation > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: Negotiation_2_2_3 > > -- 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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2013