Terracotta Discussion Forums

Hi ,

We would suggest usage of Terracotta distributed cache, it is much efficient and easier to use. Here is the link for your reference :

http://ehcache.org/documentation/get-started/about-distributed-cache

Good to know that it is resolved.

can you please share your your ehcache.xml and tc-config.xml. Are you running the Terracotta client and server on same machine.

Good to know that issue is resolved.

As if now , these are the only artefacts available for reference.

yes it's available in open source too.

Not sure , cause it's working for me , can you please try with this tc-config :

<tc:tc-config xmlns:tc="http://www.terracotta.org/config"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.terracotta.org/schema/terracotta-6.xsd">

<system>
<configuration-model>production</configuration-model>
</system>
<servers>
<server host="XXX.XXX.XXX.XXX" name="MyWorkLife Test">
<data>%(user.home)/terracotta2/server2-data</data>
<logs>%(user.home)/terracotta2/server2-logs</logs>

<index>%(user.home)/terracotta2/server2-index</index>
<statistics>%(user.home)/terracotta2/server-statistics</statistics>
<dso-port>9510</dso-port>
<jmx-port>9520</jmx-port>

<dso>
<client-reconnect-window>120</client-reconnect-window>
<persistence>
<mode>permanent-store</mode>
</persistence>
<garbage-collection>
<enabled>true</enabled>
<verbose>false</verbose>
<interval>3600</interval>
</garbage-collection>
</dso>
</server>
<update-check>
<enabled>false</enabled>
</update-check>
</servers>
<clients>
<logs>logs-%i</logs>
</clients>

</tc:tc-config>

Please don't post same issue in forum with new topics , this has already been answered here :

http://forums.terracotta.org/forums/posts/list/8226.page#39239%3Cbr%3E

We would suggest you to go for distributed ehcache , here's the link for it :

http://ehcache.org/documentation/get-started/about-distributed-cache

also yes we do have toolkits available for use , please refer to following link for more details :

http://terracotta.org/documentation/bigmemorymax/terracotta-toolkit/toolkit-intro

Can you send more details :

1) Server/client complete logs from time of issue
2) What is the use case, which caches are having problems (name).

You can make use of org.quartz.listeners.JobChainingJobListener for this , here are more details on this :

http://quartz-scheduler.org/documentation/faq#FAQ-chain

If I am getting you right then you are running a application (terracotta client) and terracotta server on say box A and then you are remotely monitoring it using dev-console from Box b. Here you can't see My application, but if this is the case it should not happen cause in this case also "My application" should appear in sidebar. Please let me know if we differ in understanding your issue.

Can you share your config which you were using earlier, with which you had aggregator issue.

We would suggest you to go for terracotta distributed caching which is much more efficient and easy to use , here's the link for more details :

http://ehcache.org/documentation/get-started/about-distributed-cache

Please don't spam forums.