Skip to main content

What is "HTTP Load Balancers" node and what is relation with sun java web server?

11 replies [Last post]
Anonymous

Hi
Thank you for reading my post.
What is relation of "HTTP Load Balancers" in administration console
with using sun java web server as load balancer?

Thanks

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
legolas wood

Hi
Thank you very much for your reply.

I should say that I have played so much with clustering and load balancing.
I have the DAS ready, I have create a Node agent in machine 2, Now i can
see node agent in DAS administration console.
when i try to create a new instance for that node agent i get the
following error.
I have both DAS and that Glassfish in my LAN.

Thanks
-----------------------------------------------------------------------------------------------

[#|2005-04-17T19:15:07.607+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:07.607+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:07.748+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerServerRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:08.592+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:08.592+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:08.685+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:09.685+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:09.685+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:09.779+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:10.779+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:10.779+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:10.873+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:11.764+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:11.764+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:11.857+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:13.076+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:13.076+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:13.233+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:14.061+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:14.061+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:14.154+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:15.045+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:15.045+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:15.139+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:16.139+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:16.139+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:16.233+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:17.233+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:17.233+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:17.342+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:18.217+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:18.217+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:18.342+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:19.202+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:19.202+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:19.327+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:20.296+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:20.296+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:20.421+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:21.389+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:21.389+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:21.499+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:22.483+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:22.483+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:22.796+0330|WARNING|sun-appserver9.1|javax.enterprise.system.tools.admin|_ThreadID=23;_ThreadName=Thread-17;_RequestID=6933a6f2-6f2e-4e5d-b0d4-a3716b194eda;|LoadBalancerApplicationRefRegistrationListener
mbeanRegistered failed. Exception = :
javax.management.InstanceNotFoundException: This operation failed,
because it could not be handled by this domain.
An example of such an operation is creating application server instances
or clusters when they are not supported by the given domain.
The actual error is: MBean instance not found:
amx:j2eeType=X-LoadBalancerMonitor,name=default-load-balancer|#]

[#|2005-04-17T19:15:23.796+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:23.796+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:24.890+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|Apply
changes could not be done for Load balancer [default-load-balancer] due
to [Connection refused: connect].|#]

[#|2005-04-17T19:15:24.890+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=14;_ThreadName=httpWorkerThread-4848-0;_RequestID=98019f51-3ccf-4eda-b1ed-1e6c7410381e;|EEADM0221:
Auto Apply changes could not be done. Exception detail is null|#]

[#|2005-04-17T19:15:58.064+0330|WARNING|sun-appserver9.1|javax.ee.enterprise.system.tools.admin|_ThreadID=20;_ThreadName=httpWorkerThread-4848-2;_RequestID=22a2bd3e-1364-417e-aacf-ccbed0f816c6;|EEADM0002:
An exception occurred starting the server instance
instance-1-computer-17-by-das.
com.sun.enterprise.ee.admin.servermgmt.AgentException: Exception
creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:184)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.isRunning(NodeAgentsConfigBean.java:191)
at
com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:338)
at
com.sun.enterprise.ee.admin.mbeans.ServersConfigMBean.startServerInstance(ServersConfigMBean.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336)
at
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77)
at $Proxy1.invoke(Unknown Source)
at
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:106)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:62)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.startServerInstance(JMXUtil.java:198)
at
com.sun.enterprise.tools.admingui.handlers.ClusterHandlers.clusterInstanceAction(ClusterHandlers.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:421)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:441)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:317)
at
com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:133)
at
com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:81)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
at
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:743)
at javax.faces.component.UICommand.broadcast(UICommand.java:368)
at
com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:160)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447)
at
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at
com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:80)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at
com.sun.enterprise.tools.admingui.servlet.DelayedInitFacesServlet.service(DelayedInitFacesServlet.java:66)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:217)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:258)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:189)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:81)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:255)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:549)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:790)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:326)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:248)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:199)
at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:313)
at
com.sun.enterprise.ee.admin.clientreg.NodeAgentRegistry.getNodeAgentConnection(NodeAgentRegistry.java:105)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.getConnection(NodeAgentProxy.java:218)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.invoke(NodeAgentProxy.java:325)
at $Proxy27.getRuntimeStatus(Unknown Source)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:176)
... 78 more
Caused by: java.rmi.ConnectIOException: Exception creating connection
to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown
Source)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
at
javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connectToServer(JMXConnectorRegistry.java:362)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:341)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:196)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:282)
... 83 more
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:549)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(SSLSocketImpl.java:351)
at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:69)
at
com.sun.appserv.management.client.AdminRMISSLClientSocketFactory.createSocket(AdminRMISSLClientSocketFactory.java:192)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 94 more
|#]

[#|2005-04-17T19:15:58.080+0330|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=20;_ThreadName=httpWorkerThread-4848-2;_RequestID=22a2bd3e-1364-417e-aacf-ccbed0f816c6;|
javax.management.MBeanException: Operation 'startServerInstance' failed
in 'servers' Config Mbean.
Target exception message: Exception creating connection to:
192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.admin.MBeanHelper.extractAndWrapTargetException(MBeanHelper.java:419)
at
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:470)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77)
at $Proxy1.invoke(Unknown Source)
at
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:106)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:62)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.startServerInstance(JMXUtil.java:198)
at
com.sun.enterprise.tools.admingui.handlers.ClusterHandlers.clusterInstanceAction(ClusterHandlers.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:421)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:441)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:317)
at
com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:133)
at
com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:81)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
at
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:743)
at javax.faces.component.UICommand.broadcast(UICommand.java:368)
at
com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:160)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447)
at
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at
com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:80)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at
com.sun.enterprise.tools.admingui.servlet.DelayedInitFacesServlet.service(DelayedInitFacesServlet.java:66)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:217)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:258)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:189)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:81)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:255)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:549)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:790)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:326)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:248)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:199)
at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
Caused by: com.sun.enterprise.admin.servermgmt.InstanceException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.admin.mbeans.ExceptionHandler.handleInstanceException(ExceptionHandler.java:85)
at
com.sun.enterprise.admin.mbeans.ExceptionHandler.handleInstanceException(ExceptionHandler.java:64)
at
com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:362)
at
com.sun.enterprise.ee.admin.mbeans.ServersConfigMBean.startServerInstance(ServersConfigMBean.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336)
at
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448)
... 68 more
Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:184)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.isRunning(NodeAgentsConfigBean.java:191)
at
com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:338)
... 76 more
Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException:
Exception creating connection to: 192.168.100.17; nested exception is|#]

[#|2005-04-17T19:15:58.080+0330|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=20;_ThreadName=httpWorkerThread-4848-2;_RequestID=22a2bd3e-1364-417e-aacf-ccbed0f816c6;|:

java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:313)
at
com.sun.enterprise.ee.admin.clientreg.NodeAgentRegistry.getNodeAgentConnection(NodeAgentRegistry.java:105)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.getConnection(NodeAgentProxy.java:218)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.invoke(NodeAgentProxy.java:325)
at $Proxy27.getRuntimeStatus(Unknown Source)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:176)
... 78 more
Caused by: java.rmi.ConnectIOException: Exception creating connection
to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown
Source)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
at
javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connectToServer(JMXConnectorRegistry.java:362)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:341)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:196)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:282)
... 83 more
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:549)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(SSLSocketImpl.java:351)
at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:69)
at
com.sun.appserv.management.client.AdminRMISSLClientSocketFactory.createSocket(AdminRMISSLClientSocketFactory.java:192)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 94 more
|#]

[#|2005-04-17T19:15:58.080+0330|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=20;_ThreadName=httpWorkerThread-4848-2;_RequestID=22a2bd3e-1364-417e-aacf-ccbed0f816c6;|
java.lang.RuntimeException:
com.sun.enterprise.admin.servermgmt.InstanceException: Exception
creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:110)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:62)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.startServerInstance(JMXUtil.java:198)
at
com.sun.enterprise.tools.admingui.handlers.ClusterHandlers.clusterInstanceAction(ClusterHandlers.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:421)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.handler.Handler.invoke(Handler.java:441)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:343)
at
com.sun.jsftemplating.layout.descriptors.LayoutElementBase.dispatchHandlers(LayoutElementBase.java:317)
at
com.sun.jsftemplating.layout.event.CommandActionListener.invokeCommandHandlers(CommandActionListener.java:133)
at
com.sun.jsftemplating.layout.event.CommandActionListener.processAction(CommandActionListener.java:81)
at javax.faces.event.ActionEvent.processListener(ActionEvent.java:77)
at
javax.faces.component.UIComponentBase.broadcast(UIComponentBase.java:743)
at javax.faces.component.UICommand.broadcast(UICommand.java:368)
at
com.sun.webui.jsf.component.WebuiCommand.broadcast(WebuiCommand.java:160)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:447)
at
javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
at
com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at
com.sun.faces.extensions.avatar.lifecycle.PartialTraversalLifecycle.execute(PartialTraversalLifecycle.java:80)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at
com.sun.enterprise.tools.admingui.servlet.DelayedInitFacesServlet.service(DelayedInitFacesServlet.java:66)
at
org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:398)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at com.sun.webui.jsf.util.UploadFilter.doFilter(UploadFilter.java:240)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:217)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:185)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
at
org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:258)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:189)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:81)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:611)
at
org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:558)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:1067)
at
org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:255)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:618)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:549)
at
com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:790)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:326)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:248)
at
com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:199)
at
com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
at
com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:103)
Caused by: com.sun.enterprise.admin.servermgmt.InstanceException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.admin.mbeans.ExceptionHandler.handleInstanceException(ExceptionHandler.java:85)
at
com.sun.enterprise.admin.mbeans.ExceptionHandler.handleInstanceException(ExceptionHandler.java:64)
at
com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:362)
at
com.sun.enterprise.ee.admin.mbeans.ServersConfigMBean.startServerInstance(ServersConfigMBean.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:353)
at
com.sun.enterprise.admin.MBeanHelper.invokeOperationInBean(MBeanHelper.java:336)
at
com.sun.enterprise.admin.config.BaseConfigMBean.invoke(BaseConfigMBean.java:448)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at sun.reflect.GeneratedMethodAccessor16.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.enterprise.admin.util.proxy.ProxyClass.invoke(ProxyClass.java:77)
at $Proxy1.invoke(Unknown Source)
at
com.sun.enterprise.admin.server.core.jmx.SunoneInterceptor.invoke(SunoneInterceptor.java:297)
at
com.sun.enterprise.tools.admingui.util.JMXUtil.invoke(JMXUtil.java:106)
... 57 more
Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:184)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.isRunning(NodeAgentsConfigBean.java:191)
at
com.sun.enterprise.ee.admin.configbeans.ServersConfigBean.startServerInstance(ServersConfigBean.java:338)
... 76 more
Caused by: com.sun.enterprise.ee.admin.servermgmt.AgentException:
Exception creating connection to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConn|#]

[#|2005-04-17T19:15:58.095+0330|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=20;_ThreadName=httpWorkerThread-4848-2;_RequestID=22a2bd3e-1364-417e-aacf-ccbed0f816c6;|ectorRegistry.java:313)
at
com.sun.enterprise.ee.admin.clientreg.NodeAgentRegistry.getNodeAgentConnection(NodeAgentRegistry.java:105)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.getConnection(NodeAgentProxy.java:218)
at
com.sun.enterprise.ee.admin.proxy.NodeAgentProxy.invoke(NodeAgentProxy.java:325)
at $Proxy27.getRuntimeStatus(Unknown Source)
at
com.sun.enterprise.ee.admin.configbeans.NodeAgentsConfigBean.getRuntimeStatus(NodeAgentsConfigBean.java:176)
... 78 more
Caused by: java.rmi.ConnectIOException: Exception creating connection
to: 192.168.100.17; nested exception is:
java.net.BindException: Address already in use: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:587)
at
sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown
Source)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2239)
at
javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connectToServer(JMXConnectorRegistry.java:362)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:341)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.connect(JMXConnectorRegistry.java:196)
at
com.sun.enterprise.ee.admin.clientreg.JMXConnectorRegistry.getConnection(JMXConnectorRegistry.java:282)
... 83 more
Caused by: java.net.BindException: Address already in use: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:516)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:549)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(SSLSocketImpl.java:351)
at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:69)
at
com.sun.appserv.management.client.AdminRMISSLClientSocketFactory.createSocket(AdminRMISSLClientSocketFactory.java:192)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 94 more
|#]

kedar wrote:
> Hi Legolas,
>
> Let me try to explain:
>
> Domain Spans machines, usually.
> One of the machines is designated as DAS, as Pankaj pointed out earlier.
> The DAS is the admin server and it manages the servers in the same
> domain. The servers can be clustered if administrator wants them so.
> The administrator has benefits of management when instances are
> clustered.
>
> Now, on the other machine, all you need is "bits".
>
> Consider the scenario: You have "m1" and "m2" as two machines. Let's
> say you want to create a cluster "c1" with instances "s1" and "s2"
> with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
> Let's call the domain where all this "logically" resides as "domain1".
>
> You do the following:
> 1- Download the glassfish.jar on both "m1" and "m2".
> 2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
> domain1 that is capable of handling clusters.
> 3- On "m1", you start domain, domain1.
> 4- On "m1", /asadmin create-node-agent na1
> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you downloaded
> (after of course, java -jar ...) This creates a domain on that machine
> as well, but you don't need it. I will file an RFE in this regard.
> 6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
> /asadmin create-node-agent --host m1 --user admin-user na2
> 7- On "m1", /asadmin start-node-agent na1
> On "m2", /asadmin start-node-agent na2
>
> Now, your topology is created and ready to go.
> You have a domain domain1, this spans "m1" and "m2".
> Node-agent "na1" is on "m1". It will control instances on "m1".
> Node-agent "na2" is on "m2". It will control instances on "m2".
>
> From this point on, forget you had machine "m2". The entire
> configuration can be done just from machine "m1".
>
> This is the beauty of the process, IMO.
>
> 8- On "m1", just try: /asadmin create-cluster c1
> 9- On "m1", /asadmin create-instance --cluster c1 --nodeagent
> na1 s1
> This puts "s1" in cluster "c1". Note that this instance is controlled by
> Node Agent "na1". This instance uses "physical resources" from "m1".
>
> 10- On "m1", (not "m2"!)
> /asadmin create-instance --cluster c1 --nodeagent na2 s2
>
> 11- On "m1", /asadmin start-cluster "c1".
>
> This is where it culminates.
> All you do is "start cluster".
> It starts instance "s1" on "m1" and "s2" on "m2".
>
> The instances have homogeneous configuration.
>
> Does this help?
>
> Regards,
> Kedar
>
> Legolas Woodland wrote:
>> Thank you for reply.
>> just as last question:
>>
>> As i said i have DAS installed and configuredin my own computer
>> i want to install some more glassfish in other computer and add them
>> to cluster.
>>
>> question is:
>>
>> Should i install glassfish clustered edition on other computers that
>> will act as nodes?
>> ant -f setup-cluster.xml
>>
>> Thankss
>>
>> On 4/17/07, *Pankaj Jairath* >> > wrote:
>>
>> Legolas Woodland wrote:
>>
>> > Thank you very much for reply.
>> >
>> > Right now i think i have setup a cluster and a load balancer
>> according
>> > to your very good weblog.
>> > I have sun java web server 7.u1 and latest blassfish installed.
>> > What i want to know is:
>> > I have one DAS, And a web server which according to your weblog
>> will
>> > balance the load between any instance that we add in
>> loadbalancer.xml .
>> >
>> > I have two questions and one problem.
>> >
>> > problem:
>> > I tried several time to create load balancer in glassfish
>> application
>> > server and then apply it to my web server, but it just return an
>> error
>> > without any stack trance, error say: Can not connect to server.
>> > My web server and glassfish both works on the same machine, so i
>> > tried: 127.0.0.1 < http://127.0.0.1>,
>> localhost and my lan ip address
>> > none of them worked.
>> > the port that i can access my web server administration console is
>> > 8989 and i used this port in HTTP Load Balancers node of glassfish
>> > administration console when i trid to create the load balancer.
>>
>> The communication between DAS and WS/LB is over SSL and the
>> host/port
>> needs to be HTTPS listener of the WebServer Instance and not that
>> of the
>> Admin Server (the Load Balancer is configured to run on the
>> WebServer
>> instance). Given that you have successfully configured the SSL setup
>> between the DAS and WS/LB, check with changing the port to the SSL
>> port
>> of the WebServer 7.0 instance.
>>
>> >
>> > IS there anything specific to change in order to make it
>> possible to
>> > apply changes to web server load balancer from glassfish console?
>> >
>> > Now my question:
>> >
>> > -what kind of glassfish i should setup in some other machines
>> to add
>> > them to the cluster? can they be normal domains or there are some
>> > specific ways to create domains to add them to cluster?
>> > can you give me the steps?
>> >
>>
>> You can create multiple server instances and group them under a
>> defined
>> cluster configuration. The cluster or the group of clustered server
>> instances are under a single domain. Domain is the administrative
>> reference - the single point / central repository of carrying out
>> the
>> administrative tasks.
>>
>> You can refer to the documentation that details the setups to work
>> with
>> clusters. This is from the /"High Availability Administration
>> Guide"/
>> under chapter 5 : /"Using Application Server Clusters" /:-
>> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>>
>> Specifically refer to the topic named - /"Working with Clusters"./
>>
>> > -I find that we can have several instance in a server? what is
>> > relation of domains with instances? why we should have several
>> > instance in a domain?
>>
>> There can be zero or more server instances in a administrative
>> domain
>> and there can one or more such domains. Each such domain has its
>> own
>> DAS. DAS is actually the designated administrative server instance
>> with
>> a default config within a domain.
>>
>> regards
>> Pankaj
>>
>> >
>> >
>> >
>> > Thanks.
>> >
>> >
>> >
>> >
>> >
>> >
>> > On 4/17/07, *Pankaj Jairath* >>
>> > Pankaj.Jairath@sun.com
>> >> wrote:
>> >
>> > Hello Legolas,
>> >
>> > If I understood your question, you are referring to the UI
>> element
>> > "HTTP
>> > Load Balancers" element of the GlassFish V2 Application
>> Server. If so
>> > let me give a brief.
>> >
>> > GlassFish V2 provides the HTTP Load Balancer which can then be
>> > deployed
>> > onto the supported WebServer - for GlassFish V2 it's the Sun
>> Java
>> > System
>> > WebServer 6.1 / 7.0. When defining the High Availability
>> deployment
>> > topology of a Java EE deployment, administrator would
>> define a
>> > cluster
>> > of application servers instances and install and configure the
>> > HTTP Load
>> > Balancer to take care of load balancing and failover of the
>> HTTP
>> > requests.
>> > To do this administrative configuration steps, the
>> end-user can
>> > use the
>> > Admin Console (GUI) or the CLI commands to define the
>> cluster, it's
>> > configuration and associate a HTTP Load Balancer with this
>> > configuration. This association defines the cluster
>> configuration and
>> > other Load Balancer configurable parameters, which the HTTP
>> Load
>> > Balancer uses to perform its HA functionality. The
>> administrator
>> > can use
>> > the Admin Console to generate this HTTP Load Balancer
>> > configuration and
>> > even push the configuration over the wire to the deployed
>> HTTP Load
>> > Balancer on a given Sun Java System WebServer.
>> >
>> > Refer to the documents provided earlier for further details
>> on how to
>> > use the Domain Administrative Server (DAS) Admin Console
>> (GUI) or
>> > CLI to
>> > administer the HTTP Load Balancer.
>> >
>> > regards
>> > Pankaj
>> >
>> > legolas wood wrote:
>> >
>> > > Hi
>> > > Thank you for reading my post.
>> > > What is relation of "HTTP Load Balancers" in administration
>> > console
>> > > with using sun java web server as load balancer?
>> > >
>> > > Thanks
>> > >
>> > >
>> >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail:
>> users-unsubscribe@glassfish.dev.java.net
>>
>> > >> >
>> > > For additional commands, e-mail:
>> > users-help@glassfish.dev.java.net
>>
>> > >> >
>> > >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> users-unsubscribe@glassfish.dev.java.net
>>
>> > >> >
>> > For additional commands, e-mail:
>> users-help@glassfish.dev.java.net
>>
>> > >> >
>> >
>> >
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Pankaj Jairath

Hello Legolas,

If I understood your question, you are referring to the UI element "HTTP
Load Balancers" element of the GlassFish V2 Application Server. If so
let me give a brief.

GlassFish V2 provides the HTTP Load Balancer which can then be deployed
onto the supported WebServer - for GlassFish V2 it's the Sun Java System
WebServer 6.1 / 7.0. When defining the High Availability deployment
topology of a Java EE deployment, administrator would define a cluster
of application servers instances and install and configure the HTTP Load
Balancer to take care of load balancing and failover of the HTTP requests.
To do this administrative configuration steps, the end-user can use the
Admin Console (GUI) or the CLI commands to define the cluster, it's
configuration and associate a HTTP Load Balancer with this
configuration. This association defines the cluster configuration and
other Load Balancer configurable parameters, which the HTTP Load
Balancer uses to perform its HA functionality. The administrator can use
the Admin Console to generate this HTTP Load Balancer configuration and
even push the configuration over the wire to the deployed HTTP Load
Balancer on a given Sun Java System WebServer.

Refer to the documents provided earlier for further details on how to
use the Domain Administrative Server (DAS) Admin Console (GUI) or CLI to
administer the HTTP Load Balancer.

regards
Pankaj

legolas wood wrote:

> Hi
> Thank you for reading my post.
> What is relation of "HTTP Load Balancers" in administration console
> with using sun java web server as load balancer?
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Legolas Woodland

Thank you very much for reply.

Right now i think i have setup a cluster and a load balancer according
to your very good weblog.
I have sun java web server 7.u1 and latest blassfish installed.
What i want to know is:
I have one DAS, And a web server which according to your weblog will balance
the load between any instance that we add in loadbalancer.xml .

I have two questions and one problem.

problem:
I tried several time to create load balancer in glassfish application server
and then apply it to my web server, but it just return an error without any
stack trance, error say: Can not connect to server.
My web server and glassfish both works on the same machine, so i tried:
127.0.0.1, localhost and my lan ip address none of them worked.
the port that i can access my web server administration console is 8989 and
i used this port in HTTP Load Balancers node of glassfish administration
console when i trid to create the load balancer.

IS there anything specific to change in order to make it possible to apply
changes to web server load balancer from glassfish console?

Now my question:

-what kind of glassfish i should setup in some other machines to add them to
the cluster? can they be normal domains or there are some specific ways to
create domains to add them to cluster?
can you give me the steps?

-I find that we can have several instance in a server? what is relation of
domains with instances? why we should have several instance in a domain?

Thanks.

On 4/17/07, Pankaj Jairath wrote:
>
> Hello Legolas,
>
> If I understood your question, you are referring to the UI element "HTTP
> Load Balancers" element of the GlassFish V2 Application Server. If so
> let me give a brief.
>
> GlassFish V2 provides the HTTP Load Balancer which can then be deployed
> onto the supported WebServer - for GlassFish V2 it's the Sun Java System
> WebServer 6.1 / 7.0. When defining the High Availability deployment
> topology of a Java EE deployment, administrator would define a cluster
> of application servers instances and install and configure the HTTP Load
> Balancer to take care of load balancing and failover of the HTTP requests.
> To do this administrative configuration steps, the end-user can use the
> Admin Console (GUI) or the CLI commands to define the cluster, it's
> configuration and associate a HTTP Load Balancer with this
> configuration. This association defines the cluster configuration and
> other Load Balancer configurable parameters, which the HTTP Load
> Balancer uses to perform its HA functionality. The administrator can use
> the Admin Console to generate this HTTP Load Balancer configuration and
> even push the configuration over the wire to the deployed HTTP Load
> Balancer on a given Sun Java System WebServer.
>
> Refer to the documents provided earlier for further details on how to
> use the Domain Administrative Server (DAS) Admin Console (GUI) or CLI to
> administer the HTTP Load Balancer.
>
> regards
> Pankaj
>
> legolas wood wrote:
>
> > Hi
> > Thank you for reading my post.
> > What is relation of "HTTP Load Balancers" in administration console
> > with using sun java web server as load balancer?
> >
> > Thanks
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
[att1.html]

Pankaj Jairath

Legolas Woodland wrote:

> Thank you very much for reply.
>
> Right now i think i have setup a cluster and a load balancer according
> to your very good weblog.
> I have sun java web server 7.u1 and latest blassfish installed.
> What i want to know is:
> I have one DAS, And a web server which according to your weblog will
> balance the load between any instance that we add in loadbalancer.xml .
>
> I have two questions and one problem.
>
> problem:
> I tried several time to create load balancer in glassfish application
> server and then apply it to my web server, but it just return an error
> without any stack trance, error say: Can not connect to server.
> My web server and glassfish both works on the same machine, so i
> tried: 127.0.0.1 , localhost and my lan ip address
> none of them worked.
> the port that i can access my web server administration console is
> 8989 and i used this port in HTTP Load Balancers node of glassfish
> administration console when i trid to create the load balancer.

The communication between DAS and WS/LB is over SSL and the host/port
needs to be HTTPS listener of the WebServer Instance and not that of the
Admin Server (the Load Balancer is configured to run on the WebServer
instance). Given that you have successfully configured the SSL setup
between the DAS and WS/LB, check with changing the port to the SSL port
of the WebServer 7.0 instance.

>
> IS there anything specific to change in order to make it possible to
> apply changes to web server load balancer from glassfish console?
>
> Now my question:
>
> -what kind of glassfish i should setup in some other machines to add
> them to the cluster? can they be normal domains or there are some
> specific ways to create domains to add them to cluster?
> can you give me the steps?
>

You can create multiple server instances and group them under a defined
cluster configuration. The cluster or the group of clustered server
instances are under a single domain. Domain is the administrative
reference - the single point / central repository of carrying out the
administrative tasks.

You can refer to the documentation that details the setups to work with
clusters. This is from the /"High Availability Administration Guide"/
under chapter 5 : /"Using Application Server Clusters" /:-
http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view

Specifically refer to the topic named - /"Working with Clusters"./

> -I find that we can have several instance in a server? what is
> relation of domains with instances? why we should have several
> instance in a domain?

There can be zero or more server instances in a administrative domain
and there can one or more such domains. Each such domain has its own
DAS. DAS is actually the designated administrative server instance with
a default config within a domain.

regards
Pankaj

>
>
>
> Thanks.
>
>
>
>
>
>
> On 4/17/07, *Pankaj Jairath* > > wrote:
>
> Hello Legolas,
>
> If I understood your question, you are referring to the UI element
> "HTTP
> Load Balancers" element of the GlassFish V2 Application Server. If so
> let me give a brief.
>
> GlassFish V2 provides the HTTP Load Balancer which can then be
> deployed
> onto the supported WebServer - for GlassFish V2 it's the Sun Java
> System
> WebServer 6.1 / 7.0. When defining the High Availability deployment
> topology of a Java EE deployment, administrator would define a
> cluster
> of application servers instances and install and configure the
> HTTP Load
> Balancer to take care of load balancing and failover of the HTTP
> requests.
> To do this administrative configuration steps, the end-user can
> use the
> Admin Console (GUI) or the CLI commands to define the cluster, it's
> configuration and associate a HTTP Load Balancer with this
> configuration. This association defines the cluster configuration and
> other Load Balancer configurable parameters, which the HTTP Load
> Balancer uses to perform its HA functionality. The administrator
> can use
> the Admin Console to generate this HTTP Load Balancer
> configuration and
> even push the configuration over the wire to the deployed HTTP Load
> Balancer on a given Sun Java System WebServer.
>
> Refer to the documents provided earlier for further details on how to
> use the Domain Administrative Server (DAS) Admin Console (GUI) or
> CLI to
> administer the HTTP Load Balancer.
>
> regards
> Pankaj
>
> legolas wood wrote:
>
> > Hi
> > Thank you for reading my post.
> > What is relation of "HTTP Load Balancers" in administration
> console
> > with using sun java web server as load balancer?
> >
> > Thanks
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>
> > For additional commands, e-mail:
> users-help@glassfish.dev.java.net
>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Legolas Woodland

Thank you for reply.
just as last question:

As i said i have DAS installed and configuredin my own computer
i want to install some more glassfish in other computer and add them to
cluster.

question is:

Should i install glassfish clustered edition on other computers that will
act as nodes?
ant -f setup-cluster.xml

Thankss

On 4/17/07, Pankaj Jairath wrote:
>
> Legolas Woodland wrote:
>
> > Thank you very much for reply.
> >
> > Right now i think i have setup a cluster and a load balancer according
> > to your very good weblog.
> > I have sun java web server 7.u1 and latest blassfish installed.
> > What i want to know is:
> > I have one DAS, And a web server which according to your weblog will
> > balance the load between any instance that we add in loadbalancer.xml .
> >
> > I have two questions and one problem.
> >
> > problem:
> > I tried several time to create load balancer in glassfish application
> > server and then apply it to my web server, but it just return an error
> > without any stack trance, error say: Can not connect to server.
> > My web server and glassfish both works on the same machine, so i
> > tried: 127.0.0.1 , localhost and my lan ip address
> > none of them worked.
> > the port that i can access my web server administration console is
> > 8989 and i used this port in HTTP Load Balancers node of glassfish
> > administration console when i trid to create the load balancer.
>
> The communication between DAS and WS/LB is over SSL and the host/port
> needs to be HTTPS listener of the WebServer Instance and not that of the
> Admin Server (the Load Balancer is configured to run on the WebServer
> instance). Given that you have successfully configured the SSL setup
> between the DAS and WS/LB, check with changing the port to the SSL port
> of the WebServer 7.0 instance.
>
> >
> > IS there anything specific to change in order to make it possible to
> > apply changes to web server load balancer from glassfish console?
> >
> > Now my question:
> >
> > -what kind of glassfish i should setup in some other machines to add
> > them to the cluster? can they be normal domains or there are some
> > specific ways to create domains to add them to cluster?
> > can you give me the steps?
> >
>
> You can create multiple server instances and group them under a defined
> cluster configuration. The cluster or the group of clustered server
> instances are under a single domain. Domain is the administrative
> reference - the single point / central repository of carrying out the
> administrative tasks.
>
> You can refer to the documentation that details the setups to work with
> clusters. This is from the /"High Availability Administration Guide"/
> under chapter 5 : /"Using Application Server Clusters" /:-
> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>
> Specifically refer to the topic named - /"Working with Clusters"./
>
> > -I find that we can have several instance in a server? what is
> > relation of domains with instances? why we should have several
> > instance in a domain?
>
> There can be zero or more server instances in a administrative domain
> and there can one or more such domains. Each such domain has its own
> DAS. DAS is actually the designated administrative server instance with
> a default config within a domain.
>
> regards
> Pankaj
>
> >
> >
> >
> > Thanks.
> >
> >
> >
> >
> >
> >
> > On 4/17/07, *Pankaj Jairath* > > > wrote:
> >
> > Hello Legolas,
> >
> > If I understood your question, you are referring to the UI element
> > "HTTP
> > Load Balancers" element of the GlassFish V2 Application Server. If
> so
> > let me give a brief.
> >
> > GlassFish V2 provides the HTTP Load Balancer which can then be
> > deployed
> > onto the supported WebServer - for GlassFish V2 it's the Sun Java
> > System
> > WebServer 6.1 / 7.0. When defining the High Availability deployment
> > topology of a Java EE deployment, administrator would define a
> > cluster
> > of application servers instances and install and configure the
> > HTTP Load
> > Balancer to take care of load balancing and failover of the HTTP
> > requests.
> > To do this administrative configuration steps, the end-user can
> > use the
> > Admin Console (GUI) or the CLI commands to define the cluster, it's
> > configuration and associate a HTTP Load Balancer with this
> > configuration. This association defines the cluster configuration
> and
> > other Load Balancer configurable parameters, which the HTTP Load
> > Balancer uses to perform its HA functionality. The administrator
> > can use
> > the Admin Console to generate this HTTP Load Balancer
> > configuration and
> > even push the configuration over the wire to the deployed HTTP Load
> > Balancer on a given Sun Java System WebServer.
> >
> > Refer to the documents provided earlier for further details on how
> to
> > use the Domain Administrative Server (DAS) Admin Console (GUI) or
> > CLI to
> > administer the HTTP Load Balancer.
> >
> > regards
> > Pankaj
> >
> > legolas wood wrote:
> >
> > > Hi
> > > Thank you for reading my post.
> > > What is relation of "HTTP Load Balancers" in administration
> > console
> > > with using sun java web server as load balancer?
> > >
> > > Thanks
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> >
> > > For additional commands, e-mail:
> > users-help@glassfish.dev.java.net
> >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> >
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
> >
>
>
[att1.html]

kedar

Hi Legolas,

Let me try to explain:

Domain Spans machines, usually.
One of the machines is designated as DAS, as Pankaj pointed out earlier.
The DAS is the admin server and it manages the servers in the same
domain. The servers can be clustered if administrator wants them so.
The administrator has benefits of management when instances are clustered.

Now, on the other machine, all you need is "bits".

Consider the scenario: You have "m1" and "m2" as two machines. Let's
say you want to create a cluster "c1" with instances "s1" and "s2"
with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
Let's call the domain where all this "logically" resides as "domain1".

You do the following:
1- Download the glassfish.jar on both "m1" and "m2".
2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
domain1 that is capable of handling clusters.
3- On "m1", you start domain, domain1.
4- On "m1", /asadmin create-node-agent na1
5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you downloaded
(after of course, java -jar ...) This creates a domain on that machine
as well, but you don't need it. I will file an RFE in this regard.
6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
/asadmin create-node-agent --host m1 --user admin-user na2
7- On "m1", /asadmin start-node-agent na1
On "m2", /asadmin start-node-agent na2

Now, your topology is created and ready to go.
You have a domain domain1, this spans "m1" and "m2".
Node-agent "na1" is on "m1". It will control instances on "m1".
Node-agent "na2" is on "m2". It will control instances on "m2".

From this point on, forget you had machine "m2". The entire
configuration can be done just from machine "m1".

This is the beauty of the process, IMO.

8- On "m1", just try: /asadmin create-cluster c1
9- On "m1", /asadmin create-instance --cluster c1 --nodeagent na1 s1
This puts "s1" in cluster "c1". Note that this instance is controlled by
Node Agent "na1". This instance uses "physical resources" from "m1".

10- On "m1", (not "m2"!)
/asadmin create-instance --cluster c1 --nodeagent na2 s2

11- On "m1", /asadmin start-cluster "c1".

This is where it culminates.
All you do is "start cluster".
It starts instance "s1" on "m1" and "s2" on "m2".

The instances have homogeneous configuration.

Does this help?

Regards,
Kedar

Legolas Woodland wrote:
> Thank you for reply.
> just as last question:
>
> As i said i have DAS installed and configuredin my own computer
> i want to install some more glassfish in other computer and add them
> to cluster.
>
> question is:
>
> Should i install glassfish clustered edition on other computers that
> will act as nodes?
> ant -f setup-cluster.xml
>
> Thankss
>
> On 4/17/07, *Pankaj Jairath* > > wrote:
>
> Legolas Woodland wrote:
>
> > Thank you very much for reply.
> >
> > Right now i think i have setup a cluster and a load balancer
> according
> > to your very good weblog.
> > I have sun java web server 7.u1 and latest blassfish installed.
> > What i want to know is:
> > I have one DAS, And a web server which according to your weblog will
> > balance the load between any instance that we add in
> loadbalancer.xml .
> >
> > I have two questions and one problem.
> >
> > problem:
> > I tried several time to create load balancer in glassfish
> application
> > server and then apply it to my web server, but it just return an
> error
> > without any stack trance, error say: Can not connect to server.
> > My web server and glassfish both works on the same machine, so i
> > tried: 127.0.0.1 < http://127.0.0.1>,
> localhost and my lan ip address
> > none of them worked.
> > the port that i can access my web server administration console is
> > 8989 and i used this port in HTTP Load Balancers node of glassfish
> > administration console when i trid to create the load balancer.
>
> The communication between DAS and WS/LB is over SSL and the host/port
> needs to be HTTPS listener of the WebServer Instance and not that
> of the
> Admin Server (the Load Balancer is configured to run on the WebServer
> instance). Given that you have successfully configured the SSL setup
> between the DAS and WS/LB, check with changing the port to the SSL
> port
> of the WebServer 7.0 instance.
>
> >
> > IS there anything specific to change in order to make it possible to
> > apply changes to web server load balancer from glassfish console?
> >
> > Now my question:
> >
> > -what kind of glassfish i should setup in some other machines to add
> > them to the cluster? can they be normal domains or there are some
> > specific ways to create domains to add them to cluster?
> > can you give me the steps?
> >
>
> You can create multiple server instances and group them under a
> defined
> cluster configuration. The cluster or the group of clustered server
> instances are under a single domain. Domain is the administrative
> reference - the single point / central repository of carrying out the
> administrative tasks.
>
> You can refer to the documentation that details the setups to work
> with
> clusters. This is from the /"High Availability Administration Guide"/
> under chapter 5 : /"Using Application Server Clusters" /:-
> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>
> Specifically refer to the topic named - /"Working with Clusters"./
>
> > -I find that we can have several instance in a server? what is
> > relation of domains with instances? why we should have several
> > instance in a domain?
>
> There can be zero or more server instances in a administrative domain
> and there can one or more such domains. Each such domain has its own
> DAS. DAS is actually the designated administrative server instance
> with
> a default config within a domain.
>
> regards
> Pankaj
>
> >
> >
> >
> > Thanks.
> >
> >
> >
> >
> >
> >
> > On 4/17/07, *Pankaj Jairath* >
> > Pankaj.Jairath@sun.com
> >> wrote:
> >
> > Hello Legolas,
> >
> > If I understood your question, you are referring to the UI
> element
> > "HTTP
> > Load Balancers" element of the GlassFish V2 Application
> Server. If so
> > let me give a brief.
> >
> > GlassFish V2 provides the HTTP Load Balancer which can then be
> > deployed
> > onto the supported WebServer - for GlassFish V2 it's the Sun
> Java
> > System
> > WebServer 6.1 / 7.0. When defining the High Availability
> deployment
> > topology of a Java EE deployment, administrator would define a
> > cluster
> > of application servers instances and install and configure the
> > HTTP Load
> > Balancer to take care of load balancing and failover of the HTTP
> > requests.
> > To do this administrative configuration steps, the end-user can
> > use the
> > Admin Console (GUI) or the CLI commands to define the
> cluster, it's
> > configuration and associate a HTTP Load Balancer with this
> > configuration. This association defines the cluster
> configuration and
> > other Load Balancer configurable parameters, which the HTTP Load
> > Balancer uses to perform its HA functionality. The administrator
> > can use
> > the Admin Console to generate this HTTP Load Balancer
> > configuration and
> > even push the configuration over the wire to the deployed
> HTTP Load
> > Balancer on a given Sun Java System WebServer.
> >
> > Refer to the documents provided earlier for further details
> on how to
> > use the Domain Administrative Server (DAS) Admin Console
> (GUI) or
> > CLI to
> > administer the HTTP Load Balancer.
> >
> > regards
> > Pankaj
> >
> > legolas wood wrote:
> >
> > > Hi
> > > Thank you for reading my post.
> > > What is relation of "HTTP Load Balancers" in administration
> > console
> > > with using sun java web server as load balancer?
> > >
> > > Thanks
> > >
> > >
> >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail:
> users-unsubscribe@glassfish.dev.java.net
>
> > > >
> > > For additional commands, e-mail:
> > users-help@glassfish.dev.java.net
>
> > > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> users-unsubscribe@glassfish.dev.java.net
>
> > > >
> > For additional commands, e-mail:
> users-help@glassfish.dev.java.net
>
> > > >
> >
> >
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Peter Fabian

Legolas
the picture (although a bit detailed and crowded) at
http://wiki.glassfish.java.net/gfwiki/Wiki.jsp?page=GlassFishV2Architecture
might help
P
kedar wrote:
> Hi Legolas,
>
> Let me try to explain:
>
> Domain Spans machines, usually.
> One of the machines is designated as DAS, as Pankaj pointed out earlier.
> The DAS is the admin server and it manages the servers in the same
> domain. The servers can be clustered if administrator wants them so.
> The administrator has benefits of management when instances are
> clustered.
>
> Now, on the other machine, all you need is "bits".
>
> Consider the scenario: You have "m1" and "m2" as two machines. Let's
> say you want to create a cluster "c1" with instances "s1" and "s2"
> with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
> Let's call the domain where all this "logically" resides as "domain1".
>
> You do the following:
> 1- Download the glassfish.jar on both "m1" and "m2".
> 2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
> domain1 that is capable of handling clusters.
> 3- On "m1", you start domain, domain1.
> 4- On "m1", /asadmin create-node-agent na1
> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you downloaded
> (after of course, java -jar ...) This creates a domain on that machine
> as well, but you don't need it. I will file an RFE in this regard.
> 6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
> /asadmin create-node-agent --host m1 --user admin-user na2
> 7- On "m1", /asadmin start-node-agent na1
> On "m2", /asadmin start-node-agent na2
>
> Now, your topology is created and ready to go.
> You have a domain domain1, this spans "m1" and "m2".
> Node-agent "na1" is on "m1". It will control instances on "m1".
> Node-agent "na2" is on "m2". It will control instances on "m2".
>
> From this point on, forget you had machine "m2". The entire
> configuration can be done just from machine "m1".
>
> This is the beauty of the process, IMO.
>
> 8- On "m1", just try: /asadmin create-cluster c1
> 9- On "m1", /asadmin create-instance --cluster c1 --nodeagent
> na1 s1
> This puts "s1" in cluster "c1". Note that this instance is controlled by
> Node Agent "na1". This instance uses "physical resources" from "m1".
>
> 10- On "m1", (not "m2"!)
> /asadmin create-instance --cluster c1 --nodeagent na2 s2
>
> 11- On "m1", /asadmin start-cluster "c1".
>
> This is where it culminates.
> All you do is "start cluster".
> It starts instance "s1" on "m1" and "s2" on "m2".
>
> The instances have homogeneous configuration.
>
> Does this help?
>
> Regards,
> Kedar
>
> Legolas Woodland wrote:
>> Thank you for reply.
>> just as last question:
>>
>> As i said i have DAS installed and configuredin my own computer
>> i want to install some more glassfish in other computer and add them
>> to cluster.
>>
>> question is:
>>
>> Should i install glassfish clustered edition on other computers that
>> will act as nodes?
>> ant -f setup-cluster.xml
>>
>> Thankss
>>
>> On 4/17/07, *Pankaj Jairath* >> > wrote:
>>
>> Legolas Woodland wrote:
>>
>> > Thank you very much for reply.
>> >
>> > Right now i think i have setup a cluster and a load balancer
>> according
>> > to your very good weblog.
>> > I have sun java web server 7.u1 and latest blassfish installed.
>> > What i want to know is:
>> > I have one DAS, And a web server which according to your weblog
>> will
>> > balance the load between any instance that we add in
>> loadbalancer.xml .
>> >
>> > I have two questions and one problem.
>> >
>> > problem:
>> > I tried several time to create load balancer in glassfish
>> application
>> > server and then apply it to my web server, but it just return an
>> error
>> > without any stack trance, error say: Can not connect to server.
>> > My web server and glassfish both works on the same machine, so i
>> > tried: 127.0.0.1 < http://127.0.0.1>,
>> localhost and my lan ip address
>> > none of them worked.
>> > the port that i can access my web server administration console is
>> > 8989 and i used this port in HTTP Load Balancers node of glassfish
>> > administration console when i trid to create the load balancer.
>>
>> The communication between DAS and WS/LB is over SSL and the
>> host/port
>> needs to be HTTPS listener of the WebServer Instance and not that
>> of the
>> Admin Server (the Load Balancer is configured to run on the
>> WebServer
>> instance). Given that you have successfully configured the SSL setup
>> between the DAS and WS/LB, check with changing the port to the SSL
>> port
>> of the WebServer 7.0 instance.
>>
>> >
>> > IS there anything specific to change in order to make it
>> possible to
>> > apply changes to web server load balancer from glassfish console?
>> >
>> > Now my question:
>> >
>> > -what kind of glassfish i should setup in some other machines
>> to add
>> > them to the cluster? can they be normal domains or there are some
>> > specific ways to create domains to add them to cluster?
>> > can you give me the steps?
>> >
>>
>> You can create multiple server instances and group them under a
>> defined
>> cluster configuration. The cluster or the group of clustered server
>> instances are under a single domain. Domain is the administrative
>> reference - the single point / central repository of carrying out
>> the
>> administrative tasks.
>>
>> You can refer to the documentation that details the setups to work
>> with
>> clusters. This is from the /"High Availability Administration
>> Guide"/
>> under chapter 5 : /"Using Application Server Clusters" /:-
>> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>>
>> Specifically refer to the topic named - /"Working with Clusters"./
>>
>> > -I find that we can have several instance in a server? what is
>> > relation of domains with instances? why we should have several
>> > instance in a domain?
>>
>> There can be zero or more server instances in a administrative
>> domain
>> and there can one or more such domains. Each such domain has its
>> own
>> DAS. DAS is actually the designated administrative server instance
>> with
>> a default config within a domain.
>>
>> regards
>> Pankaj
>>
>> >
>> >
>> >
>> > Thanks.
>> >
>> >
>> >
>> >
>> >
>> >
>> > On 4/17/07, *Pankaj Jairath* >>
>> > Pankaj.Jairath@sun.com
>> >> wrote:
>> >
>> > Hello Legolas,
>> >
>> > If I understood your question, you are referring to the UI
>> element
>> > "HTTP
>> > Load Balancers" element of the GlassFish V2 Application
>> Server. If so
>> > let me give a brief.
>> >
>> > GlassFish V2 provides the HTTP Load Balancer which can then be
>> > deployed
>> > onto the supported WebServer - for GlassFish V2 it's the Sun
>> Java
>> > System
>> > WebServer 6.1 / 7.0. When defining the High Availability
>> deployment
>> > topology of a Java EE deployment, administrator would
>> define a
>> > cluster
>> > of application servers instances and install and configure the
>> > HTTP Load
>> > Balancer to take care of load balancing and failover of the
>> HTTP
>> > requests.
>> > To do this administrative configuration steps, the
>> end-user can
>> > use the
>> > Admin Console (GUI) or the CLI commands to define the
>> cluster, it's
>> > configuration and associate a HTTP Load Balancer with this
>> > configuration. This association defines the cluster
>> configuration and
>> > other Load Balancer configurable parameters, which the HTTP
>> Load
>> > Balancer uses to perform its HA functionality. The
>> administrator
>> > can use
>> > the Admin Console to generate this HTTP Load Balancer
>> > configuration and
>> > even push the configuration over the wire to the deployed
>> HTTP Load
>> > Balancer on a given Sun Java System WebServer.
>> >
>> > Refer to the documents provided earlier for further details
>> on how to
>> > use the Domain Administrative Server (DAS) Admin Console
>> (GUI) or
>> > CLI to
>> > administer the HTTP Load Balancer.
>> >
>> > regards
>> > Pankaj
>> >
>> > legolas wood wrote:
>> >
>> > > Hi
>> > > Thank you for reading my post.
>> > > What is relation of "HTTP Load Balancers" in administration
>> > console
>> > > with using sun java web server as load balancer?
>> > >
>> > > Thanks
>> > >
>> > >
>> >
>> ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail:
>> users-unsubscribe@glassfish.dev.java.net
>>
>> > >> >
>> > > For additional commands, e-mail:
>> > users-help@glassfish.dev.java.net
>>
>> > >> >
>> > >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> users-unsubscribe@glassfish.dev.java.net
>>
>> > >> >
>> > For additional commands, e-mail:
>> users-help@glassfish.dev.java.net
>>
>> > >> >
>> >
>> >
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

--
Peter Fabian
Sun Software

AIM/skype:fabianpetergabor

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

legolas wood

Thank you for your information.

When we install Glassfish application on our computer it create one
default domain named domain1 in domains directory which we deploy our
application into it. we can create more domains if we want.

Now, If I create a new instance in an this installed application server
using asadmin> create-instance ...... what is relation of this instance
with those domain in domains directory?

Kedar, in you 5th step you said that:

5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you downloaded
.....

When we use setup-cluster.xml to install glassfish, it will create a
DAS as far as i know.
So on every machine in the network like m2,m3..... that want to make
them a domain(cluster) member we will have a DAS but we do not use it
because we have a DAS on m1?

If the above is correct, why we should add load of a DAS on every
machine like m2,m3,m4?

Thanks

Peter Fabian wrote:
> Legolas
> the picture (although a bit detailed and crowded) at
> http://wiki.glassfish.java.net/gfwiki/Wiki.jsp?page=GlassFishV2Architecture
> might help
> P
> kedar wrote:
>> Hi Legolas,
>>
>> Let me try to explain:
>>
>> Domain Spans machines, usually.
>> One of the machines is designated as DAS, as Pankaj pointed out earlier.
>> The DAS is the admin server and it manages the servers in the same
>> domain. The servers can be clustered if administrator wants them so.
>> The administrator has benefits of management when instances are
>> clustered.
>>
>> Now, on the other machine, all you need is "bits".
>>
>> Consider the scenario: You have "m1" and "m2" as two machines. Let's
>> say you want to create a cluster "c1" with instances "s1" and "s2"
>> with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
>> Let's call the domain where all this "logically" resides as "domain1".
>>
>> You do the following:
>> 1- Download the glassfish.jar on both "m1" and "m2".
>> 2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
>> domain1 that is capable of handling clusters.
>> 3- On "m1", you start domain, domain1.
>> 4- On "m1", /asadmin create-node-agent na1
>> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you downloaded
>> (after of course, java -jar ...) This creates a domain on that machine
>> as well, but you don't need it. I will file an RFE in this regard.
>> 6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
>> /asadmin create-node-agent --host m1 --user admin-user na2
>> 7- On "m1", /asadmin start-node-agent na1
>> On "m2", /asadmin start-node-agent na2
>>
>> Now, your topology is created and ready to go.
>> You have a domain domain1, this spans "m1" and "m2".
>> Node-agent "na1" is on "m1". It will control instances on "m1".
>> Node-agent "na2" is on "m2". It will control instances on "m2".
>>
>> From this point on, forget you had machine "m2". The entire
>> configuration can be done just from machine "m1".
>>
>> This is the beauty of the process, IMO.
>>
>> 8- On "m1", just try: /asadmin create-cluster c1
>> 9- On "m1", /asadmin create-instance --cluster c1 --nodeagent
>> na1 s1
>> This puts "s1" in cluster "c1". Note that this instance is controlled by
>> Node Agent "na1". This instance uses "physical resources" from "m1".
>>
>> 10- On "m1", (not "m2"!)
>> /asadmin create-instance --cluster c1 --nodeagent na2 s2
>>
>> 11- On "m1", /asadmin start-cluster "c1".
>>
>> This is where it culminates.
>> All you do is "start cluster".
>> It starts instance "s1" on "m1" and "s2" on "m2".
>>
>> The instances have homogeneous configuration.
>>
>> Does this help?
>>
>> Regards,
>> Kedar
>>
>> Legolas Woodland wrote:
>>> Thank you for reply.
>>> just as last question:
>>>
>>> As i said i have DAS installed and configuredin my own computer
>>> i want to install some more glassfish in other computer and add them
>>> to cluster.
>>>
>>> question is:
>>>
>>> Should i install glassfish clustered edition on other computers that
>>> will act as nodes?
>>> ant -f setup-cluster.xml
>>>
>>> Thankss
>>>
>>> On 4/17/07, *Pankaj Jairath* >>> > wrote:
>>>
>>> Legolas Woodland wrote:
>>>
>>> > Thank you very much for reply.
>>> >
>>> > Right now i think i have setup a cluster and a load balancer
>>> according
>>> > to your very good weblog.
>>> > I have sun java web server 7.u1 and latest blassfish installed.
>>> > What i want to know is:
>>> > I have one DAS, And a web server which according to your
>>> weblog will
>>> > balance the load between any instance that we add in
>>> loadbalancer.xml .
>>> >
>>> > I have two questions and one problem.
>>> >
>>> > problem:
>>> > I tried several time to create load balancer in glassfish
>>> application
>>> > server and then apply it to my web server, but it just return an
>>> error
>>> > without any stack trance, error say: Can not connect to server.
>>> > My web server and glassfish both works on the same machine, so i
>>> > tried: 127.0.0.1 < http://127.0.0.1>,
>>> localhost and my lan ip address
>>> > none of them worked.
>>> > the port that i can access my web server administration
>>> console is
>>> > 8989 and i used this port in HTTP Load Balancers node of
>>> glassfish
>>> > administration console when i trid to create the load balancer.
>>>
>>> The communication between DAS and WS/LB is over SSL and the
>>> host/port
>>> needs to be HTTPS listener of the WebServer Instance and not that
>>> of the
>>> Admin Server (the Load Balancer is configured to run on the
>>> WebServer
>>> instance). Given that you have successfully configured the SSL
>>> setup
>>> between the DAS and WS/LB, check with changing the port to the SSL
>>> port
>>> of the WebServer 7.0 instance.
>>>
>>> >
>>> > IS there anything specific to change in order to make it
>>> possible to
>>> > apply changes to web server load balancer from glassfish console?
>>> >
>>> > Now my question:
>>> >
>>> > -what kind of glassfish i should setup in some other machines
>>> to add
>>> > them to the cluster? can they be normal domains or there are some
>>> > specific ways to create domains to add them to cluster?
>>> > can you give me the steps?
>>> >
>>>
>>> You can create multiple server instances and group them under a
>>> defined
>>> cluster configuration. The cluster or the group of clustered server
>>> instances are under a single domain. Domain is the administrative
>>> reference - the single point / central repository of carrying
>>> out the
>>> administrative tasks.
>>>
>>> You can refer to the documentation that details the setups to work
>>> with
>>> clusters. This is from the /"High Availability Administration
>>> Guide"/
>>> under chapter 5 : /"Using Application Server Clusters" /:-
>>> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>>>
>>> Specifically refer to the topic named - /"Working with Clusters"./
>>>
>>> > -I find that we can have several instance in a server? what is
>>> > relation of domains with instances? why we should have several
>>> > instance in a domain?
>>>
>>> There can be zero or more server instances in a administrative
>>> domain
>>> and there can one or more such domains. Each such domain has
>>> its own
>>> DAS. DAS is actually the designated administrative server instance
>>> with
>>> a default config within a domain.
>>>
>>> regards
>>> Pankaj
>>>
>>> >
>>> >
>>> >
>>> > Thanks.
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On 4/17/07, *Pankaj Jairath* >>>
>>> > Pankaj.Jairath@sun.com
>>> >> wrote:
>>> >
>>> > Hello Legolas,
>>> >
>>> > If I understood your question, you are referring to the UI
>>> element
>>> > "HTTP
>>> > Load Balancers" element of the GlassFish V2 Application
>>> Server. If so
>>> > let me give a brief.
>>> >
>>> > GlassFish V2 provides the HTTP Load Balancer which can
>>> then be
>>> > deployed
>>> > onto the supported WebServer - for GlassFish V2 it's the Sun
>>> Java
>>> > System
>>> > WebServer 6.1 / 7.0. When defining the High Availability
>>> deployment
>>> > topology of a Java EE deployment, administrator would
>>> define a
>>> > cluster
>>> > of application servers instances and install and configure
>>> the
>>> > HTTP Load
>>> > Balancer to take care of load balancing and failover of
>>> the HTTP
>>> > requests.
>>> > To do this administrative configuration steps, the
>>> end-user can
>>> > use the
>>> > Admin Console (GUI) or the CLI commands to define the
>>> cluster, it's
>>> > configuration and associate a HTTP Load Balancer with this
>>> > configuration. This association defines the cluster
>>> configuration and
>>> > other Load Balancer configurable parameters, which the
>>> HTTP Load
>>> > Balancer uses to perform its HA functionality. The
>>> administrator
>>> > can use
>>> > the Admin Console to generate this HTTP Load Balancer
>>> > configuration and
>>> > even push the configuration over the wire to the deployed
>>> HTTP Load
>>> > Balancer on a given Sun Java System WebServer.
>>> >
>>> > Refer to the documents provided earlier for further details
>>> on how to
>>> > use the Domain Administrative Server (DAS) Admin Console
>>> (GUI) or
>>> > CLI to
>>> > administer the HTTP Load Balancer.
>>> >
>>> > regards
>>> > Pankaj
>>> >
>>> > legolas wood wrote:
>>> >
>>> > > Hi
>>> > > Thank you for reading my post.
>>> > > What is relation of "HTTP Load Balancers" in
>>> administration
>>> > console
>>> > > with using sun java web server as load balancer?
>>> > >
>>> > > Thanks
>>> > >
>>> > >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

kedar

legolas wood wrote:
> Thank you for your information.
>
>
> When we install Glassfish application on our computer it create one
> default domain named domain1 in domains directory which we deploy our
> application into it. we can create more domains if we want.
>
> Now, If I create a new instance in an this installed application
> server using asadmin> create-instance ...... what is relation of this
> instance with those domain in domains directory?
When you create the instance using create-instance, you are pointing
to a specific domain. A domain is identified by: its host name, admin port,
admin user and admin password. All of this is happening behind the scenes
because everything has a default value.
admin-host: localhost
admin-port: 4848
admin-user and password: taken from a file called .asadminpass in your
home folder,
because you created this domain using --savelogin. The "ant -f
setup.xml" and "ant -f
setup-cluster.xml" automatically save an encoded version of your admin
user name
and admin password :)

>
>
>
> Kedar, in you 5th step you said that:
>
> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you
> downloaded .....
>
> When we use setup-cluster.xml to install glassfish, it will create a
> DAS as far as i know.
> So on every machine in the network like m2,m3..... that want to make
> them a domain(cluster) member we will have a DAS but we do not use it
> because we have a DAS on m1?
>
You are right, but that's the DAS's configuration that you create on "m2".
Like I said, currently, there is no way to configure
/bin/all-scripts
/bin/all-config-files like asadminenv.conf

ALONE, using ant -f setup.xml, setup-cluster.xml. Unfortunately,
you HAVE to create the domain. Ask Dinesh, if there is a way to not
create a domain. Dinesh -- do you know?
> If the above is correct, why we should add load of a DAS on every
> machine like m2,m3,m4?
>
Actually, a domain (statically) is nothing but a bunch of files.
See: http://blogs.sun.com/bloggerkedar/entry/concept_of_a_glassfish_domain

So, I don't think it's a load, it is just an unnecessary step that we
can't avoid, AFAIK.

Kedar

>
> Thanks
>
>
>
> Peter Fabian wrote:
>> Legolas
>> the picture (although a bit detailed and crowded) at
>> http://wiki.glassfish.java.net/gfwiki/Wiki.jsp?page=GlassFishV2Architecture
>> might help
>> P
>> kedar wrote:
>>> Hi Legolas,
>>>
>>> Let me try to explain:
>>>
>>> Domain Spans machines, usually.
>>> One of the machines is designated as DAS, as Pankaj pointed out
>>> earlier.
>>> The DAS is the admin server and it manages the servers in the same
>>> domain. The servers can be clustered if administrator wants them so.
>>> The administrator has benefits of management when instances are
>>> clustered.
>>>
>>> Now, on the other machine, all you need is "bits".
>>>
>>> Consider the scenario: You have "m1" and "m2" as two machines. Let's
>>> say you want to create a cluster "c1" with instances "s1" and "s2"
>>> with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
>>> Let's call the domain where all this "logically" resides as "domain1".
>>>
>>> You do the following:
>>> 1- Download the glassfish.jar on both "m1" and "m2".
>>> 2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
>>> domain1 that is capable of handling clusters.
>>> 3- On "m1", you start domain, domain1.
>>> 4- On "m1", /asadmin create-node-agent na1
>>> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you
>>> downloaded
>>> (after of course, java -jar ...) This creates a domain on that
>>> machine
>>> as well, but you don't need it. I will file an RFE in this regard.
>>> 6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
>>> /asadmin create-node-agent --host m1 --user admin-user na2
>>> 7- On "m1", /asadmin start-node-agent na1
>>> On "m2", /asadmin start-node-agent na2
>>>
>>> Now, your topology is created and ready to go.
>>> You have a domain domain1, this spans "m1" and "m2".
>>> Node-agent "na1" is on "m1". It will control instances on "m1".
>>> Node-agent "na2" is on "m2". It will control instances on "m2".
>>>
>>> From this point on, forget you had machine "m2". The entire
>>> configuration can be done just from machine "m1".
>>>
>>> This is the beauty of the process, IMO.
>>>
>>> 8- On "m1", just try: /asadmin create-cluster c1
>>> 9- On "m1", /asadmin create-instance --cluster c1 --nodeagent
>>> na1 s1
>>> This puts "s1" in cluster "c1". Note that this instance is
>>> controlled by
>>> Node Agent "na1". This instance uses "physical resources" from "m1".
>>>
>>> 10- On "m1", (not "m2"!)
>>> /asadmin create-instance --cluster c1 --nodeagent na2 s2
>>>
>>> 11- On "m1", /asadmin start-cluster "c1".
>>>
>>> This is where it culminates.
>>> All you do is "start cluster".
>>> It starts instance "s1" on "m1" and "s2" on "m2".
>>>
>>> The instances have homogeneous configuration.
>>>
>>> Does this help?
>>>
>>> Regards,
>>> Kedar
>>>
>>> Legolas Woodland wrote:
>>>> Thank you for reply.
>>>> just as last question:
>>>>
>>>> As i said i have DAS installed and configuredin my own computer
>>>> i want to install some more glassfish in other computer and add
>>>> them to cluster.
>>>>
>>>> question is:
>>>>
>>>> Should i install glassfish clustered edition on other computers
>>>> that will act as nodes?
>>>> ant -f setup-cluster.xml
>>>>
>>>> Thankss
>>>>
>>>> On 4/17/07, *Pankaj Jairath* >>>> > wrote:
>>>>
>>>> Legolas Woodland wrote:
>>>>
>>>> > Thank you very much for reply.
>>>> >
>>>> > Right now i think i have setup a cluster and a load balancer
>>>> according
>>>> > to your very good weblog.
>>>> > I have sun java web server 7.u1 and latest blassfish installed.
>>>> > What i want to know is:
>>>> > I have one DAS, And a web server which according to your
>>>> weblog will
>>>> > balance the load between any instance that we add in
>>>> loadbalancer.xml .
>>>> >
>>>> > I have two questions and one problem.
>>>> >
>>>> > problem:
>>>> > I tried several time to create load balancer in glassfish
>>>> application
>>>> > server and then apply it to my web server, but it just return an
>>>> error
>>>> > without any stack trance, error say: Can not connect to server.
>>>> > My web server and glassfish both works on the same machine, so i
>>>> > tried: 127.0.0.1 < http://127.0.0.1>,
>>>> localhost and my lan ip address
>>>> > none of them worked.
>>>> > the port that i can access my web server administration
>>>> console is
>>>> > 8989 and i used this port in HTTP Load Balancers node of
>>>> glassfish
>>>> > administration console when i trid to create the load balancer.
>>>>
>>>> The communication between DAS and WS/LB is over SSL and the
>>>> host/port
>>>> needs to be HTTPS listener of the WebServer Instance and not that
>>>> of the
>>>> Admin Server (the Load Balancer is configured to run on the
>>>> WebServer
>>>> instance). Given that you have successfully configured the SSL
>>>> setup
>>>> between the DAS and WS/LB, check with changing the port to the SSL
>>>> port
>>>> of the WebServer 7.0 instance.
>>>>
>>>> >
>>>> > IS there anything specific to change in order to make it
>>>> possible to
>>>> > apply changes to web server load balancer from glassfish
>>>> console?
>>>> >
>>>> > Now my question:
>>>> >
>>>> > -what kind of glassfish i should setup in some other machines
>>>> to add
>>>> > them to the cluster? can they be normal domains or there are
>>>> some
>>>> > specific ways to create domains to add them to cluster?
>>>> > can you give me the steps?
>>>> >
>>>>
>>>> You can create multiple server instances and group them under a
>>>> defined
>>>> cluster configuration. The cluster or the group of clustered
>>>> server
>>>> instances are under a single domain. Domain is the administrative
>>>> reference - the single point / central repository of carrying
>>>> out the
>>>> administrative tasks.
>>>>
>>>> You can refer to the documentation that details the setups to work
>>>> with
>>>> clusters. This is from the /"High Availability Administration
>>>> Guide"/
>>>> under chapter 5 : /"Using Application Server Clusters" /:-
>>>> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
>>>>
>>>> Specifically refer to the topic named - /"Working with Clusters"./
>>>>
>>>> > -I find that we can have several instance in a server? what is
>>>> > relation of domains with instances? why we should have several
>>>> > instance in a domain?
>>>>
>>>> There can be zero or more server instances in a administrative
>>>> domain
>>>> and there can one or more such domains. Each such domain has
>>>> its own
>>>> DAS. DAS is actually the designated administrative server instance
>>>> with
>>>> a default config within a domain.
>>>>
>>>> regards
>>>> Pankaj
>>>>
>>>> >
>>>> >
>>>> >
>>>> > Thanks.
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On 4/17/07, *Pankaj Jairath* >>>>
>>>> > Pankaj.Jairath@sun.com
>>>> >> wrote:
>>>> >
>>>> > Hello Legolas,
>>>> >
>>>> > If I understood your question, you are referring to the UI
>>>> element
>>>> > "HTTP
>>>> > Load Balancers" element of the GlassFish V2 Application
>>>> Server. If so
>>>> > let me give a brief.
>>>> >
>>>> > GlassFish V2 provides the HTTP Load Balancer which can
>>>> then be
>>>> > deployed
>>>> > onto the supported WebServer - for GlassFish V2 it's the Sun
>>>> Java
>>>> > System
>>>> > WebServer 6.1 / 7.0. When defining the High Availability
>>>> deployment
>>>> > topology of a Java EE deployment, administrator would
>>>> define a
>>>> > cluster
>>>> > of application servers instances and install and
>>>> configure the
>>>> > HTTP Load
>>>> > Balancer to take care of load balancing and failover of
>>>> the HTTP
>>>> > requests.
>>>> > To do this administrative configuration steps, the
>>>> end-user can
>>>> > use the
>>>> > Admin Console (GUI) or the CLI commands to define the
>>>> cluster, it's
>>>> > configuration and associate a HTTP Load Balancer with this
>>>> > configuration. This association defines the cluster
>>>> configuration and
>>>> > other Load Balancer configurable parameters, which the
>>>> HTTP Load
>>>> > Balancer uses to perform its HA functionality. The
>>>> administrator
>>>> > can use
>>>> > the Admin Console to generate this HTTP Load Balancer
>>>> > configuration and
>>>> > even push the configuration over the wire to the deployed
>>>> HTTP Load
>>>> > Balancer on a given Sun Java System WebServer.
>>>> >
>>>> > Refer to the documents provided earlier for further details
>>>> on how to
>>>> > use the Domain Administrative Server (DAS) Admin Console
>>>> (GUI) or
>>>> > CLI to
>>>> > administer the HTTP Load Balancer.
>>>> >
>>>> > regards
>>>> > Pankaj
>>>> >
>>>> > legolas wood wrote:
>>>> >
>>>> > > Hi
>>>> > > Thank you for reading my post.
>>>> > > What is relation of "HTTP Load Balancers" in
>>>> administration
>>>> > console
>>>> > > with using sun java web server as load balancer?
>>>> > >
>>>> > > Thanks
>>>> > >
>>>> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Legolas Woodland

Pleas read inline

On 4/18/07, kedar wrote:
>
>
>
> legolas wood wrote:
> > Thank you for your information.
> >
> >
> > When we install Glassfish application on our computer it create one
> > default domain named domain1 in domains directory which we deploy our
> > application into it. we can create more domains if we want.
> >
> > Now, If I create a new instance in an this installed application
> > server using asadmin> create-instance ...... what is relation of this
> > instance with those domain in domains directory?
> When you create the instance using create-instance, you are pointing
> to a specific domain. A domain is identified by: its host name, admin
> port,
> admin user and admin password. All of this is happening behind the scenes
> because everything has a default value.
> admin-host: localhost
> admin-port: 4848
> admin-user and password: taken from a file called .asadminpass in your
> home folder,
> because you created this domain using --savelogin. The "ant -f
> setup.xml" and "ant -f
> setup-cluster.xml" automatically save an encoded version of your admin
> user name
> and admin password :)

Thank you for reply, but as domain i meant domains that are stored in
m2\glassfish\domains folder not DAS.
Thanks

>
> >
> >
> > Kedar, in you 5th step you said that:
> >
> > 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you
> > downloaded .....
> >
> > When we use setup-cluster.xml to install glassfish, it will create a
> > DAS as far as i know.
> > So on every machine in the network like m2,m3..... that want to make
> > them a domain(cluster) member we will have a DAS but we do not use it
> > because we have a DAS on m1?
> >
> You are right, but that's the DAS's configuration that you create on "m2".
> Like I said, currently, there is no way to configure
> /bin/all-scripts
> /bin/all-config-files like asadminenv.conf
>
> ALONE, using ant -f setup.xml, setup-cluster.xml. Unfortunately,
> you HAVE to create the domain. Ask Dinesh, if there is a way to not
> create a domain. Dinesh -- do you know?
> > If the above is correct, why we should add load of a DAS on every
> > machine like m2,m3,m4?
> >
> Actually, a domain (statically) is nothing but a bunch of files.
> See: http://blogs.sun.com/bloggerkedar/entry/concept_of_a_glassfish_domain
>
> So, I don't think it's a load, it is just an unnecessary step that we
> can't avoid, AFAIK.
>
>
> Kedar
>
> >
> > Thanks
> >
> >
> >
> > Peter Fabian wrote:
> >> Legolas
> >> the picture (although a bit detailed and crowded) at
> >>
> http://wiki.glassfish.java.net/gfwiki/Wiki.jsp?page=GlassFishV2Architecture
> >> might help
> >> P
> >> kedar wrote:
> >>> Hi Legolas,
> >>>
> >>> Let me try to explain:
> >>>
> >>> Domain Spans machines, usually.
> >>> One of the machines is designated as DAS, as Pankaj pointed out
> >>> earlier.
> >>> The DAS is the admin server and it manages the servers in the same
> >>> domain. The servers can be clustered if administrator wants them so.
> >>> The administrator has benefits of management when instances are
> >>> clustered.
> >>>
> >>> Now, on the other machine, all you need is "bits".
> >>>
> >>> Consider the scenario: You have "m1" and "m2" as two machines. Let's
> >>> say you want to create a cluster "c1" with instances "s1" and "s2"
> >>> with node-agents "na1" on "m1" and "na2" on "m2". Your DAS is on "m1".
> >>> Let's call the domain where all this "logically" resides as "domain1".
> >>>
> >>> You do the following:
> >>> 1- Download the glassfish.jar on both "m1" and "m2".
> >>> 2- On "m1", run "ant -f setup-cluster.xml". This creates the domain,
> >>> domain1 that is capable of handling clusters.
> >>> 3- On "m1", you start domain, domain1.
> >>> 4- On "m1", /asadmin create-node-agent na1
> >>> 5- On "m2", run ant -f setup-cluster.xml on glassfish.jar you
> >>> downloaded
> >>> (after of course, java -jar ...) This creates a domain on that
> >>> machine
> >>> as well, but you don't need it. I will file an RFE in this regard.
> >>> 6- On "m2" you create a node-agent *pointing to domain1 on "m1"* as:
> >>> /asadmin create-node-agent --host m1 --user admin-user na2
> >>> 7- On "m1", /asadmin start-node-agent na1
> >>> On "m2", /asadmin start-node-agent na2
> >>>
> >>> Now, your topology is created and ready to go.
> >>> You have a domain domain1, this spans "m1" and "m2".
> >>> Node-agent "na1" is on "m1". It will control instances on "m1".
> >>> Node-agent "na2" is on "m2". It will control instances on "m2".
> >>>
> >>> From this point on, forget you had machine "m2". The entire
> >>> configuration can be done just from machine "m1".
> >>>
> >>> This is the beauty of the process, IMO.
> >>>
> >>> 8- On "m1", just try: /asadmin create-cluster c1
> >>> 9- On "m1", /asadmin create-instance --cluster c1 --nodeagent
> >>> na1 s1
> >>> This puts "s1" in cluster "c1". Note that this instance is
> >>> controlled by
> >>> Node Agent "na1". This instance uses "physical resources" from "m1".
> >>>
> >>> 10- On "m1", (not "m2"!)
> >>> /asadmin create-instance --cluster c1 --nodeagent na2 s2
> >>>
> >>> 11- On "m1", /asadmin start-cluster "c1".
> >>>
> >>> This is where it culminates.
> >>> All you do is "start cluster".
> >>> It starts instance "s1" on "m1" and "s2" on "m2".
> >>>
> >>> The instances have homogeneous configuration.
> >>>
> >>> Does this help?
> >>>
> >>> Regards,
> >>> Kedar
> >>>
> >>> Legolas Woodland wrote:
> >>>> Thank you for reply.
> >>>> just as last question:
> >>>>
> >>>> As i said i have DAS installed and configuredin my own computer
> >>>> i want to install some more glassfish in other computer and add
> >>>> them to cluster.
> >>>>
> >>>> question is:
> >>>>
> >>>> Should i install glassfish clustered edition on other computers
> >>>> that will act as nodes?
> >>>> ant -f setup-cluster.xml
> >>>>
> >>>> Thankss
> >>>>
> >>>> On 4/17/07, *Pankaj Jairath* > >>>> > wrote:
> >>>>
> >>>> Legolas Woodland wrote:
> >>>>
> >>>> > Thank you very much for reply.
> >>>> >
> >>>> > Right now i think i have setup a cluster and a load balancer
> >>>> according
> >>>> > to your very good weblog.
> >>>> > I have sun java web server 7.u1 and latest blassfish installed.
> >>>> > What i want to know is:
> >>>> > I have one DAS, And a web server which according to your
> >>>> weblog will
> >>>> > balance the load between any instance that we add in
> >>>> loadbalancer.xml .
> >>>> >
> >>>> > I have two questions and one problem.
> >>>> >
> >>>> > problem:
> >>>> > I tried several time to create load balancer in glassfish
> >>>> application
> >>>> > server and then apply it to my web server, but it just return
> an
> >>>> error
> >>>> > without any stack trance, error say: Can not connect to server.
> >>>> > My web server and glassfish both works on the same machine, so
> i
> >>>> > tried: 127.0.0.1 < http://127.0.0.1>,
> >>>> localhost and my lan ip address
> >>>> > none of them worked.
> >>>> > the port that i can access my web server administration
> >>>> console is
> >>>> > 8989 and i used this port in HTTP Load Balancers node of
> >>>> glassfish
> >>>> > administration console when i trid to create the load balancer.
> >>>>
> >>>> The communication between DAS and WS/LB is over SSL and the
> >>>> host/port
> >>>> needs to be HTTPS listener of the WebServer Instance and not that
> >>>> of the
> >>>> Admin Server (the Load Balancer is configured to run on the
> >>>> WebServer
> >>>> instance). Given that you have successfully configured the SSL
> >>>> setup
> >>>> between the DAS and WS/LB, check with changing the port to the
> SSL
> >>>> port
> >>>> of the WebServer 7.0 instance.
> >>>>
> >>>> >
> >>>> > IS there anything specific to change in order to make it
> >>>> possible to
> >>>> > apply changes to web server load balancer from glassfish
> >>>> console?
> >>>> >
> >>>> > Now my question:
> >>>> >
> >>>> > -what kind of glassfish i should setup in some other machines
> >>>> to add
> >>>> > them to the cluster? can they be normal domains or there are
> >>>> some
> >>>> > specific ways to create domains to add them to cluster?
> >>>> > can you give me the steps?
> >>>> >
> >>>>
> >>>> You can create multiple server instances and group them under a
> >>>> defined
> >>>> cluster configuration. The cluster or the group of clustered
> >>>> server
> >>>> instances are under a single domain. Domain is the administrative
> >>>> reference - the single point / central repository of carrying
> >>>> out the
> >>>> administrative tasks.
> >>>>
> >>>> You can refer to the documentation that details the setups to
> work
> >>>> with
> >>>> clusters. This is from the /"High Availability Administration
> >>>> Guide"/
> >>>> under chapter 5 : /"Using Application Server Clusters" /:-
> >>>> http://docs.sun.com/app/docs/doc/819-3679/6n5spoggp?a=view
> >>>>
> >>>> Specifically refer to the topic named - /"Working with
> Clusters"./
> >>>>
> >>>> > -I find that we can have several instance in a server? what is
> >>>> > relation of domains with instances? why we should have several
> >>>> > instance in a domain?
> >>>>
> >>>> There can be zero or more server instances in a administrative
> >>>> domain
> >>>> and there can one or more such domains. Each such domain has
> >>>> its own
> >>>> DAS. DAS is actually the designated administrative server
> instance
> >>>> with
> >>>> a default config within a domain.
> >>>>
> >>>> regards
> >>>> Pankaj
> >>>>
> >>>> >
> >>>> >
> >>>> >
> >>>> > Thanks.
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> > On 4/17/07, *Pankaj Jairath* > >>>>
> >>>> > Pankaj.Jairath@sun.com
> >>>> >> wrote:
> >>>> >
> >>>> > Hello Legolas,
> >>>> >
> >>>> > If I understood your question, you are referring to the UI
> >>>> element
> >>>> > "HTTP
> >>>> > Load Balancers" element of the GlassFish V2 Application
> >>>> Server. If so
> >>>> > let me give a brief.
> >>>> >
> >>>> > GlassFish V2 provides the HTTP Load Balancer which can
> >>>> then be
> >>>> > deployed
> >>>> > onto the supported WebServer - for GlassFish V2 it's the
> Sun
> >>>> Java
> >>>> > System
> >>>> > WebServer 6.1 / 7.0. When defining the High Availability
> >>>> deployment
> >>>> > topology of a Java EE deployment, administrator would
> >>>> define a
> >>>> > cluster
> >>>> > of application servers instances and install and
> >>>> configure the
> >>>> > HTTP Load
> >>>> > Balancer to take care of load balancing and failover of
> >>>> the HTTP
> >>>> > requests.
> >>>> > To do this administrative configuration steps, the
> >>>> end-user can
> >>>> > use the
> >>>> > Admin Console (GUI) or the CLI commands to define the
> >>>> cluster, it's
> >>>> > configuration and associate a HTTP Load Balancer with this
> >>>> > configuration. This association defines the cluster
> >>>> configuration and
> >>>> > other Load Balancer configurable parameters, which the
> >>>> HTTP Load
> >>>> > Balancer uses to perform its HA functionality. The
> >>>> administrator
> >>>> > can use
> >>>> > the Admin Console to generate this HTTP Load Balancer
> >>>> > configuration and
> >>>> > even push the configuration over the wire to the deployed
> >>>> HTTP Load
> >>>> > Balancer on a given Sun Java System WebServer.
> >>>> >
> >>>> > Refer to the documents provided earlier for further details
> >>>> on how to
> >>>> > use the Domain Administrative Server (DAS) Admin Console
> >>>> (GUI) or
> >>>> > CLI to
> >>>> > administer the HTTP Load Balancer.
> >>>> >
> >>>> > regards
> >>>> > Pankaj
> >>>> >
> >>>> > legolas wood wrote:
> >>>> >
> >>>> > > Hi
> >>>> > > Thank you for reading my post.
> >>>> > > What is relation of "HTTP Load Balancers" in
> >>>> administration
> >>>> > console
> >>>> > > with using sun java web server as load balancer?
> >>>> > >
> >>>> > > Thanks
> >>>> > >
> >>>> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
[att1.html]

cs194067
Offline
Joined: 2005-09-27