How to deploy EAR on a JBOSS 5.0 Beta4-cluster

[gitu]

This is a very basic question.

Am learning to deploy an EAR on Jboss 5.0 beta4 cluster.
1. Have created a cluster setup by creating two profile (node_1 and node_2 .copied configurations from all)
2. My expection is that there is a central repository where we can drop ear and it would be pushed to all cluster nodes.
3. I have started node_1 , node_2 and all profile.

Now where is this central reporsitory where I can copy ear which will be pushed to all nodes ?
Have tried copying the ear at \server\all\deploy or \server\all\cluster\
but this isnt working as cluster.

4. Also tried by copying deployers/profileservice-beans.xml.bak to deployers/profileservice-beans.xml for node_1 , node_2 and all profile. Now starting profiles gives me this exception

[ClusterConnectionManager] Failed to start connection info
java.lang.NullPointerException
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:87)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
at org.jboss.jms.client.delegate.ClientConnectionDelegate.start(ClientConnectionDelegate.java)
at org.jboss.jms.client.JBossConnection.start(JBossConnection.java:121)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.start(ClusterConnectionManager.java:664)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.ensureAllConnectionsCreated(ClusterConnectionManager.java:426)
at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:247)
at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.putReplicantLocally(MessagingPostOffice.java:1167)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.put(MessagingPostOffice.java:1420)
at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.registerConnectionFactory(ConnectionFactoryJNDIMapper.java:240)
at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:201)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)

[brian.stansberry]

You're looking for an equivalent to the AS 4 farm directory, which doesn't exist in AS 5. I didn't plan to restore it, but enough people are asking for it that I'm reconsidering that decision.

[gitu]

Ok .. But the doc says.

The Farm Service is removed. Distributed deployments will eventually be handled by the AS 5 Profile Service, with the Profile Service (or JBoss ON) coordinating deployments across the cluster from a centralized repository. The Farm Service's function of replicating deployment archives between file systems will not be maintained.

This means there is plan to use AS5 profile service to deploy from a centralized repository without using farm service.