December 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMICROCONT-449) Enable security in tests once common-core 2.2.17 is out

by Kabir Khan (JIRA)

Enable security in tests once common-core 2.2.17 is out ------------------------------------------------------- Key: JBMICROCONT-449 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-449 Project: JBoss Microcontainer Issue Type: Task Reporter: Kabir Khan Assignee: Kabir Khan Fix For: JBossMC-2.2.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-7493) StatefulSessionUnitTestCase.testBadUserTx incorrect

by Jonathan Halliday (JIRA)

StatefulSessionUnitTestCase.testBadUserTx incorrect --------------------------------------------------- Key: JBAS-7493 URL: https://jira.jboss.org/jira/browse/JBAS-7493 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-6.0.0.M1 Reporter: Jonathan Halliday Fix For: JBossAS-6.0.0.M2 org.jboss.test.cts.test.StatefulSessionUnitTestCase.testBadUserTx incorrectly uses JMX lookup of tx statistics to verify the outcome. There are two issues with this approach 1) The exposure of tx statistics is not part of the tx integration API, it's an implementation detail of the tx manager, so it should not be relied upon. Perhaps a Synchronization instead? 2) Even if it is decided to continue with this close coupling of the test suite to a component implementation, the test does not enable statistics gathering. Since this is off by default for performance reasons, the tx counter will always be 0. This may cause the test to pass in cases where it should not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1002) EJB3-based version of the RetryInterceptor

by Brian Stansberry (JIRA)

EJB3-based version of the RetryInterceptor ------------------------------------------ Key: EJBTHREE-1002 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1002 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Looking for a conceptual equivalent to the EJB2 RetryInterceptor -- ability to reestablish a valid remoting client when the current FamilyClusterInfo does not contain any valid targets. If the approach is analogous to the RetryInterceptor case, what would be registered in JNDI is the FamilyClusterInfo itself (rather than the EJB2 Invoker). Looking this up in JNDI would provide the current list of targets. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2040) Portal Admin very slow

by frontline frontline (JIRA)

Portal Admin very slow ---------------------- Key: JBPORTAL-2040 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2040 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.5 Final Reporter: frontline frontline Attachments: jamon1.gif, jamon2.gif, jamon3.gif, server.zip We are noticing that the portal admin interface is starting to get very slow. It apparently has to do with the amount of "portal objects" in the database. The portal seems to create a dashboard for each user so if there are 10000 users there are also at least that many portal objects. In my tests I noticed that the database access takes about half of the time and the method refresh() in PortalObjectManagerBean is also very slow. This part is the slow part in that method (the iterator is probably the culprit, there seems to be some "custom" implementation for it). === Collection portals = getSelectedObject().getChildren(PortalObject.PORTAL_MASK); ArrayList portalList = new ArrayList(portals.size() + 1); for (Iterator iterator = portals.iterator(); iterator.hasNext();) { PortalObject o = (PortalObject)iterator.next(); SelectItem item = new SelectItem(o.getName()); portalList.add(item); } portalList.add(new SelectItem("", "no selection")); portalItems = (SelectItem[])portalList.toArray(new SelectItem[portalList.size()]); === This of course loops through all the "portal" type objects including all the user's dashboards. An easy optimization would be to discard the dashboard object looping when using the admin interface because the dashboards are naturally not needed there (maybe a new type of mask or something?). Other problems that would be good to check is the iterator (eg. hasNext() and getting the next object), and also why is there generated such a huge amount of SQL SELECTs (at least one per portal object). (The following assumes that I can add attachments to this issue) I have attached a zip file that can be extracted into a freshly installed (ie. extracted zip) portal installation (the AS bundled version of 2.6.5) The zip contains the "server" folder so extract it at the root of the portal installation and overwrite all files. After the portal is started you can go to the timing report page at: http://localhost:8080/test/jamon/jamonadmin.jsp There you can reset the counters, access a page in the admin console, and click refresh. After that you can sort the results by eg. the "total" column to see where time is spent. Currently it logs the sql-statements and the refresh method in PortlaObjectManagerBean. The timings for PortlaObjectManagerBean are split in three different parts with "*refresh" being the time for the whole method, "*portals" the time for iterating through the portals and "*pages" the time for looping through the pages. Now at this stage everything is OK and the response times are good. I have included a servlet that generates 10000 dashboards. Go to http://localhost:8080/test/create and wait (it takes a while, the console printsthe progress.) Load this page only once. After the dashboards have been created you can again test the admin console and check the JAmon report page for results. I have also included some screenshots from my testruns. The first (jamon1.gif) is from a newly installed instance listing the portals in the admin console. The second (jamon2.gif) is the same portal list after the dashboards have been created. The third (jamon3.gif) is after clicking "portlet instances" page. Notice how here is generated 40000 sql selects. Note that the included java db is quite fast at these selects. A mysql installation usually takes about 10 seconds for 10000 selects of this type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

5
13
0 / 0

[JBoss JIRA] Created: (JBAS-4022) EJB security-domain tag in jboss.xml for a domain defined in login-config.xml only works if java:/jaas/ prefix is absent, contrary to the documentation.

by Erica Kane (JIRA)

EJB security-domain tag in jboss.xml for a domain defined in login-config.xml only works if java:/jaas/ prefix is absent, contrary to the documentation. -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4022 URL: http://jira.jboss.com/jira/browse/JBAS-4022 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: Clustered Reporter: Erica Kane I created a security domain in the the JBoss server login-config.xml: <application-policy name = "webappDomain"> <authentication> <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required"> <module-option name = "dsJndiName">java:jdbc/web</module-option> <module-option name = "principalsQuery">select password from Users where username=?</module-option> <module-option name = "rolesQuery">select Role, 'Roles' from Roles where username=?</module-option> <module-option name = "unauthenticatedIdentity">guest</module-option> </login-module> </authentication> </application-policy> In jboss-web.xml, I have <?xml version="1.0" encoding="UTF-8"?> <jboss-web> <security-domain flushOnSessionInvalidation="true">java:/jaas/webappDomain</security-domain> <context-root>/web</context-root> </jboss-web> and this works perfectly for securing web pages. However, if I put the following tag in jboss.xml: <security-domain>java:/jaas/webappDomain</security-domain> I find that protected EJBs default to using the "other" security domain, as shown by error messages complaining about the missing user.properties file and so on (I have left "other" on the default setting of UsersRolesLoginModule). What DOES work is to put: <security-domain>webappDomain</security-domain> in jboss.xml without the java:/jaas/ prefix. However, this does not match the documentation. See http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch8.chapter.html example 8.8. Of course there the tag is set to java:/jaas/other, which for this bug would default to "other" anyway. I think it is terribly confusing to have jboss.xml and jboss-web.xml using different forms for the security-domain, but even if this is necessary for some reason it should be corrected in the documentation. Other people appear to have run into this as well: http://forum.java.sun.com/thread.jspa?threadID=773530 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-7585) Remove farm/cluster-examples-service.xml

by Brian Stansberry (JIRA)

Remove farm/cluster-examples-service.xml ---------------------------------------- Key: JBAS-7585 URL: https://jira.jboss.org/jira/browse/JBAS-7585 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M2 This do-nothing file gets deployed with each "all" config boot. Get rid of it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7497) optional dependencies for jboss-as-distribution

by Michael Brackx (JIRA)

optional dependencies for jboss-as-distribution ----------------------------------------------- Key: JBAS-7497 URL: https://jira.jboss.org/jira/browse/JBAS-7497 Project: JBoss Application Server Issue Type: Patch Security Level: Public (Everyone can see) Components: Build System Affects Versions: JBossAS-6.0.0.M1 Reporter: Michael Brackx Assignee: Paul Gier Modules depending on jboss-as-distribution probably do not want all its dependecnies as they are already in the zip. I would suggest marking the dependencies as optional in the pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-3942) twiddle.sh should read run.conf - and other small ehancements

by Paul Jenner (JIRA)

twiddle.sh should read run.conf - and other small ehancements ------------------------------------------------------------- Key: JBAS-3942 URL: http://jira.jboss.com/jira/browse/JBAS-3942 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.5.GA Reporter: Paul Jenner The twiddle.sh script should read environment variables from run.conf in the same way as the startup and shutdown scripts do - e.g. JAVA_HOME and JAVA. Additionally twiddle.sh should honous the JAVA environment variable instead of overwriting it with $JAVA_HOME/bin/java or "java". This makes it consistent with startup and shutdown which do honour JAVA. Finally the header should be changed from JBoss Shutdown script to JBoss twiddle script :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (GPD-382) Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier

by Jiri Pechanec (JIRA)

Add support for globalProcessScope and process-scope parameters in EsbActionHandler and EsbNotifier --------------------------------------------------------------------------------------------------- Key: GPD-382 URL: https://jira.jboss.org/jira/browse/GPD-382 Project: jBPM GPD Issue Type: Feature Request Components: jpdl Affects Versions: jBPM jPDL Designer 3.1.7 Reporter: Jiri Pechanec Assignee: Koen Aers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (GPD-358) Create jBPM Project Configuration Wizard

by Koen Aers (JIRA)

Create jBPM Project Configuration Wizard ---------------------------------------- Key: GPD-358 URL: https://jira.jboss.org/jira/browse/GPD-358 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Reporter: Koen Aers Assignee: Koen Aers Fix For: jBPM jPDL Designer 4.1 This wizard can be launched from the project popup menu in the Java/J2EE/Resources perspective. It will import all the libraries from the currently configured runtime. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2009