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

kridsana's avatar
kridsana
Icon for Cirrocumulus rankCirrocumulus
Jul 23, 2012

problem between F5 and Websphere?

hi

 

 

I seen this case ... F5 connect with database in IBM websphere and have persistence on

 

 

 

when I see cookie , it have 2 difference cookie , cookie persist (F5) and JSESSIONID

 

 

 

when I test , throughput and load balance is not good

 

 

 

at first i fix at connection pool in database but something still doesn't good enough

 

 

 

so i turn persistence off and use JSESSIONID alone then everything work fine

 

 

 

 

 

what difference between cookie persist and JSESSIONID ?

 

 

 

I think Websphere use JESSIONID and it interfere with cookie persist and process of F5

 

 

 

then it mean cookie persist (F5) and JSESSIONID can't work together.

 

 

 

am i thinking right?

 

config
design

5 Replies

  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jul 23, 2012
    when I test , throughput and load balance is not good how did you test and measure throughput?

     

     

    what difference between cookie persist and JSESSIONID ?i understand jsessionid is a cookie which is generated by server. bigip does nothing on it.

     

     

    are you aware of this behavior?

     

     

    sol7964: Persistence may fail for subsequent requests on Keep-Alive connections

     

    http://support.f5.com/kb/en-us/solutions/public/7000/900/sol7964.html

     

     

    just in case if you would like to try universal persistence but i think cookie insert persistence may be okay.

     

     

    sol7392: Overview of universal persistence

     

    http://support.f5.com/kb/en-us/solutions/public/7000/300/sol7392.html
  • kridsana's avatar
    kridsana
    Icon for Cirrocumulus rankCirrocumulus
    Jul 23, 2012
    i sent load using apache jmeter

     

     

    one thing that bother my mind is why disable cookie persistence and use universal persistence (write iRule to use JSESSIONID instead of cookie_persist) , everything work fine. :(

     

     

    I think about algorithm of Websphere to process order cookie that lookup for JESSIONID first make this problem, otherwise script that use in apache jmeter is bad.
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jul 23, 2012
    one thing that bother my mind is why disable cookie persistence and use universal persistence (write iRule to use JSESSIONID instead of cookie_persist) , everything work fine. :( did you pass bigip's cookie, i.e. BIGipServer, in subsequent request in jmeter test plan?
  • kridsana's avatar
    kridsana
    Icon for Cirrocumulus rankCirrocumulus
    Jul 23, 2012
    sorry i don't know script in jmeter. so i don't know why i switch persistence mode and then it work.

     

     

    now i think about your question. it might because script jmeter.
  • giltjr's avatar
    giltjr
    Icon for Nimbostratus rankNimbostratus
    Jul 23, 2012
    Are you actually using the F5 to load balance directly to WebSphere? Or is the F5 frontend'ing IBM's HTTP server?

     

     

    The JSESSIONID for WebSphere has multiple parts. The first part is a unique session id for that user/session. Then there can be 1 or more additional parts that have a unique ID for each WebSphere Server. The additional parts are separated by a colon.

     

     

    Because of how our system is setup we use a combination of the JSESSIONID and then a pool name to create a universal persistence record.

     

    We have multiple applications with separate pools that all share the same same session id. So we break out the session ID and append it with the pool name for that specific application.