November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4424) WebAuthentication:Generate a SSOID

by Anil Saldhana (JIRA)

WebAuthentication:Generate a SSOID ---------------------------------- Key: JBAS-4424 URL: http://jira.jboss.com/jira/browse/JBAS-4424 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.2.0.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.2.1.CR1 http://wiki.jboss.org/wiki/Wiki.jsp?page=WebAuthentication The feature needs to implement the sso stuff if it is desired by the user. At the least, ssoid needs to be generated and set on the session. The ssoid generation logic exists in AuthenticatorBase. -- 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

18 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-1224) Wrong Connection in JDBCCacheLoader

by Carsten Mjartan (JIRA)

Wrong Connection in JDBCCacheLoader ----------------------------------- Key: JBCACHE-1224 URL: http://jira.jboss.com/jira/browse/JBCACHE-1224 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP6, 1.4.1.SP5 Environment: 2 TreeCaches, each having 1 JDBCCacheLoader (passivation) using a different database Reporter: Carsten Mjartan Assigned To: Manik Surtani I configured 2 JBossCaches as stated above. Both use CacheLoaders which use different Database Backends (using hsqldb) and with table creation turned on. After Startup both tables are created using the cached connection of the first cacheloader, so the second cacheloader goes mad. I solved this for me by copying JDBCCacheLoader and replacing the ThreadLocal "connection" with a ThreadLocal Connection-Map using the url as the key, but I don't know if this may cause other problems (open connections?). -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1223) JDBCExtendedCacheLoader does not fully support RegionBasedMarshalling

by Carsten Mjartan (JIRA)

JDBCExtendedCacheLoader does not fully support RegionBasedMarshalling --------------------------------------------------------------------- Key: JBCACHE-1223 URL: http://jira.jboss.com/jira/browse/JBCACHE-1223 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.1.SP5 Environment: JBoss 4.2.2 with JBossCache 1.4.1SP5, own EvictionPolicy, RegionBasedMarshalling and ClassLoaders used, JDBCExtendedCacheLoader with cache passivation configured Reporter: Carsten Mjartan Assigned To: Manik Surtani JDBCExtendedCacheLoader does not override the loadNode() method to replace the thread's context classloader based on the region. So I',m getting classloading exceptions during cache eviction. loadNode() should change to protected for this to work. -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1168) Sometimes aquired locks are not released

by Jacek Halat (JIRA)

Sometimes aquired locks are not released ---------------------------------------- Key: JBCACHE-1168 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.SP4 Environment: Windows XP, jrockit90_150_06 Solaris 10 Reporter: Jacek Halat Assigned To: Jason T. Greene Attachments: TransactionStormTest.java Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache. Main loop: while (true) { for (int x = 0; x < 2; x++) { WorkThread t = new WorkThread(x == 1); threads.add(t); t.start(); } for (WorkThread separateThread : threads) { separateThread.join(); if (separateThread.getException() != null) { //separateThread.getException().getMessage(); } } int locksNum = getNumberOfLocksHeld(); // System.out.println("Locks="+locksNum); // checkpoint if (cache.getNumberOfLocksHeld()>0){ System.out.println("ERROR, locks="+locksNum); doDomethingOnCache(1); } assertEquals(0, locksNum); } Exception - after //checkpoint line numberOfLocks is grater than 0! JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. -- 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

18 years, 7 months

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback

by Jacek Halat (JIRA)

Acquired WL lock could be not released after async transaction rolback ---------------------------------------------------------------------- Key: JBCACHE-1183 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Environment: WindowsXP, jdk150_06 Reporter: Jacek Halat Assigned To: Manik Surtani In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again. -- 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

18 years, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-748) The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument.

by Nicolas Bielza (JIRA)

The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument. ------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-748 URL: http://jira.jboss.com/jira/browse/EJBTHREE-748 Project: EJB 3.0 Issue Type: Bug Environment: Embedded EJB3 container Reporter: Nicolas Bielza When looking up an entity bean, we get a proxy which implements equals() in a broken way: Here's an example: // Proxy NPE test: InitialContext ctx = new InitialContext(); Manager m = (Manager)ctx.lookup("ManagerAction/local"); try { if(m != null) { m.equals(null); } System.err.println("What bug ???"); } catch(NullPointerException e) { System.err.println("ProxyUtils NPE bug detected."); e.printStackTrace(); } And the output: ProxyUtils NPE bug detected. java.lang.NullPointerException at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:156) at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:137) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:92) at $Proxy34.equals(Unknown Source) at com.alligacom.nett.NetTransferAdminInterface.<init>(NetTransferAdminInterface.java:49) at com.alligacom.nett.NetTransferAdminInterface.main(NetTransferAdminI nterface.java:87) The incriminated line (156) in ProxyUtils is: return new Boolean(ih.toString().equals(args[0].toString())); and should be: return new Boolean(args[0] == null ? false : ih.toString().equals(args[0].toString())); -- 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

18 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-220) Support for nested properties

by Trustin Lee (JIRA)

Support for nested properties ----------------------------- Key: JBMICROCONT-220 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-220 Project: JBoss MicroContainer Issue Type: Feature Request Environment: N/A Reporter: Trustin Lee Priority: Minor Support for nested properties make beans XML more concise and easy to understand. Before: <bean name="beanX" ...> ... </bean> <bean name="propA" ...> <constructor><factory bean="beanX" method="getPropA"/></constructor> <property name="propB">...</property> </bean> <bean name="beanY" ...> <property name="propC"><inject bean="propA" property="propB"/></property> </bean> After: <bean name="beanX" ...> <property name="propA.propB">...</property> </bean> <bean name="beanY" ...>  <property name="propC"><inject bean="beanX" property="propA.propB"/></property>  <property name="propC ref="beanX.propA.propB"/> </bean> -- 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

18 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4928) Compare AS library names between 4.2.x & 5.0.x

by Dimitris Andreadis (JIRA)

Compare AS library names between 4.2.x & 5.0.x ----------------------------------------------- Key: JBAS-4928 URL: http://jira.jboss.com/jira/browse/JBAS-4928 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assigned To: Rajesh Rajasekaran Fix For: JBossAS-5.0.0.CR1 Check how similar libraries are deployed under different names in server/xxx/lib between 4.2.x & 5.0.x The names shouldn't change, unless there is a good reason for that. E.g. lib/servlet-api.jar in 4.2.x lib/javax.servlet.jar in 5.0.x -- 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

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4971) org.jboss.test.cmp2.audit.test.AuditUnitTestCase

by Dimitris Andreadis (JIRA)

org.jboss.test.cmp2.audit.test.AuditUnitTestCase ------------------------------------------------ Key: JBAS-4971 URL: http://jira.jboss.com/jira/browse/JBAS-4971 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: CMP service Reporter: Dimitris Andreadis Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 Looks like a security setup issue: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... -- 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

18 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3450) Fix org.jboss.test.webservice.jbws309.JBWS309TestCase running under JACC

by Anil Saldhana (JIRA)

Fix org.jboss.test.webservice.jbws309.JBWS309TestCase running under JACC ------------------------------------------------------------------------ Key: JBAS-3450 URL: http://jira.jboss.com/jira/browse/JBAS-3450 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Web Services Reporter: Anil Saldhana Assigned To: Thomas Diesler Fix For: JBossAS-5.0.0.Beta EJBContext.isCallerInRole checks now goes through the JACC layer. (http://jira.jboss.com/jira/browse/JBAS-2661) So there may be changes needed in the ejb-jar.xml wrt security role-refs -- 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

18 years, 7 months

5
4
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 2007