jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From danparker <daniel.par...@chordiant.com>
Subject Re: JDBC not working as expected
Date Fri, 15 Aug 2008 11:59:02 GMT

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 <daniel.parker@chordiant.com> wrote:
> 
>> From: danparker <daniel.parker@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
>> <daniel.parker@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
>> <daniel.parker@chordiant.com> wrote:
>> >>>
>> >>>> From: danparker
>> <daniel.parker@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
>> >>>> <daniel.parker@chordiant.com> wrote:
>> >>>> >
>> >>>> >> From: danparker
>> >>>> <daniel.parker@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
>> >>>> >>
>> <daniel.parker@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


Mime
View raw message