[JBoss JIRA] (WFLY-976) Multi-JSF doesn't understand new modules structure
by Stan Silvert (JIRA)
[ https://issues.jboss.org/browse/WFLY-976?page=com.atlassian.jira.plugin.s... ]
Stan Silvert commented on WFLY-976:
-----------------------------------
I've attached the CLI install file for WildFly Alpha1 and MyFaces 2.1.11. Here are detailed instructions:
Download or build the latest AS8/WildFly
Copy install-myfaces-2.1.11.cli to wildfly-8.0.0.Alpha1-SNAPSHOT/bin
start AS8/WildFly
cd to wildfly-8.0.0.Alpha1-SNAPSHOT/bin
run cli and do these two commands:
[standalone@localhost:9999 /] deploy install-myfaces-2.1.11.cli
[standalone@localhost:9999 /] /subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-2.1.11)
Edit modules/system/layers/base/org/jboss/weld/core/main/modules.xml and change the JSF API slot to MyFaces:
<module name="javax.faces.api" slot="myfaces-2.1.11"/>
Do the same for modules/system/layers/base/org/jboss/as/weld/main/modules.xml
restart AS8/WildFly
Let me know how it goes!
> Multi-JSF doesn't understand new modules structure
> --------------------------------------------------
>
> Key: WFLY-976
> URL: https://issues.jboss.org/browse/WFLY-976
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Reporter: Stan Silvert
> Assignee: Stan Silvert
> Attachments: install-myfaces-2.1.11.cli
>
>
> With the new modules structure, Multi-JSF is looking for JSF implementations in the root of the modules directory instead of in modules/system/layers/base. The reason is that Multi-JSF relies on the module.path property which points to the root by default.
> The workaround is to go ahead and install the new JSF impl wherever you wish and add that directory to JBOSS_MODULEPATH in the startup script.
> See https://community.jboss.org/wiki/DesignOfAS7Multi-JSFFeature#comment-11789
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (SECURITY-734) Slow policy evaluation with a large number of policy sets
by Anil Saldhana (JIRA)
[ https://issues.jboss.org/browse/SECURITY-734?page=com.atlassian.jira.plug... ]
Anil Saldhana commented on SECURITY-734:
----------------------------------------
[~zinal] I like github because contributions such as yours is easier to merge into the project. Thanks a lot for the contribution. :)
> Slow policy evaluation with a large number of policy sets
> ---------------------------------------------------------
>
> Key: SECURITY-734
> URL: https://issues.jboss.org/browse/SECURITY-734
> Project: PicketBox
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: picketbox_xacml_2.0.8.Final
> Environment: RedHat Linux 6.0, WebSphere Application Server 7.0
> Reporter: Maxim Zinal
> Assignee: Anil Saldhana
> Fix For: picketbox_xacml_2.0.9.Final
>
> Attachments: fix-734.patch
>
>
> We suffer a performance problem in the evaluation of large XACML configuration. We use JBoss (Sun?) XACML library to process a large number of policy sets (over 2400 policy set files) using "deny-override" combining algorithm.
> Initially the number of policies was relatively small, but it increased with time, leading to performance degradation, with 100% CPU (single)core consumption.
> After running a code sample under Java profiler, we found that 99% of time is spent in method PolicySetFinderModule.findPolicy(URI, int, VersionConstraints, PolicyMetaData).
> This method walks through a list of AbstractPolicy objects, comparing an ID of each object with it's first argument. In our configuration the number of such objects is relatively large, leading to slow execution with high CPU consumption.
> We suggest replacing the list of AbstractPolicy with a HashMap. Our experiments show that total evaluation time reduces ~50 times with a HashMap over List implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (SECURITY-734) Slow policy evaluation with a large number of policy sets
by Anil Saldhana (JIRA)
[ https://issues.jboss.org/browse/SECURITY-734?page=com.atlassian.jira.plug... ]
Anil Saldhana updated SECURITY-734:
-----------------------------------
Fix Version/s: picketbox_xacml_2.0.9.Final
Affects Version/s: picketbox_xacml_2.0.8.Final
> Slow policy evaluation with a large number of policy sets
> ---------------------------------------------------------
>
> Key: SECURITY-734
> URL: https://issues.jboss.org/browse/SECURITY-734
> Project: PicketBox
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: picketbox_xacml_2.0.8.Final
> Environment: RedHat Linux 6.0, WebSphere Application Server 7.0
> Reporter: Maxim Zinal
> Assignee: Anil Saldhana
> Fix For: picketbox_xacml_2.0.9.Final
>
> Attachments: fix-734.patch
>
>
> We suffer a performance problem in the evaluation of large XACML configuration. We use JBoss (Sun?) XACML library to process a large number of policy sets (over 2400 policy set files) using "deny-override" combining algorithm.
> Initially the number of policies was relatively small, but it increased with time, leading to performance degradation, with 100% CPU (single)core consumption.
> After running a code sample under Java profiler, we found that 99% of time is spent in method PolicySetFinderModule.findPolicy(URI, int, VersionConstraints, PolicyMetaData).
> This method walks through a list of AbstractPolicy objects, comparing an ID of each object with it's first argument. In our configuration the number of such objects is relatively large, leading to slow execution with high CPU consumption.
> We suggest replacing the list of AbstractPolicy with a HashMap. Our experiments show that total evaluation time reduces ~50 times with a HashMap over List implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years