Rob Misek

Ranch Hand
+ Follow
since Sep 24, 2002
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 Rob Misek

Hi Saurabh,

This can be achieved transparently (i.e. NO code change necessary) by using Coherence*Web, an HTTP Session management module built ontop of Coherence. You can share session state across applications and even across heterogeneous application servers, in a cluster.
17 years ago
Hi Dustin,
Absolutely, Tangosol's Coherence was built for that exact purpose. It allows you to leverage a number of caching strategies in a clustered environment incluing Replicated, Distributed/Partitioned, Near as well as "binding" to an underlying datastore for transparent persistence of cached data. Coherence maintains concurrency of the cached data across the cluster using our cluster-wide locking technology. There are a number of other features including, distributed querying (i.e. searching for objects whose properties match the search criteria), cluster-wide event notification and even grid computing support.
Drop me a line if you would like to discuss this further.
Regards,
Rob Misek
17 years ago
Hi Sathwik,
You can use our Coherence*Web HTTP session managment module to "un deprecate" the HttpSessionContext. Further, you could use Coherence to maintain your list of logged in users in memory in a concurrent and fully clustered manner.
17 years ago
Further, I am pretty sure that WebLogic follows a primary and secondary modeal for session replication so the session is not replicated to _both_ server2 and server3, just one of them.
17 years ago
Sure. Look in the conf directory. there is a *-services.xml file in which you can set all the ports.
Later,
Rob Misek
17 years ago
> I think webLogic Provides Persistent Session Managment System using (JDBC)
> for Storing Sessions to table.
Absolutely, but with this mechanism you must make a round-trip to the datastore on session modification. This, typically, is more expensive then relying on in-memory management of session state.
> They also specify in the WebLogic documentation about the Load Balancing /
> Clustering Session Management.
I could be wrong but I do not believe that there is a default mechanism for handling the management of http session across multiple applications.
Later,
Rob Misek
17 years ago
Does the user that you are running the build script as have permissions to modify the directory structure?
Later,
Rob
17 years ago
Looks like claspath stuff. I would start by verifying that examples.ejb20.basic.statefulSession.Client is in the CP of the build. It may be as easy as changing the paths in the build file.
Later,
Rob
17 years ago
Hi Colin,
Take a look at this xml file. It should give you a good idea where to start.
Later,
Rob Misek
17 years ago
You may also want to make a habit of adding CONTENT="no-cache" to your meta tag (for testing at least).
Later,
Rob Misek
17 years ago
Hi Jyothip,
Perhaps you may be interested in Coherence*Web which will gaurantee the fault-tolerance and high availability of your http session data by relying on Coherence as the backbone.
Later,
Rob Misek
17 years ago
Hi Sat,
One way to accomplish this would be to use an http session management module such as Coherence*Web included in the latest build of Coherence. This allows the use of all the different caching strategies supported by Coherence (i.e. Replicated, Distributed/Partitioned, Near/Distributed, Overflow to Disk, Write-Behind to a datastore, etc.) to manage/store you session data concurrently in a cluster.
Later,
Rob Misek
17 years ago
Hi Prakash,
I would point you to Tangosol's Coherence in-memory clustered caching product. We have developed an HTTP-Session Replication Module for Tomcat which replicates the session data in-memory across all of the cluster nodes. This approach allows for the use of non-sticky loadbalancing and pure failover (since each cluster node has all the session information).
Later.
18 years ago
One of which is Tangosol's Coherence, a Clustered Caching Solution with both Replicated and Distributed flavors.
Later.
Hi Nijeesh,
There are a few considerations when moving to clustering:
- if you are using a DB as the baskend to your app you will have change the <db-is-shared> value to false since each node in your cluster will now be accessing the same DB.
- if you have a caching mechanism in your single JVM app then you will have modify your approach so that the data can be shared (cached) across the cluster. If this is a consideration that applies to you check out Tangosol's Coherence Clustered Caching Software.
Later.

Check out Tangosol
18 years ago