Re: [jboss-user] [JBoss Microcontainer] - MemoryFileFactory in jboss-vfs 3.0.0.CR5
by Daniel Bevenius
Daniel Bevenius [http://community.jboss.org/people/beve] replied to the discussion
"MemoryFileFactory in jboss-vfs 3.0.0.CR5"
To view the discussion, visit: http://community.jboss.org/message/552681#552681
--------------------------------------------------------------
Just wanted to verify my understanding of using the InMemoryClassesDeployer...
The MemoryFileFactory class has been replaced with a InMemoryClassesDeployer which is a deployer targeted at the DESCRIBE stage. What it does is that is mounts a temporary file system (by default in the servers tmp/vfs directory) that other deployments can add things to. In the ESB case, things like a generated servlets class, a wsdl file, and schema files would be added.
So our deployers we would do somethings like this:
VirtualFile inMemRootDir = unit.getAttachment(InMemoryClassesDeployer.DYNAMIC_CLASS_KEY, VirtualFile.class);
VirtualFile wsdlFile = VFS.getChild(inMemRootDir.getPathName() + "/" + serviceInfo.getWSDLFileName());
final String wsdl = generateWsdl();
VFSUtils.writeFile(wsdlFile, wsdl.getBytes());
unit.appendMetaDataLocation(wsdlFile);
Is this the intended usage of the InMemoryClassesDeployer?
Now our deployer do not need to do any clean up in their undeploy methods as this is done by the InMemoryClassesDeployer which will remove the filesystem when the deployment is undeployed.
Regards,
/Daniel
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552681#552681]
Start a new discussion in JBoss Microcontainer at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months
[Performance Tuning] - Jboss starts very slow
by Eugene Kashin
Eugene Kashin [http://community.jboss.org/people/kesson] created the discussion
"Jboss starts very slow"
To view the discussion, visit: http://community.jboss.org/message/552671#552671
--------------------------------------------------------------
Hello all,
I hope I've chosen a right forum for my question. I have an application running on Jboss 4.2.1 GA, with underlying database (Oracle). Each time I start up the Jboss, it updates the DB schema, checking entities, indexes and foreign keys - it's just OK, it has always been so, and usually the whole process of start up takes about one minute. Without any reasonable cause (i.e., without modifying/adding entities), yesterday I tried to start up the Jboss - it took about ten minutes! And the most time was spent on "Updating DB Schema", something like 15-20 sec per table! I thought it is some performance issue with DB, but the previous version of deployment .ear file starts up itself in usual time - about one minute. Once again, there were not much changes in the last deployment, just fixing some bugs in several beans...And, once starting, application works normally in both versions, there are no performance issues. What can affect the start up time so dramatically? I don't like much the idea to start compare source files of current and previous versions, it can be quite nightmare. At least, if no one could explain it, I wonder to know, how can I switch off the database schema updating in Jboss? I've heard something about *hibernate.hbm2ddl.auto* property, but I don't know where it is. It will be pretty decent solution, since I don't make many changes in entities, but to wait 10 minutes for each re-deployment - it's too much for development stage.
I'll appreciate every help/hint/explanation.
Regards,
Eugene
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/552671#552671]
Start a new discussion in Performance Tuning at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 2 months