[JBoss Cache: Core Edition] - Re: on child insert parent, child collection updated in DB b
by bstansberry＠jboss.com
The collection eviction is done via a call to the org.hibernate.cache.access.CollectionRegionAccessStrategy interface's remove(Object) method. The Hibernate/JBC integration implements that by calling JBC's Cache.removeNode(Fqn) method.
Calls to CollectionRegionAccessStrategy.remove() are all made via org.hibernate.action.CollectionAction.evict(). That in turn is called by the execute() method of the various subclasses of CollectionAction.
The PFER call comes via org.hibernate.engine.loading.CollectionLoadContext.addCollectionToCache(...)
Above classes are all in the "core" module of Hibernate Core.
I agree that the fact this only happens under load certainly seems like a big clue. Just not sure what to make of it yet.
I don't have experience with the Bitronix TX Manager, so don't know if it would have the synchronization ordering issue. But if you were seeing that problem I'd think you'd have other issues less subtle than this one.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214697#4214697
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214697
17 years, 1 month
[EJB/JBoss] - EJB3 Timer and AS restart
by abafna
Hi,
I have a set of scheduled task in my application that fire off based on EJB3 timers at defined interval. Timing for scheduled tasks goes haywire after server restart as if current state is not stored.
The timers expire as expected until a server restart. On server restart, timers are recreated and they expire immediately since initial date/time is in the past instead of expiring at next time out. From this point onwards timers expire after interval duration milliseconds have passed i.e. after interval millisecond duration since last server restart and timer recreation.
I am using JBoss 4.2.2.GA
Anyone else faced this problem?
Is there any configuration that can be changed to store the timer state such that timers expire only at next time out and not immediately?
Or, is this expected behavior? If so, it sounds like a bug.
Thanks
Amit
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214687#4214687
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214687
17 years, 1 month
[JBoss AOP] - Re: Wherefore art thou, DOCTYPE?
by cdmunoz
Hi,
I'm trying to do a deploy on Jboss 5.0.0.GA and I'm getting the next error message:
| 15:23:46,694 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/jboss-5.0.0.GA/server/default/deploy/felectronico.ear state=Not Installed mode=Manual requiredState=Parse
| org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/C:/jboss-5.0.0.GA/server/default/deploy/felectronico.ear/felectronico.war
| at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
| at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1210)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
| at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
| at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
| at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
| at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:545)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
| at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
| at org.jboss.Main.boot(Main.java:209)
| at org.jboss.Main$1.run(Main.java:547)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to parse schema for nsURI=, baseURI=null, schemaLocation=http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199)
| at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:239)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:330)
| ... 23 more
|
I'm using in my jboss-aop.xml file placed in WEB-INF directory, this:
| <!DOCTYPE aop PUBLIC
| "-//JBoss//DTD JBOSS AOP 1.0//EN"
| "http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd">
|
just like you say, but I'm still getting that error.
What can I do right now?
Thanks a lot,
C.D
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214684#4214684
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214684
17 years, 1 month
[Beginners Corner] - Problem starting Jboss
by pranav.r.parikh＠gmail.com
Hi,
I've used JBoss on Linux but not on Windows. I downloaded the JBoss-4.2.3.GA version on Windows XP. Set up the environment variables but JBoss is not getting started. My environment variables are as follows:
CLASSPATH = .;C:\Java\jdk1.6.0_12\lib\tools.jar;C:\jboss-4.2.3.GA\bin\run.jar;
JAVA_HOME = .;C:\Java\jdk1.6.0_12;
JBOSS_HOME = C:\jboss-4.2.3.GA;
PATH =.;C:\Java\jdk1.6.0_12\bin;C:\jboss-4.2.3.GA\bin;
When I click on run.bat or run it from the command prompt, I dont get any output. I checked that the script stops at this point.
rem Add -server to the JVM options, if supported
"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
if not errorlevel == 1 (set JAVA_OPTS=%JAVA_OPTS% -server)
I'm not sure what exactly the problem is. Please let me know if anyone has encountered such problem before. Is there anything wrong with the "findstr"?
I appreciate inputs.
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214682#4214682
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214682
17 years, 1 month
[JBoss Cache: Core Edition] - Re: on child insert parent, child collection updated in DB b
by dukehoops
Brian,
Firstly, thanks for your prompt replies.
I am using Bitronix TX Manager.
It is now pretty obvious that User.userSessions collection node is NOT getting evicted from cache when login() Session flushes or tx commits. If your read is that Hibernate code should be evicting this collection node, then that's where the problem is.
Could you please reference class/method where that decision (to evict) is being made? I will step through.
I wonder whether the fact that the collection node is created and should be evicted in the same Hibernate Session is relevant (and is source of the problem). Recall that login() essentially does this:
//check if user's already logged in
begin
session.open()
usr.getSessions().isEmpty() //AFAIK this populates cache with collection node with 0 elements
//insert new element into collection
usr.addSession(new UserSession()); //guess nothing is happening in cache here
//flush session
session.flush(); //as you say user.userSessions node should be evicted (but is NOT)
commit
Hmm....
Also, let's say the above is the problem. Why isn't this ever happening when only 1 user is involved, but happens for a random subset of users under load. If work on a given user is done by a distinct thread and there are no worker threads involved, why the different results? Perhaps something somewhere is forgetting to clear some ThreadLocal (HTTP threads are pooled by tomcat)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214675#4214675
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214675
17 years, 1 month