With mod_jk, sessions are sticky by default; you have to disable them in workers.properties to not have them be sticky.
If a client isn't going to hold onto the session id, this of course can't work. A session is a conversation; if one participant in the conversation forgets its in a conversation, the conversation can't be coherent.
Is your "client" some sort of proxy server? If so, and it passes the session cookie through to the real client, who then returns it, this could work. I've written such a system before.
Thank you.. that was the answer i was looking for.
Great! When I wrote it I had a feeling it wasn't going to be what you needed, but I took a shot at it :)