Instead of
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
p.put(Context.URL_PKG_PREFIXES, jboss.naming:org.jnp.interfaces);
p.put(Context.PROVIDER_URL, localhost:1100); // HA-JNDI
// port
am sorry , its working perfectly fine. i had screwed up with the partition name
in the second partition :)
thanks a lot!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4087789#4087789
Reply to the post :
Yes, they can be in separate partitions. But, your client on node 1 will not
be able to query it's own HA-JNDI to find the EJB, because its HA-JNDI will not
have visibility to 2/3/4.
Simplest way to deal with this is to pass environment properties to your
InitialContext to tell it how to find
here is how i setup the cluster itself
i added the ip's of the other machines to the initial_hosts list in the
cluster-service.xml of that machine. Is tat all ?
TCPPING initial_hosts=10.1.30.201[7800] port_range=3
timeout=3000
Correct.
Note that none of this changes my response to your first question. If you want
to take the EJB on 2, 3 or 4 out of the cluster, you need to either undeploy it
on that node or shut down that node.
View the original post :
thanks alot, i will check mping.
with mping i wont have to have the ips of the other machines in the service and
hajndi wud work across the nodes in the cluster? that is the machines with the
ejb deployed will be clustered for the service automaticallly ?
View the original post :
one last question , in my setup i mentioned in the first post i want the
servers 2,3 and 4 to have a different partition name and 1 (central server
which routes the requests to 2,3,4) to have a different partition name. is this
possible ? or will this result in the lookup failing ?
View the
ohhh the elements are not shown properly again.
true
org.hibernate.cache.TreeCacheProvider
true
true
true
false
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061405#4061405
Reply to the post :
true
org.hibernate.cache.TreeCacheProvider
true
true
true
false
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061406#4061406
Reply to the post :
Looks like the hibernate config properties are not shown up propertly on above
post. Here are they:
true
org.hibernate.cache.TreeCacheProvider
true
true
true
false
Thanks,
Bhakta
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061403#4061403
Reply to the
Use the [ code ] button.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061412#4061412
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4061412
___
jboss-user mailing list
Here is the treecache.xml
=
?xml version=1.0 encoding=UTF-8 ?
| server
| classpath codebase=./lib archives=jboss-cache.jar, jgroups.jar /
|
| mbean code=org.jboss.cache.TreeCache
name=jboss.cache:service=TreeCache
| dependsjboss:service=Naming/depends
|
Here is the cluster-service.xml
?xml version=1.0 encoding=UTF-8?
|
| !-- =
--
| !--
--
| !-- Clustering Service Configuration
Here is the hibernate config file
=
| ?xml version='1.0' encoding='UTF-8'?
| !DOCTYPE hibernate-configuration PUBLIC
| -//Hibernate/Hibernate Configuration DTD 3.0//EN
|
http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd;
|
Here is farm-service.xml
?xml version=1.0 encoding=UTF-8?
!-- = --
!-- --
!-- Farming Service Configuration
No the problem is with farming deployment: I could able to resolve the previous
error by making element to in treecache.xml.
New Trace trace is
[ServiceConfigurator] Problem configuring service
jboss:service=FarmMember,partition=MyPartition
| java.lang.IllegalArgumentException:
Please help me out where am I going wrong with FARMING DEPLOYMENT in JBOSS with
the above environment.
Thanks in advance,
Bhakta
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4061502#4061502
Reply to the post :
mo on tht... i have managed to get the two nodes to get connected bt my problem
is tht when one fails the appl. is not automatically run on the other one. i
need to start up the appl. server again for it to happen. any thoughts or
xplanation on this?
View the original post :
if you deploy your packed application into the deploy/farm directory it will be
deployed on all clustermembers.
you have to deploy into an running aplication server - hotdeploy
so as soon as the second members will be av. the appl. will be deployed also to
him.
19 matches
Mail list logo
