You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by Geoffroy Schneck <gs...@adobe.com> on 2015/07/14 14:36:19 UTC
Idle Oak jcr sessions in AEM 6.1
Hello Oak devs,
AEM 6.1 GA logs a bunch of WARN messages of idle sessions that might be out of date, see bottom of mail .
We are in the process of logging Jira issues to prevent their apparition from the various product components involved.
However, customers can worry about this , and we would like to inform them what it means technically and why they should not worry about them .
Could someone provide us with a meaningful explanation ? @Harsh, this information could end up in an Oak KB Article .
Thanks a lot.
16.06.2015 11:32:42.779 *WARN* [0:0:0:0:0:0:0:1 [1434468762730] GET /etc/replication/agents.author.pages.json HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 3 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 11:34:17.040 *WARN* [pool-25-thread-1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 4 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 12:12:58.851 *WARN* [Statistics write back] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 43 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 18:42:31.006 *WARN* [pool-7-thread-3] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 180 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 23:26:32.367 *WARN* [0:0:0:0:0:0:0:1 [1434511592339] GET /content/dam/projects.assets.json HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 85 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 23:27:15.337 *WARN* [0:0:0:0:0:0:0:1 [1434511635319] GET /content/catalogs.pages.json HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 86 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 23:28:21.794 *WARN* [0:0:0:0:0:0:0:1 [1434511701598] GET /etc/clientcontext/default/content/jcr:content/stores.init.js HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 87 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
error.log.2015-06-16 29011 16.06.2015 23:28:22.211 *WARN* [0:0:0:0:0:0:0:1 [1434511701598] GET /etc/clientcontext/default/content/jcr:content/stores.init.js HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 87 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 23:33:56.833 *WARN* [Thread-20] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 93 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
16.06.2015 23:33:56.893 *WARN* [0:0:0:0:0:0:0:1 [1434512036632] GET /content/geometrixx-media/en/jcr:content/grid-4-par/popular_articles.fetch-popular.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has been idle for 93 minutes and might be out of date. Consider using a fresh session or explicitly refresh the session.
at org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
[cid:image001.png@01CF3C74.944BEB30]
Geoffroy Schneck
Program manager - Team Lead
Marketing Cloud Customer Care
T: +41 61 226 55 70
M: +41 79 207 45 04
email: gschneck@adobe.com<ma...@adobe.com>
Barfuesserplatz 6
CH-4001 Basel, Switzerland
www.adobe.com<http://www.adobe.com/>
[cid:image006.jpg@01D0BE42.71C4B460]
For CQ support and tips, follow us on Twitter: @AdobeMktgCare<https://twitter.com/AdobeMktgCare>
RE: Idle Oak jcr sessions in AEM 6.1
Posted by Geoffroy Schneck <gs...@adobe.com>.
Adding Harsh and Daniel again in the thread.
@Harsh feel free to comment if you need more precisions .
Geoffroy Schneck
Program manager - Team Lead
Marketing Cloud Customer Care
T: +41 61 226 55 70
M: +41 79 207 45 04
email: gschneck@adobe.com
Barfuesserplatz 6
CH-4001 Basel, Switzerland
www.adobe.com
For CQ support and tips, follow us on Twitter: @AdobeMktgCare
-----Original Message-----
From: Michael Dürig [mailto:mduerig@apache.org]
Sent: Dienstag, 14. Juli 2015 14:54
To: oak-dev@jackrabbit.apache.org
Subject: Re: Idle Oak jcr sessions in AEM 6.1
Hi,
On 14.7.15 2:36 , Geoffroy Schneck wrote:
> Hello Oak devs,
>
> AEM 6.1 GA logs a bunch of WARN messages of idle sessions that might
> be out of date, see bottom of mail .
>
> We are in the process of logging Jira issues to prevent their
> apparition from the various product components involved.
>
> However, customers can worry about this , and we would like to inform
> them what it means technically and why they should not worry about them .
The warning indicates that the session is old and you are about to access potentially outdated information.
>
> Could someone provide us with a meaningful explanation ? @Harsh, this
> information could end up in an Oak KB Article .
See
http://jackrabbit.apache.org/oak/docs/differences.html#Session_state_and_refresh_behaviour
about how sessions behave in Oak in contrast to Jackrabbit 2. There is specific mention of the warning you encounter.
Michael
>
> Thanks a lot.
>
> 16.06.2015 11:32:42.779 *WARN* [0:0:0:0:0:0:0:1 [1434468762730] GET
> /etc/replication/agents.author.pages.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 3 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 11:34:17.040 *WARN* [pool-25-thread-1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 4 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 12:12:58.851 *WARN* [Statistics write back]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 43 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 18:42:31.006 *WARN* [pool-7-thread-3]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 180 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 23:26:32.367 *WARN* [0:0:0:0:0:0:0:1 [1434511592339] GET
> /content/dam/projects.assets.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 85 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 23:27:15.337 *WARN* [0:0:0:0:0:0:0:1 [1434511635319] GET
> /content/catalogs.pages.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 86 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 23:28:21.794 *WARN* [0:0:0:0:0:0:0:1 [1434511701598] GET
> /etc/clientcontext/default/content/jcr:content/stores.init.js
> HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This
> session has been idle for 87 minutes and might be out of date.
> Consider using a fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> error.log.2015-06-16 29011 16.06.2015 23:28:22.211 *WARN*
> [0:0:0:0:0:0:0:1 [1434511701598] GET
> /etc/clientcontext/default/content/jcr:content/stores.init.js
> HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This
> session has been idle for 87 minutes and might be out of date.
> Consider using a fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 23:33:56.833 *WARN* [Thread-20]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 93 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> 16.06.2015 23:33:56.893 *WARN* [0:0:0:0:0:0:0:1 [1434512036632] GET
> /content/geometrixx-media/en/jcr:content/grid-4-par/popular_articles.f
> etch-popular.html HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 93 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(R
> efreshStrategy.java:169)
>
> cid:image001.png@01CF3C74.944BEB30
>
>
>
> *Geoffroy Schneck*
> Program manager - Team Lead
> Marketing Cloud Customer Care
>
>
>
> T: +41 61 226 55 70
>
> M: +41 79 207 45 04
>
> email: gschneck@adobe.com <ma...@adobe.com>
>
>
>
> Barfuesserplatz 6
> CH-4001 Basel, Switzerland
> www.adobe.com <http://www.adobe.com/>
>
>
>
>
>
>
>
> For CQ support and tips, follow us on Twitter: @AdobeMktgCare
> <https://twitter.com/AdobeMktgCare>
>
Re: Idle Oak jcr sessions in AEM 6.1
Posted by Michael Dürig <md...@apache.org>.
Hi,
On 14.7.15 2:36 , Geoffroy Schneck wrote:
> Hello Oak devs,
>
> AEM 6.1 GA logs a bunch of WARN messages of idle sessions that might be
> out of date, see bottom of mail .
>
> We are in the process of logging Jira issues to prevent their apparition
> from the various product components involved.
>
> However, customers can worry about this , and we would like to inform
> them what it means technically and why they should not worry about them .
The warning indicates that the session is old and you are about to
access potentially outdated information.
>
> Could someone provide us with a meaningful explanation ? @Harsh, this
> information could end up in an Oak KB Article .
See
http://jackrabbit.apache.org/oak/docs/differences.html#Session_state_and_refresh_behaviour
about how sessions behave in Oak in contrast to Jackrabbit 2. There is
specific mention of the warning you encounter.
Michael
>
> Thanks a lot.
>
> 16.06.2015 11:32:42.779 *WARN* [0:0:0:0:0:0:0:1 [1434468762730] GET
> /etc/replication/agents.author.pages.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 3 minutes and might be out of date. Consider using a fresh
> session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 11:34:17.040 *WARN* [pool-25-thread-1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 4 minutes and might be out of date. Consider using a fresh
> session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 12:12:58.851 *WARN* [Statistics write back]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 43 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 18:42:31.006 *WARN* [pool-7-thread-3]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 180 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 23:26:32.367 *WARN* [0:0:0:0:0:0:0:1 [1434511592339] GET
> /content/dam/projects.assets.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 85 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 23:27:15.337 *WARN* [0:0:0:0:0:0:0:1 [1434511635319] GET
> /content/catalogs.pages.json HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 86 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 23:28:21.794 *WARN* [0:0:0:0:0:0:0:1 [1434511701598] GET
> /etc/clientcontext/default/content/jcr:content/stores.init.js HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 87 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> error.log.2015-06-16 29011 16.06.2015 23:28:22.211 *WARN*
> [0:0:0:0:0:0:0:1 [1434511701598] GET
> /etc/clientcontext/default/content/jcr:content/stores.init.js HTTP/1.1]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 87 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 23:33:56.833 *WARN* [Thread-20]
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This session has
> been idle for 93 minutes and might be out of date. Consider using a
> fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> 16.06.2015 23:33:56.893 *WARN* [0:0:0:0:0:0:0:1 [1434512036632] GET
> /content/geometrixx-media/en/jcr:content/grid-4-par/popular_articles.fetch-popular.html
> HTTP/1.1] org.apache.jackrabbit.oak.jcr.session.RefreshStrategy This
> session has been idle for 93 minutes and might be out of date. Consider
> using a fresh session or explicitly refresh the session.
>
> at
> org.apache.jackrabbit.oak.jcr.session.RefreshStrategy$LogOnce.<init>(RefreshStrategy.java:169)
>
> cid:image001.png@01CF3C74.944BEB30
>
>
>
> *Geoffroy Schneck*
> Program manager – Team Lead
> Marketing Cloud Customer Care
>
>
>
> T: +41 61 226 55 70
>
> M: +41 79 207 45 04
>
> email: gschneck@adobe.com <ma...@adobe.com>
>
>
>
> Barfuesserplatz 6
> CH-4001 Basel, Switzerland
> www.adobe.com <http://www.adobe.com/>
>
>
>
>
>
>
>
> For CQ support and tips, follow us on Twitter: @AdobeMktgCare
> <https://twitter.com/AdobeMktgCare>
>