September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBMESSAGING-1936) Injected Resource Destinations Are Stale After MessagingClusterHealthMBean Restarts Messaging.

by Doug Grove (JIRA)

Doug Grove created JBMESSAGING-1936: --------------------------------------- Summary: Injected Resource Destinations Are Stale After MessagingClusterHealthMBean Restarts Messaging. Key: JBMESSAGING-1936 URL: https://issues.jboss.org/browse/JBMESSAGING-1936 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.8.SP5 Reporter: Doug Grove The MessagingClusterHealthMBean stops all JMS destinations and connection factories when it detects error conditions. These are then restarted when conditions allow. Various deployments are provided with connection factories and JMS destinations as Resources. These include message driven beans, WARs and Timer Services. When messaging is restarted, these Resources are declared to be stale. These Resources can not always be looked up and recreated. messaging needs to provide a mechanism for these Resources to reconnect. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-3403) Add TCLFilter/Context-based filter for logging confguration

by Andrei Tuzhilin (JIRA)

Andrei Tuzhilin created AS7-3403: ------------------------------------ Summary: Add TCLFilter/Context-based filter for logging confguration Key: AS7-3403 URL: https://issues.jboss.org/browse/AS7-3403 Project: Application Server 7 Issue Type: Feature Request Affects Versions: 7.1.0.CR1b Reporter: Andrei Tuzhilin JBoss AS7 logging configuration lacks logging separation options (per-deployment log file). Previously TCLFilter was used for that, now this option is gone with no acceptable replacement. -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] (AS7-4876) mod_cluster uses the same password for accessing sslKeyStore and sslTrustStore

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-4876: ----------------------------------- Summary: mod_cluster uses the same password for accessing sslKeyStore and sslTrustStore Key: AS7-4876 URL: https://issues.jboss.org/browse/AS7-4876 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.2.Final (EAP) Reporter: Radoslav Husar Assignee: Jean-Frederic Clere Fix For: 7.1.3.Final (EAP) Problem reported by Duncan Doyle. The passwords shouldn't be forced to be the same, in AS5 they could have been different. -- 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, 9 months

5
5
0 / 0

[JBoss JIRA] (AS7-5656) deployed JMS destinations have incorrect storage flag

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5656: -------------------------------- Summary: deployed JMS destinations have incorrect storage flag Key: AS7-5656 URL: https://issues.jboss.org/browse/AS7-5656 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.2.0.Alpha1 Reporter: Jeff Mesnil Assignee: Jeff Mesnil When the messaging subsystem was refactored to use ResourceDefinition, the JMSQueueDefinition and JMSTopicDefinition erroneously register their attributes with the configuration storage flag in the case they are deployed. When the JMS destinations are deployed, they are not part of the configuration and must be stored in runtime only. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3642) A constraint in the form lowerBuond < value < upperBound should cause a compilation error when

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3642: ------------------------------------ Summary: A constraint in the form lowerBuond < value < upperBound should cause a compilation error when Key: JBRULES-3642 URL: https://issues.jboss.org/browse/JBRULES-3642 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco A constraint in the form lowerBuond < value < upperBound for example like in: Person( 20 < age < 30 ) is not supported and then should raise a compilation error. Even worse it is silently transformed in 20 < 30 and evaluated accordingly. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (JBJCA-902) Unwanted config properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-902?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-902: ---------------------------------- Summary: Unwanted config properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter (was: Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter) Git Pull Request: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135 (was: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135) > Unwanted config properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-902 > URL: https://issues.jboss.org/browse/JBJCA-902 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.12.Final, 1.1.0.Beta2 > Reporter: Simone Gotti > Assignee: Stefano Maestri > Priority: Critical > Fix For: 1.0.13.Final, 1.1.0.Beta3 > > > With the effects of issue AS7-5644 I noticed that the connection definition with missing system properties, instead of failing, was using properties from another connection definition (with a lot of consequent problems) > After a lot of analysis the problem is that the org.jboss.jca.common.api.metadata.ra.Connector's system properties are polluted with the merged values of the user specified connectiondefinitions/adminobjects and these system properties's defaults are inserted in the user defined connectiondefinition/adminobject that don't define them. > I think that the wrong operation is in the start method of org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.java: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(raxml, cmd); > I think that merging should be between IronJacamar -> Connector and not raxml -> Connector: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(ijmd, cmd); > After this change I see that the Connector is clean and no unwanted default are added inside my connectiondefinitions/adminobjects > I'll attach the possible pull request. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-902) Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-902?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-902: ---------------------------------- Fix Version/s: 1.0.13.Final 1.1.0.Beta3 Git Pull Request: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135 (was: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135) > Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-902 > URL: https://issues.jboss.org/browse/JBJCA-902 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.12.Final, 1.1.0.Beta2 > Reporter: Simone Gotti > Assignee: Stefano Maestri > Priority: Critical > Fix For: 1.0.13.Final, 1.1.0.Beta3 > > > With the effects of issue AS7-5644 I noticed that the connection definition with missing system properties, instead of failing, was using properties from another connection definition (with a lot of consequent problems) > After a lot of analysis the problem is that the org.jboss.jca.common.api.metadata.ra.Connector's system properties are polluted with the merged values of the user specified connectiondefinitions/adminobjects and these system properties's defaults are inserted in the user defined connectiondefinition/adminobject that don't define them. > I think that the wrong operation is in the start method of org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.java: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(raxml, cmd); > I think that merging should be between IronJacamar -> Connector and not raxml -> Connector: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(ijmd, cmd); > After this change I see that the Connector is clean and no unwanted default are added inside my connectiondefinitions/adminobjects > I'll attach the possible pull request. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-902) Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-902?page=com.atlassian.jira.plugin.... ] Jesper Pedersen moved AS7-5648 to JBJCA-902: -------------------------------------------- Project: IronJacamar (was: Application Server 7) Key: JBJCA-902 (was: AS7-5648) Workflow: jira (was: GIT Pull Request workflow ) Affects Version/s: 1.1.0.Beta2 1.0.12.Final (was: 7.2.0.Alpha1) (was: 7.1.3.Final (EAP)) Component/s: Common (was: JCA) > Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-902 > URL: https://issues.jboss.org/browse/JBJCA-902 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.1.0.Beta2, 1.0.12.Final > Reporter: Simone Gotti > Assignee: Stefano Maestri > > With the effects of issue AS7-5644 I noticed that the connection definition with missing system properties, instead of failing, was using properties from another connection definition (with a lot of consequent problems) > After a lot of analysis the problem is that the org.jboss.jca.common.api.metadata.ra.Connector's system properties are polluted with the merged values of the user specified connectiondefinitions/adminobjects and these system properties's defaults are inserted in the user defined connectiondefinition/adminobject that don't define them. > I think that the wrong operation is in the start method of org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.java: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(raxml, cmd); > I think that merging should be between IronJacamar -> Connector and not raxml -> Connector: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(ijmd, cmd); > After this change I see that the Connector is clean and no unwanted default are added inside my connectiondefinitions/adminobjects > I'll attach the possible pull request. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-902) Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-902?page=com.atlassian.jira.plugin.... ] Jesper Pedersen updated JBJCA-902: ---------------------------------- Priority: Critical (was: Major) Git Pull Request: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135 (was: https://github.com/jbossas/jboss-as/pull/3134, https://github.com/jbossas/jboss-as/pull/3135) > Unwanted system properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBJCA-902 > URL: https://issues.jboss.org/browse/JBJCA-902 > Project: IronJacamar > Issue Type: Bug > Components: Common > Affects Versions: 1.0.12.Final, 1.1.0.Beta2 > Reporter: Simone Gotti > Assignee: Stefano Maestri > Priority: Critical > > With the effects of issue AS7-5644 I noticed that the connection definition with missing system properties, instead of failing, was using properties from another connection definition (with a lot of consequent problems) > After a lot of analysis the problem is that the org.jboss.jca.common.api.metadata.ra.Connector's system properties are polluted with the merged values of the user specified connectiondefinitions/adminobjects and these system properties's defaults are inserted in the user defined connectiondefinition/adminobject that don't define them. > I think that the wrong operation is in the start method of org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.java: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(raxml, cmd); > I think that merging should be between IronJacamar -> Connector and not raxml -> Connector: > cmd = (new Merger()).mergeConnectorWithCommonIronJacamar(ijmd, cmd); > After this change I see that the Connector is clean and no unwanted default are added inside my connectiondefinitions/adminobjects > I'll attach the possible pull request. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5654) Cannot restart jpa bundle after activation failure

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5654: ----------------------------------- Summary: Cannot restart jpa bundle after activation failure Key: AS7-5654 URL: https://issues.jboss.org/browse/AS7-5654 Project: Application Server 7 Issue Type: Bug Components: OSGi, Web Reporter: Thomas Diesler Assignee: Thomas Diesler {code} Caused by: java.lang.IllegalStateException at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) {code} -- 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

13 years, 9 months

1
1
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 September 2012