[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
11 years, 6 months
[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
11 years, 6 months
[JBoss JIRA] (AS7-5665) Use system property substitutions for other path manager service properties
by Galder Zamarreño (JIRA)
Galder Zamarreño created AS7-5665:
-------------------------------------
Summary: Use system property substitutions for other path manager service properties
Key: AS7-5665
URL: https://issues.jboss.org/browse/AS7-5665
Project: Application Server 7
Issue Type: Enhancement
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Priority: Minor
Hmmmm, rather unfortunate that AS7-4917 was only applied to `path` and not the other properties, i.e. `relative-to`. Use case:
{code}<modules-repo path=".openshift/config/modules" relative-to="${env.OPENSHIFT_REPO_DIR}"/>{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
11 years, 6 months
[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
11 years, 6 months
[JBoss JIRA] (JBJCA-902) Unwanted config properties in a connectiondefinition/adminobject from another connectiondefinition/adminobject in the same resource adapter
by Stefano Maestri (JIRA)
[ https://issues.jboss.org/browse/JBJCA-902?page=com.atlassian.jira.plugin.... ]
Stefano Maestri resolved JBJCA-902.
-----------------------------------
Resolution: Done
> 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
11 years, 6 months