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

CCristianS
CCristianS
Offline

Badges

Badges
3

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
0

Posts & Comments

Posts & Comments
3

Discussions

Discussions
0

Questions

Questions
3

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by CCristianS
Customize the badges you want to showcase on your profile
Adding a new node to an existing cluster - Adobe LiveCycle 14-07-2013
Hi,Our project is using Livecycle ES2.5 patch 1 on top of Weblogic.Due to some lock contentions we need to add more servers (as a urgent solution) cause we cannot fix the issue othewise soon.So adding new node to an existing cluster (Weblogic) is a pure Weblogic operations or we need to do something else on Livecycle side ?Thanks a lot !

Views

877

Likes

0

Replies

1
Lock contention on ES4 as well - Adobe LiveCycle 19-06-2013
We had some performance problems on ES2 due to a lock contention and we were advised to instal ES4 and try.It is better in terms of performance BUT we have similar lock contention problems under heavy load "[ACTIVE] ExecuteThread: '38' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock weblogic.utils.classloaders.ChangeAwareClassLoader@1b490621 BLOCKED Line 35925: "[ACTIVE] ExecuteThread: '37' for queue: 'weblogic.kernel.Default (self-tuning)'" waiting for lock org.ungoverned.m...

Views

2.7K

Likes

0

Replies

0
Lock contention on ES2 - Adobe LiveCycle 07-06-2013
Calling a dummy process by one WS client take like 50 ms.(fast enough)Calling it via 50 concurrent client ==> a degradation of 100 time ==> 5 seconds response timeVersion used ES2 with some patches. on top of weblogicInvestigations I have done show lock contention due to inneficient use of xstream parser (are instantiated each time )Any of you had similar problems ?A colleague of mine tried on ES4 and it seems there with 50 users the response time is 50 ms so as expected.this was an know issue f...

Views

1.9K

Likes

0

Replies

0