Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

I believe the problem you're seeing is more about RMI than Ehcache

Try

http://stackoverflow.com/questions/10116114/rmi-java-lang-classnotfoundexception-class-name-no-security-manager-rmi-cla

and

http://stackoverflow.com/questions/6322107/java-no-security-manager-rmi-class-loader-disabled

Were you trying to build inside "distribution" folder?

You should be able to build from the root as checked out:

http://svn.terracotta.org/svn/ehcache/tags/ehcache-2.8.3/

distribution module is used to built a fully GA kit, which uses some in-house libraries that's not open to public.

Could you describe your use case a little bit in details?

This log suggests huge values being asked to allocate over and over (around 16MB each time)

2014-02-21 13:27:28,512 [L2_L1:TCWorkerComm # 10_W] WARN com.tc.bytes.TCByteBufferFactory - Asking for a large amount of memory: 15806723 bytes

Could you point to what that might be?

How much memory does the box that runs Terracotta server have? Could you also post the terracotta server log? You might not be using BigMemory but Java NIO library (which TC server uses) does use direct memory
so it's not unusual to see the stack trace with direct buffer memory error.

No you don't need an enterprise license for RMI feature.

This is more of a JBoss EAP deployment issue then. It would be more appropriate to bring it to JBoss forum. Unless someone else has some experience with it to chime in here.

Have you tried the doc?

http://quartz-scheduler.org/api/2.2.0/org/quartz/jobs/ee/ejb/EJB3InvokerJob.html

Open Source Terracotta 3.7, latest version is now 3.7.7 available at http://terracotta.org/downloads/open-source/destination?name=terracotta-3.7.7.tar.gz&bucket=tcdistributions&file=terracotta-3.7.7.tar.gz

Sure. Here's the relevant doc http://quartz-scheduler.org/documentation/quartz-2.2.x/cookbook/ServletInitScheduler

You only need 1 JVM to run your main app with Quartz then configure a number of threads to run your jobs. Each job will run in each own thread.

It depends on your use case. What are you using Quartz for?

Have you tried setting thread context classloader?

Something like this in your OSGI app:

Thread.currentThread().setContextClassLoader(YourClass.class.getClassLoader());

There's also a propose feature to let user register a classloader with a cache instance. It's being evaluated at the moment.

Your root cause is that you're not running BigMemory with a license key.

Caused by: org.terracotta.license.LicenseException: Terracotta license key is required for Enterprise capabilities. Please place terracotta-license.key in Terracotta installed directory or in resource path. You could also specify it through system property -Dcom.tc.productkey.path=/path/to/key
at org.terracotta.license.ehcache.LicenseManager.assertLicenseValid(LicenseManager.java:286)
at net.sf.ehcache.EnterpriseFeaturesManager.<init>(EnterpriseFeaturesManager.java:62)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at net.sf.ehcache.CacheManager.retrieveFeaturesManager(CacheManager.java:2112)

just put the license file in your src/main/resources folder (where log4j.xml or ehcache.xml or other resource files live)

Thank you for your report. You can track the issue or add your own comment here for future release https://jira.terracotta.org/jira/browse/QTZ-404