January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3126) Configuration - messaging subsystem ignores -Dproperty=value -> ${property:default-value} in standalone-full.xml

by Miroslav Novak (Created) (JIRA)

Configuration - messaging subsystem ignores -Dproperty=value -> ${property:default-value} in standalone-full.xml ---------------------------------------------------------------------------------------------------------------- Key: AS7-3126 URL: https://issues.jboss.org/browse/AS7-3126 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final It looks that -Dproperty=value specified in starting command line of server is not propagated to configuration -> ${property:default-value} in standalone-full.xml. -- 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

14 years, 4 months

5
4
0 / 0

[JBoss JIRA] (AS7-3317) ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator

by Miroslav Novak (JIRA)

Miroslav Novak created AS7-3317: ----------------------------------- Summary: ClassNotFoundException during start - org.jboss.as.messaging.jms.TransactionManagerLocator Key: AS7-3317 URL: https://issues.jboss.org/browse/AS7-3317 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.0.CR1 Reporter: Miroslav Novak Assignee: Clebert Suconic Fix For: 7.1.0.Final When logging subsystem is set to DEBUG level for "org.hornetq" then ClassNotFoundException exception appears in console log: {code} 12:45:01,163 DEBUG [org.hornetq.ra.Util] (MSC service thread 1-4) org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)]: java.lang.ClassNotFoundException: org.jboss.as.messaging.jms.TransactionManagerLocator from [Module "org.hornetq.ra:main" from local module loader @6e811c88 (roots: /mnt/shared/test-eap6/server1/jboss-eap-6.0/modules)] at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:473) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:461) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:403) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:125) at org.hornetq.ra.Util.locateTM(Util.java:261) [hornetq-ra-2.2.7.Final.jar:] at org.hornetq.ra.HornetQResourceAdapter.locateTM(HornetQResourceAdapter.java:1555) [hornetq-ra-2.2.7.Final.jar:] at org.hornetq.ra.HornetQResourceAdapter.start(HornetQResourceAdapter.java:210) [hornetq-ra-2.2.7.Final.jar:] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_22] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_22] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_22] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.startContext(AbstractResourceAdapterDeployer.java:345) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2127) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1030) [ironjacamar-deployers-common-1.0.6.Final-redhat-1.jar:1.0.6.Final] at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:148) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1] at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:94) [jboss-as-connector-7.1.0.CR1-redhat-1.jar:7.1.0.CR1-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [:1.6.0_22] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [:1.6.0_22] at java.lang.Thread.run(Thread.java:679) [:1.6.0_22] {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

14 years, 4 months

4
5
0 / 0

[JBoss JIRA] (AS7-2485) Propagate property node0 to system properties

by Ondřej Chaloupka (Created) (JIRA)

Propagate property node0 to system properties --------------------------------------------- Key: AS7-2485 URL: https://issues.jboss.org/browse/AS7-2485 Project: Application Server 7 Issue Type: Sub-task Reporter: Ondřej Chaloupka Assignee: Ondrej Zizka Propagate property node0 (and other ones) to system properties for test being able to take IP address where the AS runs. -- 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

14 years, 4 months

6
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1732) Pooling strategy and configuration information needed at runtime

by Galder Zamarreno (JIRA)

Pooling strategy and configuration information needed at runtime ---------------------------------------------------------------- Key: EJBTHREE-1732 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1732 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: AS 4.2.3.GA Reporter: Galder Zamarreno There needs to be a way at runtime to see what pooling strategy (including configuration options) an EJB3 bean is using. Currently, the only way to see this is by enabling TRACE on org.jboss.ejb3 and making an invocation to that EJB3 bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

2
7
0 / 0

[JBoss JIRA] (JBRULES-3343) Evaluate modified objects in BetaNode with a slot specific strategy

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3343: ------------------------------------ Summary: Evaluate modified objects in BetaNode with a slot specific strategy Key: JBRULES-3343 URL: https://issues.jboss.org/browse/JBRULES-3343 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco Evaluate modified objects in BetaNode with a slot specific strategy -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] (AS7-3378) Allow local mechanism to be enabled or disabled on a realm.

by Darran Lofthouse (JIRA)

Darran Lofthouse created AS7-3378: ------------------------------------- Summary: Allow local mechanism to be enabled or disabled on a realm. Key: AS7-3378 URL: https://issues.jboss.org/browse/AS7-3378 Project: Application Server 7 Issue Type: Task Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Final It should be possible to switch off the local mechanism - to achieve this it may be easier to add it to the <authentication> element so it can be omitted - i.e. the authentication element will now have multiple 'stores' defined and we will support the authentication mechanism of each of them, duplicate mechanisms will result in a WARN and the subsequent stores omitted. -- 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

14 years, 4 months

2
6
0 / 0

[JBoss JIRA] (AS7-2548) Decide what to do with the sasl child of connector in the remoting subsystem

by Kabir Khan (Created) (JIRA)

Decide what to do with the sasl child of connector in the remoting subsystem ---------------------------------------------------------------------------- Key: AS7-2548 URL: https://issues.jboss.org/browse/AS7-2548 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Darran Lofthouse -- 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

14 years, 4 months

5
5
0 / 0

[JBoss JIRA] (AS7-3423) Handle deployments with a persistence provider and javax.persistence classes

by Scott Marlow (JIRA)

Scott Marlow created AS7-3423: --------------------------------- Summary: Handle deployments with a persistence provider and javax.persistence classes Key: AS7-3423 URL: https://issues.jboss.org/browse/AS7-3423 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 If an application deployment contains its own copy of a persistence provider and its own of the javax.persistence classes, deploy it as an application managed JPA application (no container managed JPA support feature are expected to be used). 1. initialize the application copy of the javax.persistence.Persistence class by setting an application deployment level PersistenceProviderResolver (via javax.persistence.spi.PersistenceProviderResolverHolder.PersistenceProviderResolver()) that would know about the persistence provider that is bundled. 2. don't inject the javax.persistence module into the deployment. 3. add a unit test that bundles a persistence provider, javax.persistence classes and uses javax.persistence.Persistence.createEntityManagerFactory(String persistenceUnitName). https://github.com/alesj/jboss-as/tree/capedwarf contains some related changes that might be worth looking at when this jira is worked around. -- 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

14 years, 4 months

2
12
0 / 0

[JBoss JIRA] Created: (AS7-1779) Manage infinispan through console

by Heiko Braun (JIRA)

Manage infinispan through console --------------------------------- Key: AS7-1779 URL: https://issues.jboss.org/browse/AS7-1779 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

4
9
0 / 0

[JBoss JIRA] Created: (JGRP-1313) RELAY: bridge multiple sites

by Bela Ban (JIRA)

RELAY: bridge multiple sites ---------------------------- Key: JGRP-1313 URL: https://issues.jboss.org/browse/JGRP-1313 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.1 The current RELAY (2.12.1) bridges only 2 local clusters (sites). Think about ways to bridge multiple sites, e.g. in a star topology (all sites bridge to a central site, but not to each other), or daisy chaining (a site A bridges to site B, which bridges to site C etc) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

1
2
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 January 2012