Establishing persistence on userid with JMS

Hey folks,

 

So I have a bit of a problem with this. We are trying to parse a log on message for a JMS service and use the userID as the persistence identifier. The problem is the behavior of the app is a little dodgy.

 

Rather than simply establishing a socket and sending a unique identifier, the application makes the connection and waits for a response from the server. The response seems to be meaningless(it provides the local node name to the client which the client can't resolve). After that the client sends its log in information.

 

The problem is that this requires the socket to be already established with the server which means that the persistence can't be ascertained until after the full socket stream is built.

 

Does anyone have any ideas about how to solve this problem? I was thinking of maybe inserting the packet into the stream from the LB but I'm not sure if that would work.