[Clustering/JBoss] - Hibernate SessionFactory w/ JBossAS Cluster
by aminlalji
Hi,
I am trying to understand the operation of hibernate in a clustered JBoss environment.
Consider the following setup:
2 JBossAS servers (load balanced vis mod_jk2) using Hibernate for persistence w/ JBossCache enabled.
Scenario 1: SERVER1 decides to act upon an object and works with it in cache. The JBossCache notifies all other caches that exist on other cluster nodes of any changes (really just sends invalid/expire notifications). Everything remains in sync... I think. What happens if SERVER2 also concurrently decides to act upon the same object? I assume the isolation level configured in the SessionFactory has a role to play in determining the resultant behaviour (and I assume the isololation levels should also match) to keep things in sync.
The alternative to this scenario is using a "clustered" SessionFactory that is shared by all nodes of the cluster (via JNDI) ... I'm not sure which scenario described above is A) Valid, and B) Best Practice and C) even Possible...
Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013652#4013652
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013652
19Â years, 2Â months
[JBoss/Spring Integration] - Re: Spring AOP Problem
by mwiles
Quite a nasty problem...
I did some digging with the debugger and found that that object which it's saying it can't find interfaces for is a dynamic proxied object. Quite irritating that it doesn't just ignore and carry on.
Not quite sure why it works when running outside of the container though.
Btw, the object which I had the same problem is the SessionFactory object which is proxied by spring/jboss. Not quite sure which.
An efficient to block this object from being scanned by spring's AOP would be great, blocking each individual method is the only way I see it working. I think the spring AOP first resolves the method and then moves on so if the method resolution fails, then it goes onto the next method. Again, why such a problem would cause a complete failure, I don't know.
It would also be interesting to see how spring's AOP/aspectJ behaves with a proxied object.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013650#4013650
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013650
19Â years, 2Â months
[JBossCache] - Re: Endless loop in JBoss Cache 1.4.1.GA
by msteiner
This how I am getting the Loop. I delete root node:
| 15:24:25,709 DEBUG [TxInterceptor] local transaction exists - registering global tx if not present for Thread[pool-1-thread-3,5,jboss]
| 15:24:25,715 DEBUG [TxInterceptor] local transaction exists - registering global tx if not present for Thread[pool-1-thread-3,5,jboss]
| 15:24:25,716 DEBUG [TxInterceptor] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=p_1.dom.pl/21, BranchQual=, localId=21] is already registered.
| 15:24:25,717 DEBUG [TxInterceptor] Running commit phase. One phase? true
| 15:24:25,717 DEBUG [TxInterceptor] Finished local commit/rollback method for GlobalTransaction:<192.168.24.106:34109>:2
| 15:24:25,717 DEBUG [TxInterceptor] Finished commit phase
| 15:24:25,740 DEBUG [BaseEvictionAlgorithm] processRemoveNodes(): Can't find node associated with fqn: /Could have been evicted earlier. Will just continue.
|
Look at: Running commit phase
Now I dont have any nodes in cache (as CacheMgmt mbean says). I put node in the cache:
| 15:26:22,976 DEBUG [TxInterceptor] local transaction exists - registering global tx if not present for Thread[pool-1-thread-5,5,jboss]
| 15:26:22,994 DEBUG [TxInterceptor] local transaction exists - registering global tx if not present for Thread[pool-1-thread-5,5,jboss]
| 15:26:22,994 DEBUG [TxInterceptor] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=p_1.dom.pl/24, BranchQual=, localId=24] is already registered.
|
Uuups , loop started...
After a while:
| 15:31:23,069 WARN [TransactionImpl] Transaction TransactionImpl:XidImpl[FormatId=257, GlobalId=programista_1.gdynia.4drivers.pl/24, BranchQual=, localId=24] timed out. status=STATUS_ACTIVE
|
Secend transaction timeouted.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013646#4013646
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013646
19Â years, 2Â months
[Tomcat, HTTPD, Servlets & JSP] - problem with JSF 1.2 on JBoss5Beta
by sedat
Hello,
I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception.
The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema.
The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception:
org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed!
at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94)
at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173)
at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114)
at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88)
at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59)
at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52)
at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145)
at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440)
at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246)
at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
at org.jboss.Main.boot(Main.java:210)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
Note that JBoss5Ex.war is my web application. What can be the problem? Any suggestions?
Thanks,
Sedat
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013644#4013644
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4013644
19Â years, 2Â months