[JBossCache] - Re: JDBCCacheLoader Problems
by chicago_pool_dude
false
/
false
org.jboss.cache.loader.JDBCCacheLoader
<!-- same as the old CacheLoaderConfig attribute -->
cache.jdbc.table.name=jbosscache
cache.jdbc.table.create=true
cache.jdbc.table.drop=false
cache.jdbc.table.primarykey=jbosscache_pk
cache.jdbc.fqn.column=fqn
cache.jdbc.fqn.type=varchar(255)
cache.jdbc.node.column=node
cache.jdbc.node.type=blob
cache.jdbc.parent.column=parent
cache.jdbc.driver=oracle.jdbc.OracleDriver
cache.jdbc.url=jdbc:oracle:thin:@localhost:1521:XE
cache.jdbc.user=system
cache.jdbc.password=password
<!-- whether the cache loader writes are asynchronous -->
true
<!-- only one cache loader in the chain may set fetchPersistentState to true.
An exception is thrown if more than one cache loader sets this to true. -->
true
<!-- determines whether this cache loader ignores writes - defaults to false. -->
true
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960440#3960440
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960440
19 years, 9 months
[JBossCache] - Re: JDBCCacheLoader Problems
by chicago_pool_dude
Thanks for your earlier replies Mr Manik Surtani I tried what you suggested but still i have problems with JDBC Cache Loader...I am assumging that there is some problem with XML file i am posting it maybe you can let me know the problem. When i use a properties file and pass it on to JDBC Cache Loader class explictly i have no problem but when i configure using xml i am not able to bind the TreeCache to JDBC. Here is the XML
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- Sample TreeCache Service Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ==================================================================== -->
<!-- Defines TreeCache configuration -->
<!-- ==================================================================== -->
jboss:service=Naming
jboss:service=TransactionManager
<!--
Configure the TransactionManager
-->
org.jboss.cache.JBossTransactionManagerLookup
<!--
Node locking level : SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
-->
REPEATABLE_READ
<!--
Valid modes are LOCAL
REPL_ASYNC
REPL_SYNC
-->
LOCAL
true
<!-- Name of cluster. Needs to be the same for all clusters, in order
to find each other
TreeCache-Cluster
-->
<!-- Max number of milliseconds to wait for a lock acquisition -->
15000
<!-- Cache loader configuration -->
<!-- Name of the eviction policy class. -->
org.jboss.cache.eviction.LRUPolicy
<!-- Specific eviction policy configurations. This is LRU -->
5
<!-- Cache wide default -->
0
0
<!--
0
0
-->
false
/
false
org.jboss.cache.loader.JDBCCacheLoader
<!-- same as the old CacheLoaderConfig attribute -->
cache.jdbc.table.name=jbosscache
cache.jdbc.table.create=true
cache.jdbc.table.drop=false
cache.jdbc.table.primarykey=jbosscache_pk
cache.jdbc.fqn.column=fqn
cache.jdbc.fqn.type=varchar(255)
cache.jdbc.node.column=node
cache.jdbc.node.type=blob
cache.jdbc.parent.column=parent
cache.jdbc.driver=oracle.jdbc.OracleDriver
cache.jdbc.url=jdbc:oracle:thin:@localhost:1521:XE
cache.jdbc.user=system
cache.jdbc.password=seshu
<!-- whether the cache loader writes are asynchronous -->
true
<!-- only one cache loader in the chain may set fetchPersistentState to true.
An exception is thrown if more than one cache loader sets this to true. -->
true
<!-- determines whether this cache loader ignores writes - defaults to false. -->
true
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960439#3960439
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960439
19 years, 9 months
[JCA/JBoss] - Problems with postgresql and bytea columns
by andydale
Hi,
Are current message parsing application works perfectly when using Hypersonic as the datasource, but i am currently experiencing a lot of problems when trying to use PostgreSQL (8.1.4) as the datasource.
The currunt description/workflow of the application is as follows. A byte array of around 300 k is received and then an Object is created from it, this is then persisted (via javax.persistance.EntityManager.persist()) and then also flushed. The saved object is then queried and parsed further by the program. This is where the problem occurs because sometimes it cannot find the saved object even though you can view it via the db admin GUI. It is like it is trying to query the object before it is properly saved in the DB and thus returning null from the DB.
I am also getting lots of error/warning messages in the log file like the one below.
anonymous wrote : 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Warning: 0, SQLState: 00000
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] StartTransactionCommand
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Warning: 0, SQLState: 00000
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] ProcessUtility
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Warning: 0, SQLState: 00000
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] CommitTransactionCommand
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Warning: 0, SQLState: 00000
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] CommitTransaction
| 2006-07-24 15:02:21,204 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Warning: 0, SQLState: 00000
Has anybody else experienced a similar issue to this when using Postgres as the datasource, and if so how should i go about fixing it?
Thanks,
Andy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960436#3960436
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3960436
19 years, 9 months