SetHandler weblogic-handler
WebLogicCluster 82.0.98.237:7001,82.0.176.3:7001
Debug ON
Debug ALL
DebugConfigInfo ON
WLLogFile c:\wl.log
DynamicServerList OFF
KeepAliveEnabled ON
KeepAliveSecs 30
其中:/TestDL是应用的上下文根
82.0.98.237:7001,82.0.176.3:7001是2台web服务器的IP地址及端口号,中间用逗号分隔。
DynamicServerList设置为OFF,在对由插件所代理的请求进行负载平衡时,不使用动态集群列表,而是使用WebLogicCluster参数指定的静态列表。
DynamicServerList 、KeepAliveEnabled、KeepAliveSecs 的设置是为了解决: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF错误。
http://dev2dev.us/thread-18058-1-1.html
Idempotent should be set to ON and if the servers do not respond within HungServerRecoverSecs (WLIOTimeoutSecs), the plug-ins fail over. If set to “OFF” the plug-ins do not fail over.
All session objects should be serializable to replicate.
If the server become frozen or hung, then there won’t be response to the proxy server until WLIOTimeoutSecs is elapsed. If neither the session replication nor Idempotent is set, then already established session won’t be replicated and will not fail over to next available server. If there is no session replication but Idempotent is set, then the request will fail-over to next server but the sticky session will be lost since the session is not replicated, so a new session will be given from the next available server in the clustered server list.
If the user cannot implement the replication due to the object serialization but can set Idempotent, then as long as the servers are doing well, the user might not see the sticky session problem; however, under an overloaded condition or a hung or frozen server, the client could end up getting a new session due to the sticky session failure.
http://bbs.middleware123.com/thread-15065-1-1.html
Can you cross verify your mod_wl_ohs.conf configuration and ensure that you have the correct IP and port configured?Also,please ensure that the weblogic server is running correctly.
Enable idempotent to ON.
Also,please try accessing the WLS console by proxying through the OHS server.
This would tell you if the issue is specifically while accessing forms application alone or with any other app.
Please have a look at the OHS log files too to see the exact error that you see in there.
-Sandeep