November 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-2184) persistence.xml java:comp/env lookup fails during deployment because ContextInitialized is not complete

by Bob Fields (Created) (JIRA)

persistence.xml java:comp/env lookup fails during deployment because ContextInitialized is not complete ------------------------------------------------------------------------------------------------------- Key: AS7-2184 URL: https://issues.jboss.org/browse/AS7-2184 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate, VFS Affects Versions: 7.0.2.Final Environment: Hibernate 3.6.7, AS 7.0.2 (also fails on AS 6.1) Reporter: Bob Fields Assignee: Scott Marlow Priority: Minor Works in AS5.1 and earlier, fails in AS6.1 and AS 7.0.2. Standard web.xml configuration, no additional listeners. Deployment using <jta-data-source>java:comp/env/jdbc/timetracker</jta-data-source> fails because ENC is not initialized when contextInitialized event occurs. Succeeds if lookup is changed to java:jboss/datasources/ExampleDS which is defined in global JNDI. -- 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, 1 month

6
12
0 / 0

[JBoss JIRA] (JBRULES-3257) MarshallerWriteContext.objectMarshallingStrategyStore contains an unpredictable list of ObjectMarshallingStrategy objects which can break WorkItemInfo unmarshalling (wrt backwards compatibility)

by Marco Rietveld (Created) (JIRA)

MarshallerWriteContext.objectMarshallingStrategyStore contains an unpredictable list of ObjectMarshallingStrategy objects which can break WorkItemInfo unmarshalling (wrt backwards compatibility) ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-3257 URL: https://issues.jboss.org/browse/JBRULES-3257 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.3.0.Beta1, 5.2.0.Final, 5.4.0.Beta1 Reporter: Marco Rietveld Assignee: Marco Rietveld Priority: Minor Fix For: 5.4.0.Beta1 The reason that this is a minor bug is that the user can always fix this by putting the proper ObjectMarshallingStrategy instance into the environment passed to the object doing the unmarshaller. The following code is where the bug is (see second comment): {code} public static void writeWorkItem(MarshallerWriteContext context, WorkItem workItem) throws IOException { // ... other code for ( String key : parameters.keySet() ) { Object object = parameters.get( key ); if ( object != null ) { stream.writeUTF( key ); // Next 2 lines: we store the _index_ of the ObjectMarshallingStrategy object in the stream int index = context.objectMarshallingStrategyStore.getStrategy( object );* stream.writeInt( index );* ObjectMarshallingStrategy strategy = context.objectMarshallingStrategyStore.getStrategy( index ); if ( strategy.accept( object ) ) { strategy.write( stream, object ); } } } } {code} The logic used above is also used when serializing the FactHandle (see here: [OutputMarshaller (most recent commit)|https://github.com/droolsjbpm/drools/blob/0dc2ef742078138e8747b17... When the marshalled (WorkItem) data is unmarshalled, the {{context.objectMarshallingStrategyStore}} must contain at least the same set of ObjectMarshallingStrategy objects that were used when the WorkItem object was marshalled. ---- Instead of using the _index_ of the class, my proposed solution is to use the class name, and throw a descriptive exception when the ObjectMarshallingStrategy object sought, can not be found. -- 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, 1 month

4
3
0 / 0

[JBoss JIRA] (AS7-2330) Web Console: Once you leave the Hosts listing by clicking on the server list, you can not get back to it

by Jim Tyrrell (Created) (JIRA)

Web Console: Once you leave the Hosts listing by clicking on the server list, you can not get back to it -------------------------------------------------------------------------------------------------------- Key: AS7-2330 URL: https://issues.jboss.org/browse/AS7-2330 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell Attachments: Screen shot 2011-10-26 at 11.06.37 AM.png Screen Shot one is the landing page, that you can not get back to, once you click a server on the left side under the Server Configurations tab on the left hand side. -- 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, 1 month

6
9
0 / 0

[JBoss JIRA] (AS7-2320) Web Console: Active/Inactive flag on the logging levels that are configued

by Jim Tyrrell (Created) (JIRA)

Web Console: Active/Inactive flag on the logging levels that are configued -------------------------------------------------------------------------- Key: AS7-2320 URL: https://issues.jboss.org/browse/AS7-2320 Project: Application Server 7 Issue Type: Feature Request Reporter: Jim Tyrrell Certain levels of logging or settings might want/need to be disabled for a certain run, but you do not want to delete them, but just mark them as "unused" so they can be enabled at a later date. -- 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, 1 month

5
5
0 / 0

[JBoss JIRA] (AS7-2369) Web Console: In Manage Deployments a large number of Server Groups results in servers you can not view

by Jim Tyrrell (Created) (JIRA)

Web Console: In Manage Deployments a large number of Server Groups results in servers you can not view ------------------------------------------------------------------------------------------------------ Key: AS7-2369 URL: https://issues.jboss.org/browse/AS7-2369 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Attachments: Screen shot 2011-10-26 at 2.28.43 PM.png See the attached screen shot, but I have created a bunch of server configurations, and I am not able to edit/view a bunch of them as they are drawn outside of the viewable area. -- 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, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1931) Unable to configure more than one pooled-connection-factory in the messaging subsystem

by Vincent MATHON (JIRA)

Unable to configure more than one pooled-connection-factory in the messaging subsystem -------------------------------------------------------------------------------------- Key: AS7-1931 URL: https://issues.jboss.org/browse/AS7-1931 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final, 7.0.1.Final, 7.0.0.Final Environment: Windows7, sun jdk 1.6_25 Reporter: Vincent MATHON Adding another pooled connection factory in the standalone-preview.xml file provided by any of the 7.0.x.Final releases as follow <pooled-connection-factory name="hornetq-ra"> <transaction mode="xa"/> <connectors> <connector-ref connector-name="in-vm"/> </connectors> <entries> <entry name="java:/JmsXA"/> </entries> </pooled-connection-factory> <pooled-connection-factory name="hornetq-ra-nonxa"> <transaction mode="local"/> <connectors> <connector-ref connector-name="in-vm"/> </connectors> <entries> <entry name="java:/JmsNonXA"/> </entries> </pooled-connection-factory> leads to the following exception: 12:44:31,621 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: org.jboss.msc.service.StartException in service jboss.messaging.pooled-connection-factory.hornetq-ra-nonxa: failed to create resource adapter at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:174) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.raactivator is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:226) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) at org.jboss.as.messaging.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:232) at org.jboss.as.messaging.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:172) ... 5 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
2
0 / 0

[JBoss JIRA] Created: (AS7-878) Add a properties file based authentication configuration for the domain management security realm.

by Darran Lofthouse (JIRA)

Add a properties file based authentication configuration for the domain management security realm. -------------------------------------------------------------------------------------------------- Key: AS7-878 URL: https://issues.jboss.org/browse/AS7-878 Project: Application Server 7 Issue Type: Task Components: Domain Management Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (AS7-892) InitialContextFactoryBuilder should use Class.forName with null ClassLoader instead of context class loader.

by Darran Lofthouse (JIRA)

InitialContextFactoryBuilder should use Class.forName with null ClassLoader instead of context class loader. ------------------------------------------------------------------------------------------------------------ Key: AS7-892 URL: https://issues.jboss.org/browse/AS7-892 Project: Application Server 7 Issue Type: Task Components: Naming Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] (AS7-2267) The Console logs the DMR commands

by Rich Raposa (Created) (JIRA)

The Console logs the DMR commands --------------------------------- Key: AS7-2267 URL: https://issues.jboss.org/browse/AS7-2267 Project: Application Server 7 Issue Type: Feature Request Reporter: Rich Raposa It would be nice if changes made to the configuration file via the Console were logged in DMR format so that the commands could be executed as a CLI script. A simpler option would be to provide a link next to a resource that shows the CLI command you would use to create that resource. For example, in the list of datasources on the Datasources Configuration tab, next to each datasource would be a link that would contain the CLI command for defining that datasource. The use case is this: I can take advantage of the ease-of-use of the Console to define a resource, then copy-and-paste the CLI command to define a script so that the resource can be defined over and over again on all of my EAP deployments. -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] (AS7-2101) Make it impossible to register 2 slave HCs with the same name

by Kabir Khan (Created) (JIRA)

Make it impossible to register 2 slave HCs with the same name ------------------------------------------------------------- Key: AS7-2101 URL: https://issues.jboss.org/browse/AS7-2101 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.1.0.CR1 AS7-1737 deals with making it impossible to create a slave HC with the same name as the master HC. However, if the master already has a slave called 'slave' and a second slave called 'slave' is registered, the first one is unregistered and the second one registered. -- 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, 1 month

3
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2011