September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5511) component upgrade to Hibernate 4.1.7.Final

by Scott Marlow (JIRA)

Scott Marlow created AS7-5511: --------------------------------- Summary: component upgrade to Hibernate 4.1.7.Final Key: AS7-5511 URL: https://issues.jboss.org/browse/AS7-5511 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.2.0.Alpha1 -- 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
2
0 / 0

[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment

by Philippe Marschall (JIRA)

Philippe Marschall created AS7-5584: --------------------------------------- Summary: Naming context read-only during SAR deployment Key: AS7-5584 URL: https://issues.jboss.org/browse/AS7-5584 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.1.1.Final Reporter: Philippe Marschall During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}} http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi... -- 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

3
9
0 / 0

[JBoss JIRA] (AS7-5438) standalone.xml: check if driver name datasource references existing driver in drivers is missing

by Radim Pavlicek (JIRA)

Radim Pavlicek created AS7-5438: ----------------------------------- Summary: standalone.xml: check if driver name datasource references existing driver in drivers is missing Key: AS7-5438 URL: https://issues.jboss.org/browse/AS7-5438 Project: Application Server 7 Issue Type: Bug Components: Server Affects Versions: 7.1.1.Final Environment: GNU/Linux Reporter: Radim Pavlicek Assignee: Jason Greene standalone.xml: <drivers> <driver name="h2" module="com.h2database.h2"> <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> </driver> <driver name="oracle" module="com.oracle.ojdbc6"> <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class> </driver> </drivers> and in datasource tag: <datasource jta="true" jndi-name="java:jboss/datasources/Glob01DS" pool-name="Glob01DS" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:oracle:thin:....cut</connection-url> <driver>oracle12</driver> wont produce any exception even if I am referencing driver which doesn't exist! -- 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
2
0 / 0

[JBoss JIRA] (AS7-4962) NPE in HornetQ RA after MDB repeatedly throws exception

by Alexandre Gattiker (JIRA)

Alexandre Gattiker created AS7-4962: --------------------------------------- Summary: NPE in HornetQ RA after MDB repeatedly throws exception Key: AS7-4962 URL: https://issues.jboss.org/browse/AS7-4962 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.1.Final Reporter: Alexandre Gattiker Assignee: Andy Taylor If an MDB throws a RuntimeException, after several redeliveries, following exception is thrown: Failed to call onMessage(): java.lang.NullPointerException at org.hornetq.ra.inflow.HornetQMessageHandler.onMessage(HornetQMessageHandler.java:336) at org.hornetq.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:983) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:48) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1113) [hornetq-core-2.2.13.Final.jar:] at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:100) [hornetq-core-2.2.13.Final.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_31] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_31] at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_31] -- 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
5
0 / 0

[JBoss JIRA] (AS7-5658) Deadlock when using configadmin from within a mgmnt op

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5658: ----------------------------------- Summary: Deadlock when using configadmin from within a mgmnt op Key: AS7-5658 URL: https://issues.jboss.org/browse/AS7-5658 Project: Application Server 7 Issue Type: Bug Components: ConfigAdmin Reporter: Thomas Diesler Assignee: David Bosschaert Priority: Critical Fix For: 7.2.0.Alpha1 Nested mgmnt ops deadlock. This could easily happen when ConfigAdmin is used from within a BundleActivator during deploy. -- 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
3
0 / 0

[JBoss JIRA] (AS7-3621) f:validateBean disabled="true" is lost following POST-back

by Richard Kennard (JIRA)

Richard Kennard created AS7-3621: ------------------------------------ Summary: f:validateBean disabled="true" is lost following POST-back Key: AS7-3621 URL: https://issues.jboss.org/browse/AS7-3621 Project: Application Server 7 Issue Type: Bug Reporter: Richard Kennard As discussed on FORGE-460: Richard: "I think an 'easy default' would be to just add <f:validateBean disabled="#{true}"/> to each search field. However this doesn't appear to survive POST-back (i.e. it works for one click, but then fails after that). Are you aware of this? Is it a bug? I attach a minimal test case. I'd be most grateful if you could look at it". Emmanuel: "Yes that's definitely a bug. I'd bet in the JSF engine". Pete: "Richard, could you open an AS7 bug. Assign it to Stan (or if you can't assign, ask me to)". Minimal test case attached to FORGE-460: https://issues.jboss.org/secure/attachment/12351185/emmanuel.zip -- 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

4
7
0 / 0

[JBoss JIRA] Created: (AS7-1044) Add ability to launch H2 console from AS7 console for standalone mode

by Pete Muir (JIRA)

Add ability to launch H2 console from AS7 console for standalone mode --------------------------------------------------------------------- Key: AS7-1044 URL: https://issues.jboss.org/browse/AS7-1044 Project: Application Server 7 Issue Type: Feature Request Reporter: Pete Muir See http://www.h2database.com/html/tutorial.html#tutorial_starting_h2_console for the console. Add ability to easily access this for the H2 datasources. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

10
10
0 / 0

[JBoss JIRA] (AS7-4784) Unify generic AttributeDefinition implementations

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-4784: -------------------------------- Summary: Unify generic AttributeDefinition implementations Key: AS7-4784 URL: https://issues.jboss.org/browse/AS7-4784 Project: Application Server 7 Issue Type: Enhancement Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Reporter: Tomaz Cerar Assignee: Tomaz Cerar Fix For: 7.2.0.Alpha1 The objective of this task is to cleanup AttributeDefinition implementations as some of them are just implementing the class but not following any conventions they should so they cannot be used in combination with ResourceDefinition. We also have multiple - ObjectTypeAttributeDefinition - PropertiesAttributeDefinition that are defined in different modules and have bit different implementation. There are some other generic AttributeDefinition implementations that should be cleaned up and moved to controller module -- 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

1
1
0 / 0

[JBoss JIRA] (AS7-3332) c:catch tag apparently doesn't work when using facelets.

by Alexander Picoli (JIRA)

Alexander Picoli created AS7-3332: ------------------------------------- Summary: c:catch tag apparently doesn't work when using facelets. Key: AS7-3332 URL: https://issues.jboss.org/browse/AS7-3332 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.0.2.Final Environment: JBoss application server running on a Windows 7 platform, inside eclipse platform. Reporter: Alexander Picoli Assignee: Stan Silvert When using the JSTL c:catch tag inside JSP pages, and I access an EL expression that throws a custom exception, the tag works fine. But when I use it with facelets, the c:catch is ignored and a HTTP500 message is sent to the client. -- 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

2
8
0 / 0

[JBoss JIRA] (AS7-5502) Upgrade logging tooling and fix annotations

by James Perkins (JIRA)

James Perkins created AS7-5502: ---------------------------------- Summary: Upgrade logging tooling and fix annotations Key: AS7-5502 URL: https://issues.jboss.org/browse/AS7-5502 Project: Application Server 7 Issue Type: Task Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 7.2.0.Alpha1 -- 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
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 September 2012