[JBoss JIRA] (DROOLS-2397) PMML modules have classloader issues in OSGi
by Tibor Zimányi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2397?page=com.atlassian.jira.plugi... ]
Tibor Zimányi commented on DROOLS-2397:
---------------------------------------
8
> PMML modules have classloader issues in OSGi
> --------------------------------------------
>
> Key: DROOLS-2397
> URL: https://issues.jboss.org/browse/DROOLS-2397
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.6.0.Final
> Environment: Equinox OSGi container, Java 8
> Reporter: Jens Reimann
> Assignee: Lance Leverich
> Labels: drools-core
>
> The drools PMML modules (drools-pmml and kie-pmml) both suffer from a few class loader issues when running inside an OSGi container.
> The KieBase built for transforming the PMML model to Drools model selects the wrong class loader (based on the context class loader). The JAXB instance creator fails with the same problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-9058) Inconsistent attribute desription of security domain
by Justin Cook (JIRA)
[ https://issues.jboss.org/browse/WFLY-9058?page=com.atlassian.jira.plugin.... ]
Justin Cook reassigned WFLY-9058:
---------------------------------
Assignee: (was: Justin Cook)
> Inconsistent attribute desription of security domain
> ----------------------------------------------------
>
> Key: WFLY-9058
> URL: https://issues.jboss.org/browse/WFLY-9058
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Juraj Duráni
> Priority: Minor
> Fix For: Awaiting Volunteers
>
>
> Some attributes have inconsistent description (obtained using 'read-resource-description' operation):
> - Missing module attribute:
> {code:plain|title=Missing module attribute}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/mapping=classic:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "Mapping configuration. Configures a list of mapping modules to be used for principal, role, attribute and credential mapping.",
> "deprecated" => {
> "since" => "1.3.0",
> "reason" => "The Security subsystem is deprecated and may be removed, significantly revised, or limited to managed domain legacy server use in future versions."
> },
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {"mapping-modules" => {
> "type" => LIST,
> "description" => "List of modules that map principal, role, and credential information",
> "expressions-allowed" => false,
> "nillable" => true,
> "deprecated" => {
> "since" => "1.2.0",
> "reason" => "Use of this attribute is deprecated, use resource"
> },
> "value-type" => {
> "code" => {
> "description" => "Class name of the module to be instantiated.",
> "type" => STRING,
> "nillable" => false,
> "min-length" => 1
> },
> "type" => {
> "description" => "Type of mapping this module performs. Allowed values are principal, role, attribute or credential..",
> "type" => STRING,
> "nillable" => false
> },
> "module-options" => {
> "description" => "List of module options containing a name/value pair.",
> "type" => OBJECT,
> "value-type" => STRING,
> "nillable" => true
> }
> },
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> }},
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {"mapping-module" => {
> "description" => "List of modules that map principal, role, and credential information",
> "model-description" => undefined
> }}
> }
> }
> {code}
> - Module description in policy-module refers to "login module"
> {code:plain|title=Inaccurate description}
> [standalone@localhost:9990 /] /subsystem=security/security-domain=other/authorization=classic/policy-module=a:read-resource-description
> {
> "outcome" => "success",
> "result" => {
> "description" => "List of authentication modules",
> "access-constraints" => {
> "sensitive" => {"security-domain" => {"type" => "core"}},
> "application" => {"security-domain" => {"type" => "security"}}
> },
> "attributes" => {
> "code" => {
> "type" => STRING,
> "description" => "Class name of the module to be instantiated.",
> "expressions-allowed" => false,
> "nillable" => false,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "flag" => {
> "type" => STRING,
> "description" => "The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.",
> "expressions-allowed" => true,
> "nillable" => false,
> "allowed" => [
> "required",
> "requisite",
> "sufficient",
> "optional"
> ],
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module" => {
> "type" => STRING,
> "description" => "Name of JBoss Module where the login module is located.",
> "expressions-allowed" => false,
> "nillable" => true,
> "min-length" => 1L,
> "max-length" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> },
> "module-options" => {
> "type" => OBJECT,
> "description" => "List of module options containing a name/value pair.",
> "expressions-allowed" => true,
> "nillable" => true,
> "value-type" => STRING,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "no-services"
> }
> },
> "operations" => undefined,
> "notifications" => undefined,
> "children" => {}
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4018) Remove alias and read-aliases in a batch causes blocking behavior
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4018?page=com.atlassian.jira.plugi... ]
Michal Petrov reassigned WFCORE-4018:
-------------------------------------
Assignee: Michal Petrov
> Remove alias and read-aliases in a batch causes blocking behavior
> -----------------------------------------------------------------
>
> Key: WFCORE-4018
> URL: https://issues.jboss.org/browse/WFCORE-4018
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Claudio Miranda
> Assignee: Michal Petrov
>
> Calling :remove-alias and :read-aliases on key-store resource in a composite operation makes the resource blocked.
> Generate two self signed certificates on a key-store resource and store it.
> {code}
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar,distinguished-name="cn=claudio,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar2,distinguished-name="cn=claudio2,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:store()
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> {
> "outcome" => "success",
> "result" => [
> "foobar2",
> "foobar"
> ]
> }
> {code}
> {code}
> batch
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:remove-alias(alias=foobar)
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> run-batch
> {code}
> The above just blocks the prompt.
> Then the blocking operation is show as:
> {code}
> /host=master/core-service=management/service=management-operations:read-resource(include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => {"active-operation" => {
> "352328021" => {
> "access-mechanism" => "NATIVE",
> "address" => [
> ("host" => "master"),
> ("core-service" => "management"),
> ("service" => "management-operations")
> ],
> "caller-thread" => "management-handler-thread - 1",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "read-resource",
> "running-time" => 10032404L
> },
> "-1467399640" => {
> "access-mechanism" => "NATIVE",
> "address" => [],
> "caller-thread" => "management-handler-thread - 2",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "composite",
> "running-time" => 260150849919L
> }
> }}
> }
> {code}
> After timeout there is the following message on CLI prompt
> {code}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-2
> Operation: /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> Failure: WFLYCTL0409: Execution of operation 'read-aliases' on remote process at address '[
> ("host" => "master"),
> ("server" => "server-three")
> ]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation
> {code}
> To fix the problem in HAL I will run it as individual commands.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2892) Session reset doesn't clear path memory
by Christian Liebhardt (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2892?page=com.atlassian.jira.plugi... ]
Christian Liebhardt commented on DROOLS-2892:
---------------------------------------------
I did a first test with a snapshot build of 7.12.0 (commit f3c90f6040714b4e9b34f8fffb3cdaeb4dc501ff) and the issue appears to be resolved. We will run a final test with 7.11.0.Final as soon as it's available.
> Session reset doesn't clear path memory
> ---------------------------------------
>
> Key: DROOLS-2892
> URL: https://issues.jboss.org/browse/DROOLS-2892
> Project: Drools
> Issue Type: Bug
> Reporter: Christian Liebhardt
> Assignee: Mario Fusco
>
> As discussed in https://groups.google.com/forum/#!topic/drools-usage/V8ypP1o5SwM :
> In order to reduce memory allocations we are calling _StatefulKnowledgeSessionImpl.reset()_ to bring a disposed session back into life. From our understanding this is the same method which the Drools session cache would use. During our tests we found that some of our rules don't trigger if we use this approach. We also found that the reset method leaves _PathMemory_ instances behind in the memory. As soon as we cleared the memory explicitly by calling _session.getNodeMemories().clear()_ after every _session.reset()_ the rules fired again as usual. So we are wondering if the current implementation of _session.reset()_ is incomplete.
> We are aware that _session.reset()_ is an internal method. However this issue should also affect the session cache feature of Drools. At the same time it would be nice to have a public interface to _session.reset()_ since in our application reusing a session is beneficial but we don't need the session cache as we can easily remember the last session which we used for processing and it seems more straightforward to just bring that one back to life instead of storing and retrieving it from a cache.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months