March 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3193?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3193: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1082617 > upgrade Generic JMS RA to 1.0.4.Final > ------------------------------------- > > Key: WFLY-3193 > URL: https://issues.jboss.org/browse/WFLY-3193 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JCA, JMS > Affects Versions: 8.0.0.Final > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.1.Final > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3193) upgrade Generic JMS RA to 1.0.4.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-3193: --------------------------------- Summary: upgrade Generic JMS RA to 1.0.4.Final Key: WFLY-3193 URL: https://issues.jboss.org/browse/WFLY-3193 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: JCA, JMS Affects Versions: 8.0.0.Final Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 8.0.1.Final -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3192) AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3192?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-3192: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=901324 > AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class > ------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-3192 > URL: https://issues.jboss.org/browse/WFLY-3192 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EE > Affects Versions: 8.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation is found in the class. > The specification says: > A class must not declare more than one AroundInvoke method. > The JBoss AS allows more such methods and then it chooses one of them which is used as the interceptor. > It becomes even more important to check the interceptor validity now with the new feature introduced by AS7-5897 (server side non-EE interceptors for EE invocations). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3192) AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-3192: --------------------------------------- Summary: AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation are found in the class Key: WFLY-3192 URL: https://issues.jboss.org/browse/WFLY-3192 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: EE Affects Versions: 8.0.0.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet AroundInvokeAnnotationParsingProcessor should fail when more methods with @AroundInvoke annotation is found in the class. The specification says: A class must not declare more than one AroundInvoke method. The JBoss AS allows more such methods and then it chooses one of them which is used as the interceptor. It becomes even more important to check the interceptor validity now with the new feature introduced by AS7-5897 (server side non-EE interceptors for EE invocations). -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3191) Console uses hardcoded hornetq-server name as "default" causes issue while moniroting JMS metrics

by Jay Kumar SenSharma (JIRA)

Jay Kumar SenSharma created WFLY-3191: ----------------------------------------- Summary: Console uses hardcoded hornetq-server name as "default" causes issue while moniroting JMS metrics Key: WFLY-3191 URL: https://issues.jboss.org/browse/WFLY-3191 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: 8.0.1.Final Environment: All Reporter: Jay Kumar SenSharma Assignee: Heiko Braun Looks like the API [1] is using hardcoded hornetQ server name as "default" inside the "QueueMetrics.java" as following: {code} final HelpSystem.AddressCallback addressCallback = new HelpSystem.AddressCallback() { @Override public ModelNode getAddress() { ModelNode address = new ModelNode(); address.get(ModelDescriptionConstants.ADDRESS).set(RuntimeBaseAddress.get()); address.get(ModelDescriptionConstants.ADDRESS).add("subsystem", "messaging"); address.get(ModelDescriptionConstants.ADDRESS).add("hornetq-server", "default"); address.get(ModelDescriptionConstants.ADDRESS).add("jms-queue", "*"); return address; } }; {code} - Above is causing issue if someone alters the "Hornetq-server" name to something else. In that case the Console will not be able to display the QueueMetrics for any JMS Queue or Topic. - See attached Screenshot with the When the HornetQ server name was changed to "testing" {code} <subsystem xmlns="urn:jboss:domain:messaging:2.0"> <hornetq-server name="testing"> . . </hornetq-server> </subsystem> {code} [1] https://github.com/hal/core/blob/master/gui/src/main/java/org/jboss/as/co... -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2303) mod_cluster XSD is missing property and worker-timeout definitions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2303: ----------------------------------------------- Michal Babacek <mbabacek(a)redhat.com> changed the Status of [bug 1020142|https://bugzilla.redhat.com/show_bug.cgi?id=1020142] from ON_QA to VERIFIED > mod_cluster XSD is missing property and worker-timeout definitions > ------------------------------------------------------------------ > > Key: WFLY-2303 > URL: https://issues.jboss.org/browse/WFLY-2303 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 8.0.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > * worker-timeout > * property > are missing. > Also missing in 7.x -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ] Scott Marlow reopened WFLY-2881: -------------------------------- reopening to go with the pull request https://github.com/wildfly/wildfly/pull/6098 against WFLY-2881. > org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout > -------------------------------------------------------------------------------------- > > Key: WFLY-2881 > URL: https://issues.jboss.org/browse/WFLY-2881 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Frank Langelage > Assignee: Eduardo Martins > Fix For: 8.0.1.Final > > Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml > > > Running build with smoke tests on current github sources I get failure in this test case. > HOUR_OF_DAY is not 0 as expected but 1. > I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName. > See attached files for more. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3190) Make it possible to use custom vault with CLI

by Kabir Khan (JIRA)

Kabir Khan created WFLY-3190: -------------------------------- Summary: Make it possible to use custom vault with CLI Key: WFLY-3190 URL: https://issues.jboss.org/browse/WFLY-3190 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: CLI Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 9.0.0.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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-101) JMSService.start is doing blocking I/O

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-101?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-101: ---------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 1082103|https://bugzilla.redhat.com/show_bug.cgi?id=1082103] from NEW to POST > JMSService.start is doing blocking I/O > -------------------------------------- > > Key: WFLY-101 > URL: https://issues.jboss.org/browse/WFLY-101 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Alpha1 > > > flag the start context as asynchronous -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-459) 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out

by Petr Široký (JIRA)

Petr Široký created DROOLS-459: ---------------------------------- Summary: 5.6.x: update version to 5.6.1-SNAPSHOT as 5.6.0.Final is already out Key: DROOLS-459 URL: https://issues.jboss.org/browse/DROOLS-459 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Petr Široký Assignee: Michael Biarnes Kiefer The version in 5.6.x branch is still 5.6.0-SNAPSHOT, even though the 5.6.0.Final has been already released. Please update the version to 5.6.1-SNAPSHOT. Similarly with jBPM, the version should be updated to 5.5.1-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

11 years, 11 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 March 2014