> Reinier van den Born wrote: > > Thanks Bart, Mike, Jeroen, and Ard :-), > > > > We finally see some log messages. Actually all the ones > Bart mentions, > > except the 3rd (init failed). > > (btw. DEBUG level is overdoing it a bit, they are all INFO messages) > > > > Is there anything you want us to look for in these > messages, or is the > > fact that they are there enough do draw conclusions? > Just check when you edit and save a document that you see a > "Incoming slide event: " message in the site log about the document.
Reinier indicated that he saw this 'incoming slide event'. @Reinier : my 2 cents are that meta data might not be invalidated correctly....We'll have to sort this out -Ard > > Bart > > > > > > Reinier > > > > > > Bart van der Schans wrote: > > > Hi Reinier, > > > > > > You just have to set the log level to debug in your logging > > > configuration, you don't need to compile anything. Set the > following > > > logging category to debug (the one from the EventLogger): > > > > > > nl.hippo.client.event > > > > > > Jeroen already did email a log4j example on how to do > this. If you > > are > using tomcat take a look the following page for some > logging tips: > > > > > > http://wiki.hippo.nl/display/CMS/Deployment+on+Tomcat+6+with+MySQL+and > > +ActiveMQ > > > > > > > > > > > > Log messages to look for are: > > > "Initialize JMS" > > > "JMS initialization successful" > > > "Initializing JMS failed, will retry in 1000 milliseconds." > > > "Incoming slide event: " > > > > > > Regards, > > > Bart > > > > > > > > > > > > > > > Reinier van den Born wrote: > > >> Hi Ard, > > >> > > >> Do I understand correctly that you are saying that the java > > adapter >> cannot be configured to write DEBUG messages to the >> > > log, so you want us to rebuild it with the logger set to debug? > > >> > > >> Mind you, we use the java adapter out of the box, so if > it doesn't > > (or >> only partially) cache for us, it will not do so >> > for anyone > > using that jar (= anyone using that version of the HST?). > > >> > > >> Reinier > > >> > > >> > > >> > > >> Ard Schrijvers wrote: > > >> > Hello Reinier, > > >> > > > >> > You need to set the EventLogger to debug in the adapter: > > >> > > > >> > > > >> > > > >> > > > http://svn.hippocms.org/viewvc/hippo-repository-java-adapter/trunk/hip > > po > > >> > > > >> > > > -repository-update-notifier/src/java/nl/hippo/client/event/EventLogger > > .j > > >> > ava?revision=11238&view=markup > > >> > > > >> > -Ard > > >> > > > >> >> Hi Ard, > > >> >> > > >> >> It is not entirely clear to me how I should log the JMS. > > >> >> There is a page on the Hippo website concerned with > solving >> > > >> invalidation problems >> >> > > (http://www.hippocms.org/display/CMS/Solving+Cache+Invalidatio > > >> >> n+Problems) but that seems rather outdated. > > >> >> > > >> >> In our logkit.xconf in hippo-repository... I find the >> >> > > following entries: > > >> >> > > >> >> ... > > >> >> <category log-level="INFO" name="jms"> >> >> <log-target > > id-ref="root"/> >> >> <log-target id-ref="error"/> >> >> > </category> > > >> >> ... > > >> >> <category log-level="DEBUG" name="jms.manager"> >> >> > > <log-target id-ref="slide"/> >> >> </category> >> >> ... > > >> >> <category log-level="WARN" name="slide"> >> >> ... > > >> >> <category log-level="INFO" name="jms-cluster"> >> >> > > <log-target id-ref="slide"/> >> >> </category> >> >> ... > > >> >> </category> > > >> >> ... > > >> >> > > >> >> When I look in slide.log.<date>.log >> >> I see > messages like: > > >> >> > > >> >> DEBUG 2008-07-01 15:35:20 > [fortress.slide.notification] >> >> > > Sending event: Slid >> >> eEvent[type=update, > namespace=default >> > > >> name=/files/default.www/content/e-overheid > > >> >> /evenementen/2008/07/test-8-juli.xml] > > >> >> DEBUG 2008-07-01 15:35:00 > [fortress.slide.notification] >> >> > > Publishing message >> >> > > '[EMAIL PROTECTED]' > > >> >> > > >> >> Is this what you mean? Otherwise, can you tell me > how to >> >> > > properly configure logging for jms and what to look for in >> >> > > which log file? > > >> >> > > >> >> Thanks, > > >> >> > > >> >> Reinier > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> Ard Schrijvers wrote: > > >> >>> Hello Reinier, > > >> >>> > > >> >>> I have one more question: it could be that you > aren't caching > > the >> >>> document's content at all, hence the documents > content is > > >> >> updated all >> >>> the time, but not the properties. The > > properties might not >> >> invalidate >> >>> if no jms is > arriving. > > Can you log the jms and confirm that after a >> >>> repository > > change, jms messages are arriving? > > >> >>> > > >> >>> Regards Ard > > >> >>> > > >> >>>> Hi Bart, > > >> >>>> > > >> >>>> We're just using the HST. The dependency on the > version of > > >> >> HST pulls >> >>>> in the java adapter etc. > > >> >>>> But anyway, to cut things short, here is a list of all the > > jars in >> >>>> the war. > > >> >>>> > > >> >>>> > > >> >>>> Reinier > > >> >>>> > > >> >>>> > > >> >>>> Bart van der Schans wrote: > > >> >>>>> Reinier van den Born wrote: > > >> >>>>>> Hi Bart, > > >> >>>>>> > > >> >>>>>> Attached is the pom of the project. > > >> >>>>> Unfortunately I cannot see it from the pom. You > have to >> > > >> look at the >> >>>>> actual jars in your build/deployment. > > >> >>>>> > > >> >>>>> Regards, > > >> >>>>> Bart > > >> >>>>> > > >> >>>>>> Reinier > > >> >>>>>> > > >> >>>>>> > > >> >>>>>> Reinier van den Born wrote: > > >> >>>>>> > Hi Bart, > > >> >>>>>> > > > >> >>>>>> > Can't get a hold on Denis for a quick answer. > Maybe you > > >> >>>> can take a >> >>>>>> look > yourself? > > >> >>>>>> > It is the frontend of the e-overheid project. > > >> >>>>>> > > > >> >>>>>> > Reinier > > >> >>>>>> > > > >> >>>>>> > > > >> >>>>>> > Bart van der Schans wrote: > > >> >>>>>> >> Reinier, > > >> >>>>>> >> > > >> >>>>>> >> Which version of the java adapter are you using? > > >> >>>>>> >> > > >> >>>>>> >> Regards, > > >> >>>>>> >> Bart > > >> >>>>>> >> > > >> >>>>>> >> Ard Schrijvers wrote: > > >> >>>>>> >>> Hello Reinier, > > >> >>>>>> >>> > > >> >>>>>> >>> This makes me believe the invalidation in > the >> >>>> > > repository adapter >> >>>>>> is not >>> working entirely > correct. We > > need someone to >> >>>> sort it out. > > >> >>>>>> Can you tell >>> me how urgent it is, because I > won't >> > > >> be able to >> >>>>>> take a look at it today. > > >> >>>>>> >>> Also one person knowing a lot about the > adapter will be > > in >> >>>>>> office next >>> week because on holiday atm. > > >> >>>>>> >>> > > >> >>>>>> >>> Pls let me know and thanks for sorting out the issue. > > >> >>>>>> >>> > > >> >>>>>> >>> Regards Ard > > >> >>>>>> >>> > > >> >>>>>> >>> > > >> >>>>>> >>> > > > >> >>>>>> >>> > The value we see in DAV for the property > is the >> > > >>>> updated value. > > >> >>>>>> >>> > > > >> >>>>>> >>> > Reinier > > >> >>>>>> >>> > > > >> >>>>>> >>> > > > >> >>>>>> >>> > Ard Schrijvers wrote: > > >> >>>>>> >>> > > Hello Reinier, > > >> >>>>>> >>> > > > > >> >>>>>> >>> > > Hopefully you can test one more thing > for me >> >> > > (and then I >> >>>>>> fully do >>> > > believe it is a > caching bug, > > though it >> >>>> must be in >> >>>>>> the Repository >>> > > > > Adapter then, a tool I am not to >> >> familiar >> >>>>>> > with (more > > with cocoon's >>> > > cache) but I should be able to >> >>>>>> > > reproduce it then and fix >>> > it). So the >>> > > >> > >>>> thing you > > might >> >>>>>> want to test for me: > > >> >>>>>> >>> > > > > >> >>>>>> >>> > > If in the frontend, the property date is not >> > > >>>> equal to the >> >>>>>>>>>> date in the >>> > > > document (which > > might thus >> >>>> indicate only >> >>>>>> partial >>> > > > invalidation worked, >>> > > in other >> >>>> words, only the >> > > >>>>>> document itself invalidated >>> > (though, without >>> > >> > > >>>>> knowing >> >>>>>> the repo adapter I can hardly > imagine how... > > :-) )) and >> >>>> not >>> > > >> >>>>>> the property. Now, if, > > after you have this situation, you >> >>>>>>>> can >> > >>>>>> browse > > >>> > > the repository with something like webdav >> >>>> > pilot, and > > >> >>>>>> look at the >>> > > webdav property on the > document. Can >> > > >>>> you confirm >> >>>>>> that this is the >>> > > correct webdav > > property, thus >> >>>> the changed >> >>>>>> value. If > so, I >>> > > > need to look >>> > > at the adapter >> >>>>>> invalidation > mechanism, > > >>> > > >>> > > Regards Ard >>> >>> > >> >>>>>>>> Hi Ard, >>> > >> > > >>> > >> In addition to my previous >> >>>> answer (I >> > >>>>>> get > > my info from the guy that >>> > >> did the >> >> > implementation, so > > >> >>>>>> there is a bit of delay on the line :-) >>> > >> >>> > We > > have >> >>>>>> printed the date as it is in the document > together >>> > > > >> >>>> with the >> >>>>>>>>>>>> extracted property > next to each > > other. Normally they are >> >>>>>>>>>> identical. > > >> >>>>>> >>> > >> It proved that after modifying the > document they > > would >> >>>>>> differ: the >> >>>>>> >>> > >> property > showing the > > old value. > > >> >>>>>> >>> > >> A restart of tomcat would sync them again. > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> Reinier > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> Ard Schrijvers wrote: > > >> >>>>>> >>> > >>> Hello, > > >> >>>>>> >>> > >>> > > >> >>>>>> >>> > >>> The frontend you describe is an > extended cms, a > > cocoon >> >>>>>>>>>>>> frontend or a >>> > >>> other frontend? > > >> >>>>>> >>> > >>> > > >> >>>>>> >>> > >>> How is the property containing the date called? > > >> >>>> How do you > > >> >>>>>>>>>>>> store this >>> > >>> date? Something like >> >>>> > > 20080702 or in a >> >>>>>> more Date like >>> > format? If > the >>> > > > >>> latter, >> >>>> you need to >> >>>>>> add this property to be > > 'date' indexed to the >>> > >>> >> >>>> indexing.xml >> >>>>>> > > configuration of the repository. Can you tell me the >>> > >>> >> > > >>>>>> format you store the property in. > > >> >>>>>> >>> > >>> > > >> >>>>>> >>> > >>> It does not seem to me to be a caching > issue, >> > > >>>> because the >> >>>>>>>>>> frontend >>> > >>> result > seems to be > > invalidated >> >>>> and rendered >> >>>>>> (improperly >>> > >> > > though) again, >>> > >>> right? > > >> >>>>>> >>> > >>> > > >> >>>>>> >>> > >>> Furthermore, can you show me the dasls > which >> > > >>>> should do the >> >>>>>>>>>>>> sorting? I >>> > >>> have used > > things like this >> >>>> really many >> >>>>>> times, so sorting > > should >>> > >>> definitely work. Pls >> >>>> provide the > >> >>>>>> > > information asked for and >>> > >> I'll take a >>> > >>> >> >>>> > > look, >>> >> >>>>>>>>>> >>> > >>> Regards Ard >>> > >>> > >>> > >>>> Hi > > >> >> all, >>> > >>>>>>>>>>>>>>>>>> We experience a problem > that seems > > >> to have to do >> >>>>>> with >>> > caching and >>> > >>>> DASL > > queries. > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> Situation: > > >> >>>>>> >>> > >>>> We have documents containing a date. > The date is > > >> >>>>>> extracted >>> > >> and turned >>> > >>>> into a > DAV property. > > >> >>>>>> Documents are organised in folders. > > >> >>>>>> >>> > >>>> We have three pages that list documents. > > >> >>>>>> >>> > >>>> One lists all docs within a folder. > This uses > > >> >>>> a simple >> >>>>>>>>>> DASL-query. > > >> >>>>>> >>> > >>>> The other two list a subset of all > documents >> > > >>>> ordered on >> >>>>>>>>>> this date. > > >> >>>>>> >>> > >>>> These pages use a similar query but > with a >> > > >>>> sort (on >>> >> >>>>>>>>>>> date) and a limit (first > 20 or so). > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> There are several problems: > > >> >>>>>> >>> > >>>> When we add a new document, it rarely > shows up > > >> >>>> on any of >> >>>>>>>>>> the pages. > > >> >>>>>> >>> > >>>> When we change a date, the new date > is shown >> > > >>>> in the >>> >> >>>>>>>>> listing, but the >>> > >>>> > list is not > > sorted accordingly. > > >> >>>>>> This differs per >>> > >>>> page: the full > listing usually > > is >> >>>>>> correct, but the limited >>> > >> listings > >>> > >>>> > > >> >> are in the >> >>>>>> wrong order. > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> When we reset everything (repo+frontend), >> > > >>>> everything is >> >>>>>> as >>> > >> expected. > > >> >>>>>> >>> > >>>> We have two installation: one running > repo on > > >> >>>> jetty and >> >>>>>>>>>>>> frontend on >>> > >>>> tomcat, > > other running both on >> >>>>>> tomcat. Problems are more > or >>> > >> > > less the >>> > >> >>>>>>>> same on >> >>>>>> either installation. > > >> >>>>>> >>> > >>>> (on jetty we used repo: 1.2.14.rc1 > and 1.2.15.1, > > on >> >>>>>> tomcat only >>> > >>>> 1.2.14.rc1) >>> > >>>> > >>> > >>>> > > Any >> >>>>>> ideas? > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> Thanks, > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> Reinier > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> -- > > >> >>>>>> >>> > >>>> > > >> >>>>>> >>> > >>>> Reinier van den Born >> >>>>>> >>> > > >>>> >> > > >>>>>> >>> > >>>> HintTech B.V. > > >> >>>>>> >>> > >>>> Rotterdamseweg 183c, 2629 HD Delft > >>> > >>>> T: > > >> >>>>>> +31(0)15 268 2573 >>> > >>>> F: +31(0)15 268 > 2567 >>> >> > > >>>>>>> M: > > >> >>>>>> +31(0)6 494 171 36 >>> > >>>> -- >>> > >>>> > HintTech levert > > >> >>>>>> specialisten op het gebied van >>> > >> >> >>>> > > softwareontwikkeling >>> > >> >>>>>>>>>> (.NET en Java), > > projectmanagement, >> >>>> informatiebeveiliging >>> > >> > >>>>>>>> > > en business >>> > >>>> consulting. > > >> >>>>>> >>> > >>>> KvK Den Haag nr. 27242282 | BTW nr. > > NL8062.16.396.B01 >> >>>>>>>>>>>>>> >>> > >>> > > ******************************************** > > >> >>>>>> >>> > >>> Hippocms-dev: Hippo CMS development public > > mailinglist >> >>>>>>>>>>>>> >>> > >>> Searchable archives > can be found at: > > >> >>>>>> >>> > >>> <a > > >> >>>> > href=ttp://hippocms-dev.markmail.org/">MarkMail</a> and >> > > >>>>>>>>>>>> <a >> >>>>>> > > href="http://www.nabble.com/Hippo-CMS-f26633.html";>Nable</a>. > > >> >>>>>> >>> > >> -- > > >> >>>>>> >>> > >> > > >> >>>>>> >>> > >> Reinier van den Born >> >>>>>> >>> > >> >> > > >>>>>> >>> > >> HintTech B.V. > > >> >>>>>> >>> > >> Rotterdamseweg 183c, 2629 HD Delft >>> > > >> >> >> > > T: +31(0)15 >> >>>>>> 268 2573 >>> > >> F: +31(0)15 268 > 2567 >>> > >> > > M: > > >> >>>> +31(0)6 494 171 > > >> >>>>>> 36 >>> > >> -- >>> > >> HintTech levert > specialisten op >> > > >>>> het gebied >> >>>>>> van >>> > softwareontwikkeling >>> > >> > > (.NET en Java), >> >>>>>> projectmanagement, informatiebeveiliging > > >>> > en >> >>>> business >>> > >> >> >>>>>> consulting. > > >> >>>>>> >>> > >> KvK Den Haag nr. 27242282 | BTW nr. > > >> >>>> NL8062.16.396.B01 >>> > > >> >>>>>>>>> >>> > > ******************************************** > > >> >>>>>> >>> > > Hippocms-dev: Hippo CMS development > public >> >>>> > > mailinglist >>> >> >>>>>>>> >>> > > Searchable archives > can be found > > at: > > >> >>>>>> >>> > > MarkMail: > http://hippocms-dev.markmail.org >>> > > > >> >>>>> Nabble: > > >> >>>>>> http://www.nabble.com/Hippo-CMS-f26633.html > > >> >>>>>> >>> > > > > >> >>>>>> >>> > > > >> >>>>>> >>> > -- > > >> >>>>>> >>> > > > >> >>>>>> >>> > Reinier van den Born > > >> >>>>>> >>> > > > >> >>>>>> >>> > HintTech B.V. > > >> >>>>>> >>> > Rotterdamseweg 183c, 2629 HD Delft >>> > T: > > >> >>>> +31(0)15 268 2573 > > >> >>>>>>>>>> F: +31(0)15 268 2567 >>> > M: +31(0)6 494 > 171 36 >>> > > > -- >> >>>>>>>>>> HintTech levert specialisten op het > gebied van >>> > > > >> >>>>>> softwareontwikkeling (.NET en Java), > projectmanagement, >>> > > > >> >>>>>> informatiebeveiliging en business consulting. > > >> >>>>>> >>> > KvK Den Haag nr. 27242282 | BTW nr. > > >> >>>> NL8062.16.396.B01 >>> > > > >> >>>>>>>>> ******************************************** > > >> >>>>>> >>> Hippocms-dev: Hippo CMS development public >> >>>> > > mailinglist >>> >>> >> >>>>>> Searchable archives can be found at: > > >> >>>>>> >>> MarkMail: http://hippocms-dev.markmail.org > >>> Nabble: > > >> >>>>>> http://www.nabble.com/Hippo-CMS-f26633.html > > >> >>>>>> >>> > > >> >>>>>> >> > > >> >>>>>> >> > > >> >>>>>> > > > >> >>>>>> > ******************************************** > > >> >>>>>> > Hippocms-dev: Hippo CMS development public > mailinglist > > > > >> >>>>>> Searchable archives can be found at: > > >> >>>>>> > MarkMail: http://hippocms-dev.markmail.org > Nabble: > > >> >>>>>> http://www.nabble.com/Hippo-CMS-f26633.html > > >> >>>>>> > > > >> >>>>>> > > >> >>>>>> -- > > >> >>>>>> > > >> >>>>>> Reinier van den Born > > >> >>>>>> > > >> >>>>>> HintTech B.V. > > >> >>>>>> Rotterdamseweg 183c, 2629 HD Delft >> >>>>>> T: > +31(0)15 > > 268 2573 >> >>>>>> F: +31(0)15 268 2567 >> >>>>>> M: > +31(0)6 494 171 > > 36 >> >>>>>> -- >> >>>>>> HintTech levert specialisten op > het gebied > > van >> >>>> softwareontwikkeling >> >>>>>> (.NET en Java), > > projectmanagement, informatiebeveiliging >> >>>> en business >> > > >>>>>> consulting. > > >> >>>>>> KvK Den Haag nr. 27242282 | BTW nr. > NL8062.16.396.B01 >> > > >>>>>> >> >>>> -- >> >>>> >> >>>> Reinier van den Born > >> >>>> >> > > >>>> HintTech B.V. > > >> >>>> Rotterdamseweg 183c, 2629 HD Delft >> >>>> T: > +31(0)15 268 > > 2573 >> >>>> F: +31(0)15 268 2567 >> >>>> M: +31(0)6 494 > 171 36 >> > > >>>> -- >> >>>> HintTech levert specialisten op het gebied > van >> >> > > softwareontwikkeling >> >>>> (.NET en Java), projectmanagement, > > informatiebeveiliging >> >> en business >> >>>> consulting. > > >> >>>> KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01 >> > > >>>> >> >>> ******************************************** > > >> >>> Hippocms-dev: Hippo CMS development public > mailinglist >> >>> > > >> >>> Searchable archives can be found at: > > >> >>> MarkMail: http://hippocms-dev.markmail.org >> >>> Nabble: > > http://www.nabble.com/Hippo-CMS-f26633.html > > >> >>> > > >> >> -- > > >> >> > > >> >> Reinier van den Born > > >> >> > > >> >> HintTech B.V. > > >> >> Rotterdamseweg 183c, 2629 HD Delft >> >> T: > +31(0)15 268 2573 > > >> >> F: +31(0)15 268 2567 >> >> M: +31(0)6 494 171 36 >> > >> -- >> > > >> HintTech levert specialisten op het gebied van >> >> > > softwareontwikkeling (.NET en Java), projectmanagement, >> >> > > informatiebeveiliging en business consulting. > > >> >> KvK Den Haag nr. 27242282 | BTW nr. > NL8062.16.396.B01 >> >> > > >> > ******************************************** > > >> > Hippocms-dev: Hippo CMS development public > mailinglist >> > >> > > > Searchable archives can be found at: > > >> > MarkMail: http://hippocms-dev.markmail.org >> > Nabble: > > http://www.nabble.com/Hippo-CMS-f26633.html > > >> > > > >> > > >> -- > > >> > > >> Reinier van den Born > > >> > > >> HintTech B.V. > > >> Rotterdamseweg 183c, 2629 HD Delft >> T: +31(0)15 268 > 2573 >> F: > > +31(0)15 268 2567 >> M: +31(0)6 494 171 36 >> -- >> > HintTech levert > > specialisten op het gebied van softwareontwikkeling >> (.NET en > > Java), >> projectmanagement, informatiebeveiliging en business > > consulting. > > >> KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01 >> > > > > > > -- > > > > Reinier van den Born > > > > HintTech B.V. > > Rotterdamseweg 183c, 2629 HD Delft > > T: +31(0)15 268 2573 > > F: +31(0)15 268 2567 > > M: +31(0)6 494 171 36 > > -- > > HintTech levert specialisten op het gebied van softwareontwikkeling > > (.NET en Java), projectmanagement, informatiebeveiliging en > business > > consulting. > > KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01 > > > > > -- > Hippo B.V. - Amsterdam > Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 > > Hippo USA Inc. - San Francisco > 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 > ----------------------------------------------------------------- > http://www.onehippo.com - [EMAIL PROTECTED] > ----------------------------------------------------------------- > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > > Searchable archives can be found at: > MarkMail: http://hippocms-dev.markmail.org > Nabble: http://www.nabble.com/Hippo-CMS-f26633.html > > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist Searchable archives can be found at: MarkMail: http://hippocms-dev.markmail.org Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
