Forum Discussion

Syed_89523's avatar
Syed_89523
Icon for Nimbostratus rankNimbostratus
Apr 10, 2012

Weblogic Setup

I have pulled in to troubleshoot newly deployed weblogic setup for the one my client. Randomly user can't print the invoice from the weblogic server. I follow the guidelines from the weblogic deployment guide

 

http://www.f5.com/pdf/deployment-guides/f5-weblogic-dg.pdf

 

I used three profiles to optimized my traffic but currently i am getting lot resets when show the profiles. I am unsure if it is good or bad, please help.

 

 

[501:Active] log b profile bea-tcp-wan show

 

PROFILE TCP bea-tcp-wan parent tcp-wan-optimized

 

| idle timeout 300

 

| Conn (open, CLOSE-WAIT) = (1032, 1)

 

| Conn (FIN-WAIT, TIME_WAIT) = (0, 0)

 

| Conn (accept, not accept) = (730542, 0) (estab, fail) = (0, 0)

 

| Conn (abandon, expire) = (17, 39374) Resets = 182282 Bad cksm = 0

 

| (rxbadseg, rxooseg, txrexmits) = (0, 1027, 202965)

 

| SYN cache overflow = 0 (rxcookie, rxbadcookie) = (0, 0)

 

[501:Active] log b profile bea-tcp-wan list

 

profile tcp bea-tcp-wan {

 

defaults from tcp-wan-optimized

 

}

 

 

 

[501:Active] log b profile bea-tcp-lan show

 

PROFILE TCP bea-tcp-lan parent tcp-lan-optimized

 

| idle timeout 300

 

| Conn (open, CLOSE-WAIT) = (99, 0)

 

| Conn (FIN-WAIT, TIME_WAIT) = (0, 2)

 

| Conn (accept, not accept) = (0, 0) (estab, fail) = (50019, 23417)

 

| Conn (abandon, expire) = (257, 551) Resets = 453 Bad cksm = 0

 

| (rxbadseg, rxooseg, txrexmits) = (0, 111, 0)

 

| SYN cache overflow = 0 (rxcookie, rxbadcookie) = (0, 0)

 

[501:Active] log

 

 

 

 

501:Active] log b profile bea-oneconnect show all

 

PROFILE ONECONNECT bea-oneconnect parent oneconnect

 

| (curr, max, reuse, new) = (74, 294, 5.923M, 74352)

 

[501:Active] log

 

 

 

==============

 

VIP configuration

 

===============

 

 

[501:Active] log b virtual XXXX list

 

virtual XXXX-virtual {

 

snat automap

 

pool XXXX-pool

 

destination 10.30.6.35:http

 

ip protocol tcp

 

persist bea-cookie

 

profiles {

 

bea-oneconnect {}

 

bea-tcp-lan {

 

serverside

 

}

 

bea-tcp-wan {

 

clientside

 

}

 

http {}

 

}