Ben J. Christensen

October 19, 2007 • 10:30 pm

Websphere Multi-JVM jsessionid

Works just like it should

Two JVMs with different contexts but the same domain now use the same jsessionid so they can talk back and forth in the same browser without jsessionid schizophrenia.

Like this:

Be the first to like this post.

Filed under: Architecture, Code, Production

Leave a Reply Cancel reply

Enter your comment here...

Fill in your details below or click an icon to log in:

Email (required) (Address never made public)

Name (required)

Website

You are commenting using your WordPress.com account. ( Log Out / Change )

You are commenting using your Twitter account. ( Log Out / Change )

You are commenting using your Facebook account. ( Log Out / Change )

Cancel

Connecting to %s

Twitter Updates

"The first thing a leader needs to learn to do is communicate—tell his team where they’re going and why." nymag.com/news/features/… 3 days ago
Coda 2 is very nice ( panic.com/coda/). Great for Javascript+D3 prototyping with rapid feedback: http://t.co/zq0uI256 5 days ago
The love and hate of Node.js mailinator.blogspot.co.uk/2012/05/love-a… via @sbtourist 6 days ago
"Happy or sad, "good enough" is getting "good enougher" all the time." mailinator.blogspot.co.uk/2012/05/love-a… 6 days ago
"Facing a sea of infinity, it's easy to despair … the challenge is … to be comfortable with the undone." sethgodin.typepad.com/seths_blog/201… 6 days ago

Ben J. Christensen

Websphere Multi-JVM jsessionid

Like this:

Leave a Reply Cancel reply

Twitter Updates

Meta

Follow “Ben J. Christensen”