[JBoss JIRA] (WFLY-1631) Duplicated message ids in web, undertow, jsf and osgi subsystems
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1631?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1631:
-----------------------------------------------
Farah Juma <fjuma(a)redhat.com> changed the Status of [bug 980823|https://bugzilla.redhat.com/show_bug.cgi?id=980823] from NEW to ASSIGNED
> Duplicated message ids in web, undertow, jsf and osgi subsystems
> -----------------------------------------------------------------
>
> Key: WFLY-1631
> URL: https://issues.jboss.org/browse/WFLY-1631
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF, OSGi, Web (Undertow)
> Affects Versions: 8.0.0.Alpha2
> Reporter: Ivo Studensky
> Assignee: Tomaz Cerar
> Priority: Critical
> Fix For: 8.0.0.CR1
>
>
> There is a lot of duplicated or different messages in JBossWeb and Undertow subsystems which has the same ids.
> different messages:
> {noformat}
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "JSF version slot '%s' is missing from module %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12604, value = "WildFlyConversationAwareViewHandler was improperly initialized. Expected ViewHandler parent.")
> {noformat}
> duplicated messages with the same content:
> {noformat}
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12600, value = "Could not load JSF managed bean class: %s")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12601, value = "JSF managed bean class %s has no default constructor")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12602, value = "Failed to parse %s, managed beans defined in this file will not be available")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version '%s'. Default version '%s' will be used instead.")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFLogger.java: @Message(id = 12603, value = "Unknown JSF version %s %s will be used instead")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12650, value = "Failed to load annotated class: %s")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12651, value = "Annotation %s in class %s is only allowed on classes")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12652, value = "Instance creation failed")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12653, value = "Instance destruction failed")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12654, value = "Thread local injection container not set")
> jsf/subsystem/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s")
> jsf/injection/src/main/java/org/jboss/as/jsf/JSFMessages.java: @Message(id = 12655, value = "@ManagedBean is only allowed at class level %s")
> web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18039, value = "Failed to create context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18039, value = "Failed to create context")
> web/src/main/java/org/jboss/as/web/WebMessages.java: @Message(id = 18040, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18040, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18200, value = "Failed to start welcome context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18200, value = "Failed to start welcome context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18201, value = "Failed to destroy welcome context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18202, value = "Error calling onStartup for servlet container initializer: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18203, value = "Error instantiating container component: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18204, value = "Clustering not supported, falling back to non-clustered session manager")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18205, value = "Cannot setup overlays for [%s] due to custom resources")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18206, value = "Webapp [%s] is unavailable due to startup errors")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18208, value = "Failed to start context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18208, value = "Failed to start context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18209, value = "Failed to destroy context")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18210, value = "Register web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> osgi/integration/http/src/main/java/org/jboss/as/osgi/httpservice/WebLogger.java: @Message(id = 18210, value = "Register web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18214, value = "Error during login/password authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18214, value = "Error during login/password authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18215, value = "Error during certificate authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18215, value = "Error during certificate authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18216, value = "Error during digest authenticate")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18216, value = "Error during digest authenticate")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18217, value = "Error obtaining authorization helper")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18218, value = "Exception in obtaining server authentication manager")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18219, value = "JASPI validation for unprotected request context %s failed")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18220, value = "Caught Exception: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18220, value = "Caught Exception: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18221, value = "Error forwarding to login page: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18222, value = "Error forwarding to error page: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18224, value = "Unregister web context: %s")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18224, value = "Unregister web context: %s")
> undertow/src/main/java/org/wildfly/extension/undertow/UndertowLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.")
> web/src/main/java/org/jboss/as/web/WebLogger.java: @Message(id = 18226, value = "Skipped SCI for jar: %s.")
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil edited comment on WFLY-3791 at 8/29/14 9:43 AM:
-------------------------------------------------------------
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file in Wildfly as base.
Take a look at my securtiy section
<subsystem xmlns="urn:jboss:domain:security:1.2">
<security-domains>
<security-domain name="pw_encrypted_MSSQL_CAS_DS" cache-type="default">
<authentication>
<login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">
<module-option name="username" value="XXXX"/>
<module-option name="password" value="XXX"/>
<module-option name="managedConnectionFactoryName" value="jboss.jca:service=TxCM,name=MSSQL_CAS_DS"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="other" cache-type="default">
<authentication>
<login-module code="Remoting" flag="optional">
<module-option name="password-stacking" value="useFirstPass"/>
</login-module>
<login-module code="RealmDirect" flag="required">
<module-option name="password-stacking" value="useFirstPass"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="jboss-web-policy" cache-type="default">
<authorization>
<policy-module code="Delegating" flag="required"/>
</authorization>
</security-domain>
<security-domain name="jboss-ejb-policy" cache-type="default">
<authorization>
<policy-module code="Delegating" flag="required"/>
</authorization>
</security-domain>
</security-domains>
</subsystem>
Cheers,
was (Author: ofbizbrazil):
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file
Cheers,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3791) Error on ModelControllerClient to list sections
by ofbiz brazil (JIRA)
[ https://issues.jboss.org/browse/WFLY-3791?page=com.atlassian.jira.plugin.... ]
ofbiz brazil commented on WFLY-3791:
------------------------------------
Hi Darran,
Is there any difference in standalone.xml that i need to put, because I migrated mine from jboss 7.1.1 to wildfly? Using the default file
Cheers,
> Error on ModelControllerClient to list sections
> -----------------------------------------------
>
> Key: WFLY-3791
> URL: https://issues.jboss.org/browse/WFLY-3791
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 8.1.0.Final
> Environment: Java 7
> Reporter: ofbiz brazil
> Assignee: Darran Lofthouse
>
> Hello,
> When there's a client trying to list a node for a security section, Wildfly says it does not exist but on Jboss 7.1.1 it works fine.
> Java Code:
> --------------
> final ModelNode request = new ModelNode();
> request.get(ClientConstants.OP).set("read-resource");
> request.get("recursive").set(true);
> request.get(ClientConstants.OP_ADDR).add("subsystem", "security");
> final ModelControllerClient client = ModelControllerClient.Factory.create(InetAddress.getByName("127.0.0.1"), 9999);
> final ModelNode response = client.execute(new OperationBuilder(request).build());
> final String section = response.get(ClientConstants.RESULT).get("security-domain")
> .get("pw_MSSQL_CAS_DS")
> Result:
> ---------
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014807: Management resource '[(\"subsystem\" => \"security\")]' not found",
> "rolled-back" => true
> }
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (AS7-3050) RESTEasy: Boolean configuration parameters don't reject non-sense content
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-3050?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-3050:
----------------------------------------------
Katerina Novotna <kanovotn(a)redhat.com> changed the Status of [bug 1121661|https://bugzilla.redhat.com/show_bug.cgi?id=1121661] from ON_QA to VERIFIED
> RESTEasy: Boolean configuration parameters don't reject non-sense content
> -------------------------------------------------------------------------
>
> Key: AS7-3050
> URL: https://issues.jboss.org/browse/AS7-3050
> Project: Application Server 7
> Issue Type: Bug
> Components: REST
> Affects Versions: 7.1.0.Beta1b
> Reporter: Pavel Janousek
> Assignee: Weinan Li
> Fix For: Awaiting Volunteers
>
>
> RESTEasy can be configured through several configuration options in WAR application deployment file WEB-INF/web.xml. These options which are type of Boolean (= true, false; maybe we should do support for 0 and 1 too), other invalid or non-sense setting should be rejected as invalid deployment description and a such application should not be deployed at all.
> Affected options are:
> - resteasy.scan
> - resteasy.scan.providers
> - resteasy.scan.resources
> - resteasy.use.builtin.providers
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-69) NullPointerException adding KeyStore to realm with {allow-resource-service-restart=true}
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFCORE-69?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFCORE-69:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1073866|https://bugzilla.redhat.com/show_bug.cgi?id=1073866] from POST to MODIFIED
> NullPointerException adding KeyStore to realm with {allow-resource-service-restart=true}
> ----------------------------------------------------------------------------------------
>
> Key: WFCORE-69
> URL: https://issues.jboss.org/browse/WFCORE-69
> Project: WildFly Core
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha4
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 1.0.0.Alpha6
>
>
> Executing the following CLI commands: -
> {code:title=CLI Commands}
> ./core-service=management/security-realm=SSLRealm:add
> ./core-service=management/security-realm=SSLRealm/server-identity=ssl:add(keystore-password=keystore_password, keystore-relative-to=jboss.server.config.dir, keystore-path=server.keystore){allow-resource-service-restart=true}
> {code}
> Results in the following NullPointerException being recorded: -
> {noformat}
> 15:23:28,074 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 6) WFLYCTL0013: Operation ("add") failed - address: ([
> ("core-service" => "management"),
> ("security-realm" => "SSLRealm"),
> ("server-identity" => "ssl")
> ]): java.lang.NullPointerException
> at org.jboss.as.domain.management.security.SecurityRealmAddHandler.addSSLServices(SecurityRealmAddHandler.java:596) [wildfly-domain-management-1.0.0.Alpha6-SNAPSHOT.jar:1.0.0.Alpha6-SNAPSHOT]
> at org.jboss.as.domain.management.security.SecurityRealmAddHandler.installServices(SecurityRealmAddHandler.java:188) [wildfly-domain-management-1.0.0.Alpha6-SNAPSHOT.jar:1.0.0.Alpha6-SNAPSHOT]
> at org.jboss.as.domain.management.security.SecurityRealmParentRestartHandler.recreateParentService(SecurityRealmParentRestartHandler.java:66) [wildfly-domain-management-1.0.0.Alpha6-SNAPSHOT.jar:1.0.0.Alpha6-SNAPSHOT]
> at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:74) [wildfly-controller-1.0.0.Alpha6-SNAPSHOT.jar:1.0.0.Alpha6-SNAPSHOT]
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:664) [wildfly-controller-1.0.0.Alpha6-SNAPSHOT.jar:1.0.0.Alpha6-SNAPSHOT]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-2358) setting <jacc-star-role-allow> in jboss-web.xml does not set allRolesMode to "authOnly"
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-2358?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-2358:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1022240|https://bugzilla.redhat.com/show_bug.cgi?id=1022240] from NEW to MODIFIED
> setting <jacc-star-role-allow> in jboss-web.xml does not set allRolesMode to "authOnly"
> ----------------------------------------------------------------------------------------
>
> Key: WFLY-2358
> URL: https://issues.jboss.org/browse/WFLY-2358
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (JBoss Web)
> Affects Versions: 8.0.0.Beta1
> Reporter: Derek Horton
> Assignee: Remy Maucherat
>
> I am trying to get only authentication (no authorization) to work for web application.
> In EAP 5, all that was required was to set the <role-name> to a '*' in
> the <security-constraint> of the web.xml. I tried this in EAP 6,
> however, it did not work.
> I then found the <jacc-star-role-allow> setting that goes in the
> jboss-web.xml. Unfortunately, adding this option did not cause the
> wildcard ('*') role-name to work for allowing any authenticated user
> to access the web application.
> Using the following system property does appear to work:
> org.apache.catalina.realm.RealmBase.ALL_ROLES_MODE=authOnly
> How reproducible:
> Everytime.
> Steps to Reproduce:
> 1. Set <role-name>*</role-name> in the security-contraint
> 2. Set <jacc-star-role-allow>true</jacc-star-role-allow> in jboss-web.xml
> 3. Set the security-domain so that no roles are assigned to a user
> 4. Attempt to access the web app
> Actual results:
> 403 - access denied
> Expected results:
> 200 - access allowed
> Additional info:
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (DROOLS-586) Drools doesn't calculate maximum expiration time properly
by kairat kushaev (JIRA)
[ https://issues.jboss.org/browse/DROOLS-586?page=com.atlassian.jira.plugin... ]
kairat kushaev updated DROOLS-586:
----------------------------------
Description:
Hello guys,
we found some contradiction between actual Drools behavior,
We use the following Rule:
import drools.test.Event;
dialect "mvel"
declare Event
@role(event)
@expires(10s)
end
rule "ExampleRule"
when
( $a : Event(name == "event a") ) and
( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
then
System.out.println("bingo!");
end
In the code above Drools should wait for the second event when the first event came. But it turns out that Drools doesn't wait for the second event because of @expires tag. The value in this tag is less than this after value.
According to documentation
"The engine will make this analysis for the whole rulebase and find the offset for every event type. Whenever an implicit expiration offset clashes with the explicit expiration offset, then engine will use the greater of the two."
but it is not calculating maximal expiration offset. Also we are using STREAM mode.
Could you please clarify the situation?
was:
Hello guys,
we found some contradiction between actual Drools behaviour,
We use the following Rule:
import com.opensoft.mom.domain.Event;
import java.util.List;
import java.util.ArrayList;
import com.opensoft.mom.domain.MessageModelMap;
global com.opensoft.mom.service.actions.Actions actions;
dialect "mvel"
declare Event
@role(event)
@expires(10m)
end
rule "ExampleRule"
when
((($Time_delay_order:Event((this.isBelongToEventFormat(38)) && (this.getComparableStringValue("XXXXX") == Event.getDecodedString("ok")))))and(($Time_delay_submit:Event((this.isBelongToEventFormat(39)) && (this.getComparableStringValue("XXXXXX") == Event.getDecodedString("ok")) && (this after[1ms,0h15m20s] $Time_delay_order)))))
then
List recipients0 = new ArrayList();
recipients0.add(Event.getDecodedString("XXXXXXXXXX(a)gmail.com"));
MessageModelMap template0 = new MessageModelMap();
template0.setValue("XXXXXXXXXX", $Time_delay_order.getComparableStringValue("XXXXX"));
template0.setValue("XXXXXXXXXX", $Time_delay_order.getComparableStringValue("XXXXX"));
String subject0 = Event.getDecodedString("");
actions.sendMail(recipients0, subject0, 14, template0);
end
In the code above Drools should wait for the second rule when the first rule has fired. But it turns out that Drools doesn't wait for the second Rule because of @expires tag. The value in this tag is less than this after value.
According to documentation
"The engine will make this analysis for the whole rulebase and find the offset for every event type. Whenever an implicit expiration offset clashes with the explicit expiration offset, then engine will use the greater of the two."
but it is not calculating maximal expiration offset.
Also we turned on STREAM mode.
Could you please clarify the situation?
> Drools doesn't calculate maximum expiration time properly
> ---------------------------------------------------------
>
> Key: DROOLS-586
> URL: https://issues.jboss.org/browse/DROOLS-586
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Linux, Java SE 1.7
> Reporter: kairat kushaev
> Assignee: Mark Proctor
> Fix For: 6.1.0.Final
>
>
> Hello guys,
> we found some contradiction between actual Drools behavior,
> We use the following Rule:
> import drools.test.Event;
> dialect "mvel"
> declare Event
> @role(event)
> @expires(10s)
> end
> rule "ExampleRule"
> when
> ( $a : Event(name == "event a") ) and
> ( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) )
> then
> System.out.println("bingo!");
> end
> In the code above Drools should wait for the second event when the first event came. But it turns out that Drools doesn't wait for the second event because of @expires tag. The value in this tag is less than this after value.
> According to documentation
> "The engine will make this analysis for the whole rulebase and find the offset for every event type. Whenever an implicit expiration offset clashes with the explicit expiration offset, then engine will use the greater of the two."
> but it is not calculating maximal expiration offset. Also we are using STREAM mode.
> Could you please clarify the situation?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months