[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not have the desired effect of producing logs;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}};
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File `standalone-full.xml` can be configured via cli but it does not produce any log;
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no file ejb-access.log
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no logs in `standalone/log/server.log`;
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no logs in console
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}};
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
[ https://issues.jboss.org/browse/WFWIP-181?page=com.atlassian.jira.plugin.... ]
Tommasso Borgato updated WFWIP-181:
-----------------------------------
Description:
File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}} is produced;
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
was:
File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
We verified that with the following:
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no file {{standalone/log/ejb-access.log}};
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in {{standalone/log/server.log}};
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
: no logs in console;
> Access logging for EJBs: no logs produced
> -----------------------------------------
>
> Key: WFWIP-181
> URL: https://issues.jboss.org/browse/WFWIP-181
> Project: WildFly WIP
> Issue Type: Bug
> Components: Logging
> Reporter: Tommasso Borgato
> Assignee: James Perkins
> Priority: Blocker
>
> File {{standalone-full.xml}} can be configured via cli but it does not produce any log;
> We verified that with the following:
> {noformat}
> <access-log>
> <file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
> <formatter name="p1"/>
> </file-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no file {{standalone/log/ejb-access.log}} is produced;
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> or
> {noformat}
> <access-log>
> <server-log-handler name="server1">
> <formatter name="p1"/>
> </server-log-handler>
> <formatter>
> <json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in {{standalone/log/server.log}};
> {noformat}
> <access-log>
> <console-handler name="console1">
> <formatter name="p1"/>
> </console-handler>
> <formatter>
> <pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
> </formatter>
> </access-log>
> {noformat}
> : no logs in console;
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (WFWIP-181) Access logging for EJBs: no logs produced
by Tommasso Borgato (Jira)
Tommasso Borgato created WFWIP-181:
--------------------------------------
Summary: Access logging for EJBs: no logs produced
Key: WFWIP-181
URL: https://issues.jboss.org/browse/WFWIP-181
Project: WildFly WIP
Issue Type: Bug
Components: Logging
Reporter: Tommasso Borgato
Assignee: James Perkins
File `standalone-full.xml` can be configured via cli but it does not produce any log;
{noformat}
<access-log>
<file-handler name="file1" path="ejb-access.log" relative-to="jboss.server.log.dir">
<formatter name="p1"/>
</file-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no file ejb-access.log
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
or
{noformat}
<access-log>
<server-log-handler name="server1">
<formatter name="p1"/>
</server-log-handler>
<formatter>
<json-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no logs in `standalone/log/server.log`;
{noformat}
<access-log>
<console-handler name="console1">
<formatter name="p1"/>
</console-handler>
<formatter>
<pattern-formatter name="p1" pattern="date time ip client ejb method event server thread"/>
</formatter>
</access-log>
{noformat}
no logs in console
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4468) Invalid result with collect, mvel and ForceEagerActivationOption.YES
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-4468?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-4468:
--------------------------------
Sprint: 2019 Week 35-37
> Invalid result with collect, mvel and ForceEagerActivationOption.YES
> --------------------------------------------------------------------
>
> Key: DROOLS-4468
> URL: https://issues.jboss.org/browse/DROOLS-4468
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.25.0.Final
> Reporter: Martin Weiler
> Assignee: Mario Fusco
> Priority: Major
> Attachments: case02445433-testcase.zip
>
>
> A rule updates a list in a fact:
> {noformat}
> rule "Init"
> dialect "mvel"
> when
> $fl: FactWithList(items.size()==0)
> then
> $fl.getItems().add("A");
> $fl.getItems().add("B");
> update($fl);
> end
> {noformat}
> A second rule verifies if other facts exist, matching the items in the updated list:
> {noformat}
> rule "Expected Outcome"
> dialect "mvel"
> when
> $fl: FactWithList($itemList : items != null)
> $l: java.util.ArrayList(size > 0) from collect(FactWithString($itemList contains stringValue));
> then
> System.out.println("--> Rule: " + kcontext.getRule().getName() + " fired, " + $fl + ", collect list: " + $l.size());
> end
> {noformat}
> This rule is *not* fired if
> * mvel dialect is used *and*
> * Drools is executed with {{ForceEagerActivationOption.YES}} (jBPM use case)
> Note: This worked in 7.17 and earlier!
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-2581) Java-level deadlock in Drools ProjectClassLoader
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-2581?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-2581:
-------------------------------------
Fixed by https://github.com/kiegroup/drools/commit/6b7840d98b0175b8efc83acf1e7b8cb...
> Java-level deadlock in Drools ProjectClassLoader
> ------------------------------------------------
>
> Key: DROOLS-2581
> URL: https://issues.jboss.org/browse/DROOLS-2581
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.5.0.Final
> Environment: * 7.5.0.Final-redhat-4 from RHDM 7.0
> Reporter: Kylin Soong
> Assignee: Mario Fusco
> Priority: Critical
> Attachments: t.dump
>
>
> After install the RHDM 7.0 and started it, it's not possible to restart or stop, Java-level deadlock cause this:
> {code}
> Found one Java-level deadlock:
> =============================
> "ForkJoinPool.commonPool-worker-1":
> waiting to lock monitor 0x000000000418a588 (object 0x00000006e56789b8, a org.drools.core.common.ProjectClassLoader),
> which is held by "EJB default - 1"
> "EJB default - 1":
> waiting to lock monitor 0x0000000007fd7bc8 (object 0x00000006e77d7a78, a org.drools.core.common.ProjectClassLoader$DefaultInternalTypesClassLoader),
> which is held by "ForkJoinPool.commonPool-worker-1"
> Java stack information for the threads listed above:
> ===================================================
> "ForkJoinPool.commonPool-worker-1":
> at java.lang.ClassLoader.loadClass(ClassLoader.java:404)
> - waiting to lock <0x00000006e56789b8> (a org.drools.core.common.ProjectClassLoader)
> at org.drools.core.common.ProjectClassLoader.internalLoadClass(ProjectClassLoader.java:167)
> at org.drools.core.common.ProjectClassLoader$DefaultInternalTypesClassLoader.loadClass(ProjectClassLoader.java:423)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2583)
> at java.lang.Class.getDeclaredFields(Class.java:1916)
> at org.drools.compiler.builder.impl.TypeDeclarationCache.processFieldsPosition(TypeDeclarationCache.java:206)
> at org.drools.compiler.builder.impl.TypeDeclarationCache.initTypeDeclaration(TypeDeclarationCache.java:151)
> at org.drools.compiler.builder.impl.TypeDeclarationCache.getAndRegisterTypeDeclaration(TypeDeclarationCache.java:91)
> at org.drools.compiler.builder.impl.TypeDeclarationBuilder.getAndRegisterTypeDeclaration(TypeDeclarationBuilder.java:69)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.getAndRegisterTypeDeclaration(KnowledgeBuilderImpl.java:1860)
> at org.drools.compiler.rule.builder.PatternBuilder.processClassObjectType(PatternBuilder.java:306)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:181)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:151)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:133)
> at org.drools.compiler.rule.builder.GroupElementBuilder.build(GroupElementBuilder.java:66)
> at org.drools.compiler.rule.builder.RuleBuilder.build(RuleBuilder.java:105)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addRule(KnowledgeBuilderImpl.java:1281)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.lambda$compileRulesLevel$3(KnowledgeBuilderImpl.java:1242)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl$$Lambda$1035/1743914198.accept(Unknown Source)
> at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291)
> at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
> "EJB default - 1":
> at java.lang.ClassLoader.loadClass(ClassLoader.java:404)
> - waiting to lock <0x00000006e77d7a78> (a org.drools.core.common.ProjectClassLoader$DefaultInternalTypesClassLoader)
> at org.drools.core.common.ProjectClassLoader$DefaultInternalTypesClassLoader.loadType(ProjectClassLoader.java:431)
> at org.drools.core.common.ProjectClassLoader.loadType(ProjectClassLoader.java:177)
> at org.drools.core.common.ProjectClassLoader.loadClass(ProjectClassLoader.java:149)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.mvel2.util.ParseTools.forNameWithInner(ParseTools.java:2178)
> at org.mvel2.ParserConfiguration.checkForDynamicImport(ParserConfiguration.java:154)
> at org.mvel2.ParserConfiguration.hasImport(ParserConfiguration.java:175)
> at org.mvel2.ParserContext.hasImport(ParserContext.java:386)
> at org.mvel2.compiler.PropertyVerifier.getBeanProperty(PropertyVerifier.java:175)
> at org.mvel2.compiler.PropertyVerifier.analyze(PropertyVerifier.java:132)
> at org.mvel2.compiler.ExpressionCompiler.verify(ExpressionCompiler.java:392)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:281)
> at org.mvel2.util.ParseTools.subCompileExpression(ParseTools.java:2064)
> at org.mvel2.ast.Negation.<init>(Negation.java:40)
> at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:1233)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:126)
> at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:67)
> at org.mvel2.MVEL.analyze(MVEL.java:680)
> at org.mvel2.MVEL.analyze(MVEL.java:685)
> at org.drools.compiler.rule.builder.dialect.mvel.MVELExprAnalyzer.analyzeExpression(MVELExprAnalyzer.java:130)
> at org.drools.compiler.rule.builder.dialect.mvel.MVELDialect.analyzeExpression(MVELDialect.java:509)
> at org.drools.compiler.rule.builder.dialect.mvel.MVELDialect.analyzeExpression(MVELDialect.java:491)
> at org.drools.compiler.rule.builder.PatternBuilder.buildAnalysis(PatternBuilder.java:1602)
> at org.drools.compiler.rule.builder.PatternBuilder.buildEval(PatternBuilder.java:1497)
> at org.drools.compiler.rule.builder.PatternBuilder.createAndBuildPredicate(PatternBuilder.java:1339)
> at org.drools.compiler.rule.builder.PatternBuilder.buildExpression(PatternBuilder.java:974)
> at org.drools.compiler.rule.builder.PatternBuilder.buildCcdDescr(PatternBuilder.java:946)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:767)
> at org.drools.compiler.rule.builder.PatternBuilder.processConstraintsAndBinds(PatternBuilder.java:627)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:184)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:151)
> at org.drools.compiler.rule.builder.PatternBuilder.build(PatternBuilder.java:133)
> at org.drools.compiler.rule.builder.GroupElementBuilder.build(GroupElementBuilder.java:66)
> at org.drools.compiler.rule.builder.RuleBuilder.build(RuleBuilder.java:105)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addRule(KnowledgeBuilderImpl.java:1281)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.lambda$compileRulesLevel$3(KnowledgeBuilderImpl.java:1242)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl$$Lambda$1035/1743914198.accept(Unknown Source)
> at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
> at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
> at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1374)
> at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
> at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291)
> at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
> at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
> at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
> at java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:160)
> at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:174)
> at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
> at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileRulesLevel(KnowledgeBuilderImpl.java:1238)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileRules(KnowledgeBuilderImpl.java:1218)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileKnowledgePackages(KnowledgeBuilderImpl.java:1056)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildRules(KnowledgeBuilderImpl.java:2630)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.buildPackages(KnowledgeBuilderImpl.java:2565)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildPackages(CompositeKnowledgeBuilderImpl.java:109)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(CompositeKnowledgeBuilderImpl.java:99)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.buildKnowledgePackages(AbstractKieProject.java:238)
> at org.drools.compiler.kie.builder.impl.AbstractKieProject.verify(AbstractKieProject.java:65)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieProject(KieBuilderImpl.java:356)
> at org.drools.compiler.kie.builder.impl.KieBuilderImpl.buildKieModule(KieBuilderImpl.java:348)
> at org.kie.scanner.KieRepositoryScannerImpl.build(KieRepositoryScannerImpl.java:248)
> at org.kie.scanner.KieRepositoryScannerImpl.buildArtifact(KieRepositoryScannerImpl.java:198)
> at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:154)
> at org.kie.scanner.KieRepositoryScannerImpl.loadArtifact(KieRepositoryScannerImpl.java:149)
> - locked <0x00000006e6e94d50> (a org.kie.scanner.KieRepositoryScannerImpl)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.loadKieModuleFromMavenRepo(KieRepositoryImpl.java:192)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:138)
> at org.drools.compiler.kie.builder.impl.KieRepositoryImpl.getKieModule(KieRepositoryImpl.java:115)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:184)
> at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:176)
> at org.kie.server.services.impl.KieServerImpl.createContainer(KieServerImpl.java:269)
> - locked <0x00000006e6d9c1a0> (a org.kie.server.services.impl.KieContainerInstanceImpl)
> at org.kie.server.services.impl.ContainerManager.installContainersSync(ContainerManager.java:43)
> at org.kie.server.services.impl.ContainerManager.installContainers(ContainerManager.java:33)
> at org.kie.server.jms.ContainerManagerEJB.installContainers(ContainerManagerEJB.java:38)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:90)
> at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:101)
> at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.tx.EjbBMTInterceptor.handleInvocation(EjbBMTInterceptor.java:103)
> at org.jboss.as.ejb3.tx.BMTInterceptor.processInvocation(BMTInterceptor.java:58)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:40)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.singleton.SingletonComponentInstanceAssociationInterceptor.processInvocation(SingletonComponentInstanceAssociationInterceptor.java:53)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
> at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509)
> at org.jboss.as.ejb3.concurrency.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:110)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438)
> at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:609)
> at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53)
> at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
> at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.LogDiagnosticContextRecoveryInterceptor.processInvocation(LogDiagnosticContextRecoveryInterceptor.java:82)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422)
> at org.jboss.as.ejb3.component.interceptors.AsyncFutureInterceptorFactory$2$2.runInvocation(AsyncFutureInterceptorFactory.java:152)
> at org.jboss.as.ejb3.component.interceptors.AsyncInvocationTask.run(AsyncInvocationTask.java:81)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Found 1 deadlock.
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml
by Michael Biarnes Kiefer (Jira)
[ https://issues.jboss.org/browse/DROOLS-2254?page=com.atlassian.jira.plugi... ]
Michael Biarnes Kiefer updated DROOLS-2254:
-------------------------------------------
Fix Version/s: 7.27.0.Final
(was: 7.26.0.Final)
> Automate .proto files rebuild in pom.xml
> ----------------------------------------
>
> Key: DROOLS-2254
> URL: https://issues.jboss.org/browse/DROOLS-2254
> Project: Drools
> Issue Type: Task
> Components: tools
> Affects Versions: 7.5.0.Final
> Reporter: Dmitry Volodin
> Assignee: Dmitry Volodin
> Priority: Minor
> Fix For: 7.27.0.Final
>
>
> According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files.
> This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
