Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

federicos727792
federicos727792
Offline

Badges

Badges
15

Accepted Solutions

Accepted Solutions
3

Likes Received

Likes Received
4

Posts

Posts
49

Discussions

Discussions
21

Questions

Questions
28

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by federicos727792
Customize the badges you want to showcase on your profile
Re: This session has been closed - Adobe Experience Manager 30-01-2017
Feike, Thx for the link. We're going to try that.Jörg, Only rarely. Indeed it looks like a race condition.

Views

2.9K

Likes

0

Replies

0
Re: This session has been closed - Adobe Experience Manager 30-01-2017
It iterates the result hits and adds some of the properties to a set, but I think that doesn't really matter, as query.getResult() fails before going into that method.

Views

2.9K

Likes

0

Replies

1
Re: This session has been closed - Adobe Experience Manager 30-01-2017
Ah yes, I forgot to mention that we're changing that soon, closing the resource resolver in fact.But that would fix a potential session / memory leak, not the problem we're having. Also a quick inspection of the source code showed that sessions themselves are not reused.

Views

2.9K

Likes

0

Replies

3
This session has been closed - Adobe Experience Manager 29-01-2017
Hey, we're seeing this problem (session closed) randomly and in general under heavy load. 25.01.201704:23:19.269 *ERROR* [pool-7-thread-5]com.xxx.global.aem.web.service.widget.WidgetPollingSchedulerRun failed java.lang.IllegalStateException:This session has been closed at com.google.common.base.Preconditions.checkState(Preconditions.java:150) at org.apache.jackrabbit.oak.core.ContentSessionImpl.checkLive(ContentSessionImpl.java:85) at org.apache.jackrabbit.oak.core.MutableRoot.checkLive(MutableR...

Views

4.5K

Likes

0

Replies

7
Re: How to create a system user in AEM 6.1? - Adobe Experience Manager 18-01-2017
Thanks for the quick answer. During my testing I've found that it works too.Thx,Federico

Views

2.0K

Likes

0

Replies

0
Re: How to create a system user in AEM 6.1? - Adobe Experience Manager 17-01-2017
Hi srikanth,Were you able to resolve this?

Views

2.0K

Likes

0

Replies

0
Re: AEM / JCR in read only mode - Adobe Experience Manager 22-12-2016
Thanks a lot for all the comments. We're also considering using https://adobe-consulting-services.github.io/acs-aem-commons/features/system-notifications.html, which afaik will not enforce it, but should be enough for our use case.

Views

2.2K

Likes

0

Replies

1
Re: compaction - which nodes are being deleted - Adobe Experience Manager 23-11-2016
Opkar, Nope, I wasn't using the rm-all flag. Jörg,Thanks a lot for the article. I was doing exactly that. The tip of the stacktrace generation when creating a new session is quite neat!In the end the problem was an hourly invoked process that was rebuilding some content packages and downloading them from aem. The rebuilding operation increases the size of the repository by the same amount as the package size (which is over one GB). I suppose this is because of the appending nature of the JCR imp...

Views

712

Likes

0

Replies

0
Re: compaction - which nodes are being deleted - Adobe Experience Manager 22-11-2016
Hi guys, thanks for the answers.I've seen some of these articles before, however the main problem is that the repository is growing really fast (like 1gb per hour) without any activity that could explain it. I've tried an off-line compaction. It was relatively fast (3 minutes) and the compression was quite good, however after restarting aem the repository started to grow again. Hence I really need to investigate the root cause of the problem.The latest suspect is the integration with adobe targe...

Views

705

Likes

0

Replies

0
compaction - which nodes are being deleted - Adobe Experience Manager 20-11-2016
We've problems with a repository growing out of control. Luckily compaction helps a lot (we're using online compaction), but I'd like to determine what is being deleted (compacted).I'm using java -Dlogback.configurationFile=/tmp/logback.xml -jar ~/Downloads/oak-run-1.4.9.jar compact repository/segmentstore/ >>/tmp/oak-run.logwith logback logging at trace level to try to determine what is being deleted. Although it seems to be pretty close, it's not really telling me the path of the nodes that ar...

Views

1.6K

Likes

2

Replies

6