[JBoss JIRA] Created: (JBCACHE-1346) NullPointerException thrown by CacheInvocationDelegate
by Galder Zamarreno (JIRA)
NullPointerException thrown by CacheInvocationDelegate
------------------------------------------------------
Key: JBCACHE-1346
URL: http://jira.jboss.com/jira/browse/JBCACHE-1346
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Fix For: 2.2.0.GA
New bug introduced in JBossCache 2.2.x when setting up Singleton Store
Cache Loader.
Caused by: java.lang.NullPointerException
at org.jboss.cache.invocation.CacheInvocationDelegate.addCacheListener(CacheInvocationDelegate.java:247)
at org.jboss.cache.loader.SingletonStoreCacheLoader.setCache(SingletonStoreCacheLoader.java:144)
at org.jboss.cache.loader.CacheLoaderManager.setCacheInLoader(CacheLoaderManager.java:272)
at org.jboss.cache.loader.CacheLoaderManager.createCacheLoader(CacheLoaderManager.java:250)
at org.jboss.cache.loader.CacheLoaderManager.createCacheLoader(CacheLoaderManager.java:182)
at org.jboss.cache.loader.CacheLoaderManager.injectDependencies(CacheLoaderManager.java:90)
The problem arises from the fact that SingletonStoreCacheLoader tries to
add a cache listener before CacheInvocationDelegate has been initialised:
SingletonStoreCacheLoader:
@Override
public void setCache(CacheSPI c)
{
super.setCache(c);
c.addCacheListener(new SingletonStoreListener());
}
Listener probably needs to be added at some kind of start() method.
--
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, 2 months
[JBoss JIRA] Created: (JBAS-5526) DB Connections established which fail check-valid-connection-sql do not immediatly close their connection
by Dan Killey (JIRA)
DB Connections established which fail check-valid-connection-sql do not immediatly close their connection
---------------------------------------------------------------------------------------------------------
Key: JBAS-5526
URL: http://jira.jboss.com/jira/browse/JBAS-5526
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-4.2.2.GA
Environment: Red Hat Enterprise 5.1, MS SQL Server 2005
Reporter: Dan Killey
When a DB connection is attempted to be created where it is configured with check-valid-connection-sql, if the socket/connection succeeds but the check-valid-connection-sql statement fails a connection remains open until GC. In a large volume environment this can lead to many sockets being opened until GC occurs and can thus run into file handle limits.
If a valid TCP connection was established, but the SQL fails, I am suggesting the connection should also be closed at the time of failure, not waiting till GC.
--
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, 2 months
[JBoss JIRA] Updated: (JBAS-2793) Quick overview wrt. to used modules + version
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2793?page=all ]
Dimitris Andreadis updated JBAS-2793:
-------------------------------------
Fix Version/s: (was: JBossAS-5.0.0.CR1)
> Quick overview wrt. to used modules + version
> ---------------------------------------------
>
> Key: JBAS-2793
> URL: http://jira.jboss.com/jira/browse/JBAS-2793
> Project: JBoss Application Server
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Build System
> Environment: JBoss 4.x, OS: *x
> Reporter: Jens Elkner
> Assigned To: Dimitris Andreadis
> Priority: Optional
> Attachments: components2html.xsl, createComponentList.sh
>
>
> Sometimes one needs to know, which thirdparty modules are used by jboss and especially which version. So a simple html formatted overview would be handy.
> Since the info is already there, I made a simple script + stylesheet to create such an html file, which might packaged with the docs ...
> Feel free to use/modify it as you want ;-)
--
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, 2 months
[JBoss JIRA] Created: (JBCACHE-1342) For MC deployment, convert any potential beans into proper JavaBeans
by Galder Zamarreno (JIRA)
For MC deployment, convert any potential beans into proper JavaBeans
--------------------------------------------------------------------
Key: JBCACHE-1342
URL: http://jira.jboss.com/jira/browse/JBCACHE-1342
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Cache loaders
Affects Versions: 2.1.0.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Minor
Fix For: 2.2.0.GA
Some of the beans that can be injected into a JBC instance
via MC are not really proper beans. Some of the configuration
options that can be configured don't have the corresponding
set/get operations. Without them, you can't them in the
following fashion:
<property name="foo">bar</property>
For example, for JDBCCacheLoaderConfig, you can set the
following properties like that:
<properties>
cache.jdbc.table.primarykey=jbosscache_pk
cache.jdbc.fqn.column=fqn
cache.jdbc.fqn.type=character varying
cache.jdbc.node.column=node
cache.jdbc.node.type=bytea
cache.jdbc.parent.column=parentfqn
cache.jdbc.sql-concat=1||2
</properties>
Make JDBCCacheLoaderConfig a proper JavaBean and check
whether any other cache loaders have the same issue.
--
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, 2 months