[JBoss JIRA] (DROOLS-1364) InMemorySessionFactory has apparent memory leak
by Maciej Swiderski (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1364?page=com.atlassian.jira.plugi... ]
Maciej Swiderski commented on DROOLS-1364:
------------------------------------------
first of all if you use rules only you should not use runtime manager. It's api is meant for jBPM use cases where kie session management is much more advanced (configuration wise). Second of all, you should dispose runtime engine after you're done with it making sure the ksession is then removed from runtime manager properly.
I'd recommend to not use runtime manager when you don't need to use jBPM. Further more, it will decrease number of dependencies that are jBPM specific.
> InMemorySessionFactory has apparent memory leak
> -----------------------------------------------
>
> Key: DROOLS-1364
> URL: https://issues.jboss.org/browse/DROOLS-1364
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 6.5.0.Final
> Reporter: Eli Israel
> Assignee: Maciej Swiderski
>
> I'm running drools with a runtime manager creating using PerRequest strategy and SessionCache turned on. (I process a LOT of requests but I want each one to be isolated)
> The SessionCache properly gets rid of sessions that have hung around too long, which is great.
> But the InMemorySessionFactory keeps a copy of every session it ever created, which -- it seems to me -- impedes garbage collection of unneeded, old sessions.
> It's possible I'm just reading this wrong, but examinations of running code using VisualVM show a LOT of RightTuple objects hanging around, attached to sessions and their GC root appears to be the InMemorySessionFactory.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2021) "ls /socket-binding-group=*" should print proper error message
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2021?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-2021:
-----------------------------------
IllegalArgumentException is due to resource result conversion "resourceResult.asPropertyList();" fails in [LsHandler.java|https://github.com/wildfly/wildfly-core/blob/master/cli/sr...]
result below can not and should not be convert to list:
{noformat}
{
"outcome" => "success",
"result" => {
"step-1" => {
"outcome" => "success",
"result" => [
"local-destination-outbound-socket-binding",
"remote-destination-outbound-socket-binding",
"socket-binding"
]
},
"step-2" => {
"outcome" => "success",
"result" => [{
"address" => [("socket-binding-group" => "standard-sockets")],
"outcome" => "success",
"result" => {
"default-interface" => "public",
"name" => "standard-sockets",
"port-offset" => expression "${jboss.socket.binding.port-offset:0}",
"local-destination-outbound-socket-binding" => undefined,
"remote-destination-outbound-socket-binding" => {"mail-smtp" => undefined},
"socket-binding" => {
"management-http" => undefined,
"management-https" => undefined,
"ajp" => undefined,
"http" => undefined,
"https" => undefined,
"txn-recovery-environment" => undefined,
"txn-status-manager" => undefined
}
}
}]
}
}
}
{noformat}
The error message can be more informative by providing command parameter.
But it's not like failure description of command: ls /subsystem=* . which fails due to _registry_ is null in [ReadChildrenTypesHandler.java|https://github.com/wildfly/wildfly-core/blo...] since there is no "concrete" resource inside that address.
> "ls /socket-binding-group=*" should print proper error message
> --------------------------------------------------------------
>
> Key: WFCORE-2021
> URL: https://issues.jboss.org/browse/WFCORE-2021
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 3.0.0.Alpha12
> Reporter: Chao Wang
> Assignee: Chao Wang
>
> "ls /socket-binding-group=*" should print proper error message. Similar operation "ls /subsystem=*" print good error message.
> {noformat}
> [standalone@localhost:9990 /] ls /subsystem=*
> {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0030: No resource definition is registered for address [(\"subsystem\" => \"*\")]"}}
> [standalone@localhost:9990 /] ls /socket-binding-group=*
> Exception for ls /socket-binding-group=*: java.lang.IllegalArgumentException
> [standalone@localhost:9990 /]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (WFCORE-2022) Can not invoke read-resource-description on multi target address with a resource named server.
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFCORE-2022:
-----------------------------------
Summary: Can not invoke read-resource-description on multi target address with a resource named server.
Key: WFCORE-2022
URL: https://issues.jboss.org/browse/WFCORE-2022
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 3.0.0.Alpha12
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
To reproduce, invoke:
{noformat}
/subsystem=undertow/server=*/http-listener=*:read-resource-description
{
"outcome" => "failed",
"result" => [],
"failure-description" => "WFLYCTL0030: No resource definition is registered for address [
(\"subsystem\" => \"undertow\"),
(\"server\" => \"*\")
]",
"rolled-back" => true
}
{noformat}
The address is valid but the operation fails at org.jboss.as.controller.operations.global.GlobalOperationHandlers.RegistrationAddressResolver#executeMultiTargetChildren when checking the condition:
{noformat}
if (path.getKey().equals(RUNNING_SERVER) && path.isWildcard() && newRemaining.size() > 0)
{noformat}
The check was added for WFCORE-948 but makes any multi target operation with a server resource fails (such as Undertow server or messaging-activemq server resources).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months