You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-users@jakarta.apache.org by danparker <da...@chordiant.com> on 2008/08/08 05:25:53 UTC
JDBC not working as expected
http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
cache_FDN_WithJDBC.ccf
We've got three cache regions we want to have the contents in memory(for
performance) and spooled out to the database so that we can recover in a
failover situation. Attached is the configuration file. We are seeing the
memory cache fill up but nothing is going into the database.
I've set the DiskUsagePattern=update and IsSpool=True - is there something
else I'm missing?
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Aaron
The stats are showing that the JDBC cache is working - this is with
diskusagepatternname=swap. Although I never saw anything go into the
database only purgatory.
Detail for region [InteractionControllerProcessCache]
All Regions
Key Eternal? Create time Max Life (s) Till Expiration (s)
[GAN: groupId=[groupId=InteractionControllerProcessCache,
InteractionControllerProcessCache], attrName=-1252094005] false 8/13/08
11:16 PM 28800 28798 View | Remove
[GAN: groupId=[groupId=InteractionControllerProcessCache,
InteractionControllerProcessCache], attrName=generic_PG-1252094005] false
8/13/08 11:16 PM 28800 28798 View | Remove
Stats for region [InteractionControllerProcessCache]
Region Name = InteractionControllerProcessCache
HitCountRam = 20
HitCountAux = 0
---------------------------LRU Memory Cache
List Size = 2
Map Size = 2
Put Count = 13
Hit Count = 20
Miss Count = 19
---------------------------JDBC/Abstract Disk Cache
Update Count = 1
Get Count = 19
Size = 0
Active DB Connections = 0
Idle DB Connections = 2
DB URL = jdbc:oracle:thin:@ncddb-lod1613.nam.nsroot.net:1526:CHRDANT1
Purgatory Hits = 0
Purgatory Size = 1
Working = true
Alive = true
Empty = true
When I set it to UPDATE nothing makes it into the JDBC cache, shouldn't
every put get added to memory and the JDBC cache, that's the behaviour we
are after.
I set the MaxObjects for the memory cache to 4 and the diskUsuagePattern to
UPDATE and these are the stats
Detail for region [InteractionControllerProcessCache]
All Regions
Key Eternal? Create time Max Life (s) Till Expiration (s)
[GAN: groupId=[groupId=InteractionControllerProcessCache,
InteractionControllerProcessCache], attrName=generic_PG-1252156007] false
8/13/08 11:48 PM 28800 28799 View | Remove
[GAN: groupId=[groupId=InteractionControllerProcessCache,
InteractionControllerProcessCache], attrName=-1252156008] false 8/13/08
11:48 PM 28800 28798 View | Remove
[GAN: groupId=[groupId=InteractionControllerProcessCache,
InteractionControllerProcessCache], attrName=-1252156007] false 8/13/08
11:48 PM 28800 28781 View | Remove
Stats for region [InteractionControllerProcessCache]
Region Name = InteractionControllerProcessCache
HitCountRam = 39
HitCountAux = 0
---------------------------LRU Memory Cache
List Size = 3
Map Size = 3
Put Count = 21
Hit Count = 39
Miss Count = 26
---------------------------JDBC/Abstract Disk Cache
Update Count = 1
Get Count = 26
Size = 0
Active DB Connections = 0
Idle DB Connections = 1
DB URL = jdbc:oracle:thin:@ncddb-lod1613.nam.nsroot.net:1526:CHRDANT1
Purgatory Hits = 0
Purgatory Size = 1
Working = true
Alive = true
Empty = false
Size = 3
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975352.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
It looks like we are using the putInGroup and getFromGroup so we can use the
list api that returns all the keys in the cache. We're using JCS in this
instance in a security system so we can have very fast access to things like
getAllUsersforRole. Any plans to add connivence API's like getGroupKeys to
the CacheAccess when you deprecate GroupCacheAccess (it's not showing the
javadoc as deprecated).
Dan
Aaron Smuts wrote:
>
> Good. Sorry about the bug. We really need to formally deprecate the
> group code, if it isn't already.
>
> Cheers,
>
> Aaron
>
>
> --- On Thu, 8/14/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Thursday, August 14, 2008, 2:45 PM
>> Aaron
>>
>> Your right it was the groups that caused the issue. As soon
>> as I took out
>> the groups the JDBCDiskCache started working. It was
>> basically an exception
>> whilst prepare statement the exception that was going
>> uncaught. It was
>> getting the element attributes which in this case were
>> group related and it
>> was expecting.
>>
>> * Case closed *
>>
>> Thanks for your help. We've been grappling with
>> failover for our production
>> environment.
>>
>>
>>
>> Aaron Smuts wrote:
>> >
>> > Hmmn. This might be a problem with groups and the
>> JDBC disk cache. I'll
>> > have to look into it. In any case, groups are
>> deprecated. I don't
>> > recommend using them.
>> >
>> > Aaron
>> >
>> >
>> > --- On Wed, 8/13/08, danparker
>> <da...@chordiant.com> wrote:
>> >
>> >> From: danparker
>> <da...@chordiant.com>
>> >> Subject: Re: JDBC not working as expected
>> >> To: jcs-users@jakarta.apache.org
>> >> Date: Wednesday, August 13, 2008, 10:02 PM
>> >> When I sent the tryBeforeInsert=true and
>> MaxPurgatory to 10
>> >> and I exceed that
>> >> I get the following exception
>> >>
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> >> Exception in thread
>> >>
>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>> >> java.lang.ClassCastException:
>> >> org.apache.jcs.engine.control.group.GroupAttrName
>> >> incompatible with
>> >> java.lang.String
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> at
>> >>
>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>> >>
>> >> Aaron Smuts wrote:
>> >> >
>> >> > Call get stats and see if the auxiliary is in
>> error.
>> >> Look for errors and
>> >> > warnings in the logs.
>> >> >
>> >> > Aaron
>> >> >
>> >> >
>> >> > --- On Tue, 8/12/08, danparker
>> >> <da...@chordiant.com> wrote:
>> >> >
>> >> >> From: danparker
>> >> <da...@chordiant.com>
>> >> >> Subject: Re: JDBC not working as expected
>> >> >> To: jcs-users@jakarta.apache.org
>> >> >> Date: Tuesday, August 12, 2008, 1:52 PM
>> >> >> We are using version 1.3.
>> >> >>
>> >> >> We've changed DiskUsagePattern to
>> >> DiskUsagePatternName
>> >> >> but it had not
>> >> >> effect. Still nothing in the database.
>> >> >>
>> >> >> I'm building a workspace were I can
>> test this
>> >> >> independant of our load test
>> >> >> environment.
>> >> >>
>> >> >>
>> >> >>
>> >> >> hanasakijiji wrote:
>> >> >> >
>> >> >> > What version of JCS? Are you seeing
>> this
>> >> bug?
>> >> >> >
>> >> >>
>> >>
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >> >> >
>> >> >>
>> >>
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> >> >> > *** is short not String - looks like
>> they
>> >> come from an
>> >> >> enum or public
>> >> >> > static short ....
>> >> >> >
>> >> >> > might try testBeforeInsert=true and
>> see if
>> >> any selects
>> >> >> are hitting the
>> >> >> > DB at all from the database logs.
>> >> >> >
>> >> >> > Let us know if you find the solution
>> and what
>> >> it is.
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Aug 7, 2008 at 11:25 PM,
>> danparker
>> >> >> <da...@chordiant.com>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >> >> >> cache_FDN_WithJDBC.ccf
>> >> >> >>
>> >> >> >> We've got three cache
>> regions we want
>> >> to have
>> >> >> the contents in memory(for
>> >> >> >> performance) and spooled out to
>> the
>> >> database so
>> >> >> that we can recover in a
>> >> >> >> failover situation. Attached is
>> the
>> >> configuration
>> >> >> file. We are seeing the
>> >> >> >> memory cache fill up but nothing
>> is going
>> >> into the
>> >> >> database.
>> >> >> >>
>> >> >> >> I've set the
>> DiskUsagePattern=update
>> >> and
>> >> >> IsSpool=True - is there
>> >> >> >> something
>> >> >> >> else I'm missing?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> View this message in context:
>> >> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >> >> >> Sent from the JCS - Users
>> mailing list
>> >> archive at
>> >> >> Nabble.com.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> >> To unsubscribe, e-mail:
>> >> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> >> For additional commands, e-mail:
>> >> >> jcs-users-help@jakarta.apache.org
>> >> >> >>
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> > To unsubscribe, e-mail:
>> >> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> > For additional commands, e-mail:
>> >> >> jcs-users-help@jakarta.apache.org
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> >> >> Sent from the JCS - Users mailing list
>> archive at
>> >> >> Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail:
>> >> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail:
>> >> >> jcs-users-help@jakarta.apache.org
>> >> >
>> >> >
>> >>
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>> >> Sent from the JCS - Users mailing list archive at
>> >> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18990314.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18997541.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by Aaron Smuts <as...@yahoo.com>.
Good. Sorry about the bug. We really need to formally deprecate the group code, if it isn't already.
Cheers,
Aaron
--- On Thu, 8/14/08, danparker <da...@chordiant.com> wrote:
> From: danparker <da...@chordiant.com>
> Subject: Re: JDBC not working as expected
> To: jcs-users@jakarta.apache.org
> Date: Thursday, August 14, 2008, 2:45 PM
> Aaron
>
> Your right it was the groups that caused the issue. As soon
> as I took out
> the groups the JDBCDiskCache started working. It was
> basically an exception
> whilst prepare statement the exception that was going
> uncaught. It was
> getting the element attributes which in this case were
> group related and it
> was expecting.
>
> * Case closed *
>
> Thanks for your help. We've been grappling with
> failover for our production
> environment.
>
>
>
> Aaron Smuts wrote:
> >
> > Hmmn. This might be a problem with groups and the
> JDBC disk cache. I'll
> > have to look into it. In any case, groups are
> deprecated. I don't
> > recommend using them.
> >
> > Aaron
> >
> >
> > --- On Wed, 8/13/08, danparker
> <da...@chordiant.com> wrote:
> >
> >> From: danparker
> <da...@chordiant.com>
> >> Subject: Re: JDBC not working as expected
> >> To: jcs-users@jakarta.apache.org
> >> Date: Wednesday, August 13, 2008, 10:02 PM
> >> When I sent the tryBeforeInsert=true and
> MaxPurgatory to 10
> >> and I exceed that
> >> I get the following exception
> >>
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> >> Exception in thread
> >>
> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
> >> java.lang.ClassCastException:
> >> org.apache.jcs.engine.control.group.GroupAttrName
> >> incompatible with
> >> java.lang.String
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
> >> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> at
> >>
> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
> >>
> >> Aaron Smuts wrote:
> >> >
> >> > Call get stats and see if the auxiliary is in
> error.
> >> Look for errors and
> >> > warnings in the logs.
> >> >
> >> > Aaron
> >> >
> >> >
> >> > --- On Tue, 8/12/08, danparker
> >> <da...@chordiant.com> wrote:
> >> >
> >> >> From: danparker
> >> <da...@chordiant.com>
> >> >> Subject: Re: JDBC not working as expected
> >> >> To: jcs-users@jakarta.apache.org
> >> >> Date: Tuesday, August 12, 2008, 1:52 PM
> >> >> We are using version 1.3.
> >> >>
> >> >> We've changed DiskUsagePattern to
> >> DiskUsagePatternName
> >> >> but it had not
> >> >> effect. Still nothing in the database.
> >> >>
> >> >> I'm building a workspace were I can
> test this
> >> >> independant of our load test
> >> >> environment.
> >> >>
> >> >>
> >> >>
> >> >> hanasakijiji wrote:
> >> >> >
> >> >> > What version of JCS? Are you seeing
> this
> >> bug?
> >> >> >
> >> >>
> >>
> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
> >> >> >
> >> >>
> >>
> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
> >> >> > *** is short not String - looks like
> they
> >> come from an
> >> >> enum or public
> >> >> > static short ....
> >> >> >
> >> >> > might try testBeforeInsert=true and
> see if
> >> any selects
> >> >> are hitting the
> >> >> > DB at all from the database logs.
> >> >> >
> >> >> > Let us know if you find the solution
> and what
> >> it is.
> >> >> >
> >> >> >
> >> >> > On Thu, Aug 7, 2008 at 11:25 PM,
> danparker
> >> >> <da...@chordiant.com>
> >> >> > wrote:
> >> >> >>
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> >> >> >> cache_FDN_WithJDBC.ccf
> >> >> >>
> >> >> >> We've got three cache
> regions we want
> >> to have
> >> >> the contents in memory(for
> >> >> >> performance) and spooled out to
> the
> >> database so
> >> >> that we can recover in a
> >> >> >> failover situation. Attached is
> the
> >> configuration
> >> >> file. We are seeing the
> >> >> >> memory cache fill up but nothing
> is going
> >> into the
> >> >> database.
> >> >> >>
> >> >> >> I've set the
> DiskUsagePattern=update
> >> and
> >> >> IsSpool=True - is there
> >> >> >> something
> >> >> >> else I'm missing?
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> View this message in context:
> >> >> >>
> >> >>
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> >> >> >> Sent from the JCS - Users
> mailing list
> >> archive at
> >> >> Nabble.com.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >>
> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail:
> >> >> jcs-users-unsubscribe@jakarta.apache.org
> >> >> >> For additional commands, e-mail:
> >> >> jcs-users-help@jakarta.apache.org
> >> >> >>
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >>
> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail:
> >> >> jcs-users-unsubscribe@jakarta.apache.org
> >> >> > For additional commands, e-mail:
> >> >> jcs-users-help@jakarta.apache.org
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
> >> >> Sent from the JCS - Users mailing list
> archive at
> >> >> Nabble.com.
> >> >>
> >> >>
> >> >>
> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail:
> >> >> jcs-users-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail:
> >> >> jcs-users-help@jakarta.apache.org
> >> >
> >> >
> >>
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> >> jcs-users-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail:
> >> jcs-users-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
> >> Sent from the JCS - Users mailing list archive at
> >> Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> jcs-users-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> >> jcs-users-help@jakarta.apache.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18990314.html
> Sent from the JCS - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Aaron
Your right it was the groups that caused the issue. As soon as I took out
the groups the JDBCDiskCache started working. It was basically an exception
whilst prepare statement the exception that was going uncaught. It was
getting the element attributes which in this case were group related and it
was expecting.
* Case closed *
Thanks for your help. We've been grappling with failover for our production
environment.
Aaron Smuts wrote:
>
> Hmmn. This might be a problem with groups and the JDBC disk cache. I'll
> have to look into it. In any case, groups are deprecated. I don't
> recommend using them.
>
> Aaron
>
>
> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Wednesday, August 13, 2008, 10:02 PM
>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>> and I exceed that
>> I get the following exception
>>
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> Exception in thread
>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>> java.lang.ClassCastException:
>> org.apache.jcs.engine.control.group.GroupAttrName
>> incompatible with
>> java.lang.String
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>
>> Aaron Smuts wrote:
>> >
>> > Call get stats and see if the auxiliary is in error.
>> Look for errors and
>> > warnings in the logs.
>> >
>> > Aaron
>> >
>> >
>> > --- On Tue, 8/12/08, danparker
>> <da...@chordiant.com> wrote:
>> >
>> >> From: danparker
>> <da...@chordiant.com>
>> >> Subject: Re: JDBC not working as expected
>> >> To: jcs-users@jakarta.apache.org
>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>> >> We are using version 1.3.
>> >>
>> >> We've changed DiskUsagePattern to
>> DiskUsagePatternName
>> >> but it had not
>> >> effect. Still nothing in the database.
>> >>
>> >> I'm building a workspace were I can test this
>> >> independant of our load test
>> >> environment.
>> >>
>> >>
>> >>
>> >> hanasakijiji wrote:
>> >> >
>> >> > What version of JCS? Are you seeing this
>> bug?
>> >> >
>> >>
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >> >
>> >>
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> >> > *** is short not String - looks like they
>> come from an
>> >> enum or public
>> >> > static short ....
>> >> >
>> >> > might try testBeforeInsert=true and see if
>> any selects
>> >> are hitting the
>> >> > DB at all from the database logs.
>> >> >
>> >> > Let us know if you find the solution and what
>> it is.
>> >> >
>> >> >
>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>> >> <da...@chordiant.com>
>> >> > wrote:
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >> >> cache_FDN_WithJDBC.ccf
>> >> >>
>> >> >> We've got three cache regions we want
>> to have
>> >> the contents in memory(for
>> >> >> performance) and spooled out to the
>> database so
>> >> that we can recover in a
>> >> >> failover situation. Attached is the
>> configuration
>> >> file. We are seeing the
>> >> >> memory cache fill up but nothing is going
>> into the
>> >> database.
>> >> >>
>> >> >> I've set the DiskUsagePattern=update
>> and
>> >> IsSpool=True - is there
>> >> >> something
>> >> >> else I'm missing?
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >> >> Sent from the JCS - Users mailing list
>> archive at
>> >> Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> >> Sent from the JCS - Users mailing list archive at
>> >> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18990314.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
UPDATE
we discovered the issue we had ....elementAttribute.diskUsuagePatternName
not cacheAttributes.diskUsuagePatternname
It's working as we expected now.
Off to performance test it now.
Again - thanks for everyone's help. Greatly appreciated.
Dan
danparker wrote:
>
> Aaron
>
> I have diskUsuagePatternName = UPDATE and a Purgatory size of only 1 - I
> want it to goto disk straight away. It's not doing it. Even with update
> it's waiting for the memory to overflow before it goes to disk.
>
> Does the JDBC cache have to be on a remote server for this to work. Is
> there an implementation you have that is a RemoteJDBCDiskCache that will
> put a copy of whatever goes into memory into disk also with every put? It
> seems like the JDBC Cache is only acting like an overflow not a backup.
>
> Dan
>
>
> Aaron Smuts wrote:
>>
>> Purgatory is a queue inside the disk auxiliary. If it makes it to
>> purgatory, it's on the way to disk.
>>
>> It gets into purgatory based on the disk usage pattern. If it is spool,
>> then it goes when memory is full. If update, it goes on put.
>>
>>
>>
>> --- On Thu, 8/14/08, danparker <da...@chordiant.com> wrote:
>>
>>> From: danparker <da...@chordiant.com>
>>> Subject: Re: JDBC not working as expected
>>> To: jcs-users@jakarta.apache.org
>>> Date: Thursday, August 14, 2008, 12:55 PM
>>> I changed the db url and it blow up as expected. The logs
>>> not showing us
>>> writing into the database
>>>
>>> My understanding from reading the docs and the various
>>> posts is that
>>>
>>> - It writes to memory
>>> - It writes items to purgatory and additionally to the db
>>>
>>> What seems to be happening is
>>>
>>> - Writes to memory
>>> - Writes to purgatory but only spools to disk when it's
>>> full
>>>
>>> Dan
>>>
>>>
>>> hanasakijiji wrote:
>>> >
>>> > Are you seeing a transaction that is rolled back or no
>>> transaction at
>>> > all and no insert/updates? db logging should tell you
>>> this.
>>> > Are you sure you are checking the same DB that jcs is
>>> configured too?
>>> > I have seem some interesting projects that shared a DB
>>> between them
>>> > and hosed themselves with bad/none configuration
>>> management.
>>> >
>>> > On Thu, Aug 14, 2008 at 2:02 PM, danparker
>>> <da...@chordiant.com>
>>> > wrote:
>>> >>
>>> >> I've now got some logging coming out and
>>> it's saying that it's putting
>>> >> stuff
>>> >> on the disk, but we don't see it. We're
>>> connected to Oracle and I noticed
>>> >> the code just closes the connection but
>>> doesn't commit any transaction
>>> >> could
>>> >> this be the issue?
>>> >>
>>> >>
>>> >>
>>> >> Aaron Smuts wrote:
>>> >>>
>>> >>> Hmmn. This might be a problem with groups and
>>> the JDBC disk cache.
>>> >>> I'll
>>> >>> have to look into it. In any case, groups are
>>> deprecated. I don't
>>> >>> recommend using them.
>>> >>>
>>> >>> Aaron
>>> >>>
>>> >>>
>>> >>> --- On Wed, 8/13/08, danparker
>>> <da...@chordiant.com> wrote:
>>> >>>
>>> >>>> From: danparker
>>> <da...@chordiant.com>
>>> >>>> Subject: Re: JDBC not working as expected
>>> >>>> To: jcs-users@jakarta.apache.org
>>> >>>> Date: Wednesday, August 13, 2008, 10:02 PM
>>> >>>> When I sent the tryBeforeInsert=true and
>>> MaxPurgatory to 10
>>> >>>> and I exceed that
>>> >>>> I get the following exception
>>> >>>>
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R
>>> >>>> Exception in thread
>>> >>>>
>>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>>> >>>> java.lang.ClassCastException:
>>> >>>>
>>> org.apache.jcs.engine.control.group.GroupAttrName
>>> >>>> incompatible with
>>> >>>> java.lang.String
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>>> SystemErr R at
>>> >>>>
>>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>> >>>>
>>> >>>> Aaron Smuts wrote:
>>> >>>> >
>>> >>>> > Call get stats and see if the
>>> auxiliary is in error.
>>> >>>> Look for errors and
>>> >>>> > warnings in the logs.
>>> >>>> >
>>> >>>> > Aaron
>>> >>>> >
>>> >>>> >
>>> >>>> > --- On Tue, 8/12/08, danparker
>>> >>>> <da...@chordiant.com> wrote:
>>> >>>> >
>>> >>>> >> From: danparker
>>> >>>> <da...@chordiant.com>
>>> >>>> >> Subject: Re: JDBC not working as
>>> expected
>>> >>>> >> To: jcs-users@jakarta.apache.org
>>> >>>> >> Date: Tuesday, August 12, 2008,
>>> 1:52 PM
>>> >>>> >> We are using version 1.3.
>>> >>>> >>
>>> >>>> >> We've changed
>>> DiskUsagePattern to
>>> >>>> DiskUsagePatternName
>>> >>>> >> but it had not
>>> >>>> >> effect. Still nothing in the
>>> database.
>>> >>>> >>
>>> >>>> >> I'm building a workspace were
>>> I can test this
>>> >>>> >> independant of our load test
>>> >>>> >> environment.
>>> >>>> >>
>>> >>>> >>
>>> >>>> >>
>>> >>>> >> hanasakijiji wrote:
>>> >>>> >> >
>>> >>>> >> > What version of JCS? Are
>>> you seeing this
>>> >>>> bug?
>>> >>>> >> >
>>> >>>> >>
>>> >>>>
>>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>>> >>>> >> >
>>> >>>> >>
>>> >>>>
>>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>>> >>>> >> > *** is short not String -
>>> looks like they
>>> >>>> come from an
>>> >>>> >> enum or public
>>> >>>> >> > static short ....
>>> >>>> >> >
>>> >>>> >> > might try
>>> testBeforeInsert=true and see if
>>> >>>> any selects
>>> >>>> >> are hitting the
>>> >>>> >> > DB at all from the database
>>> logs.
>>> >>>> >> >
>>> >>>> >> > Let us know if you find the
>>> solution and what
>>> >>>> it is.
>>> >>>> >> >
>>> >>>> >> >
>>> >>>> >> > On Thu, Aug 7, 2008 at 11:25
>>> PM, danparker
>>> >>>> >>
>>> <da...@chordiant.com>
>>> >>>> >> > wrote:
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >>
>>> >>>>
>>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>>> >>>> >> >> cache_FDN_WithJDBC.ccf
>>> >>>> >> >>
>>> >>>> >> >> We've got three
>>> cache regions we want
>>> >>>> to have
>>> >>>> >> the contents in memory(for
>>> >>>> >> >> performance) and spooled
>>> out to the
>>> >>>> database so
>>> >>>> >> that we can recover in a
>>> >>>> >> >> failover situation.
>>> Attached is the
>>> >>>> configuration
>>> >>>> >> file. We are seeing the
>>> >>>> >> >> memory cache fill up but
>>> nothing is going
>>> >>>> into the
>>> >>>> >> database.
>>> >>>> >> >>
>>> >>>> >> >> I've set the
>>> DiskUsagePattern=update
>>> >>>> and
>>> >>>> >> IsSpool=True - is there
>>> >>>> >> >> something
>>> >>>> >> >> else I'm missing?
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >> >> --
>>> >>>> >> >> View this message in
>>> context:
>>> >>>> >> >>
>>> >>>> >>
>>> >>>>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>>> >>>> >> >> Sent from the JCS -
>>> Users mailing list
>>> >>>> archive at
>>> >>>> >> Nabble.com.
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >>
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> >> >> To unsubscribe, e-mail:
>>> >>>> >>
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>>> >> >> For additional commands,
>>> e-mail:
>>> >>>> >> jcs-users-help@jakarta.apache.org
>>> >>>> >> >>
>>> >>>> >> >>
>>> >>>> >> >
>>> >>>> >> >
>>> >>>> >>
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> >> > To unsubscribe, e-mail:
>>> >>>> >>
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>>> >> > For additional commands,
>>> e-mail:
>>> >>>> >> jcs-users-help@jakarta.apache.org
>>> >>>> >> >
>>> >>>> >> >
>>> >>>> >> >
>>> >>>> >>
>>> >>>> >> --
>>> >>>> >> View this message in context:
>>> >>>> >>
>>> >>>>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>>> >>>> >> Sent from the JCS - Users mailing
>>> list archive at
>>> >>>> >> Nabble.com.
>>> >>>> >>
>>> >>>> >>
>>> >>>> >>
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> >> To unsubscribe, e-mail:
>>> >>>> >>
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>>> >> For additional commands, e-mail:
>>> >>>> >> jcs-users-help@jakarta.apache.org
>>> >>>> >
>>> >>>> >
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> > To unsubscribe, e-mail:
>>> >>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>>> > For additional commands, e-mail:
>>> >>>> jcs-users-help@jakarta.apache.org
>>> >>>> >
>>> >>>> >
>>> >>>> >
>>> >>>>
>>> >>>> --
>>> >>>> View this message in context:
>>> >>>>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>>> >>>> Sent from the JCS - Users mailing list
>>> archive at
>>> >>>> Nabble.com.
>>> >>>>
>>> >>>>
>>> >>>>
>>> ---------------------------------------------------------------------
>>> >>>> To unsubscribe, e-mail:
>>> >>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>>> For additional commands, e-mail:
>>> >>>> jcs-users-help@jakarta.apache.org
>>> >>>
>>> >>>
>>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >>> For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
>>> >> Sent from the JCS - Users mailing list archive at
>>> Nabble.com.
>>> >>
>>> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> >> For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>> >>
>>> >>
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> > For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18988551.html
>>> Sent from the JCS - Users mailing list archive at
>>> Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p19003818.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Aaron
I have diskUsuagePatternName = UPDATE and a Purgatory size of only 1 - I
want it to goto disk straight away. It's not doing it. Even with update it's
waiting for the memory to overflow before it goes to disk.
Does the JDBC cache have to be on a remote server for this to work. Is there
an implementation you have that is a RemoteJDBCDiskCache that will put a
copy of whatever goes into memory into disk also with every put? It seems
like the JDBC Cache is only acting like an overflow not a backup.
Dan
Aaron Smuts wrote:
>
> Purgatory is a queue inside the disk auxiliary. If it makes it to
> purgatory, it's on the way to disk.
>
> It gets into purgatory based on the disk usage pattern. If it is spool,
> then it goes when memory is full. If update, it goes on put.
>
>
>
> --- On Thu, 8/14/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Thursday, August 14, 2008, 12:55 PM
>> I changed the db url and it blow up as expected. The logs
>> not showing us
>> writing into the database
>>
>> My understanding from reading the docs and the various
>> posts is that
>>
>> - It writes to memory
>> - It writes items to purgatory and additionally to the db
>>
>> What seems to be happening is
>>
>> - Writes to memory
>> - Writes to purgatory but only spools to disk when it's
>> full
>>
>> Dan
>>
>>
>> hanasakijiji wrote:
>> >
>> > Are you seeing a transaction that is rolled back or no
>> transaction at
>> > all and no insert/updates? db logging should tell you
>> this.
>> > Are you sure you are checking the same DB that jcs is
>> configured too?
>> > I have seem some interesting projects that shared a DB
>> between them
>> > and hosed themselves with bad/none configuration
>> management.
>> >
>> > On Thu, Aug 14, 2008 at 2:02 PM, danparker
>> <da...@chordiant.com>
>> > wrote:
>> >>
>> >> I've now got some logging coming out and
>> it's saying that it's putting
>> >> stuff
>> >> on the disk, but we don't see it. We're
>> connected to Oracle and I noticed
>> >> the code just closes the connection but
>> doesn't commit any transaction
>> >> could
>> >> this be the issue?
>> >>
>> >>
>> >>
>> >> Aaron Smuts wrote:
>> >>>
>> >>> Hmmn. This might be a problem with groups and
>> the JDBC disk cache.
>> >>> I'll
>> >>> have to look into it. In any case, groups are
>> deprecated. I don't
>> >>> recommend using them.
>> >>>
>> >>> Aaron
>> >>>
>> >>>
>> >>> --- On Wed, 8/13/08, danparker
>> <da...@chordiant.com> wrote:
>> >>>
>> >>>> From: danparker
>> <da...@chordiant.com>
>> >>>> Subject: Re: JDBC not working as expected
>> >>>> To: jcs-users@jakarta.apache.org
>> >>>> Date: Wednesday, August 13, 2008, 10:02 PM
>> >>>> When I sent the tryBeforeInsert=true and
>> MaxPurgatory to 10
>> >>>> and I exceed that
>> >>>> I get the following exception
>> >>>>
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R
>> >>>> Exception in thread
>> >>>>
>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>> >>>> java.lang.ClassCastException:
>> >>>>
>> org.apache.jcs.engine.control.group.GroupAttrName
>> >>>> incompatible with
>> >>>> java.lang.String
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
>> SystemErr R at
>> >>>>
>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>> >>>>
>> >>>> Aaron Smuts wrote:
>> >>>> >
>> >>>> > Call get stats and see if the
>> auxiliary is in error.
>> >>>> Look for errors and
>> >>>> > warnings in the logs.
>> >>>> >
>> >>>> > Aaron
>> >>>> >
>> >>>> >
>> >>>> > --- On Tue, 8/12/08, danparker
>> >>>> <da...@chordiant.com> wrote:
>> >>>> >
>> >>>> >> From: danparker
>> >>>> <da...@chordiant.com>
>> >>>> >> Subject: Re: JDBC not working as
>> expected
>> >>>> >> To: jcs-users@jakarta.apache.org
>> >>>> >> Date: Tuesday, August 12, 2008,
>> 1:52 PM
>> >>>> >> We are using version 1.3.
>> >>>> >>
>> >>>> >> We've changed
>> DiskUsagePattern to
>> >>>> DiskUsagePatternName
>> >>>> >> but it had not
>> >>>> >> effect. Still nothing in the
>> database.
>> >>>> >>
>> >>>> >> I'm building a workspace were
>> I can test this
>> >>>> >> independant of our load test
>> >>>> >> environment.
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>> >> hanasakijiji wrote:
>> >>>> >> >
>> >>>> >> > What version of JCS? Are
>> you seeing this
>> >>>> bug?
>> >>>> >> >
>> >>>> >>
>> >>>>
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >>>> >> >
>> >>>> >>
>> >>>>
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> >>>> >> > *** is short not String -
>> looks like they
>> >>>> come from an
>> >>>> >> enum or public
>> >>>> >> > static short ....
>> >>>> >> >
>> >>>> >> > might try
>> testBeforeInsert=true and see if
>> >>>> any selects
>> >>>> >> are hitting the
>> >>>> >> > DB at all from the database
>> logs.
>> >>>> >> >
>> >>>> >> > Let us know if you find the
>> solution and what
>> >>>> it is.
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > On Thu, Aug 7, 2008 at 11:25
>> PM, danparker
>> >>>> >>
>> <da...@chordiant.com>
>> >>>> >> > wrote:
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >>
>> >>>>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >>>> >> >> cache_FDN_WithJDBC.ccf
>> >>>> >> >>
>> >>>> >> >> We've got three
>> cache regions we want
>> >>>> to have
>> >>>> >> the contents in memory(for
>> >>>> >> >> performance) and spooled
>> out to the
>> >>>> database so
>> >>>> >> that we can recover in a
>> >>>> >> >> failover situation.
>> Attached is the
>> >>>> configuration
>> >>>> >> file. We are seeing the
>> >>>> >> >> memory cache fill up but
>> nothing is going
>> >>>> into the
>> >>>> >> database.
>> >>>> >> >>
>> >>>> >> >> I've set the
>> DiskUsagePattern=update
>> >>>> and
>> >>>> >> IsSpool=True - is there
>> >>>> >> >> something
>> >>>> >> >> else I'm missing?
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >> --
>> >>>> >> >> View this message in
>> context:
>> >>>> >> >>
>> >>>> >>
>> >>>>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >>>> >> >> Sent from the JCS -
>> Users mailing list
>> >>>> archive at
>> >>>> >> Nabble.com.
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >>
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> >> >> To unsubscribe, e-mail:
>> >>>> >>
>> jcs-users-unsubscribe@jakarta.apache.org
>> >>>> >> >> For additional commands,
>> e-mail:
>> >>>> >> jcs-users-help@jakarta.apache.org
>> >>>> >> >>
>> >>>> >> >>
>> >>>> >> >
>> >>>> >> >
>> >>>> >>
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> >> > To unsubscribe, e-mail:
>> >>>> >>
>> jcs-users-unsubscribe@jakarta.apache.org
>> >>>> >> > For additional commands,
>> e-mail:
>> >>>> >> jcs-users-help@jakarta.apache.org
>> >>>> >> >
>> >>>> >> >
>> >>>> >> >
>> >>>> >>
>> >>>> >> --
>> >>>> >> View this message in context:
>> >>>> >>
>> >>>>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> >>>> >> Sent from the JCS - Users mailing
>> list archive at
>> >>>> >> Nabble.com.
>> >>>> >>
>> >>>> >>
>> >>>> >>
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> >> To unsubscribe, e-mail:
>> >>>> >>
>> jcs-users-unsubscribe@jakarta.apache.org
>> >>>> >> For additional commands, e-mail:
>> >>>> >> jcs-users-help@jakarta.apache.org
>> >>>> >
>> >>>> >
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> > To unsubscribe, e-mail:
>> >>>> jcs-users-unsubscribe@jakarta.apache.org
>> >>>> > For additional commands, e-mail:
>> >>>> jcs-users-help@jakarta.apache.org
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>>
>> >>>> --
>> >>>> View this message in context:
>> >>>>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>> >>>> Sent from the JCS - Users mailing list
>> archive at
>> >>>> Nabble.com.
>> >>>>
>> >>>>
>> >>>>
>> ---------------------------------------------------------------------
>> >>>> To unsubscribe, e-mail:
>> >>>> jcs-users-unsubscribe@jakarta.apache.org
>> >>>> For additional commands, e-mail:
>> >>>> jcs-users-help@jakarta.apache.org
>> >>>
>> >>>
>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> >>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >>>
>> >>>
>> >>>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
>> >> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >>
>> >>
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18988551.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18997502.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by Aaron Smuts <as...@yahoo.com>.
Purgatory is a queue inside the disk auxiliary. If it makes it to purgatory, it's on the way to disk.
It gets into purgatory based on the disk usage pattern. If it is spool, then it goes when memory is full. If update, it goes on put.
--- On Thu, 8/14/08, danparker <da...@chordiant.com> wrote:
> From: danparker <da...@chordiant.com>
> Subject: Re: JDBC not working as expected
> To: jcs-users@jakarta.apache.org
> Date: Thursday, August 14, 2008, 12:55 PM
> I changed the db url and it blow up as expected. The logs
> not showing us
> writing into the database
>
> My understanding from reading the docs and the various
> posts is that
>
> - It writes to memory
> - It writes items to purgatory and additionally to the db
>
> What seems to be happening is
>
> - Writes to memory
> - Writes to purgatory but only spools to disk when it's
> full
>
> Dan
>
>
> hanasakijiji wrote:
> >
> > Are you seeing a transaction that is rolled back or no
> transaction at
> > all and no insert/updates? db logging should tell you
> this.
> > Are you sure you are checking the same DB that jcs is
> configured too?
> > I have seem some interesting projects that shared a DB
> between them
> > and hosed themselves with bad/none configuration
> management.
> >
> > On Thu, Aug 14, 2008 at 2:02 PM, danparker
> <da...@chordiant.com>
> > wrote:
> >>
> >> I've now got some logging coming out and
> it's saying that it's putting
> >> stuff
> >> on the disk, but we don't see it. We're
> connected to Oracle and I noticed
> >> the code just closes the connection but
> doesn't commit any transaction
> >> could
> >> this be the issue?
> >>
> >>
> >>
> >> Aaron Smuts wrote:
> >>>
> >>> Hmmn. This might be a problem with groups and
> the JDBC disk cache.
> >>> I'll
> >>> have to look into it. In any case, groups are
> deprecated. I don't
> >>> recommend using them.
> >>>
> >>> Aaron
> >>>
> >>>
> >>> --- On Wed, 8/13/08, danparker
> <da...@chordiant.com> wrote:
> >>>
> >>>> From: danparker
> <da...@chordiant.com>
> >>>> Subject: Re: JDBC not working as expected
> >>>> To: jcs-users@jakarta.apache.org
> >>>> Date: Wednesday, August 13, 2008, 10:02 PM
> >>>> When I sent the tryBeforeInsert=true and
> MaxPurgatory to 10
> >>>> and I exceed that
> >>>> I get the following exception
> >>>>
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R
> >>>> Exception in thread
> >>>>
> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
> >>>> java.lang.ClassCastException:
> >>>>
> org.apache.jcs.engine.control.group.GroupAttrName
> >>>> incompatible with
> >>>> java.lang.String
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
> >>>> [8/14/08 0:50:21:693 EDT] 000000aa
> SystemErr R at
> >>>>
> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
> >>>>
> >>>> Aaron Smuts wrote:
> >>>> >
> >>>> > Call get stats and see if the
> auxiliary is in error.
> >>>> Look for errors and
> >>>> > warnings in the logs.
> >>>> >
> >>>> > Aaron
> >>>> >
> >>>> >
> >>>> > --- On Tue, 8/12/08, danparker
> >>>> <da...@chordiant.com> wrote:
> >>>> >
> >>>> >> From: danparker
> >>>> <da...@chordiant.com>
> >>>> >> Subject: Re: JDBC not working as
> expected
> >>>> >> To: jcs-users@jakarta.apache.org
> >>>> >> Date: Tuesday, August 12, 2008,
> 1:52 PM
> >>>> >> We are using version 1.3.
> >>>> >>
> >>>> >> We've changed
> DiskUsagePattern to
> >>>> DiskUsagePatternName
> >>>> >> but it had not
> >>>> >> effect. Still nothing in the
> database.
> >>>> >>
> >>>> >> I'm building a workspace were
> I can test this
> >>>> >> independant of our load test
> >>>> >> environment.
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >> hanasakijiji wrote:
> >>>> >> >
> >>>> >> > What version of JCS? Are
> you seeing this
> >>>> bug?
> >>>> >> >
> >>>> >>
> >>>>
> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
> >>>> >> >
> >>>> >>
> >>>>
> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
> >>>> >> > *** is short not String -
> looks like they
> >>>> come from an
> >>>> >> enum or public
> >>>> >> > static short ....
> >>>> >> >
> >>>> >> > might try
> testBeforeInsert=true and see if
> >>>> any selects
> >>>> >> are hitting the
> >>>> >> > DB at all from the database
> logs.
> >>>> >> >
> >>>> >> > Let us know if you find the
> solution and what
> >>>> it is.
> >>>> >> >
> >>>> >> >
> >>>> >> > On Thu, Aug 7, 2008 at 11:25
> PM, danparker
> >>>> >>
> <da...@chordiant.com>
> >>>> >> > wrote:
> >>>> >> >>
> >>>> >> >>
> >>>> >>
> >>>>
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> >>>> >> >> cache_FDN_WithJDBC.ccf
> >>>> >> >>
> >>>> >> >> We've got three
> cache regions we want
> >>>> to have
> >>>> >> the contents in memory(for
> >>>> >> >> performance) and spooled
> out to the
> >>>> database so
> >>>> >> that we can recover in a
> >>>> >> >> failover situation.
> Attached is the
> >>>> configuration
> >>>> >> file. We are seeing the
> >>>> >> >> memory cache fill up but
> nothing is going
> >>>> into the
> >>>> >> database.
> >>>> >> >>
> >>>> >> >> I've set the
> DiskUsagePattern=update
> >>>> and
> >>>> >> IsSpool=True - is there
> >>>> >> >> something
> >>>> >> >> else I'm missing?
> >>>> >> >>
> >>>> >> >>
> >>>> >> >>
> >>>> >> >> --
> >>>> >> >> View this message in
> context:
> >>>> >> >>
> >>>> >>
> >>>>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> >>>> >> >> Sent from the JCS -
> Users mailing list
> >>>> archive at
> >>>> >> Nabble.com.
> >>>> >> >>
> >>>> >> >>
> >>>> >> >>
> >>>> >>
> >>>>
> ---------------------------------------------------------------------
> >>>> >> >> To unsubscribe, e-mail:
> >>>> >>
> jcs-users-unsubscribe@jakarta.apache.org
> >>>> >> >> For additional commands,
> e-mail:
> >>>> >> jcs-users-help@jakarta.apache.org
> >>>> >> >>
> >>>> >> >>
> >>>> >> >
> >>>> >> >
> >>>> >>
> >>>>
> ---------------------------------------------------------------------
> >>>> >> > To unsubscribe, e-mail:
> >>>> >>
> jcs-users-unsubscribe@jakarta.apache.org
> >>>> >> > For additional commands,
> e-mail:
> >>>> >> jcs-users-help@jakarta.apache.org
> >>>> >> >
> >>>> >> >
> >>>> >> >
> >>>> >>
> >>>> >> --
> >>>> >> View this message in context:
> >>>> >>
> >>>>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
> >>>> >> Sent from the JCS - Users mailing
> list archive at
> >>>> >> Nabble.com.
> >>>> >>
> >>>> >>
> >>>> >>
> >>>>
> ---------------------------------------------------------------------
> >>>> >> To unsubscribe, e-mail:
> >>>> >>
> jcs-users-unsubscribe@jakarta.apache.org
> >>>> >> For additional commands, e-mail:
> >>>> >> jcs-users-help@jakarta.apache.org
> >>>> >
> >>>> >
> >>>>
> ---------------------------------------------------------------------
> >>>> > To unsubscribe, e-mail:
> >>>> jcs-users-unsubscribe@jakarta.apache.org
> >>>> > For additional commands, e-mail:
> >>>> jcs-users-help@jakarta.apache.org
> >>>> >
> >>>> >
> >>>> >
> >>>>
> >>>> --
> >>>> View this message in context:
> >>>>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
> >>>> Sent from the JCS - Users mailing list
> archive at
> >>>> Nabble.com.
> >>>>
> >>>>
> >>>>
> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail:
> >>>> jcs-users-unsubscribe@jakarta.apache.org
> >>>> For additional commands, e-mail:
> >>>> jcs-users-help@jakarta.apache.org
> >>>
> >>>
> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> >>> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >>>
> >>>
> >>>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
> >> Sent from the JCS - Users mailing list archive at
> Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18988551.html
> Sent from the JCS - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
RE: JDBC not working as expected
Posted by Tim Cronin <tc...@interwoven.com>.
What do you have DiskUsagePattern set to?
I think I saw if you set it to update it will write to the DB.
-----Original Message-----
From: danparker [mailto:daniel.parker@chordiant.com]
Sent: Thursday, August 14, 2008 2:55 PM
To: jcs-users@jakarta.apache.org
Subject: Re: JDBC not working as expected
I changed the db url and it blow up as expected. The logs not showing us
writing into the database
My understanding from reading the docs and the various posts is that
- It writes to memory
- It writes items to purgatory and additionally to the db
What seems to be happening is
- Writes to memory
- Writes to purgatory but only spools to disk when it's full
Dan
hanasakijiji wrote:
>
> Are you seeing a transaction that is rolled back or no transaction at
> all and no insert/updates? db logging should tell you this.
> Are you sure you are checking the same DB that jcs is configured too?
> I have seem some interesting projects that shared a DB between them
> and hosed themselves with bad/none configuration management.
>
> On Thu, Aug 14, 2008 at 2:02 PM, danparker
<da...@chordiant.com>
> wrote:
>>
>> I've now got some logging coming out and it's saying that it's
putting
>> stuff
>> on the disk, but we don't see it. We're connected to Oracle and I
noticed
>> the code just closes the connection but doesn't commit any
transaction
>> could
>> this be the issue?
>>
>>
>>
>> Aaron Smuts wrote:
>>>
>>> Hmmn. This might be a problem with groups and the JDBC disk cache.
>>> I'll
>>> have to look into it. In any case, groups are deprecated. I don't
>>> recommend using them.
>>>
>>> Aaron
>>>
>>>
>>> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>>>
>>>> From: danparker <da...@chordiant.com>
>>>> Subject: Re: JDBC not working as expected
>>>> To: jcs-users@jakarta.apache.org
>>>> Date: Wednesday, August 13, 2008, 10:02 PM
>>>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>>>> and I exceed that
>>>> I get the following exception
>>>>
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>>>> Exception in thread
>>>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>>>> java.lang.ClassCastException:
>>>> org.apache.jcs.engine.control.group.GroupAttrName
>>>> incompatible with
>>>> java.lang.String
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDi
skCache.java:392)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.
java:244)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePu
t(AbstractDiskCache.java:603)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.jav
a:688)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQ
ueue.java:607)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>>
org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.jav
a:575)
>>>>
>>>> Aaron Smuts wrote:
>>>> >
>>>> > Call get stats and see if the auxiliary is in error.
>>>> Look for errors and
>>>> > warnings in the logs.
>>>> >
>>>> > Aaron
>>>> >
>>>> >
>>>> > --- On Tue, 8/12/08, danparker
>>>> <da...@chordiant.com> wrote:
>>>> >
>>>> >> From: danparker
>>>> <da...@chordiant.com>
>>>> >> Subject: Re: JDBC not working as expected
>>>> >> To: jcs-users@jakarta.apache.org
>>>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>>>> >> We are using version 1.3.
>>>> >>
>>>> >> We've changed DiskUsagePattern to
>>>> DiskUsagePatternName
>>>> >> but it had not
>>>> >> effect. Still nothing in the database.
>>>> >>
>>>> >> I'm building a workspace were I can test this
>>>> >> independant of our load test
>>>> >> environment.
>>>> >>
>>>> >>
>>>> >>
>>>> >> hanasakijiji wrote:
>>>> >> >
>>>> >> > What version of JCS? Are you seeing this
>>>> bug?
>>>> >> >
>>>> >>
>>>>
https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plu
gin.system.issuetabpanels:comment-tabpanel#action_12490995
>>>> >> >
>>>> >>
>>>>
http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICo
mpositeCacheAttributes.html
>>>> >> > *** is short not String - looks like they
>>>> come from an
>>>> >> enum or public
>>>> >> > static short ....
>>>> >> >
>>>> >> > might try testBeforeInsert=true and see if
>>>> any selects
>>>> >> are hitting the
>>>> >> > DB at all from the database logs.
>>>> >> >
>>>> >> > Let us know if you find the solution and what
>>>> it is.
>>>> >> >
>>>> >> >
>>>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>>>> >> <da...@chordiant.com>
>>>> >> > wrote:
>>>> >> >>
>>>> >> >>
>>>> >>
>>>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>>>> >> >> cache_FDN_WithJDBC.ccf
>>>> >> >>
>>>> >> >> We've got three cache regions we want
>>>> to have
>>>> >> the contents in memory(for
>>>> >> >> performance) and spooled out to the
>>>> database so
>>>> >> that we can recover in a
>>>> >> >> failover situation. Attached is the
>>>> configuration
>>>> >> file. We are seeing the
>>>> >> >> memory cache fill up but nothing is going
>>>> into the
>>>> >> database.
>>>> >> >>
>>>> >> >> I've set the DiskUsagePattern=update
>>>> and
>>>> >> IsSpool=True - is there
>>>> >> >> something
>>>> >> >> else I'm missing?
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> --
>>>> >> >> View this message in context:
>>>> >> >>
>>>> >>
>>>>
http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.h
tml
>>>> >> >> Sent from the JCS - Users mailing list
>>>> archive at
>>>> >> Nabble.com.
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >>
>>>>
---------------------------------------------------------------------
>>>> >> >> To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> >> For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >> >>
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >>
>>>>
---------------------------------------------------------------------
>>>> >> > To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> > For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >>
>>>> >> --
>>>> >> View this message in context:
>>>> >>
>>>>
http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.h
tml
>>>> >> Sent from the JCS - Users mailing list archive at
>>>> >> Nabble.com.
>>>> >>
>>>> >>
>>>> >>
>>>>
---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >
>>>> >
>>>>
---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail:
>>>> jcs-users-unsubscribe@jakarta.apache.org
>>>> > For additional commands, e-mail:
>>>> jcs-users-help@jakarta.apache.org
>>>> >
>>>> >
>>>> >
>>>>
>>>> --
>>>> View this message in context:
>>>>
http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.h
tml
>>>> Sent from the JCS - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>>
>>>>
---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
>>>> jcs-users-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> jcs-users-help@jakarta.apache.org
>>>
>>>
---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>>
http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.h
tml
>> Sent from the JCS - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context:
http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18988551.h
tml
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
I changed the db url and it blow up as expected. The logs not showing us
writing into the database
My understanding from reading the docs and the various posts is that
- It writes to memory
- It writes items to purgatory and additionally to the db
What seems to be happening is
- Writes to memory
- Writes to purgatory but only spools to disk when it's full
Dan
hanasakijiji wrote:
>
> Are you seeing a transaction that is rolled back or no transaction at
> all and no insert/updates? db logging should tell you this.
> Are you sure you are checking the same DB that jcs is configured too?
> I have seem some interesting projects that shared a DB between them
> and hosed themselves with bad/none configuration management.
>
> On Thu, Aug 14, 2008 at 2:02 PM, danparker <da...@chordiant.com>
> wrote:
>>
>> I've now got some logging coming out and it's saying that it's putting
>> stuff
>> on the disk, but we don't see it. We're connected to Oracle and I noticed
>> the code just closes the connection but doesn't commit any transaction
>> could
>> this be the issue?
>>
>>
>>
>> Aaron Smuts wrote:
>>>
>>> Hmmn. This might be a problem with groups and the JDBC disk cache.
>>> I'll
>>> have to look into it. In any case, groups are deprecated. I don't
>>> recommend using them.
>>>
>>> Aaron
>>>
>>>
>>> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>>>
>>>> From: danparker <da...@chordiant.com>
>>>> Subject: Re: JDBC not working as expected
>>>> To: jcs-users@jakarta.apache.org
>>>> Date: Wednesday, August 13, 2008, 10:02 PM
>>>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>>>> and I exceed that
>>>> I get the following exception
>>>>
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>>>> Exception in thread
>>>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>>>> java.lang.ClassCastException:
>>>> org.apache.jcs.engine.control.group.GroupAttrName
>>>> incompatible with
>>>> java.lang.String
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>>>
>>>> Aaron Smuts wrote:
>>>> >
>>>> > Call get stats and see if the auxiliary is in error.
>>>> Look for errors and
>>>> > warnings in the logs.
>>>> >
>>>> > Aaron
>>>> >
>>>> >
>>>> > --- On Tue, 8/12/08, danparker
>>>> <da...@chordiant.com> wrote:
>>>> >
>>>> >> From: danparker
>>>> <da...@chordiant.com>
>>>> >> Subject: Re: JDBC not working as expected
>>>> >> To: jcs-users@jakarta.apache.org
>>>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>>>> >> We are using version 1.3.
>>>> >>
>>>> >> We've changed DiskUsagePattern to
>>>> DiskUsagePatternName
>>>> >> but it had not
>>>> >> effect. Still nothing in the database.
>>>> >>
>>>> >> I'm building a workspace were I can test this
>>>> >> independant of our load test
>>>> >> environment.
>>>> >>
>>>> >>
>>>> >>
>>>> >> hanasakijiji wrote:
>>>> >> >
>>>> >> > What version of JCS? Are you seeing this
>>>> bug?
>>>> >> >
>>>> >>
>>>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>>>> >> >
>>>> >>
>>>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>>>> >> > *** is short not String - looks like they
>>>> come from an
>>>> >> enum or public
>>>> >> > static short ....
>>>> >> >
>>>> >> > might try testBeforeInsert=true and see if
>>>> any selects
>>>> >> are hitting the
>>>> >> > DB at all from the database logs.
>>>> >> >
>>>> >> > Let us know if you find the solution and what
>>>> it is.
>>>> >> >
>>>> >> >
>>>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>>>> >> <da...@chordiant.com>
>>>> >> > wrote:
>>>> >> >>
>>>> >> >>
>>>> >>
>>>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>>>> >> >> cache_FDN_WithJDBC.ccf
>>>> >> >>
>>>> >> >> We've got three cache regions we want
>>>> to have
>>>> >> the contents in memory(for
>>>> >> >> performance) and spooled out to the
>>>> database so
>>>> >> that we can recover in a
>>>> >> >> failover situation. Attached is the
>>>> configuration
>>>> >> file. We are seeing the
>>>> >> >> memory cache fill up but nothing is going
>>>> into the
>>>> >> database.
>>>> >> >>
>>>> >> >> I've set the DiskUsagePattern=update
>>>> and
>>>> >> IsSpool=True - is there
>>>> >> >> something
>>>> >> >> else I'm missing?
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >> >> --
>>>> >> >> View this message in context:
>>>> >> >>
>>>> >>
>>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>>>> >> >> Sent from the JCS - Users mailing list
>>>> archive at
>>>> >> Nabble.com.
>>>> >> >>
>>>> >> >>
>>>> >> >>
>>>> >>
>>>> ---------------------------------------------------------------------
>>>> >> >> To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> >> For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >> >>
>>>> >> >>
>>>> >> >
>>>> >> >
>>>> >>
>>>> ---------------------------------------------------------------------
>>>> >> > To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> > For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >> >
>>>> >> >
>>>> >> >
>>>> >>
>>>> >> --
>>>> >> View this message in context:
>>>> >>
>>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>>>> >> Sent from the JCS - Users mailing list archive at
>>>> >> Nabble.com.
>>>> >>
>>>> >>
>>>> >>
>>>> ---------------------------------------------------------------------
>>>> >> To unsubscribe, e-mail:
>>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>>> >> For additional commands, e-mail:
>>>> >> jcs-users-help@jakarta.apache.org
>>>> >
>>>> >
>>>> ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail:
>>>> jcs-users-unsubscribe@jakarta.apache.org
>>>> > For additional commands, e-mail:
>>>> jcs-users-help@jakarta.apache.org
>>>> >
>>>> >
>>>> >
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>>>> Sent from the JCS - Users mailing list archive at
>>>> Nabble.com.
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail:
>>>> jcs-users-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> jcs-users-help@jakarta.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
>> Sent from the JCS - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18988551.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by hanasaki jiji <ha...@gmail.com>.
Are you seeing a transaction that is rolled back or no transaction at
all and no insert/updates? db logging should tell you this.
Are you sure you are checking the same DB that jcs is configured too?
I have seem some interesting projects that shared a DB between them
and hosed themselves with bad/none configuration management.
On Thu, Aug 14, 2008 at 2:02 PM, danparker <da...@chordiant.com> wrote:
>
> I've now got some logging coming out and it's saying that it's putting stuff
> on the disk, but we don't see it. We're connected to Oracle and I noticed
> the code just closes the connection but doesn't commit any transaction could
> this be the issue?
>
>
>
> Aaron Smuts wrote:
>>
>> Hmmn. This might be a problem with groups and the JDBC disk cache. I'll
>> have to look into it. In any case, groups are deprecated. I don't
>> recommend using them.
>>
>> Aaron
>>
>>
>> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>>
>>> From: danparker <da...@chordiant.com>
>>> Subject: Re: JDBC not working as expected
>>> To: jcs-users@jakarta.apache.org
>>> Date: Wednesday, August 13, 2008, 10:02 PM
>>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>>> and I exceed that
>>> I get the following exception
>>>
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>>> Exception in thread
>>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>>> java.lang.ClassCastException:
>>> org.apache.jcs.engine.control.group.GroupAttrName
>>> incompatible with
>>> java.lang.String
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>>
>>> Aaron Smuts wrote:
>>> >
>>> > Call get stats and see if the auxiliary is in error.
>>> Look for errors and
>>> > warnings in the logs.
>>> >
>>> > Aaron
>>> >
>>> >
>>> > --- On Tue, 8/12/08, danparker
>>> <da...@chordiant.com> wrote:
>>> >
>>> >> From: danparker
>>> <da...@chordiant.com>
>>> >> Subject: Re: JDBC not working as expected
>>> >> To: jcs-users@jakarta.apache.org
>>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>>> >> We are using version 1.3.
>>> >>
>>> >> We've changed DiskUsagePattern to
>>> DiskUsagePatternName
>>> >> but it had not
>>> >> effect. Still nothing in the database.
>>> >>
>>> >> I'm building a workspace were I can test this
>>> >> independant of our load test
>>> >> environment.
>>> >>
>>> >>
>>> >>
>>> >> hanasakijiji wrote:
>>> >> >
>>> >> > What version of JCS? Are you seeing this
>>> bug?
>>> >> >
>>> >>
>>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>>> >> >
>>> >>
>>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>>> >> > *** is short not String - looks like they
>>> come from an
>>> >> enum or public
>>> >> > static short ....
>>> >> >
>>> >> > might try testBeforeInsert=true and see if
>>> any selects
>>> >> are hitting the
>>> >> > DB at all from the database logs.
>>> >> >
>>> >> > Let us know if you find the solution and what
>>> it is.
>>> >> >
>>> >> >
>>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>>> >> <da...@chordiant.com>
>>> >> > wrote:
>>> >> >>
>>> >> >>
>>> >>
>>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>>> >> >> cache_FDN_WithJDBC.ccf
>>> >> >>
>>> >> >> We've got three cache regions we want
>>> to have
>>> >> the contents in memory(for
>>> >> >> performance) and spooled out to the
>>> database so
>>> >> that we can recover in a
>>> >> >> failover situation. Attached is the
>>> configuration
>>> >> file. We are seeing the
>>> >> >> memory cache fill up but nothing is going
>>> into the
>>> >> database.
>>> >> >>
>>> >> >> I've set the DiskUsagePattern=update
>>> and
>>> >> IsSpool=True - is there
>>> >> >> something
>>> >> >> else I'm missing?
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> View this message in context:
>>> >> >>
>>> >>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>>> >> >> Sent from the JCS - Users mailing list
>>> archive at
>>> >> Nabble.com.
>>> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> >> For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> > For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>>> >> Sent from the JCS - Users mailing list archive at
>>> >> Nabble.com.
>>> >>
>>> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> > For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>>> Sent from the JCS - Users mailing list archive at
>>> Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
> Sent from the JCS - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
I've now got some logging coming out and it's saying that it's putting stuff
on the disk, but we don't see it. We're connected to Oracle and I noticed
the code just closes the connection but doesn't commit any transaction could
this be the issue?
Aaron Smuts wrote:
>
> Hmmn. This might be a problem with groups and the JDBC disk cache. I'll
> have to look into it. In any case, groups are deprecated. I don't
> recommend using them.
>
> Aaron
>
>
> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Wednesday, August 13, 2008, 10:02 PM
>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>> and I exceed that
>> I get the following exception
>>
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> Exception in thread
>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>> java.lang.ClassCastException:
>> org.apache.jcs.engine.control.group.GroupAttrName
>> incompatible with
>> java.lang.String
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>
>> Aaron Smuts wrote:
>> >
>> > Call get stats and see if the auxiliary is in error.
>> Look for errors and
>> > warnings in the logs.
>> >
>> > Aaron
>> >
>> >
>> > --- On Tue, 8/12/08, danparker
>> <da...@chordiant.com> wrote:
>> >
>> >> From: danparker
>> <da...@chordiant.com>
>> >> Subject: Re: JDBC not working as expected
>> >> To: jcs-users@jakarta.apache.org
>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>> >> We are using version 1.3.
>> >>
>> >> We've changed DiskUsagePattern to
>> DiskUsagePatternName
>> >> but it had not
>> >> effect. Still nothing in the database.
>> >>
>> >> I'm building a workspace were I can test this
>> >> independant of our load test
>> >> environment.
>> >>
>> >>
>> >>
>> >> hanasakijiji wrote:
>> >> >
>> >> > What version of JCS? Are you seeing this
>> bug?
>> >> >
>> >>
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >> >
>> >>
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> >> > *** is short not String - looks like they
>> come from an
>> >> enum or public
>> >> > static short ....
>> >> >
>> >> > might try testBeforeInsert=true and see if
>> any selects
>> >> are hitting the
>> >> > DB at all from the database logs.
>> >> >
>> >> > Let us know if you find the solution and what
>> it is.
>> >> >
>> >> >
>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>> >> <da...@chordiant.com>
>> >> > wrote:
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >> >> cache_FDN_WithJDBC.ccf
>> >> >>
>> >> >> We've got three cache regions we want
>> to have
>> >> the contents in memory(for
>> >> >> performance) and spooled out to the
>> database so
>> >> that we can recover in a
>> >> >> failover situation. Attached is the
>> configuration
>> >> file. We are seeing the
>> >> >> memory cache fill up but nothing is going
>> into the
>> >> database.
>> >> >>
>> >> >> I've set the DiskUsagePattern=update
>> and
>> >> IsSpool=True - is there
>> >> >> something
>> >> >> else I'm missing?
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >> >> Sent from the JCS - Users mailing list
>> archive at
>> >> Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> >> Sent from the JCS - Users mailing list archive at
>> >> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18986589.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Correction - I found it. We do use Groups
danparker wrote:
>
> Aaron
>
> I don't see any evidence in the code that we are using groups. It's just
> simple put's. I'm not sure why group id's are showing up in the admin
> page.
>
> Dan
>
>
> Aaron Smuts wrote:
>>
>> Hmmn. This might be a problem with groups and the JDBC disk cache. I'll
>> have to look into it. In any case, groups are deprecated. I don't
>> recommend using them.
>>
>> Aaron
>>
>>
>> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>>
>>> From: danparker <da...@chordiant.com>
>>> Subject: Re: JDBC not working as expected
>>> To: jcs-users@jakarta.apache.org
>>> Date: Wednesday, August 13, 2008, 10:02 PM
>>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>>> and I exceed that
>>> I get the following exception
>>>
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>>> Exception in thread
>>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>>> java.lang.ClassCastException:
>>> org.apache.jcs.engine.control.group.GroupAttrName
>>> incompatible with
>>> java.lang.String
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>>
>>> Aaron Smuts wrote:
>>> >
>>> > Call get stats and see if the auxiliary is in error.
>>> Look for errors and
>>> > warnings in the logs.
>>> >
>>> > Aaron
>>> >
>>> >
>>> > --- On Tue, 8/12/08, danparker
>>> <da...@chordiant.com> wrote:
>>> >
>>> >> From: danparker
>>> <da...@chordiant.com>
>>> >> Subject: Re: JDBC not working as expected
>>> >> To: jcs-users@jakarta.apache.org
>>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>>> >> We are using version 1.3.
>>> >>
>>> >> We've changed DiskUsagePattern to
>>> DiskUsagePatternName
>>> >> but it had not
>>> >> effect. Still nothing in the database.
>>> >>
>>> >> I'm building a workspace were I can test this
>>> >> independant of our load test
>>> >> environment.
>>> >>
>>> >>
>>> >>
>>> >> hanasakijiji wrote:
>>> >> >
>>> >> > What version of JCS? Are you seeing this
>>> bug?
>>> >> >
>>> >>
>>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>>> >> >
>>> >>
>>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>>> >> > *** is short not String - looks like they
>>> come from an
>>> >> enum or public
>>> >> > static short ....
>>> >> >
>>> >> > might try testBeforeInsert=true and see if
>>> any selects
>>> >> are hitting the
>>> >> > DB at all from the database logs.
>>> >> >
>>> >> > Let us know if you find the solution and what
>>> it is.
>>> >> >
>>> >> >
>>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>>> >> <da...@chordiant.com>
>>> >> > wrote:
>>> >> >>
>>> >> >>
>>> >>
>>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>>> >> >> cache_FDN_WithJDBC.ccf
>>> >> >>
>>> >> >> We've got three cache regions we want
>>> to have
>>> >> the contents in memory(for
>>> >> >> performance) and spooled out to the
>>> database so
>>> >> that we can recover in a
>>> >> >> failover situation. Attached is the
>>> configuration
>>> >> file. We are seeing the
>>> >> >> memory cache fill up but nothing is going
>>> into the
>>> >> database.
>>> >> >>
>>> >> >> I've set the DiskUsagePattern=update
>>> and
>>> >> IsSpool=True - is there
>>> >> >> something
>>> >> >> else I'm missing?
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> View this message in context:
>>> >> >>
>>> >>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>>> >> >> Sent from the JCS - Users mailing list
>>> archive at
>>> >> Nabble.com.
>>> >> >>
>>> >> >>
>>> >> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> >> For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >> >>
>>> >> >>
>>> >> >
>>> >> >
>>> >>
>>> ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> > For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >> >
>>> >> >
>>> >> >
>>> >>
>>> >> --
>>> >> View this message in context:
>>> >>
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>>> >> Sent from the JCS - Users mailing list archive at
>>> >> Nabble.com.
>>> >>
>>> >>
>>> >>
>>> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail:
>>> >> jcs-users-unsubscribe@jakarta.apache.org
>>> >> For additional commands, e-mail:
>>> >> jcs-users-help@jakarta.apache.org
>>> >
>>> >
>>> ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> > For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>> >
>>> >
>>> >
>>>
>>> --
>>> View this message in context:
>>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>>> Sent from the JCS - Users mailing list archive at
>>> Nabble.com.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> jcs-users-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> jcs-users-help@jakarta.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18989018.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Aaron
I don't see any evidence in the code that we are using groups. It's just
simple put's. I'm not sure why group id's are showing up in the admin page.
Dan
Aaron Smuts wrote:
>
> Hmmn. This might be a problem with groups and the JDBC disk cache. I'll
> have to look into it. In any case, groups are deprecated. I don't
> recommend using them.
>
> Aaron
>
>
> --- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Wednesday, August 13, 2008, 10:02 PM
>> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
>> and I exceed that
>> I get the following exception
>>
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
>> Exception in thread
>> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
>> java.lang.ClassCastException:
>> org.apache.jcs.engine.control.group.GroupAttrName
>> incompatible with
>> java.lang.String
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
>> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
>> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>>
>> Aaron Smuts wrote:
>> >
>> > Call get stats and see if the auxiliary is in error.
>> Look for errors and
>> > warnings in the logs.
>> >
>> > Aaron
>> >
>> >
>> > --- On Tue, 8/12/08, danparker
>> <da...@chordiant.com> wrote:
>> >
>> >> From: danparker
>> <da...@chordiant.com>
>> >> Subject: Re: JDBC not working as expected
>> >> To: jcs-users@jakarta.apache.org
>> >> Date: Tuesday, August 12, 2008, 1:52 PM
>> >> We are using version 1.3.
>> >>
>> >> We've changed DiskUsagePattern to
>> DiskUsagePatternName
>> >> but it had not
>> >> effect. Still nothing in the database.
>> >>
>> >> I'm building a workspace were I can test this
>> >> independant of our load test
>> >> environment.
>> >>
>> >>
>> >>
>> >> hanasakijiji wrote:
>> >> >
>> >> > What version of JCS? Are you seeing this
>> bug?
>> >> >
>> >>
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >> >
>> >>
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> >> > *** is short not String - looks like they
>> come from an
>> >> enum or public
>> >> > static short ....
>> >> >
>> >> > might try testBeforeInsert=true and see if
>> any selects
>> >> are hitting the
>> >> > DB at all from the database logs.
>> >> >
>> >> > Let us know if you find the solution and what
>> it is.
>> >> >
>> >> >
>> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>> >> <da...@chordiant.com>
>> >> > wrote:
>> >> >>
>> >> >>
>> >>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >> >> cache_FDN_WithJDBC.ccf
>> >> >>
>> >> >> We've got three cache regions we want
>> to have
>> >> the contents in memory(for
>> >> >> performance) and spooled out to the
>> database so
>> >> that we can recover in a
>> >> >> failover situation. Attached is the
>> configuration
>> >> file. We are seeing the
>> >> >> memory cache fill up but nothing is going
>> into the
>> >> database.
>> >> >>
>> >> >> I've set the DiskUsagePattern=update
>> and
>> >> IsSpool=True - is there
>> >> >> something
>> >> >> else I'm missing?
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >> >> Sent from the JCS - Users mailing list
>> archive at
>> >> Nabble.com.
>> >> >>
>> >> >>
>> >> >>
>> >>
>> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >>
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> > For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >> >
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> >> Sent from the JCS - Users mailing list archive at
>> >> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> >> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> >> jcs-users-help@jakarta.apache.org
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18987262.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by Aaron Smuts <as...@yahoo.com>.
Hmmn. This might be a problem with groups and the JDBC disk cache. I'll have to look into it. In any case, groups are deprecated. I don't recommend using them.
Aaron
--- On Wed, 8/13/08, danparker <da...@chordiant.com> wrote:
> From: danparker <da...@chordiant.com>
> Subject: Re: JDBC not working as expected
> To: jcs-users@jakarta.apache.org
> Date: Wednesday, August 13, 2008, 10:02 PM
> When I sent the tryBeforeInsert=true and MaxPurgatory to 10
> and I exceed that
> I get the following exception
>
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R
> Exception in thread
> "CacheEventQueue.QProcessor-InteractionControllerProcessCache"
> java.lang.ClassCastException:
> org.apache.jcs.engine.control.group.GroupAttrName
> incompatible with
> java.lang.String
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
> [8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
> org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
>
> Aaron Smuts wrote:
> >
> > Call get stats and see if the auxiliary is in error.
> Look for errors and
> > warnings in the logs.
> >
> > Aaron
> >
> >
> > --- On Tue, 8/12/08, danparker
> <da...@chordiant.com> wrote:
> >
> >> From: danparker
> <da...@chordiant.com>
> >> Subject: Re: JDBC not working as expected
> >> To: jcs-users@jakarta.apache.org
> >> Date: Tuesday, August 12, 2008, 1:52 PM
> >> We are using version 1.3.
> >>
> >> We've changed DiskUsagePattern to
> DiskUsagePatternName
> >> but it had not
> >> effect. Still nothing in the database.
> >>
> >> I'm building a workspace were I can test this
> >> independant of our load test
> >> environment.
> >>
> >>
> >>
> >> hanasakijiji wrote:
> >> >
> >> > What version of JCS? Are you seeing this
> bug?
> >> >
> >>
> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
> >> >
> >>
> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
> >> > *** is short not String - looks like they
> come from an
> >> enum or public
> >> > static short ....
> >> >
> >> > might try testBeforeInsert=true and see if
> any selects
> >> are hitting the
> >> > DB at all from the database logs.
> >> >
> >> > Let us know if you find the solution and what
> it is.
> >> >
> >> >
> >> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
> >> <da...@chordiant.com>
> >> > wrote:
> >> >>
> >> >>
> >>
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> >> >> cache_FDN_WithJDBC.ccf
> >> >>
> >> >> We've got three cache regions we want
> to have
> >> the contents in memory(for
> >> >> performance) and spooled out to the
> database so
> >> that we can recover in a
> >> >> failover situation. Attached is the
> configuration
> >> file. We are seeing the
> >> >> memory cache fill up but nothing is going
> into the
> >> database.
> >> >>
> >> >> I've set the DiskUsagePattern=update
> and
> >> IsSpool=True - is there
> >> >> something
> >> >> else I'm missing?
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> >> >> Sent from the JCS - Users mailing list
> archive at
> >> Nabble.com.
> >> >>
> >> >>
> >> >>
> >>
> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail:
> >> jcs-users-unsubscribe@jakarta.apache.org
> >> >> For additional commands, e-mail:
> >> jcs-users-help@jakarta.apache.org
> >> >>
> >> >>
> >> >
> >> >
> >>
> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> >> jcs-users-unsubscribe@jakarta.apache.org
> >> > For additional commands, e-mail:
> >> jcs-users-help@jakarta.apache.org
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
> >> Sent from the JCS - Users mailing list archive at
> >> Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> jcs-users-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> >> jcs-users-help@jakarta.apache.org
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
> Sent from the JCS - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
When I sent the tryBeforeInsert=true and MaxPurgatory to 10 and I exceed that
I get the following exception
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R Exception in thread
"CacheEventQueue.QProcessor-InteractionControllerProcessCache"
java.lang.ClassCastException:
org.apache.jcs.engine.control.group.GroupAttrName incompatible with
java.lang.String
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doesElementExist(JDBCDiskCache.java:392)
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCache.doUpdate(JDBCDiskCache.java:244)
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.auxiliary.disk.AbstractDiskCache$MyCacheListener.handlePut(AbstractDiskCache.java:603)
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.engine.CacheEventQueue$PutEvent.doRun(CacheEventQueue.java:688)
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.engine.CacheEventQueue$AbstractCacheEvent.run(CacheEventQueue.java:607)
[8/14/08 0:50:21:693 EDT] 000000aa SystemErr R at
org.apache.jcs.engine.CacheEventQueue$QProcessor.run(CacheEventQueue.java:575)
Aaron Smuts wrote:
>
> Call get stats and see if the auxiliary is in error. Look for errors and
> warnings in the logs.
>
> Aaron
>
>
> --- On Tue, 8/12/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: Re: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Tuesday, August 12, 2008, 1:52 PM
>> We are using version 1.3.
>>
>> We've changed DiskUsagePattern to DiskUsagePatternName
>> but it had not
>> effect. Still nothing in the database.
>>
>> I'm building a workspace were I can test this
>> independant of our load test
>> environment.
>>
>>
>>
>> hanasakijiji wrote:
>> >
>> > What version of JCS? Are you seeing this bug?
>> >
>> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
>> >
>> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
>> > *** is short not String - looks like they come from an
>> enum or public
>> > static short ....
>> >
>> > might try testBeforeInsert=true and see if any selects
>> are hitting the
>> > DB at all from the database logs.
>> >
>> > Let us know if you find the solution and what it is.
>> >
>> >
>> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
>> <da...@chordiant.com>
>> > wrote:
>> >>
>> >>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> >> cache_FDN_WithJDBC.ccf
>> >>
>> >> We've got three cache regions we want to have
>> the contents in memory(for
>> >> performance) and spooled out to the database so
>> that we can recover in a
>> >> failover situation. Attached is the configuration
>> file. We are seeing the
>> >> memory cache fill up but nothing is going into the
>> database.
>> >>
>> >> I've set the DiskUsagePattern=update and
>> IsSpool=True - is there
>> >> something
>> >> else I'm missing?
>> >>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> >> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>> >>
>> >>
>> >>
>> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> >> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >>
>> >>
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> > For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18975743.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by Aaron Smuts <as...@yahoo.com>.
Call get stats and see if the auxiliary is in error. Look for errors and warnings in the logs.
Aaron
--- On Tue, 8/12/08, danparker <da...@chordiant.com> wrote:
> From: danparker <da...@chordiant.com>
> Subject: Re: JDBC not working as expected
> To: jcs-users@jakarta.apache.org
> Date: Tuesday, August 12, 2008, 1:52 PM
> We are using version 1.3.
>
> We've changed DiskUsagePattern to DiskUsagePatternName
> but it had not
> effect. Still nothing in the database.
>
> I'm building a workspace were I can test this
> independant of our load test
> environment.
>
>
>
> hanasakijiji wrote:
> >
> > What version of JCS? Are you seeing this bug?
> >
> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
> >
> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
> > *** is short not String - looks like they come from an
> enum or public
> > static short ....
> >
> > might try testBeforeInsert=true and see if any selects
> are hitting the
> > DB at all from the database logs.
> >
> > Let us know if you find the solution and what it is.
> >
> >
> > On Thu, Aug 7, 2008 at 11:25 PM, danparker
> <da...@chordiant.com>
> > wrote:
> >>
> >>
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> >> cache_FDN_WithJDBC.ccf
> >>
> >> We've got three cache regions we want to have
> the contents in memory(for
> >> performance) and spooled out to the database so
> that we can recover in a
> >> failover situation. Attached is the configuration
> file. We are seeing the
> >> memory cache fill up but nothing is going into the
> database.
> >>
> >> I've set the DiskUsagePattern=update and
> IsSpool=True - is there
> >> something
> >> else I'm missing?
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> >> Sent from the JCS - Users mailing list archive at
> Nabble.com.
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> >> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
> Sent from the JCS - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
We are using version 1.3.
We've changed DiskUsagePattern to DiskUsagePatternName but it had not
effect. Still nothing in the database.
I'm building a workspace were I can test this independant of our load test
environment.
hanasakijiji wrote:
>
> What version of JCS? Are you seeing this bug?
> https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
> http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
> *** is short not String - looks like they come from an enum or public
> static short ....
>
> might try testBeforeInsert=true and see if any selects are hitting the
> DB at all from the database logs.
>
> Let us know if you find the solution and what it is.
>
>
> On Thu, Aug 7, 2008 at 11:25 PM, danparker <da...@chordiant.com>
> wrote:
>>
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> cache_FDN_WithJDBC.ccf
>>
>> We've got three cache regions we want to have the contents in memory(for
>> performance) and spooled out to the database so that we can recover in a
>> failover situation. Attached is the configuration file. We are seeing the
>> memory cache fill up but nothing is going into the database.
>>
>> I've set the DiskUsagePattern=update and IsSpool=True - is there
>> something
>> else I'm missing?
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> Sent from the JCS - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18952403.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by hanasaki jiji <ha...@gmail.com>.
What version of JCS? Are you seeing this bug?
https://issues.apache.org/jira/browse/JCS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490995
http://jakarta.apache.org/jcs/apidocs/org/apache/jcs/engine/behavior/ICompositeCacheAttributes.html
*** is short not String - looks like they come from an enum or public
static short ....
might try testBeforeInsert=true and see if any selects are hitting the
DB at all from the database logs.
Let us know if you find the solution and what it is.
On Thu, Aug 7, 2008 at 11:25 PM, danparker <da...@chordiant.com> wrote:
>
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> cache_FDN_WithJDBC.ccf
>
> We've got three cache regions we want to have the contents in memory(for
> performance) and spooled out to the database so that we can recover in a
> failover situation. Attached is the configuration file. We are seeing the
> memory cache fill up but nothing is going into the database.
>
> I've set the DiskUsagePattern=update and IsSpool=True - is there something
> else I'm missing?
>
>
>
> --
> View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> Sent from the JCS - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by danparker <da...@chordiant.com>.
Thanks - I discovered the DiskUsagePatternName from another post shortly
after posting this one.
We've corrected the typos but we are not seeing anything in the database at
all.
We also set IsLateral, IsRemote to TRUE and kept IsSpool to TRUE out of
desperation.
Any other suggestions?
Aaron Smuts wrote:
>
> There is at least one typo
>
> . . .
>
> jcs.auxiliary.JDBCInteraction=org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCacheFactory
> jcs.auxiliary.ICPC.attributes=org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCacheAttributes
>
> . . .
>
> "JDBCInteraction" should be "ICPC".
>
> I think that the "DiskUsagePattern" should be "DiskUsagePatternName". I
> think there might be a typo in the docs. Sorry.
>
> Aaron
>
> --- On Thu, 8/7/08, danparker <da...@chordiant.com> wrote:
>
>> From: danparker <da...@chordiant.com>
>> Subject: JDBC not working as expected
>> To: jcs-users@jakarta.apache.org
>> Date: Thursday, August 7, 2008, 8:25 PM
>> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
>> cache_FDN_WithJDBC.ccf
>>
>> We've got three cache regions we want to have the
>> contents in memory(for
>> performance) and spooled out to the database so that we can
>> recover in a
>> failover situation. Attached is the configuration file. We
>> are seeing the
>> memory cache fill up but nothing is going into the
>> database.
>>
>> I've set the DiskUsagePattern=update and IsSpool=True -
>> is there something
>> else I'm missing?
>>
>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
>> Sent from the JCS - Users mailing list archive at
>> Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> jcs-users-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
>> jcs-users-help@jakarta.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-users-help@jakarta.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18948985.html
Sent from the JCS - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org
Re: JDBC not working as expected
Posted by Aaron Smuts <as...@yahoo.com>.
There is at least one typo
. . .
jcs.auxiliary.JDBCInteraction=org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCacheFactory
jcs.auxiliary.ICPC.attributes=org.apache.jcs.auxiliary.disk.jdbc.JDBCDiskCacheAttributes
. . .
"JDBCInteraction" should be "ICPC".
I think that the "DiskUsagePattern" should be "DiskUsagePatternName". I think there might be a typo in the docs. Sorry.
Aaron
--- On Thu, 8/7/08, danparker <da...@chordiant.com> wrote:
> From: danparker <da...@chordiant.com>
> Subject: JDBC not working as expected
> To: jcs-users@jakarta.apache.org
> Date: Thursday, August 7, 2008, 8:25 PM
> http://www.nabble.com/file/p18884628/cache_FDN_WithJDBC.ccf
> cache_FDN_WithJDBC.ccf
>
> We've got three cache regions we want to have the
> contents in memory(for
> performance) and spooled out to the database so that we can
> recover in a
> failover situation. Attached is the configuration file. We
> are seeing the
> memory cache fill up but nothing is going into the
> database.
>
> I've set the DiskUsagePattern=update and IsSpool=True -
> is there something
> else I'm missing?
>
>
>
> --
> View this message in context:
> http://www.nabble.com/JDBC-not-working-as-expected-tp18884628p18884628.html
> Sent from the JCS - Users mailing list archive at
> Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-users-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-users-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-users-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-users-help@jakarta.apache.org