SUNW.iws - "Connection refused" when probing a uri in monitor_uri_list

Question

Hi,
I use Sun Cluster 3.2 and would like to set Sun Webserver 7u2 as failover resource.
I configured Resource Group which contain Logical Hostname and Sun Webserver as data resource (using SUNW.iws). I set all nedded data and turn on the resource.
I've got the messages:
Feb 11 01:25:21 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: Failed to connect to host ha-web and port 80: Connection refused.
Feb 11 01:25:36 krasnal-A last message repeated 7 times
Feb 11 01:25:37 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: A resource restart attempt on resource Webserver-server in resource group Webserver-gr has been blocked because the number of restarts within the past Retry_interval (620 seconds) would exceed Retry_count (2)
Feb 11 01:25:37 krasnal-A SC[SUNW.iws:5,Webserver-gr,Webserver-server,iws_svc_start]: Failed to start iPlanet Web Server.
Feb 11 01:25:37 krasnal-A Cluster.RGM.rgmd: Method <iws_svc_start> failed on resource <Webserver-server> in resource group <Webserver-gr> [exit code <1>, time used: 7% of timeout <300 seconds>]
server has been shutdown
In this moment the second node on cluster start the resource and do the same. Monitor, failed, turn off. :-( . Resource are switched 3 times between nodes and at the end get offline status.
The most important is that connection refused for uri in monitor_uri_list and resource in cluster isn't start or triggering restart/failover.
It is look like the failover monitor try check resource on port 80 after service start and when notice that service (Webserver) not started - turn down the interface on this node and turn up on second node. Service (webserver) can;t start becouse the interface are down.
I've found some similar problems which are describes on sunsolve:
http://sunsolve.sun.com/search/document.do?assetkey=1-1-4900125-1
and
http://sunsolve.sun.com/search/document.do?assetkey=1-1-4967197-1
I'm beginner in cluster problems and maybe I did some big mistake, but ...some help me
Irek

Answer 1

Solved!
I read this post: http://forum.java.sun.com/thread.jspa?messageID=3966316
and now get things work.
If you installed NetBeans, you should notice that in your {tomcat_home}/conf/web.xml, NetBeans add these:
  <filter>
    <filter-name>HTTPMonitorFilter</filter-name>
    <filter-class>org.netbeans.modules.web.monitor.server.MonitorFilter</filter-class>
    <init-param>
      <param-name>netbeans.monitor.ide</param-name>
      <param-value>127.0.0.1:8082</param-value>
    </init-param>
  </filter>
  <filter-mapping>
    <filter-name>HTTPMonitorFilter</filter-name>
    <url-pattern>/*</url-pattern>
    <dispatcher>REQUEST</dispatcher>
    <dispatcher>FORWARD</dispatcher>
    <dispatcher>INCLUDE</dispatcher>
    <dispatcher>ERROR</dispatcher>
  </filter-mapping>Now you should comment out these lines and then can get connected.