[JBoss/Spring Integration] - Re: Spring deployer + cluster
by alesj
anonymous wrote : Does the applicationcontext get registred under jndi?
Yes.
This is the code that does it (AbstractBeanFactoryLoader class):
NonSerializableFactory is used, since we don't want to impound Serializability to all of our beans.
| // JNDI stuff
|
| public static void bind(BeanFactory beanFactory, String name) throws BeansException
| {
| InitialContext ctx = null;
| try
| {
| ctx = new InitialContext();
| NonSerializableFactory.rebind(ctx, name, beanFactory);
| }
| catch (NamingException e)
| {
| throw new FatalBeanException("Unable to bind BeanFactory into JNDI", e);
| }
| finally
| {
| if (ctx != null)
| {
| try
| {
| ctx.close();
| }
| catch (Throwable ignored)
| {
| }
| }
| }
| }
|
anonymous wrote : Would it mean that using a cluster jndi I would have a single bean shared through the cluster
Hmm ... never tried it. But you can probably try HAJndi.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994398#3994398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994398
19 years, 4 months
[JBoss/Spring Integration] - EJB3 SLSB from Spring MVC
by leetgeezer
Hello,
I am designing an app using Spring MVC + EJB3. Both Web and EJB modules get packaged into MyApp.ear and deployed into JBoss 4.0.5GA. Currently, to reference the stateless session bean (local if.) from one of the Controllers, I say:
| InitialContext ctx = new InitialContext();
| userService = (UserService) ctx.lookup(
| "MyApp/UserServiceBean/local");
|
What I don't like, however, is that this method relies on "MyApp/UserServiceBean/local" string (What if, say, MyApp name changes?)
My question is: is there any better way (DI?) to reference the stateless session bean locally? I checked Spring's LocalStatelessSessionProxyFactoryBean but it appears that it applies to EJB 2.1 (Home IF's & stuff). Does @EJB or @Resource apply here?
Regards,
Leet Geezer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994397#3994397
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994397
19 years, 4 months
[JBossCache] - Re: Problem with JBoss JDBCCacheLoader
by archanaa_panda
Thanks a lot, Hany. Yes I seem to have goofed up with the cache configuration. The real one is below :)). Sorry about that. I will definitely try your suggestion - this looks to be a very plausible reason for the problem. I will let you know the result in my next post. In the meantime, just take a look at the actual configuration I am posting below and let me know if you find anything else that attracts your attention-
<?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- Sample TreeCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=ArchTreeCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
| <!--
| Configure the TransactionManager
| -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute>
|
| <!--
| Isolation level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <!--
| <attribute name="NodeLockingScheme">OPTIMISTIC</attribute>
| -->
|
| <attribute name="IsolationLevel">READ_COMMITTED</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">REPL_SYNC</attribute>
|
| <!--
| Just used for async repl: use a replication queue
| -->
| <attribute name="UseReplQueue">false</attribute>
|
| <!--
| Replication interval for replication queue (in ms)
| -->
| <attribute name="ReplQueueInterval">0</attribute>
|
| <!--
| Max number of elements which trigger replication
| -->
| <attribute name="ReplQueueMaxElements">0</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">ArchTreeCache-Cluster</attribute>
|
| <!-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| <attribute name="ClusterProperties"></attribute>
| -->
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
| -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true -->
| <UDP mcast_addr="228.1.3.4" mcast_port="48866"
| ip_ttl="64" ip_mcast="true"
| mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
| ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
| loopback="true"/>
| <PING timeout="20000" num_initial_members="3"
| up_thread="false" down_thread="false"/>
| <MERGE2 min_interval="10000" max_interval="20000"/>
| <!-- <FD shun="true" up_thread="true" down_thread="true" />-->
| <FD_SOCK/>
| <VERIFY_SUSPECT timeout="1500"
| up_thread="false" down_thread="false"/>
| <pbcast.NAKACK gc_lag="50" retransmit_timeout="600,1200,2400,4800"
| max_xmit_size="8192" up_thread="false" down_thread="false"/>
| <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10"
| down_thread="false"/>
| <pbcast.STABLE desired_avg_gossip="20000"
| up_thread="false" down_thread="false"/>
| <FRAG frag_size="8192"
| down_thread="false" up_thread="false"/>
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
| shun="true" print_local_addr="true"/>
| <pbcast.STATE_TRANSFER up_thread="true" down_thread="true"/>
| </config>
| </attribute>
|
|
| <!--
| Whether or not to fetch state on joining a cluster
| NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
| -->
| <attribute name="FetchInMemoryState">true</attribute>
|
| <!--
| The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">500000</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">200000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">15000</attribute>
|
|
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass"></attribute>
|
| <!--
| Indicate whether to use marshalling or not. Set this to true if you are running under a scoped
| class loader, e.g., inside an application server. Default is "false".
| -->
|
| <attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>true</shared>
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
| <properties>
| cache.jdbc.table.name=jbosscache
| cache.jdbc.table.create=true
| cache.jdbc.table.drop=false
| cache.jdbc.table.primarykey=jbosscache_pk
| cache.jdbc.fqn.column=fqn
| cache.jdbc.fqn.type=varchar(255)
| cache.jdbc.node.column=node
| cache.jdbc.node.type=blob
| cache.jdbc.parent.column=parent
| cache.jdbc.driver=oracle.jdbc.driver.OracleDriver
| cache.jdbc.url=jdbc:oracle:thin:@132.186.106.26:1541:ACRMDEV
| cache.jdbc.user=FASTDEV
| cache.jdbc.password=fastdev123$
| </properties>
| <async>false</async>
| <fetchPersistentState>true</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
| </cacheloader>
| </config>
| </attribute>
| </mbean>
|
|
|
|
| <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
| <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
| <!-- <depends>jboss.cache:service=TreeCache</depends>-->
| <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
| <!-- </mbean>-->
|
|
| </server>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994389#3994389
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994389
19 years, 4 months