For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Nicholas_Zurfl1's avatar
Nicholas_Zurfl1
Icon for Nimbostratus rankNimbostratus
Nov 02, 2008

Parsing JMS

Has anyone ever experienced parsing JMS?

 

 

I have a project where the client messages succeed when all communications are sent to a single pool member but if the connections are divided (load balanced) between two servers the client generates the exception:

 

Message producer creation failed: server return error id 99

 

 

I added a source IP persistence profile to the virtual server with a timeout of 3 seconds. When I test JMS messages at a 3 second delay they complete successfully.

 

 

I would like to decode the JMS packet captures but I have yet to find a way.

 

 

It would also be neat if I could create an iRule that could parse the client and server communications.

 

 

Any suggestions?
application delivery
dev
devops
iRules

3 Replies

  • The_Bhattman's avatar
    The_Bhattman
    Icon for Nimbostratus rankNimbostratus
    Nov 11, 2008
    I am not an expert on JMS but I suppose you should be able to inspect the client messages

     

     

    One way is to use an irule that inspects the traffic such as TCP::collect. You can read about here: http://devcentral.f5.com/wiki/default.aspx/iRules/TCP__collect.html

     

     

    Hope this helps

     

    CB

     

     

     

     

  • Rakesh_74947's avatar
    Rakesh_74947
    Icon for Nimbostratus rankNimbostratus
    Sep 02, 2009
    have you got the solution for this as I am also getting the same exception?

     

     

    thanks
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Sep 02, 2009
    I'd suggest you add persistence to the VIP with a timeout much longer than three seconds--maybe something like 3600 seconds.

     

     

    Aaron