November 2006 - jboss-jira - Jboss List Archives

Mail Delivery System

by mancy thomas

Mail transaction failed. Partial message is available.

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-485) Refactor the current Collection classes (list and set)

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-485?page=comments#action_12346353 ] Ben Wang commented on JBCACHE-485: ---------------------------------- Elias, looks like you got your cvs right back and checked it in already? -Ben > Refactor the current Collection classes (list and set) > ------------------------------------------------------ > > Key: JBCACHE-485 > URL: http://jira.jboss.com/jira/browse/JBCACHE-485 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Priority: Critical > Fix For: PojoCache > > Attachments: icache.diff, set.diff > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Current implementation of Collection uses direct coupling to the cache store indices. E.g., we map them into subtree according to index ordering. This is not very desirable for performance reason. We should consider to provide a indirect mapping such that it is considered a graph instead of ordered tree. > Or we should investigate whether it is possible to use a proxy operates on java.util.* classes such that we don't need to have our own implementation. The JDK lincense aside, ArrayList, e.g., uses an internal transient array. Is it possible to "aspectize" on that array only? -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-627) Fix org.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase failure.

by Ron Sigal (JIRA)

Fix org.jboss.test.remoting.transport.multiplex.MultiplexInvokerShutdownTestCase failure. ----------------------------------------------------------------------------------------- Key: JBREM-627 URL: http://jira.jboss.com/jira/browse/JBREM-627 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Priority: Minor Fix For: 2.2.0.Alpha3 (Bluto) It seems that MultiplexInvokerShutdownTestCase is failing because once the client finishes, TestDriver unilaterally shuts down the server. In the case of MultiplexInvokerShutdownTestCase, the server also has a test method, which isn't given enough time to finish, so the test fails and reports " Got server results = false". -- 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

19 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-327) JBossStringBuilder.deleteCharAt always fails

by David Lloyd (JIRA)

JBossStringBuilder.deleteCharAt always fails -------------------------------------------- Key: JBBUILD-327 URL: http://jira.jboss.com/jira/browse/JBBUILD-327 Project: JBoss Build System Issue Type: Bug Affects Versions: JBossRetro-1.0.4.GA Reporter: David Lloyd Assigned To: David Lloyd Fix For: JBossRetro-1.0.5.GA JBossStringBuilder.deleteCharAt calls up to JBossStringBuilder.delete, setting the "end" parameter to 1. Unfortunately, this makes delete() fail because end is less than start for most values of start. -- 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

19 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1087) org.jboss.portal.test.wsrp.v1.producer.MarkupTestCase test failure

by Rajesh Rajasekaran (JIRA)

org.jboss.portal.test.wsrp.v1.producer.MarkupTestCase test failure ------------------------------------------------------------------ Key: JBPORTAL-1087 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1087 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran Assigned To: Chris Laprun Priority: Critical Fix For: 2.6 Final Test Case: testGetMarkupWithDispatcherPortlet Error: expected:<...> but was:< ...> junit.framework.ComparisonFailure: expected:<...> but was:<...> at org.jboss.portal.test.wsrp.v1.producer.MarkupTestCase.checkMarkupResponse(MarkupTestCase.java:418) at org.jboss.portal.test.wsrp.v1.producer.MarkupTestCase.testGetMarkupWithDispatcherPortlet(MarkupTestCase.java:349) The failure is with jboss-4.0.4.GA. I see the above test was fixed in the CC run from 15 Oct to 16Oct. http://cruisecontrol.jboss.com/cc/buildresults/jboss-portal-2.6-testsuite Probably the fixes were not included in the tag. https://svn.jboss.org/repos/portal/tags/JBoss_Portal_2_6_0_SNAPSHOT1/ -- 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

19 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3832) CMR Relationships not updated after rollback

by Jay Perkins (JIRA)

CMR Relationships not updated after rollback -------------------------------------------- Key: JBAS-3832 URL: http://jira.jboss.com/jira/browse/JBAS-3832 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service Affects Versions: JBossAS-4.0.4.GA Environment: Windows XP Professional Version 5.1 Service Pack 2 Reporter: Jay Perkins Assigned To: Alexey Loubyansky After alot of research, I have come to the following conclusion. Performing a rollback does not rollback any changes made to a CMR relationship altered in concurrent transactions. The changes made to the database seem to be rolled back, but the entity that contains the CMR relationship will still contain the association. Entity of type A has one to many relationship with Entity of type B Start Transaction 1 Load Entity A1 Create Entity B1 Add Entity B1 to Entity A1 CMR relationship Suspend Transaction 1 Start Transaction 2 Create Entity B2 Add Entity B2 to Entity A1 Rollback Transaction 2 Resume Transaction 1 Call CMR relationship to get B entities from A1 Returns RelationSet with 2 Entities Get NoSuchObjectLocalException when accesing CMP field from entity B2 found in the returned RelationSet because the creation of B2 was rolled back but the relationship between A1 and B2 still existed in memory. Conclusion: The CMR relationship is not being cleaned up when Transaction 2 is rolled back. Transaction 1 will get a RelationSet that contains a reference to the rolled back entity B2. If you use the per transaction entity instance cache (to jboss.xml below) <instance-cache>org.jboss.ejb.plugins.PerTxEntityInstanceCache</instance-cache> You will avoid the problem because each transaction is working on a separate instance of the entity. However, this is not a real workaround, because a side effect is that you also would not see commits that occurred in transaction 2, within transaction 1. -- 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

19 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3833) Cannot unregister HAMembershipListener

by Brian Stansberry (JIRA)

Cannot unregister HAMembershipListener -------------------------------------- Key: JBAS-3833 URL: http://jira.jboss.com/jira/browse/JBAS-3833 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 org.jboss.ha.framework.server.HAPartitiomImpl.java: public void unregisterMembershipListener(HAMembershipListener listener) { boolean isAsynch = (this.allowSyncListeners == false) || (listener instanceof AsynchHAMembershipListener) || (listener instanceof AsynchHAMembershipExtendedListener); if( isAsynch ) { synchronized(this.asynchListeners) { this.asynchListeners.add(listener); } } else { synchronized(this.synchListeners) { this.synchListeners.add(listener); } } } "synchListeners.add" should be "synchListeners.remove" -- 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

19 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-3826) Add core libs to repository

by Thomas Diesler (JIRA)

Add core libs to repository --------------------------- Key: JBAS-3826 URL: http://jira.jboss.com/jira/browse/JBAS-3826 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.5.GA Reporter: Thomas Diesler Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA There is no 4.0.5.GA in http://repository.jboss.com/jbossas/core-libs/ -- 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

19 years, 6 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=all ] Anil Saldhana updated JBAS-1824: -------------------------------- Fix Version/s: (was: JBossAS-4.0.5.SP1 ) Adding this to 4.2.0 release as this is not a bug fix but a new feature, > JACC: <role-name>*</role-name> in web.xml > ----------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Priority: Minor > Fix For: JBossAS-4.2.0.CR1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-1824) JACC: <role-name>*</role-name> in web.xml

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1824?page=comments#action_12346329 ] Dimitris Andreadis commented on JBAS-1824: ------------------------------------------ If this is a new feature it should really go in the 4.2.0.CR1 release. > JACC: <role-name>*</role-name> in web.xml > ----------------------------------------- > > Key: JBAS-1824 > URL: http://jira.jboss.com/jira/browse/JBAS-1824 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Security > Affects Versions: JBossAS-4.0.2 Final > Environment: - > Reporter: Roland R?z > Assigned To: Anil Saldhana > Priority: Minor > Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > In some cases I wish to do authentication without authorisation. For example everybody has access to my web-resource, but I want to know who she/he is. > Therefore the accessing user must login. > So my web.xml contains the following snippet: > ... > <security-constraint> > <web-resource-collection> > <web-resource-name>Protected Helloworld example</web-resource-name> > <description/> > <url-pattern>/servlet/HelloWorldExample</url-pattern> > <http-method>POST</http-method> > <http-method>GET</http-method> > </web-resource-collection> > <auth-constraint> > <role-name>*</role-name> > </auth-constraint> > </security-constraint> > <login-config> > <auth-method>BASIC</auth-method> > <realm-name>public</realm-name> > </login-config> > ... > The web app runs with this configuration in Tomcat 5.5.8 standalone but not in Jboss. > To run it in Jboss I have to add the following element: > <security-role> > <role-name>aRole</role-name> > </security-role> > The JACC spec (section 3.1.3.1, paragraph 3)states : > " ?. When an auth-constraint names the reserved role-name, "*", all of the patterns in the containing security-constraint must be combined with all of the roles defined in the web application." > JBoss implemented this by combining all of the patterns with all roles defined in the web.xml and assumes that each role has to be defined in the web.xml. > But the web applications roles are probably defined in other files than the web.xml. In our case we use JACC with an external authentication provider. And each time, the roles changes, I also would have to modify the web.xml. > It is desirable if the auth-contraint with the role-name "*" acceppts "all" roles and not only those that are defined in the web.xml. > Or is this a JACC spec issue? > Regards, > Andrea -- 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

19 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2006