December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1156) Ensure Stateless EJBs 2.1 Home define only one "create()" method with no arguments

by Andrew Lee Rubinger (JIRA)

Ensure Stateless EJBs 2.1 Home define only one "create()" method with no arguments ---------------------------------------------------------------------------------- Key: EJBTHREE-1156 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1156 Project: EJB 3.0 Issue Type: Bug Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Fix For: AS 5.0.0.Beta3 EJB3 Core Specification 4.6.8 Bullet 4: A session bean's remote home interface must define one or more create<METHOD> meth- ods. A stateless session bean must define exactly one create method with no arguments. Same applies for Local. -- 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

16 years, 4 months

2
5
0 / 0

[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

16 years, 4 months

2
4
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

16 years, 4 months

2
2
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

16 years, 4 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

16 years, 4 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

16 years, 4 months

2
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1228) Optimistic lock interceptor always acquires write locks for nodes in workspace at commit time

by Manik Surtani (JIRA)

Optimistic lock interceptor always acquires write locks for nodes in workspace at commit time --------------------------------------------------------------------------------------------- Key: JBCACHE-1228 URL: http://jira.jboss.com/jira/browse/JBCACHE-1228 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Optimistic Locking Affects Versions: 1.4.1.SP7 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.1.SP8, 2.1.0.GA Even when nodes in the workspace is not dirty. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBSER-99) The stream header should be optional

by David Lloyd (JIRA)

The stream header should be optional ------------------------------------ Key: JBSER-99 URL: http://jira.jboss.com/jira/browse/JBSER-99 Project: JBoss Serialization Issue Type: Feature Request Reporter: David Lloyd Assigned To: Clebert Suconic Priority: Minor Fix For: 1.1.0 Beta JBossObjectOutputStream writes a protocol header ("jbs1{") in its constructor. This can be a problem if your underlying stream isn't "ready" for this data yet. There should be an optional boolean parameter in the constructor that allows you to disable the header. A similar change would be made on the ObjectInput side. -- 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

16 years, 4 months

1
0
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

16 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1193) Adaptive buffering

by Tim Fox (JIRA)

Adaptive buffering ------------------ Key: JBMESSAGING-1193 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1193 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assigned To: Tim Fox Fix For: 2.0.0 Beta We can implement clever client side buffering where the consumer effectively starts off as slowConsumers = true (no buffering), then the time to process a message is measured and the buffer size computed dynamically according to that. -- 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

16 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007