Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Alex Kozlenkov wrote:

Starting an application four times in a row exhausts the maximum number of connections for the evaluation copy and stops until I restart the server--perhaps there is another reason for this behaviour.

Correct, if you start four instances of your application each one will consume a connection.

The trial version is limited to four simultaneous connections. If one of your applications stops (the VM must terminate) the connection should be made available again.

We are more than willing to help you out -- if you need a trial license that supports more than four connections you can get in touch with us at sales@terracottatech.com.

Taylor

This raises two questions.
(a) How do we clean up the shared objects?
(b) The evaluation version is then really restrictive as even non-concurrent sequential runs against a shared object seem to count.
Thanks, Alex

Alex Kozlenkov wrote:

This raises two questions.
(a) How do we clean up the shared objects?

You should not be accumulating objects in your shared datastructures unless you are explicitly intending to do so.

For example if you are using a queue, when you add an object to the queue the queue will hold that object. If your application quits that object will still be in the queue. When your application performs a take() the object will no longer be in the queue and will not live indefinitely (the queue will of course).

It may be that you have shared everything in your app unintentionally. You should only share the objects which need to be shared. We generally show a picture of an application running with Terracotta that has a small subset of shared objects and the rest of the heap is local to the VM.

Another alternative is that you can call clear() on any collection that you want to clear out - but that usage would be application specific.

In general I think it is probably best for us to engage over a different medium than these support forums. I believe you mentioned that some TC representatives are already engaged with your organization. You could also send an email to me at tgautier@terracottatech.com or sales@terracottatech.com and we can setup a phone call to go over these issues.

(b) The evaluation version is then really restrictive as even non-concurrent sequential runs against a shared object seem to count.
Thanks, Alex

The evaluation version allows 4 simultaneous connections. If you run an application, and then stop it, another application can connect. This can happen indefinitely - the limit is only on the number of simultaneously connected Java VMs.

Alex,

I've posted the Master/Worker pattern and an implementation, a parallel web spider, that uses it.

Read more at http://javathink.blogspot.com/2006/09/lets-go-distributed-how-to-build.html

Taylor

Hi TC team,

I found the toturials very helpful to start using TC solutions for clustering Java Apps.

For this forum readers, I'am posting this link http://www.informit.com/guides/content.asp?g=java&seqNum=264&rl=1
could be useful to get an idea about techniques that TC is using to cluster Java Apps.

Great work TC team, go ahead.

Cheers.

Thanks!

Regards,

Gordon

Taylor wrote:

The trial version is limited to four simultaneous connections.

Is this still true?

Mike

The open source version which is currently functionally the same as the enterprise version has no limitations on connections or server uptime. The only restriction is that if you redistribute it you have to do a form of GUI attribution.

Cheers,
Steve