[JBoss JIRA] (DROOLS-5353) Avoid ClassLoader retention in LambdaIntrospector
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5353?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi edited comment on DROOLS-5353 at 5/22/20 2:43 AM:
--------------------------------------------------------------------
-It will likely require to implement a custom WeakHashMap or to change the Map structure which seems to be overkill. I would rather deal with cache size. Closing.-
was (Author: tkobayashi):
It will likely require to implement a custom WeakHashMap or to change the Map structure which seems to be overkill. I would rather deal with cache size. Closing.
> Avoid ClassLoader retention in LambdaIntrospector
> -------------------------------------------------
>
> Key: DROOLS-5353
> URL: https://issues.redhat.com/browse/DROOLS-5353
> Project: Drools
> Issue Type: Enhancement
> Components: executable model
> Affects Versions: 7.37.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Change LambdaIntrospector$ClassIdentifier not to retain ClassLoader itself so that we no longer need to worry about ClassLoader leak.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5358) Add a way to define ResourceType inside kiebase
by Mario Fusco (Jira)
[ https://issues.redhat.com/browse/DROOLS-5358?page=com.atlassian.jira.plug... ]
Mario Fusco updated DROOLS-5358:
--------------------------------
Sprint: 2020 Week 22-24 (from May 25)
> Add a way to define ResourceType inside kiebase
> -----------------------------------------------
>
> Key: DROOLS-5358
> URL: https://issues.redhat.com/browse/DROOLS-5358
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Mario Fusco
> Priority: Major
>
> Step to reproduce
> 1) create a project with multiple pmml files, each in its own package (eg. resources/package_name/file.pmml)
> 2) create a kmodule xml and define one kiebase for each package
> 3) compile the kjar
> 4) in the kjar the files/classes are all in the proper place (i.e. in the expected package)
> 5) add the kjar in a new project
> 6) in the new project invoke
> KieServices.get().newKieClasspathContainer().getKieBase(kbaseName);
> The jar packages are inside the kieBase.getPackages(), but they are not marked as "PMMLType" packages - so it is necessary to invoke the (PMML)AssemblerService to wrap the content of the (jar) packages inside correct PMMLType packages and put them in the knowledge base
> The following snippet is a temporary workaround (inside CanonicalKieModule.createKieBase(KieBaseModelImpl, KieProject, ResultsImpl, KieBaseConfiguration))
> {code:java}
> for (KiePackage pk : pkgs) {
> // Workaround to "mark" already compiled packages (as found inside the kjar and retrieved by createKiePackages(kieProject, kBaseModel, messages, kBaseConf))
> // as "PMML" packages
> boolean isInternalKnowldgePackage = pk instanceof InternalKnowledgePackage;
> final InternalKnowledgePackage originalPackage = kieBase.getPackage(pk.getName());
> if (originalPackage != null && isInternalKnowldgePackage && ((InternalKnowledgePackage) pk).getResourceTypePackages().get(ResourceType.PMML) != null) {
> originalPackage.getResourceTypePackages().put(ResourceType.PMML, ((InternalKnowledgePackage) pk).getResourceTypePackages().get(ResourceType.PMML));
> } else if (originalPackage == null) {
> kieBase.addPackages(pkgs);
> }
> }
> {code}
> The idea is to get the "type" information from newly compiled package and put it in the existing one (that also contains al the other compiled classes).
> Ideally, we should be able to completely skip the (PMML)AssemblerService invocation (that recreate new packages)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (DROOLS-5353) Avoid ClassLoader retention in LambdaIntrospector
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5353?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi closed DROOLS-5353.
-------------------------------------
Fix Version/s: (was: 7.38.0.Final)
Resolution: Won't Do
It will likely require to implement a custom WeakHashMap or to change the Map structure which seems to be overkill. I would rather deal with cache size. Closing.
> Avoid ClassLoader retention in LambdaIntrospector
> -------------------------------------------------
>
> Key: DROOLS-5353
> URL: https://issues.redhat.com/browse/DROOLS-5353
> Project: Drools
> Issue Type: Enhancement
> Components: executable model
> Affects Versions: 7.37.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> Change LambdaIntrospector$ClassIdentifier not to retain ClassLoader itself so that we no longer need to worry about ClassLoader leak.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4979) WFLYSRV0137: No deployment content with hash
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4979?page=com.atlassian.jira.plug... ]
James Perkins commented on WFCORE-4979:
---------------------------------------
Yes. The error itself seems valid. The main thing in question is how the deployment got removed. I've attached just the standalone directory from the server and you can see in there are no messages logged where {{simple-servlet.war}} was undeployed. However I did use the server as a remote tester for some Arquillian tests and you can see that deployment being undeployed.
> WFLYSRV0137: No deployment content with hash
> --------------------------------------------
>
> Key: WFCORE-4979
> URL: https://issues.redhat.com/browse/WFCORE-4979
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: standalone.zip
>
>
> I saw the following when attempting to start a server.
> {code}
> jperkins@localhost ~/servers/wildfly-19.1.0.Final $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jperkins/servers/wildfly-19.1.0.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=com.yourkit,org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 11:43:21,055 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final-SNAPSHOT
> 11:43:21,410 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 11:43:21,421 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 11:43:21,545 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
> 11:43:22,184 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.11.4.Final
> 11:43:22,703 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,774 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 37) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "simple-servlet.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 7e2e9824daa6775b04ed1eb5b012c7372f69c4a6 is available in the deployment content repository for deployment 'simple-servlet.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 11:43:22,823 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 11:43:22,853 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 24ms
> {code}
> The deployment is there in the model, but doesn't appear to be in the file structure.
> {code}
> [standalone@embedded /] /deployment=simple-servlet.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{
> "hash" => bytes {
> 0x7e, 0x2e, 0x98, 0x24, 0xda, 0xa6, 0x77, 0x5b,
> 0x04, 0xed, 0x1e, 0xb5, 0xb0, 0x12, 0xc7, 0x37,
> 0x2f, 0x69, 0xc4, 0xa6
> },
> "archive" => undefined
> }],
> "enabled" => true,
> "name" => "simple-servlet.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "simple-servlet.war",
> "subdeployment" => undefined,
> "subsystem" => undefined
> }
> }
> {code}
> I've zipped up the server in case it helps. https://www.dropbox.com/s/an9wj3n41vr0m30/failed-deployment-wildfly-19.1....
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4979) WFLYSRV0137: No deployment content with hash
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4979?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-4979:
----------------------------------
Attachment: standalone.zip
> WFLYSRV0137: No deployment content with hash
> --------------------------------------------
>
> Key: WFCORE-4979
> URL: https://issues.redhat.com/browse/WFCORE-4979
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: standalone.zip
>
>
> I saw the following when attempting to start a server.
> {code}
> jperkins@localhost ~/servers/wildfly-19.1.0.Final $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jperkins/servers/wildfly-19.1.0.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=com.yourkit,org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 11:43:21,055 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final-SNAPSHOT
> 11:43:21,410 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 11:43:21,421 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 11:43:21,545 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
> 11:43:22,184 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.11.4.Final
> 11:43:22,703 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,774 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 37) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "simple-servlet.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 7e2e9824daa6775b04ed1eb5b012c7372f69c4a6 is available in the deployment content repository for deployment 'simple-servlet.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 11:43:22,823 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 11:43:22,853 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 24ms
> {code}
> The deployment is there in the model, but doesn't appear to be in the file structure.
> {code}
> [standalone@embedded /] /deployment=simple-servlet.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{
> "hash" => bytes {
> 0x7e, 0x2e, 0x98, 0x24, 0xda, 0xa6, 0x77, 0x5b,
> 0x04, 0xed, 0x1e, 0xb5, 0xb0, 0x12, 0xc7, 0x37,
> 0x2f, 0x69, 0xc4, 0xa6
> },
> "archive" => undefined
> }],
> "enabled" => true,
> "name" => "simple-servlet.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "simple-servlet.war",
> "subdeployment" => undefined,
> "subsystem" => undefined
> }
> }
> {code}
> I've zipped up the server in case it helps. https://www.dropbox.com/s/an9wj3n41vr0m30/failed-deployment-wildfly-19.1....
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4979) WFLYSRV0137: No deployment content with hash
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4979?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-4979:
----------------------------------
Attachment: (was: standalone.zip)
> WFLYSRV0137: No deployment content with hash
> --------------------------------------------
>
> Key: WFCORE-4979
> URL: https://issues.redhat.com/browse/WFCORE-4979
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
>
> I saw the following when attempting to start a server.
> {code}
> jperkins@localhost ~/servers/wildfly-19.1.0.Final $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jperkins/servers/wildfly-19.1.0.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=com.yourkit,org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 11:43:21,055 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final-SNAPSHOT
> 11:43:21,410 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 11:43:21,421 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 11:43:21,545 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
> 11:43:22,184 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.11.4.Final
> 11:43:22,703 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,774 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 37) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "simple-servlet.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 7e2e9824daa6775b04ed1eb5b012c7372f69c4a6 is available in the deployment content repository for deployment 'simple-servlet.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 11:43:22,823 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 11:43:22,853 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 24ms
> {code}
> The deployment is there in the model, but doesn't appear to be in the file structure.
> {code}
> [standalone@embedded /] /deployment=simple-servlet.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{
> "hash" => bytes {
> 0x7e, 0x2e, 0x98, 0x24, 0xda, 0xa6, 0x77, 0x5b,
> 0x04, 0xed, 0x1e, 0xb5, 0xb0, 0x12, 0xc7, 0x37,
> 0x2f, 0x69, 0xc4, 0xa6
> },
> "archive" => undefined
> }],
> "enabled" => true,
> "name" => "simple-servlet.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "simple-servlet.war",
> "subdeployment" => undefined,
> "subsystem" => undefined
> }
> }
> {code}
> I've zipped up the server in case it helps. https://www.dropbox.com/s/an9wj3n41vr0m30/failed-deployment-wildfly-19.1....
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (WFCORE-4979) WFLYSRV0137: No deployment content with hash
by James Perkins (Jira)
[ https://issues.redhat.com/browse/WFCORE-4979?page=com.atlassian.jira.plug... ]
James Perkins updated WFCORE-4979:
----------------------------------
Attachment: standalone.zip
> WFLYSRV0137: No deployment content with hash
> --------------------------------------------
>
> Key: WFCORE-4979
> URL: https://issues.redhat.com/browse/WFCORE-4979
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: James Perkins
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: standalone.zip
>
>
> I saw the following when attempting to start a server.
> {code}
> jperkins@localhost ~/servers/wildfly-19.1.0.Final $ ./bin/standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/jperkins/servers/wildfly-19.1.0.Final
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=com.yourkit,org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 11:43:21,055 INFO [org.jboss.modules] (main) JBoss Modules version 1.10.2.Final-SNAPSHOT
> 11:43:21,410 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
> 11:43:21,421 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
> 11:43:21,545 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
> 11:43:22,184 INFO [org.wildfly.security] (ServerService Thread Pool -- 24) ELY00001: WildFly Elytron version 1.11.4.Final
> 11:43:22,703 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,774 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 37) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
> 11:43:22,815 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "simple-servlet.war")]) - failure description: "WFLYSRV0137: No deployment content with hash 7e2e9824daa6775b04ed1eb5b012c7372f69c4a6 is available in the deployment content repository for deployment 'simple-servlet.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
> 11:43:22,823 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
> 11:43:22,853 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 24ms
> {code}
> The deployment is there in the model, but doesn't appear to be in the file structure.
> {code}
> [standalone@embedded /] /deployment=simple-servlet.war:read-resource
> {
> "outcome" => "success",
> "result" => {
> "content" => [{
> "hash" => bytes {
> 0x7e, 0x2e, 0x98, 0x24, 0xda, 0xa6, 0x77, 0x5b,
> 0x04, 0xed, 0x1e, 0xb5, 0xb0, 0x12, 0xc7, 0x37,
> 0x2f, 0x69, 0xc4, 0xa6
> },
> "archive" => undefined
> }],
> "enabled" => true,
> "name" => "simple-servlet.war",
> "owner" => undefined,
> "persistent" => true,
> "runtime-name" => "simple-servlet.war",
> "subdeployment" => undefined,
> "subsystem" => undefined
> }
> }
> {code}
> I've zipped up the server in case it helps. https://www.dropbox.com/s/an9wj3n41vr0m30/failed-deployment-wildfly-19.1....
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month