[JBoss JIRA] (DROOLS-4256) Make Quarkus extension hot reload to also work with new rules
by Edoardo Vacchi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4256?page=com.atlassian.jira.plugi... ]
Edoardo Vacchi commented on DROOLS-4256:
----------------------------------------
WIP: Drools "unit" of compilation is really the package: DRLs are just "broken down" packages. Thus, an API should be provided to compile package-wise. Current API is FS-oriented or too "smart" ("project" or "kiebase" oriented).
> Make Quarkus extension hot reload to also work with new rules
> -------------------------------------------------------------
>
> Key: DROOLS-4256
> URL: https://issues.jboss.org/browse/DROOLS-4256
> Project: Drools
> Issue Type: Task
> Reporter: Mario Fusco
> Assignee: Edoardo Vacchi
> Priority: Major
>
> At the moment hot reload of Kogito extesnsion for Quarkus only works when modifying an existing rule. It should also work when new rules (or entire drl files) are added or removed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months
[JBoss JIRA] (WFLY-12226) IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-12226?page=com.atlassian.jira.plugin... ]
Brian Stansberry reassigned WFLY-12226:
---------------------------------------
Assignee: Brian Stansberry (was: Emmanuel Hugonnet)
Resolution: Done
I'm resolving this as we've worked around it. The Artemis issue tracks the real fix.
> IJ020017: Invalid archive: file://RaActivatoractivemq-ra WARN during start with standalone-full*.xml
> ----------------------------------------------------------------------------------------------------
>
> Key: WFLY-12226
> URL: https://issues.jboss.org/browse/WFLY-12226
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 18.0.0.Beta1
> Reporter: Ondrej Kotek
> Assignee: Brian Stansberry
> Priority: Critical
> Fix For: 17.0.1.Final, 18.0.0.Beta1
>
>
> There is a warning during start with standalone-full*.xml:
> {noformat}
> 12:19:04,432 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
> 12:19:04,440 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
> 12:19:04,441 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 83) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
> 12:19:04,441 WARN [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020017: Invalid archive: file://RaActivatoractivemq-ra
> 12:19:04,486 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started
> 12:19:04,486 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
> 12:19:04,492 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
> 12:19:04,493 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
> {noformat}
> For an automation checking the server log for issues, this WARN causes false positive. Hence, I set the Priority to Critical.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 3 months