October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-677) Compression marshalling fails intermittently.

by Ron Sigal (JIRA)

Compression marshalling fails intermittently. --------------------------------------------- Key: JBREM-677 URL: http://jira.jboss.com/jira/browse/JBREM-677 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Boon) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta2 (Boon) When used with EJB's, CompressingUnMarshaller intermittently throws java.io.IOException: Not in GZIP format. -- 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, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-4646) Fix org.jboss.test.cluster.multicfg.web.field.test.StateTransferTestCase

by Brian Stansberry (JIRA)

Fix org.jboss.test.cluster.multicfg.web.field.test.StateTransferTestCase ------------------------------------------------------------------------ Key: JBAS-4646 URL: http://jira.jboss.com/jira/browse/JBAS-4646 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry -- 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, 7 months

2
10
0 / 0

[JBoss JIRA] Created: (JBCACHE-1122) Be able to define regions using regular expressions

by Manik Surtani (JIRA)

Be able to define regions using regular expressions --------------------------------------------------- Key: JBCACHE-1122 URL: http://jira.jboss.com/jira/browse/JBCACHE-1122 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Eviction Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Particularly useful once we have regions as a top-level construct, with region-specific configuration. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-968) Test on 80 node cluster

by Manik Surtani (JIRA)

Test on 80 node cluster ----------------------- Key: JBCACHE-968 URL: http://jira.jboss.com/jira/browse/JBCACHE-968 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1169) some methods in eviction queue classes have package-only visibility - can it be changed?

by dana enescu (JIRA)

some methods in eviction queue classes have package-only visibility - can it be changed? ---------------------------------------------------------------------------------------- Key: JBCACHE-1169 URL: http://jira.jboss.com/jira/browse/JBCACHE-1169 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 2.0.0.GA Reporter: dana enescu Assigned To: Manik Surtani Priority: Minor I have been trying to implement my own cache eviction policy. The most convenient way for me was to extend LFU, instead of implementing the interfaces from scratch. However, the ctor and the prune() method in LFUQueue have package-only visibility, so I had to do a nasty workaround. There may be similar issues in other classes of the eviction package. IMO it would be better that these methods are made either public or protected, depending on what you want to expose to the users. I did not report it as a bug but rather as a feature request, since I do not know the developer's intent. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability

by Elias Ross (JIRA)

Move component construction out of Cache into Configuration to allow for better configurability ----------------------------------------------------------------------------------------------- Key: JBCACHE-1024 URL: http://jira.jboss.com/jira/browse/JBCACHE-1024 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani There's a lot of logic embedded in CacheImpl.start() and create() as to what specific object instances are created. For example, the JGroups Channel, or the InterceptorChainFactory are directly constructed here and users have no control on this. A bunch of other objects are also created based on class names and whatnot; these are configurable to some extent but why does the CacheImpl need to know how to build these? What really should be done is allow the Configuration class to play the role as factory class, and take out all factory details from the Cache itself. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1011) memory based eviction policy

by Mircea Markus (JIRA)

memory based eviction policy ---------------------------- Key: JBCACHE-1011 URL: http://jira.jboss.com/jira/browse/JBCACHE-1011 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 2.1.0.GA As with Java5 java offers support for determining the size of objects. An memory based eviction policy can be written for this java version only. The basic idea is to let the user to specify the amount of memory he wants to use. -- 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, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-816) Create a CacheProxy to allow cache replication across WANs

by Manik Surtani (JIRA)

Create a CacheProxy to allow cache replication across WANs ---------------------------------------------------------- Key: JBCACHE-816 URL: http://jira.jboss.com/jira/browse/JBCACHE-816 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.3.0 This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). For more details and some brainstorming ideas, see: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-711) Replication eats out exception on the remote node

by Ben Wang (JIRA)

Replication eats out exception on the remote node ------------------------------------------------- Key: JBCACHE-711 URL: http://jira.jboss.com/jira/browse/JBCACHE-711 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.0.0 I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce. 21:51:32,490 INFO [TxInterceptor] There was a problem handling this request java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable. at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113) at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110) at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88) at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114) at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4548) Testsuite failures due to EJBs starting before datasource

by Brian Stansberry (JIRA)

Testsuite failures due to EJBs starting before datasource --------------------------------------------------------- Key: JBAS-4548 URL: http://jira.jboss.com/jira/browse/JBAS-4548 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB2 Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Dimitris Andreadis A number of unit tests are failing due to EJB2 deployment failures. The tests deploy an ear; contents of the ear are an ejb2 jar and a -ds.xml file. The ejb jar is deploying before the datasource, and thus ejb deployment fails when the datasource cannot be found in JNDI. See forum thread for detailed discussion. The testsuite failures due to this that I'm aware of are: org.jboss.test.testbeancluster.test.CacheInvalidationUnitTestCase org.jboss.test.testbeancluster.test.RetryInterceptorUnitTestCase org.jboss.test.testbeancluster.test.SingleRetryInterceptorUnitTestCase -- 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, 7 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007