Pazhanikanthan Periasamy

Greenhorn
+ Follow
since Jul 18, 2011
Merit badge: grant badges
For More
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Pazhanikanthan Periasamy

Yes if you satisfy following 3 :

1. If you are trying SSO, then you need to have both managed servers within same domain connected to same Authentication Security Provider.
2. You should have same JSESSION Cookie ID for both applications
3. You should have a Web Server / Load Balancer in front of the managed servers so the FQDN (Fully Qualified Domain Name) URL is same.

Hope this helps.
12 years ago
1. What verison of WebLogic server are you using?
2. What do you mean by stale?
12 years ago
Dont worry about them.

You dint even work for more than 10 days. Dont worry as long as you are starting your career in India and you dont want to put that company in your resume.
12 years ago
We built a mechanism in my previous project.

It was a high performance web application (website) of a big airline company hosting their enterprise content site.

We use ehcache internally to cache the objects / even HTML fragments for faster rendering.

Static Content (HTML), we cache it indefinitely and ensure that the cache is flushed by the Content Management Server responsible to publish content. It creates a JMS message and pushes the message into a TOPIC configured within WebLogic App Server. Within the application there is generic Cache listener which listens to the topic and receive the message and acts accordingly.

Since the app is deployed in a cluster all cluster nodes receive the message from the topic.

12 years ago
Please give us details when this occurs?

Was it during startup?

And also which Auth Provider is your domain connected to?
12 years ago
Do you realize what this technique will result in?

1. Let us say the queue contains multiple messages to be processed, and if the 1st message has a rollback error like the one which you described, none of the other messages will never be processed.

I would advice you a mechanism to create error queues and throw the erroneous messages into it for processing by another bean.
12 years ago
I dont think this has got anything to do with Weblogic or the way you have installed cluster.

Do you know how the application caches the drop down data?
12 years ago
WebLogic stores it under:

BEA_HOME\user_projects\domains\<<domainName>>\servers\AdminServer\tmp\_WL_user
12 years ago
Why dont you set a Timeout on Web Service call as 10 seconds?

What Web Service API are you using?
12 years ago