May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4095) mod_cluster AdvertiseListenerImpl does not take multicast-port setting into account

by Michal Babacek (JIRA)

Michal Babacek created AS7-4095: ----------------------------------- Summary: mod_cluster AdvertiseListenerImpl does not take multicast-port setting into account Key: AS7-4095 URL: https://issues.jboss.org/browse/AS7-4095 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Michal Babacek Assignee: Michal Babacek The undermentioned configuration: {code:lang=xml} +++ <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> +++ <socket-binding name="modcluster" port="0" multicast-address="224.0.1.105" multicast-port="6666"/> +++ </socket-binding-group> +++ {code} does not affect the actual port the mod_cluster is looking for advertisement: {code} 05:11:22,295 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364 {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] (AS7-4098) mod_cluster subsystem does not take proxy-list attribute into account

by Michal Babacek (JIRA)

Michal Babacek created AS7-4098: ----------------------------------- Summary: mod_cluster subsystem does not take proxy-list attribute into account Key: AS7-4098 URL: https://issues.jboss.org/browse/AS7-4098 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Michal Babacek Assignee: Paul Ferraro With the AS7 current master *{color:green}89daec9{color}*, the following configuration: {code:lang=xml} <subsystem xmlns="urn:jboss:domain:modcluster:1.0"> <mod-cluster-config proxy-list="perf05:8888"> <ssl password="tomcat" certificate-key-file="/tmp/Client/client-keystore.jsk" ca-certificate-file="/tmp/Client/client-keystore.jsk"/> </mod-cluster-config> </subsystem> {code} leads to the default, "advertising enabled" behaviour (e.g. might be related to [AS7-4095]): {noformat} [JBoss] 07:10:12,426 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final [JBoss] 07:10:12,473 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-4) Listening to proxy advertisements on 224.0.1.105:23364 {noformat}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] (JGRP-1462) TCPConnectionMap: move socket establishment out of common path

by Bela Ban (JIRA)

Bela Ban created JGRP-1462: ------------------------------ Summary: TCPConnectionMap: move socket establishment out of common path Key: JGRP-1462 URL: https://issues.jboss.org/browse/JGRP-1462 Project: JGroups Issue Type: Enhancement Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0.10, 3.1 TCPConnectionMap$Mapper.getConnection() acquires a lock and returns the an existing connection, or creates a new one if needed. The problem is that - while we try to establish a new connection - *existing* connections will have to wait before being returned until connection establishment has completed (or failed). For instance, if we have valid connections to members B, C and D, and try to establish a connection to (failed) member E, all threads will try to send data to A, B and C will be blocked until they can acquire the lock ! SOLUTION: move socket creation under a different lock. {Suggested by S. Simeonoff) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-4781) Reconnect to remote JMS / TopicConnection after reoboot As7

by Sueleyman Vurucu (JIRA)

Sueleyman Vurucu created AS7-4781: ------------------------------------- Summary: Reconnect to remote JMS / TopicConnection after reoboot As7 Key: AS7-4781 URL: https://issues.jboss.org/browse/AS7-4781 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.1.Final Reporter: Sueleyman Vurucu Fix For: 7.1.3.Final (EAP) After a server remote jms won't reconnect. Remote EJB works well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (AS7-4783) Domain tests are dependent on the value of the JBOSS_HOME environment var

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4783: ----------------------------------- Summary: Domain tests are dependent on the value of the JBOSS_HOME environment var Key: AS7-4783 URL: https://issues.jboss.org/browse/AS7-4783 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas Assignee: Stuart Douglas If this is incorrectly set the domain tests will fail. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3504) Ruleflow groups are deactivating before firing the last activation in the group

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3504: -------------------------------------- Summary: Ruleflow groups are deactivating before firing the last activation in the group Key: JBRULES-3504 URL: https://issues.jboss.org/browse/JBRULES-3504 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.4.0.CR1, 5.3.1.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.4.0.Final, 5.5.0.Beta1 The fix to JBRULES-3374 introduced a regression where the ruleflow group was being deactivated before firing the last activation in the group. This is wrong, among other things, because that activation can execute working memory actions that might activate other rules in the same group, in which case the ruleflow group should not be deactivated in the first place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
6
0 / 0

[JBoss JIRA] (JBRULES-3503) A firing doing a retraction of the currently firing activation itself causes that activation to be remove twice and then a NPE

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3503: ------------------------------------ Summary: A firing doing a retraction of the currently firing activation itself causes that activation to be remove twice and then a NPE Key: JBRULES-3503 URL: https://issues.jboss.org/browse/JBRULES-3503 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco This bug is reproducible by running org.drools.examples.troubleticket.TroubleTicketExample -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] (AS7-2764) Show configured / effective bind address of a server

by Wolf-Dieter Fink (Created) (JIRA)

Show configured / effective bind address of a server ---------------------------------------------------- Key: AS7-2764 URL: https://issues.jboss.org/browse/AS7-2764 Project: Application Server 7 Issue Type: Feature Request Components: Console Affects Versions: 7.1.0.Beta1, 7.1.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Heiko Braun The bind address of a server can be dedicated configured for each server of a host controller. This should be reflected by the management console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
2
0 / 0

[JBoss JIRA] (AS7-4779) Update the add-user.sh images to reflect the latest guided workflow

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-4779: ------------------------------------- Summary: Update the add-user.sh images to reflect the latest guided workflow Key: AS7-4779 URL: https://issues.jboss.org/browse/AS7-4779 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.2.0.Alpha1 No point updating 7.1.x as EAP users don't get an image to guide them. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] (AS7-4778) Using directory-grouping in host.xml servers element fails

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-4778: ------------------------------------- Summary: Using directory-grouping in host.xml servers element fails Key: AS7-4778 URL: https://issues.jboss.org/browse/AS7-4778 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Attempting to start a server when <servers directory-grouping="by-type"> is set fails. [Host Controller] 10:30:20,760 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010907: Failed to start server (server-two): java.lang.IllegalArgumentException: No enum const class org.jboss.as.host.controller.DirectoryGrouping.by-type [Host Controller] at java.lang.Enum.valueOf(Enum.java:196) [classes.jar:1.6.0_31] [Host Controller] at org.jboss.as.host.controller.DirectoryGrouping.valueOf(DirectoryGrouping.java:33) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.DirectoryGrouping.fromModel(DirectoryGrouping.java:80) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.ModelCombiner.getServerLaunchCommand(ModelCombiner.java:262) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.ModelCombiner.createConfiguration(ModelCombiner.java:178) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.createManagedServer(ServerInventoryImpl.java:476) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:163) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:150) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:521) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.operations.StartServersHandler.cleanStartServers(StartServersHandler.java:114) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.operations.StartServersHandler.access$300(StartServersHandler.java:50) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.operations.StartServersHandler$1.execute(StartServersHandler.java:94) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.executeDirect(PrepareStepHandler.java:122) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:74) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.startServers(DomainModelControllerService.java:443) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:403) [jboss-as-host-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] [Host Controller] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31] The cause is DirectoryGrouping.fromModel() is using an insufficiently sophisticated approach that would only work with the values BY_TYPE or BY_SERVER. Those values are not what will get stored in the model. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 May 2012