代码之家 › 专栏 › 技术社区 › ssedano

使用代理插件的WebLogic9.2负载平衡和集群问题

cluster-computing weblogic

ssedano · 技术社区 · 15 年前

我在WebLogic9.2中有一个集群,它有2个节点(172.20.1.68:7101、172.20.1.23:7102)、1个adminserver(172.20.1.23:7001)和1个balancer(apache代理插件)172.20.1.49:7103。

问题是我的申请不起作用。

如有任何意见,我们将不胜感激。

非常感谢!

编辑:

这里是我的相关httpd.conf,我没有节,而是我有这个:

<VirtualHost *:80>
        ServerName fake.server.name  
        DocumentRoot "/usr/local/apache_ssl/htdocs"  
        <Location /myApp/>  
             SetHandler weblogic-handler  
             WebLogicCluster 172.20.1.23:7102,172.20.1.68:7101  
             Debug All   
             DebugConfigInfo ALL  
             WLLogFile logs/p.log  
              KeepAliveEnabled ON  
             KeepAliveSecs 15  
        </Location>  

        <Location /psoc-app>
             SetHandler weblogic-handler
             WebLogicCluster 172.20.1.23:7102,172.20.1.68:7101
              KeepAliveEnabled ON
             KeepAliveSecs 15
        </Location>

    WLLogFile logs/p.log
    ErrorLog logs/_log_error
    CustomLog logs/_log common
</VirtualHost>

/tmp/wlproxy.log请求:

================New Request: [GET /myApp/path HTTP/1.1] =================
Thu Jul 29 14:30:00 2010 <1382912804066002> INFO: SSL is not configured
Thu Jul 29 14:30:00 2010 <1382912804066002> Using Uri /myApp/path
Thu Jul 29 14:30:00 2010 <1382912804066002> After trimming path: '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> The final request string is '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> SEARCHING       id=[172.20.1.23:7102,172.20.1.68:7101] from current ID=[172.20.1.23:7102,172.20.1.68:7101]
Thu Jul 29 14:30:00 2010 <1382912804066002> The two ids matched
Thu Jul 29 14:30:00 2010 <1382912804066002> @@@FOUND...id=[172.20.1.23:7102,172.20.1.68:7101], server_name=[172.20.1.49], server_port=[80]
Thu Jul 29 14:30:00 2010 <1382912804066002> attempt #0 out of a max of 5
Thu Jul 29 14:30:00 2010 <1382912804066002> Trying a pooled connection for '172.20.1.68/7101/7106'
Thu Jul 29 14:30:00 2010 <1382912804066002> getPooledConn: No more connections in the pool for Host[172.20.1.68] Port[7101] SecurePort[7106]
Thu Jul 29 14:30:00 2010 <1382912804066002> general list: trying connect to '172.20.1.68'/7101/7106 at line 2619 for '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> INFO: New NON-SSL URL
Thu Jul 29 14:30:00 2010 <1382912804066002> Connect returns -1, and error no set to 115, msg 'Operation now in progress'
Thu Jul 29 14:30:00 2010 <1382912804066002> EINPROGRESS in connect() - selecting
Thu Jul 29 14:30:00 2010 <1382912804066002> Local Port of the socket is 38958
Thu Jul 29 14:30:00 2010 <1382912804066002> Remote Host 172.20.1.68 Remote Port 7101
Thu Jul 29 14:30:00 2010 <1382912804066002> general list: created a new connection to '172.20.1.68'/7101 for '/myApp/path', Local port:38958
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 404 Not Found]
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: StatusLine set to [404 Not Found]
Thu Jul 29 14:30:00 2010 <1382912804066002> parsed all headers OK
Thu Jul 29 14:30:00 2010 <1382912804066002> sendResponse() : r->status = '404'
Thu Jul 29 14:30:00 2010 <1382912804066002> canRecycle: conn=1 status=404 isKA=0 clen=1214 isCTE=0
Thu Jul 29 14:30:00 2010 <1382912804066002> closeConn: URL.canRecycle() returns false, deleting URL '172.20.1.68/7101'
Thu Jul 29 14:30:00 2010 <1382912804066002> request [/myApp/path] processed sucessfully..................

抱歉,我只是无法让格式化程序工作

1 回复 | 直到 14 年前

JoseK 15 年前

从目前的评论来看,有三件事值得注意和尝试:

A) 在apacheconf中它指向哪里 /tmp/wlproxy.log ? 这个问题是我们是否正在查看正确的conf文件,或者是否有另一个Apache实例正在运行?

/usr/sbin/fuser /tmp/wlproxy.log

您还可以尝试在关闭Apache的情况下运行fuser,看看它是否仍然显示拥有该文件的pid?

B) 插件调试日志显示apache请求到达集群中的第二台服务器并得到404。

Thu Jul 29 14:30:00 2010 <1382912804066002> general list: created a new connection to '172.20.1.68'/7101 for '/myApp/path', Local port:38958 
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 404 Not Found] 
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: StatusLine set to [404 Not Found]

应用程序是否明确部署并在上可用 172.20.1.68:7101/myApp/path 也?

/psoc-app