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:[EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> > 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 <[EMAIL PROTECTED]> wrote: >>> >>>> From: danparker <[EMAIL PROTECTED]> >>>> 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 >>>> <[EMAIL PROTECTED]> wrote: >>>> > >>>> >> From: danparker >>>> <[EMAIL PROTECTED]> >>>> >> 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 >>>> >> <[EMAIL PROTECTED]> >>>> >> > 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: >>>> >> [EMAIL PROTECTED] >>>> >> >> For additional commands, e-mail: >>>> >> [EMAIL PROTECTED] >>>> >> >> >>>> >> >> >>>> >> > >>>> >> > >>>> >> >>>> --------------------------------------------------------------------- >>>> >> > To unsubscribe, e-mail: >>>> >> [EMAIL PROTECTED] >>>> >> > For additional commands, e-mail: >>>> >> [EMAIL PROTECTED] >>>> >> > >>>> >> > >>>> >> > >>>> >> >>>> >> -- >>>> >> 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: >>>> >> [EMAIL PROTECTED] >>>> >> For additional commands, e-mail: >>>> >> [EMAIL PROTECTED] >>>> > >>>> > >>>> --------------------------------------------------------------------- >>>> > To unsubscribe, e-mail: >>>> [EMAIL PROTECTED] >>>> > For additional commands, e-mail: >>>> [EMAIL PROTECTED] >>>> > >>>> > >>>> > >>>> >>>> -- >>>> 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: >>>> [EMAIL PROTECTED] >>>> For additional commands, e-mail: >>>> [EMAIL PROTECTED] >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> -- >> 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: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
