[Persistence] - Ehcache as Hibernate Second Level cache configuring problem
by sergey.olifirenko
Hello!
I use JBoss 4.2.2
My problem is following:
I have application packaged as ear. Application has separated class loader configured via *.ear/META-INF/jboss-app.xml.
I use ehcache as second level cache provider. I had to add ehcache lib to JBOSS_HOME/server/default/lib. Because hibernate libs a loaded by parent classloader and can't see ehcache lib inside of ear.
persistence.xml is correctly configured with following props:
property name="hibernate.cache.use_second_level_cache" value = "true"
property name="hibernate.cache.use_query_cache" value="true"
property name="hibernate.cache.provider_class"
value="org.hibernate.cache.EhCacheProvider"
property name="hibernate.cache.provider_configuration" value="_ehcache.xml"
After such configuration server always runs with following:
10:09:50,800 ERROR [STDERR] Nov 10, 2009 10:09:50 AM net.sf.ehcache.config.Confi
gurationFactory parseConfiguration
WARNING: No configuration found. Configuring ehcache from ehcache-failsafe.xml
found in the classpath: jar:file:/C:/java_Program_Files/jboss-4.2.2.GA/server/de
fault/lib/ehcache-core-1.7.0.jar!/ehcache-failsafe.xml
Hibernate doesn't see my _ehcache.xml.
I've tried put _ehcache.xml in:
ear root.
ear's META-INF, jar's META-INF
I need advise where I can put my ehcache configuration file so Hibernate be able to parse it. Prefferably configuration should be packaged in ear.
Thank you!
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264750#4264750
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264750
16 years, 5 months
[EJB] - EJB Remote Invocation Problem
by catmarch2004
Hi,
I have some issues with EJB remote procedure returning. The target application server is a JBoss App Server. In-explicably, the remote call is unable to locate the class being returned and subsequently throws a ClassNotFoundException. After tracing, it seems that the JBoss remoting mechanism is unable to locate the classes despite the dependencies between each plug-in.
Attempts to resolve this using Buddy Policy (either registered or global) did not work.
In my Eclipse RCP application, I currently have 4 plug-ins
n plug-in A (where the EJB interfaces are stored)
n plug-in B (where the classes being returned by interfaces in A are stored)
n plug-in C (my RCP main app is stored)
n plug-in D (the plugin containing the code that will call the interfaces in A.)
I have set up the plug-in dependencies so that it works this way:
n plug-in A depends on plug-in B
n plug-in B has no dependency
n plug-in C depends on plug-in D
n plug-in D depends on A
So the dependency chart looks something like C èä D èä A èä B. I have also added to the MANIFEST.MF the packages needed to be exported as well.
I am baffled to why the recommended solutions (dependencies and Buddy-Policy) did not work. I am able to get it to work by changing the ContextClassLoader, but frankly, using that will involve a lot of boiler plate code that makes my eyes bleed. I am posting my problem here to see if I can get this resolved without resorting to the ContextClassLoader hack.
Any advice or solutions will be most appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264748#4264748
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264748
16 years, 5 months
[jBPM Users] - Re: jbpm 4.1 - How to stop these Debug Messages in jboss
by makarandk502
logging.properties in my eclipse project ( same as examples coming with jbpm 4.1) has following contents
can you help me in this regard ?
I have not changed logging.properties as I couldn't see any property having value as DEBUG and it is changed to INFO
I changed following in server/default/conf/jboss-log4j.xml. This is only property which has DEBUG value ( that is also commented )
<!-- category name="org.hibernate.SQL">
</category -->
| handlers= java.util.logging.ConsoleHandler
| redirect.commons.logging = enabled
|
| java.util.logging.ConsoleHandler.level = FINE
| java.util.logging.ConsoleHandler.formatter = org.jbpm.internal.log.LogFormatter
|
| org.jbpm.level=FINE
| # org.jbpm.pvm.internal.tx.level=FINE
| # org.jbpm.pvm.internal.wire.level=FINE
| # org.jbpm.pvm.internal.util.level=FINE
|
| org.hibernate.level=INFO
| org.hibernate.cfg.SettingsFactory.level=SEVERE
| org.hibernate.cfg.HbmBinder.level=SEVERE
| # org.hibernate.SQL.level=FINEST
| # org.hibernate.type.level=FINEST
| # org.hibernate.tool.hbm2ddl.SchemaExport.level=FINEST
| # org.hibernate.transaction.level=FINEST
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264746#4264746
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4264746
16 years, 5 months