[JBoss JIRA] Created: (JBAS-9113) Verify consistent handling of default values and resolved expressions when populating the domain model.
by Darran Lofthouse (JIRA)
Verify consistent handling of default values and resolved expressions when populating the domain model.
-------------------------------------------------------------------------------------------------------
Key: JBAS-9113
URL: https://issues.jboss.org/browse/JBAS-9113
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Darran Lofthouse
Fix For: 7.0.0.CR1
On reading the descriptors and executing the operations care needs to be taken to ensure either default values or resolved expressions are not transferred into the domain model - the consequence of this is that when the descriptors are re-written if these values are present in the model they are written as is loosing any default handling / expression resolving.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] Created: (JBRULES-2293) Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal
by Steve Ronderos (JIRA)
Classpath resources being scanned by ResourceChangeScanner could cause improper resource removal
------------------------------------------------------------------------------------------------
Key: JBRULES-2293
URL: https://jira.jboss.org/jira/browse/JBRULES-2293
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Windows XP
Java 5
Running in Oracle OC4J 10.1.3.2
Reporter: Steve Ronderos
Assignee: Mark Proctor
I encountered an issue today with my KnowledgeAgent removing resources from its RuleBase shortly after creating it. I have the ResourceChangeScanner running in my application.
I tracked the issue back to the scan() method in ResourceChangeScannerImpl. It appears that the method is trying to identify resources that are no longer available and remove them from both the RuleBase and future scans. To do this it is checking lastModified on the resource and on a result of 0 removing the resource. The resources that I configured in my change-set definitely still exist, but due to URL handler implementation provided by my classloader, getLastModified always returns 0. (The resource I'm retrieving is coming from a jar that is in my application's classpath and the URL handler implementation is oracle.classloader.SharedCodeSourceURL)
Full Email Group trail: http://www.nabble.com/Issue-with-ResourceChangeScanner-td25792358.html
Michael recommends to never scan classpath resources.
--
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
12 years, 8 months
[JBoss JIRA] (AS7-2083) Exception when specifying discovery-group-ref under connection-factory / pooled-connection-factory in messaging subsystem
by Evangelos Parchas (Created) (JIRA)
Exception when specifying discovery-group-ref under connection-factory / pooled-connection-factory in messaging subsystem
-------------------------------------------------------------------------------------------------------------------------
Key: AS7-2083
URL: https://issues.jboss.org/browse/AS7-2083
Project: Application Server 7
Issue Type: Bug
Components: JMS
Affects Versions: 7.0.1.Final
Environment: Ubuntu 11.04 64bit, Java 1.6
Reporter: Evangelos Parchas
Assignee: Clebert Suconic
An error is produced when specifying a "discovery-group-ref" under either a "connection-factory" or "pooled-connection-factory" in the messaging subsystem configuration:
{code}
<connection-factory name="RemoteConnectionFactory">
<discovery-group-ref discovery-group-name="dg-group1"/>
<entries>
<entry name="java:/RemoteConnectionFactory"/>
</entries>
</connection-factory>
{code}
{code}
<pooled-connection-factory name="RemoteXAConnectionFactory">
<discovery-group-ref discovery-group-name="dg-group1"/>
<entries>
<entry name="java:/RemoteXAConnectionFactory"/>
</entries>
<transaction mode="xa"/>
</pooled-connection-factory>
{code}
The exception present in the server.log is:
{code}
14:40:45,466 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-16) MSC00001: Failed to start service jboss.raactivator: org.jboss.msc.service.St
artException in service jboss.raactivator: Failed to activate resource adapter RemoteXAConnectionFactory
at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:98)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765)
at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_26]
Caused by: org.jboss.jca.deployers.common.DeployException: Deployment org.hornetq.ra.HornetQResourceAdapter failed
at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.initAndInject(AbstractResourceAdap
terDeploymentService.java:382)
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:900)
at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:825)
at org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator.doDeploy(ResourceAdapterActivatorService.java:140)
at org.jboss.as.connector.services.ResourceAdapterActivatorService.start(ResourceAdapterActivatorService.java:93)
... 5 more
Caused by: java.lang.NoSuchMethodException: org.hornetq.ra.HornetQResourceAdapter.setDiscoveryGroupName(java.lang.String)
at java.lang.Class.getMethod(Class.java:1605) [:1.6.0_26]
at org.jboss.as.connector.util.Injection.inject(Injection.java:149)
at org.jboss.as.connector.metadata.deployment.AbstractResourceAdapterDeploymentService$AbstractAS7RaDeployer.initAndInject(AbstractResourceAdap
terDeploymentService.java:374)
... 9 more
{code}
Looking at HornetQResourceAdapter, it does not provide a method called "setDiscoveryGroupName" but a "setDiscoveryAddress" which bears the javadoc that it corresponds to the discovery group name.
This prevents successful configuration of the messaging subsystem for clustered environments
--
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
12 years, 8 months