October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5132) Connection timeout to local port 9999 with clustered AS 7.1.1.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-5132?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-5132: ---------------------------------------------- Pavel Jelinek <pjelinek(a)redhat.com> changed the Status of [bug 900988|https://bugzilla.redhat.com/show_bug.cgi?id=900988] from ON_QA to ASSIGNED > Connection timeout to local port 9999 with clustered AS 7.1.1.Final > ------------------------------------------------------------------- > > Key: AS7-5132 > URL: https://issues.jboss.org/browse/AS7-5132 > Project: Application Server 7 > Issue Type: Bug > Components: Domain Management > Affects Versions: 7.1.1.Final > Environment: Fedora 17 on Amazon EC2 > Reporter: Jack Lund > Assignee: Emanuel Muckenhuber > Labels: as7, cluster, domain > Fix For: 7.1.3.Final (EAP), EAP 6.1.0.Alpha (7.2.0.Final) > > > A clustered configuration of two AS 7 instances has an issue with the connection to port 9999 timing out when starting up. The instances are configured as per https://docs.jboss.org/author/display/AS71/AS7+Cluster+Howto. On startup, we get the following error randomly for one or more of the server instances: > {quote} > [Server:server-two] 16:36:03,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.net.ConnectException: JBAS012144: Could not connect to remote://10.108.25.156:9999. The connection timed out > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:161) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > [Server:server-two] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > [Server:server-two] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > [Server:server-two] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > [Server:server-two] Caused by: java.net.ConnectException: JBAS012144: Could not connect to remote://nephele-beta-jboss1:9999. The connection timed out > [Server:server-two] at org.jboss.as.protocol.ProtocolChannelClient.connectSync(ProtocolChannelClient.java:155) [jboss-as-protocol-7.1.1.Final.jar:7.1.1.Final] > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.openChannel(HostControllerServerConnection.java:158) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerServerConnection.connect(HostControllerServerConnection.java:86) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > [Server:server-two] at org.jboss.as.server.mgmt.domain.HostControllerServerClient.start(HostControllerServerClient.java:135) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > [Server:server-two] ... 5 more > {quote} > We usually have to restart the master server instance 10-15 times before all server instances start up without this error, which suggests a race condition between the listening and connecting sockets. Note that this is running on the equivalent of a single-core, fairly slow machine currently, which may be exacerbating the effects. -- 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-2135) Change distributed config on address settings to Page instead of Block

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2135?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2135: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 1011074|https://bugzilla.redhat.com/show_bug.cgi?id=1011074] There is PAGE policy in all standalone and domain files/profiles. Verified in EAP 6.2.0.ER4. > Change distributed config on address settings to Page instead of Block > ---------------------------------------------------------------------- > > Key: WFLY-2135 > URL: https://issues.jboss.org/browse/WFLY-2135 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.0.0.Alpha4 > Reporter: Clebert Suconic > Assignee: Clebert Suconic > Fix For: 8.0.0.Beta1 > > > We have had so many cases of questions about why the producing is blocked when not consuming. > Users are expecting Page by default, so we should change the default. -- 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-2135) Change distributed config on address settings to Page instead of Block

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2135?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2135: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 1011074|https://bugzilla.redhat.com/show_bug.cgi?id=1011074] from ON_QA to VERIFIED > Change distributed config on address settings to Page instead of Block > ---------------------------------------------------------------------- > > Key: WFLY-2135 > URL: https://issues.jboss.org/browse/WFLY-2135 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.0.0.Alpha4 > Reporter: Clebert Suconic > Assignee: Clebert Suconic > Fix For: 8.0.0.Beta1 > > > We have had so many cases of questions about why the producing is blocked when not consuming. > Users are expecting Page by default, so we should change the default. -- 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-2071) Messaging queue attributes must be read-only

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2071?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2071: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> changed the Status of [bug 1004789|https://bugzilla.redhat.com/show_bug.cgi?id=1004789] from ON_QA to VERIFIED > Messaging queue attributes must be read-only > -------------------------------------------- > > Key: WFLY-2071 > URL: https://issues.jboss.org/browse/WFLY-2071 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Beta1 > > > Currently, the messaging subsystem's queue and jms-queue resources defines attributes that are writable (eg filter and durable attribute). > This is not correct, once a queue is created with these attributes, they can not be changed for the lifetime of a queue (a durable queue can not become non-durable). -- 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-2071) Messaging queue attributes must be read-only

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2071?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2071: ----------------------------------------------- Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 1004789|https://bugzilla.redhat.com/show_bug.cgi?id=1004789] Verified in EAP 6.2.0.ER4. Attribute selector on queue is read-only now. Thanks Jeff for the change. > Messaging queue attributes must be read-only > -------------------------------------------- > > Key: WFLY-2071 > URL: https://issues.jboss.org/browse/WFLY-2071 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.Beta1 > > > Currently, the messaging subsystem's queue and jms-queue resources defines attributes that are writable (eg filter and durable attribute). > This is not correct, once a queue is created with these attributes, they can not be changed for the lifetime of a queue (a durable queue can not become non-durable). -- 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] (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> 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. > 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

12 years, 9 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> 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

12 years, 9 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

12 years, 9 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

12 years, 9 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

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