October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2069) can not switch from connector to discovery-group-name for JMS (pooled-) connection factories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2069: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 1001612|https://bugzilla.redhat.com/show_bug.cgi?id=1001612] from ON_QA to VERIFIED > can not switch from connector to discovery-group-name for JMS (pooled-) connection factories > --------------------------------------------------------------------------------------------- > > Key: WFLY-2069 > URL: https://issues.jboss.org/browse/WFLY-2069 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Beta1 > > > connectors and discovery-group-name are alternative attributes of JMS (pooled) connection factories. > If a resource defines one of this attribute, it must be able to "switch" to the other by running a batch command to: > 1. undefine the attribute > 2. write the value of the other attribute > This currently does not work: > {noformat} > [standalone@localhost:9999 /] batch > [standalone@localhost:9999 / #] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) > #1 /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) > [standalone@localhost:9999 / #] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1) > #2 /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1) > [standalone@localhost:9999 / #] run-batch > {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS011630: Alternative attribute of (connector) is already defined."}} > {noformat} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2069) can not switch from connector to discovery-group-name for JMS (pooled-) connection factories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2069?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2069: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 1001612|https://bugzilla.redhat.com/show_bug.cgi?id=1001612] BZ was verified in EAP 6.2.0.ER4 by following batch: batch /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1) run-batch In this way connector for connection factory can be undefined and set discovery-group. Or discovery-group undefined and changed set connector. This must be done in a batch or commands will fail as it is reported in description. > can not switch from connector to discovery-group-name for JMS (pooled-) connection factories > --------------------------------------------------------------------------------------------- > > Key: WFLY-2069 > URL: https://issues.jboss.org/browse/WFLY-2069 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Beta1 > > > connectors and discovery-group-name are alternative attributes of JMS (pooled) connection factories. > If a resource defines one of this attribute, it must be able to "switch" to the other by running a batch command to: > 1. undefine the attribute > 2. write the value of the other attribute > This currently does not work: > {noformat} > [standalone@localhost:9999 /] batch > [standalone@localhost:9999 / #] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) > #1 /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:undefine-attribute(name=connector) > [standalone@localhost:9999 / #] /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1) > #2 /subsystem=messaging/hornetq-server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=discovery-group-name,value=dg-group1) > [standalone@localhost:9999 / #] run-batch > {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS011630: Alternative attribute of (connector) is already defined."}} > {noformat} -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-5107) define connectors as alternatives to discovery-group

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5107?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5107: ---------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 1001612|https://bugzilla.redhat.com/show_bug.cgi?id=1001612] from ON_QA to VERIFIED > define connectors as alternatives to discovery-group > ---------------------------------------------------- > > Key: AS7-5107 > URL: https://issues.jboss.org/browse/AS7-5107 > Project: Application Server 7 > Issue Type: Bug > Components: JMS > Affects Versions: 7.1.2.Final (EAP) > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: EAP 6.1.0.Alpha (7.2.0.Final) > > > cluster-connections, bridges and JMS connection factories must define either connectors or discovery-group but not both. > The choice is handled in the messaging susbsystem parser but it's not enforced by the attributes' definitions. Admin operations are not shielded against a misconfiguration by changing directly these attributes -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-924) Reduce the log level of optional components failing to start log message (JBAS011006 message id)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-924?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-924: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> made a comment on [bug 900711|https://bugzilla.redhat.com/show_bug.cgi?id=900711] Verified in EAP 6.2.0.ER4. > Reduce the log level of optional components failing to start log message (JBAS011006 message id) > ------------------------------------------------------------------------------------------------ > > Key: WFLY-924 > URL: https://issues.jboss.org/browse/WFLY-924 > Project: WildFly > Issue Type: Enhancement > Components: EE > Affects Versions: 8.0.0.Alpha2 > Environment: JBoss EAP 6.0 GA, web services subsystem removed, war deployed containing Metro or CXF web services implementation > Reporter: Brad Maxwell > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha3 > > > It tries to create this class if CXF is packaged in the war: org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > And this stack is logged as a warning: > 11:08:40,879 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.test.war:main" from Service Module Loader > 11:08:40,905 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > If Metro is packaged in the war, it tries to load com.sun.xml.ws.transport.http.servlet.WSAsyncListener and logs a warning with this stack: > 16:48:57,302 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-924) Reduce the log level of optional components failing to start log message (JBAS011006 message id)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-924?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-924: ---------------------------------------------- Jan Martiska <jmartisk(a)redhat.com> changed the Status of [bug 900711|https://bugzilla.redhat.com/show_bug.cgi?id=900711] from ON_QA to VERIFIED > Reduce the log level of optional components failing to start log message (JBAS011006 message id) > ------------------------------------------------------------------------------------------------ > > Key: WFLY-924 > URL: https://issues.jboss.org/browse/WFLY-924 > Project: WildFly > Issue Type: Enhancement > Components: EE > Affects Versions: 8.0.0.Alpha2 > Environment: JBoss EAP 6.0 GA, web services subsystem removed, war deployed containing Metro or CXF web services implementation > Reporter: Brad Maxwell > Assignee: jaikiran pai > Fix For: 8.0.0.Alpha3 > > > It tries to create this class if CXF is packaged in the war: org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > And this stack is logged as a warning: > 11:08:40,879 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.test.war:main" from Service Module Loader > 11:08:40,905 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] > If Metro is packaged in the war, it tries to load com.sun.xml.ws.transport.http.servlet.WSAsyncListener and logs a warning with this stack: > 16:48:57,302 WARN [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class com.sun.xml.ws.transport.http.servlet.WSAsyncListener$1 > at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:83) [jboss-as-ee-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2226) Web Console adds two slashes in the address

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-2226?page=com.atlassian.jira.plugin.... ] Heiko Braun reassigned WFLY-2226: --------------------------------- Assignee: Harald Pehl (was: Heiko Braun) the redirect from [1] seems to be wrong. can you look into it Harald? [1] http://localhost:9990 > Web Console adds two slashes in the address > ------------------------------------------- > > Key: WFLY-2226 > URL: https://issues.jboss.org/browse/WFLY-2226 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.0.0.Beta1 > Reporter: Jorge Solorzano > Assignee: Harald Pehl > Priority: Trivial > > The web console adds two slashes to the address after the port > http://localhost:9990//console/App.html -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1070) Memory leak if hashCode of Transaction isn't stable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1070?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1070: ------------------------------------------------ Vladimir Rastseluev <vrastsel(a)redhat.com> changed the Status of [bug 1007608|https://bugzilla.redhat.com/show_bug.cgi?id=1007608] from ON_QA to VERIFIED > Memory leak if hashCode of Transaction isn't stable > --------------------------------------------------- > > Key: JBJCA-1070 > URL: https://issues.jboss.org/browse/JBJCA-1070 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.19.Final, 1.1.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.20.Final, 1.1.1.Final > > > Happens in TransactionSynchronizer -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1070) Memory leak if hashCode of Transaction isn't stable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1070?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1070: ------------------------------------------------ Vladimir Rastseluev <vrastsel(a)redhat.com> made a comment on [bug 1007608|https://bugzilla.redhat.com/show_bug.cgi?id=1007608] Verified on EAP 6.2.0 ER4 > Memory leak if hashCode of Transaction isn't stable > --------------------------------------------------- > > Key: JBJCA-1070 > URL: https://issues.jboss.org/browse/JBJCA-1070 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.19.Final, 1.1.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.20.Final, 1.1.1.Final > > > Happens in TransactionSynchronizer -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1083) PreparedStatement cache constraints not maintained

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1083?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1083: ------------------------------------------------ Vladimir Rastseluev <vrastsel(a)redhat.com> made a comment on [bug 1008763|https://bugzilla.redhat.com/show_bug.cgi?id=1008763] Verified on EAP 6.2.0 ER4 > PreparedStatement cache constraints not maintained > -------------------------------------------------- > > Key: JBJCA-1083 > URL: https://issues.jboss.org/browse/JBJCA-1083 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.20.Final, 1.1.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.21.Final, 1.1.1.Final > > > The PreparedStatement cache doesn't maintain its constraint on the number of cached entries -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1083) PreparedStatement cache constraints not maintained

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1083?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1083: ------------------------------------------------ Vladimir Rastseluev <vrastsel(a)redhat.com> changed the Status of [bug 1008763|https://bugzilla.redhat.com/show_bug.cgi?id=1008763] from ON_QA to VERIFIED > PreparedStatement cache constraints not maintained > -------------------------------------------------- > > Key: JBJCA-1083 > URL: https://issues.jboss.org/browse/JBJCA-1083 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Affects Versions: 1.0.20.Final, 1.1.0.Final > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.21.Final, 1.1.1.Final > > > The PreparedStatement cache doesn't maintain its constraint on the number of cached entries -- 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, 3 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 October 2013