Nabble - tc-users

Terracotta Master Worker + Guice

2009-10-30T15:43:41Z

Greetings,

I have been trying to get a Terracotta Master Worker project going with Guice but I seem to have run into a problem with Guice's Provider class. Every time I try to inject a class with a Provider i.e

@Inject
public void MyAppService(Provider<DAOService> daoProvider)
{
...
}

I am getting a class not found exception on the class that is bound as the provider, even if I instrument the class explicitly.

In terms of code I have the following

----- Provider ------
public class DAOServiceProvider implements Provider<DAOService>
{
public DAOService get()
{
return new DAOServiceImpl();
}
}

---- Master -------

public class WorkMaster
{
public void run()
{
Injector injector = Guice.createInjector(new AbstractModule() {

            @Override
         protected void configure()
            {

               bind(DAOService.class).toProvider(DAOServiceProvider.class);
            }
        });

Work work = injector.getInstance(Work.class);
}
}

---- Worker ----

public class Work implements Callable<int>
{
private Provider<DAOService> serviceProvider;

@Inject
public Work(Provider<DAOService> serviceProvider)
{
this.serviceProvider = serviceProvider;
}

public int call() throws Exception
{
return serviceProvider.get().getUserCount();
}
}

---- tc-config.xml -----

<?xml version="1.0" encoding="UTF-8"?>
<con:tc-config xmlns:con="http://www.terracotta.org/config">
<servers>
<server host="%i" name="localhost">
<dso-port>9510</dso-port>
<jmx-port>9520</jmx-port>
<data>terracotta/server-data</data>
<logs>terracotta/server-logs</logs>
<statistics>terracotta/cluster-statistics</statistics>
</server>
</servers>
<clients>
<logs>terracotta/client-logs</logs>
<modules>
<module name="tim-masterworker" version="2.1.1" />
<module name="tim-guice-1.0" version="1.2.1" />
</modules>
</clients>
<application>
<dso>
<instrumented-classes>
<include>
<class-expression>com.magpieti.terraguice.*</class-expression>
</include>
<include>
                    <class-expression>c com.magpieti.terraguice.DAOServiceProvider$$FastClassByGuice</class-expression>
                </include>
<include>
<class-expression>com.google.inject.*</class-expression>
</include>
</instrumented-classes>
<additional-boot-jar-classes>
<include>sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl</include>
<include>sun.reflect.annotation.AnnotationInvocationHandler</include>
<include>sun.reflect.generics.repository.ConstructorRepository</include>
<include>sun.reflect.generics.factory.CoreReflectionFactory</include>
<include>sun.reflect.generics.tree.MethodTypeSignature</include>
<include>sun.reflect.generics.scope.ConstructorScope</include>
<include>sun.reflect.generics.tree.ClassTypeSignature</include>
<include>sun.reflect.generics.tree.VoidDescriptor</include>
<include>sun.reflect.generics.tree.SimpleClassTypeSignature</include>
</additional-boot-jar-classes>
</dso>
</application>
</con:tc-config>

Currently, when the "serviceProvider.get().getUserCount()' is executed I get the following stack trace

com.tc.exception.TCClassNotFoundException: java.lang.ClassNotFoundException: com.magpieti.terraguice.DAOServiceProvider $$FastClassByGuice$$4081c943
at com.tc.object.TCObjectPhysical.resolveReference(TCObjectPhysical.java:151)
at com.google.inject.cglib.reflect.FastMember.__tc_getfc(FastMember.java)
at com.google.inject.cglib.reflect.FastConstructor.newInstance(FastConstructor.java:40)
at com.google.inject.DefaultConstructionProxyFactory$2.newInstance(DefaultConstructionProxyFactory.java:67)
at com.google.inject.ConstructorInjector.construct(ConstructorInjector.java:142)
at com.google.inject.InjectorImpl$ImplicitBinding.get(InjectorImpl.java:1006)
at com.google.inject.BoundProviderFactory.get(BoundProviderFactory.java:60)
at com.google.inject.InjectorImpl$9$1.call(InjectorImpl.java:708)
at com.google.inject.InjectorImpl.callInContext(InjectorImpl.java:747)
at com.google.inject.InjectorImpl$9.get(InjectorImpl.java:702)
at com.magpieti.terraguice.Work.call(SimpleWork.java:24)
at com.magpieti.terraguice.Work.call(SimpleWork.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:270)
at java.util.concurrent.FutureTask.run(FutureTask.java:55)
at org.terracotta.executor.support.DefaultDistributedWork.run(DefaultDistributedWork.java:25)
at org.terracotta.executor.DistributedWorkerService.doExecute(DistributedWorkerService.java:92)
at org.terracotta.masterworker.AbstractWorker$WorkPipeListener$1.run(AbstractWorker.java:131)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:270)
at java.util.concurrent.FutureTask.run(FutureTask.java:55)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.ClassNotFoundException: com.magpieti.terraguice.DAOServiceProvider$$FastClassByGuice$$4081c943
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at sun.misc.Launcher$AppClassLoader.findClass(Launcher.java)
at java.lang.ClassLoader.loadClass(ClassLoader.java:319)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330)
at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:399)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.tc.object.loaders.StandardClassProvider.getClassFor(StandardClassProvider.java:88)
at com.tc.object.ClientObjectManagerImpl.lookup(ClientObjectManagerImpl.java:539)
at com.tc.object.ClientObjectManagerImpl.lookupObject(ClientObjectManagerImpl.java:442)
at com.tc.object.ClientObjectManagerImpl.lookupObject(ClientObjectManagerImpl.java:430)
at com.tc.object.TCObjectPhysical.resolveReference(TCObjectPhysical.java:149)
... 22 more

Is it immediately obvious anyone why this would be a problem? Why is the Terracotta class loader unable to find this particular class?

As a side note, if I inject the class that the Provider is providing instead of the whole provider it seems to work.

Thanks,
Adam

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: welcome script not available

2009-09-23T19:10:34Z

Ah yes, that worked perfectly! I had watched the screencasts, but they all started from the welcome app. Thanks for pointing this out.

On Wed, Sep 23, 2009 at 9:58 PM, Gary Keim <gkeim@...> wrote:

Steve was referring to tools/pojo/samples{sh,bat}.

From: tc-users-bounces@... [mailto:tc-users-bounces@...] On Behalf Of Dominick Accattato
Sent: Wednesday, September 23, 2009 6:57 PM
To: tc-users@...
Subject: Re: [tc-users] welcome script not available

@Alex, Thanks for clearing that up, but wouldn't a welcome app still be useful even for the integration products?

@Steven, are you referring to the "start-demo-server.sh" that's located in [TC_HOME]/samples ?

On Wed, Sep 23, 2009 at 9:45 PM, Steven Harris <steve@...> wrote:

The sample launcher still exists if that's the part you need.

Cheers,

Steve

On Sep 23, 2009, at 6:10 PM, Alex Miller <amiller@...> wrote:

Yes, the welcome scripts were removed to reflect a new focus on our integration products like sessions, Hibernate second level cache, and (soon) Ehcache.

On Sep 23, 2009, at 6:08 PM, Dominick Accattato wrote:

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums

read the text files that accompany the download

checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).

searched the wiki

tried searching the mailing list

google search

That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4451 (20090923) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: welcome script not available

2009-09-23T18:58:43Z

Steve was referring to tools/pojo/samples{sh,bat}.

From: tc-users-bounces@... [mailto:tc-users-bounces@...] On Behalf Of Dominick Accattato
Sent: Wednesday, September 23, 2009 6:57 PM
To: tc-users@...
Subject: Re: [tc-users] welcome script not available

@Alex, Thanks for clearing that up, but wouldn't a welcome app still be useful even for the integration products?

@Steven, are you referring to the "start-demo-server.sh" that's located in [TC_HOME]/samples ?

On Wed, Sep 23, 2009 at 9:45 PM, Steven Harris <steve@...> wrote:

The sample launcher still exists if that's the part you need.

Cheers,

Steve

On Sep 23, 2009, at 6:10 PM, Alex Miller <amiller@...> wrote:

Yes, the welcome scripts were removed to reflect a new focus on our integration products like sessions, Hibernate second level cache, and (soon) Ehcache.

On Sep 23, 2009, at 6:08 PM, Dominick Accattato wrote:

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums

read the text files that accompany the download

checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).

searched the wiki

tried searching the mailing list

google search

That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4451 (20090923) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: welcome script not available

2009-09-23T18:56:33Z

On Wed, Sep 23, 2009 at 9:45 PM, Steven Harris <steve@...> wrote:

The sample launcher still exists if that's the part you need.

Cheers,
Steve

On Sep 23, 2009, at 6:10 PM, Alex Miller <amiller@...> wrote:

Yes, the welcome scripts were removed to reflect a new focus on our integration products like sessions, Hibernate second level cache, and (soon) Ehcache.

On Sep 23, 2009, at 6:08 PM, Dominick Accattato wrote:

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums
read the text files that accompany the download
checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).

searched the wiki
tried searching the mailing list
google search
That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!
_______________________________________________
tc-users mailing list
tc-users@...tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: welcome script not available

2009-09-23T18:45:57Z

The sample launcher still exists if that's the part you need.

Cheers,

Steve

On Sep 23, 2009, at 6:10 PM, Alex Miller <amiller@...> wrote:

Yes, the welcome scripts were removed to reflect a new focus on our integration products like sessions, Hibernate second level cache, and (soon) Ehcache.

On Sep 23, 2009, at 6:08 PM, Dominick Accattato wrote:

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums
read the text files that accompany the download
checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).

searched the wiki
tried searching the mailing list
google search
That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: welcome script not available

2009-09-23T18:10:47Z

Yes, the welcome scripts were removed to reflect a new focus on our integration products like sessions, Hibernate second level cache, and (soon) Ehcache.

On Sep 23, 2009, at 6:08 PM, Dominick Accattato wrote:

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums
read the text files that accompany the download
checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).

searched the wiki
tried searching the mailing list
google search
That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

welcome script not available

2009-09-23T18:08:58Z

Hi,

I just downloaded the latest tar release of Terracotta ES 3.1.0 here (http://www.terracotta.org/web/display/orgsite/DownloadCatalog). It downloaded and unpacked fine, however I do not see the welcome.sh script in any of the directories including the bin. Here are other places I've searched to find more information:

I've searched the forums
read the text files that accompany the download
checked the release_notes (http://www.terracotta.org/web/display/docs/Release+Notes).
searched the wiki
tried searching the mailing list
google search

That said, I am able to run the samples individually from the command line. However, I was wondering if that welcome script has been removed. If so, why? Thanks in advance for any information you can shed on the subject... and thanks for all the hard work!

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: error using masterworker tim - 2.1.0 in multiple war project

2009-09-16T01:07:19Z

Hi Artie.

> i am having an issue using tim-masterworker 2.1.0 with tc 3.1 and having
> multiple wars. I currently have one war as the master and another war as
> the worker. The master loads fine but when i try to load the worker i get
> this error:
>
> Caused by: java.lang.ClassCastException:

If you're sharing the same terracotta root (the topology instance)
between different web applications (the master and the worker), you
have to enable such a behavior in your terracotta configuration, just
take a look here:

http://www.terracotta.org/web/display/docs/Configuration+Guide+and+Reference#ConfigurationGuideandReference-appgroups

> when they are in the same tomcat instance and this error:
>
> com.tc.exception.TCClassNotFoundException: java.lang.ClassNotFoundException:
> No registered loader for description: %%Tomcat.Catalina:localhost:/master,
> trying to load org.terracotta.message.topology.TopologyManager

Did you install the terracotta integration module for Tomcat?
Just issue the following command from inside the terracotta bin directory:

$ sh tim-get.sh install tim-tomcat-6.0

> is the intent to have one war with both the master and work in it then push
> that war to all the servers?

There's no restriction on your deployment type: you can deploy one war
containing the master + another war for the worker, as well as a
single war containing both master and worker.
You just have to properly configure your application by following the
instructions above.

Let us know.
Cheers,

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

error using masterworker tim - 2.1.0 in multiple war project

2009-09-15T14:03:56Z

i am having an issue using tim-masterworker 2.1.0 with tc 3.1 and
having multiple wars. I currently have one war as the master and
another war as the worker. The master loads fine but when i try to
load the worker i get this error:

Caused by: java.lang.ClassCastException: The field 'instance' with
root name 'org.terracotta.message.topology.TopologyManager.instance'
cannot be assigned to a variable of type org/terracotta/message/
topology/TopologyManager. This root has a type
org.terracotta.message.topology.TopologyManager. Perhaps you have the
same root name assigned more than once to variables of different types.
at org.terracotta.message.topology.TopologyManager.__tc_setinstance
(TopologyManager.java)
at org.terracotta.message.topology.TopologyManager.<clinit>
(TopologyManager.java:29)
... 52 more

when they are in the same tomcat instance and this error:

com.tc.exception.TCClassNotFoundException:
java.lang.ClassNotFoundException: No registered loader for
description: %%Tomcat.Catalina:localhost:/master, trying to load
org.terracotta.message.topology.TopologyManager

then they are in different tomcat instances.

is the intent to have one war with both the master and work in it then
push that war to all the servers? i did notice that there were a few
master object roots. is that normal?

please help

thanx

artie
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-09-04T07:52:10Z

On Thu, Sep 3, 2009 at 3:57 AM, Taylor
Gautier<tgautier@...> wrote:

> Sounds great. Just make sure on the serialization part - what you are
> trying to optimize is the object count in Terracotta. So a simple test
> would be to run say 10,000 objects through TC and observe the object created
> count in the console and make sure it is constant.

It works just like that, now: live objects count is kept constant.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: New features for next Tim-Messaging releases

2009-09-02T18:57:29Z

Sounds great. Just make sure on the serialization part - what you are trying to optimize is the object count in Terracotta. So a simple test would be to run say 10,000 objects through TC and observe the object created count in the console and make sure it is constant.

Anything else indicates clustered objects (wrappers etc) that you must optimize out because the entire point is to ensure that message puts do not add to the object count.

----- Original Message -----
From: "Sergio Bossa" <sergio.bossa@...>
To: "tc-forge-dev" <tc-forge-dev@...>, "tc-users" <tc-users@...>
Sent: Tuesday, September 1, 2009 3:11:59 AM GMT -08:00 US/Canada Pacific
Subject: Re: [tc-users] New features for next Tim-Messaging releases

Hi guys,

first of all: thanks everyone for your feedback!

FYI, I've planned the following new features for the next release,
which I'd like to cut in a few weeks:

https://jira.terracotta.org/jira/browse/FORGE-549 (message
serialization support)
https://jira.terracotta.org/jira/browse/FORGE-548 (selective consumer support)
https://jira.terracotta.org/jira/browse/FORGE-518 (message expiration support)

I'm currently working on message serialization, which is almost
finished and supports Java Serialization, Json, XML and GoogleProtoBuf
encoding.

Feedback is as always welcome.
Cheers,

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: New features for next Tim-Messaging releases

2009-09-01T03:11:59Z

Hi guys,

first of all: thanks everyone for your feedback!

FYI, I've planned the following new features for the next release,
which I'd like to cut in a few weeks:

https://jira.terracotta.org/jira/browse/FORGE-549 (message
serialization support)
https://jira.terracotta.org/jira/browse/FORGE-548 (selective consumer support)
https://jira.terracotta.org/jira/browse/FORGE-518 (message expiration support)

I'm currently working on message serialization, which is almost
finished and supports Java Serialization, Json, XML and GoogleProtoBuf
encoding.

Feedback is as always welcome.
Cheers,

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-25T06:04:09Z

On Mon, Aug 24, 2009 at 4:50 PM, Jason
Voegele<jvoegele@...> wrote:

> I definitely think this could be useful. Would there be some way of mapping a
> work item to the data that it uses in some way?

Isn't that somewhat accomplished by using Terracotta Cluster Events?
Or did I miss your point?

> We have actually built something like this on top of tim-messaging, which we
> use to build and publish artifacts and web sites for the Terracotta Forge
> projects. If you are interested in taking a look you can check out the
> project from here:
>
> https://svn.terracotta.org/repo/forge/projects/DistributedWorkQueue/trunk

Cool, I didn't know that: glad to see terracotta eats its own food :)

> Having a RESTful interface built-in to tim-messaging itself would of course be
> very helpful to build systems such as that.

Agree: it will definitely be in the todo-list.

Thanks for your feedback,
Cheers,

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-24T07:50:29Z

On Friday 14 August 2009 01:04:24 pm Sergio Bossa wrote:
> some time has passed since the latest Tim-Messaging 2.0 release, and
> I'm now starting to think about new features for next releases.
> Here are a few new features I was thinking at:
>
> 1) Given that data-affinity is more and more import, it may be good to
> improve affinity-routing for tim-masterworker.

I definitely think this could be useful. Would there be some way of mapping a
work item to the data that it uses in some way?

> 2) It may be cool to add a json-over-http interface to tim-pipes,
> providing restful access to topologies and pipes.
> 3) It may be even cooler to add a restful interface to
> tim-masterworker, implementing a scalable, fault-tolerant, rest-based
> master/worker server.

We have actually built something like this on top of tim-messaging, which we
use to build and publish artifacts and web sites for the Terracotta Forge
projects. If you are interested in taking a look you can check out the
project from here:

https://svn.terracotta.org/repo/forge/projects/DistributedWorkQueue/trunk

Having a RESTful interface built-in to tim-messaging itself would of course be
very helpful to build systems such as that.

--
Jason Voegele
It is always the best policy to tell the truth, unless, of course,
you are an exceptionally good liar.
-- Jerome K. Jerome
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-24T00:56:40Z

On Sat, Aug 22, 2009 at 4:36 PM, Hung Huynh<hhuynh@...> wrote:

> Is there a way to let a rouge worker timeout if it gets stuck?

Thanks for your input, Hung.
Do you mind making a more detailed description of your use case and
feature request?

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-22T07:36:52Z

Is there a way to let a rouge worker timeout if it gets stuck?

I've scanned the javadocs but couldn't find anything like that.

Sergio Bossa wrote:

> Hi guys,
>
> some time has passed since the latest Tim-Messaging 2.0 release, and
> I'm now starting to think about new features for next releases.
> Here are a few new features I was thinking at:
>
> 1) Given that data-affinity is more and more import, it may be good to
> improve affinity-routing for tim-masterworker.
> 2) It may be cool to add a json-over-http interface to tim-pipes,
> providing restful access to topologies and pipes.
> 3) It may be even cooler to add a restful interface to
> tim-masterworker, implementing a scalable, fault-tolerant, rest-based
> master/worker server.
>
> What do you think?
> Do you have any other particular idea/feature/suggestion?
>
> Thanks,
> Cheers!
>
> Sergio B.
>
>

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-15T09:34:40Z

Strings should be best.

On Aug 15, 2009, at 5:58 AM, Sergio Bossa <sergio.bossa@...>
wrote:

> On Sat, Aug 15, 2009 at 1:58 AM, Taylor
> Gautier<tgautier@...> wrote:
>
>> I would add serialization of messages to the list. Serializing should
>> provide big improvements to throughput and messages behave more like
>> messages and not distributed memory.
>
> That's definitely a great idea: I'll put it on top of my list.
>
> Talking about the serialized object, would it be better (for
> increasing throughput) to serialize and share it in terracotta as a
> string, or as a byte array?
>
> --
> Sergio Bossa
> Software Passionate and Open Source Enthusiast.
> URL: http://www.linkedin.com/in/sergiob

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: New features for next Tim-Messaging releases

2009-08-15T08:54:45Z

RE: [tc-users] New features for next Tim-Messaging releases

Yeah the rest-based interfaces sound real useful. We did something similar with the Authinator for a distributed cache at https://svn.terracotta.org/repo/forge/projects/authinator/trunk

The serialization based framework also sounds real useful.
Cheers

-----Original Message-----
From: tc-users-bounces@... [tc-users-bounces@...] On Behalf Of Sergio Bossa
Sent: Friday, August 14, 2009 10:04 AM
To: tc-forge-dev; tc-users
Subject: [tc-users] New features for next Tim-Messaging releases

Hi guys,

some time has passed since the latest Tim-Messaging 2.0 release, and
I'm now starting to think about new features for next releases.
Here are a few new features I was thinking at:

1) Given that data-affinity is more and more import, it may be good to
improve affinity-routing for tim-masterworker.
2) It may be cool to add a json-over-http interface to tim-pipes,
providing restful access to topologies and pipes.
3) It may be even cooler to add a restful interface to
tim-masterworker, implementing a scalable, fault-tolerant, rest-based
master/worker server.

What do you think?
Do you have any other particular idea/feature/suggestion?

Thanks,
Cheers!

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-15T06:00:31Z

On Fri, Aug 14, 2009 at 7:13 PM, Alex Miller<amiller@...> wrote:

> Sergio, maybe it would be good to put
> these ideas up where people could discuss? Like your blog or our forums.
> I'm sure we could point a little traffic your way somehow.

Thanks Alex.
I'll write a short blog post about it as soon as possible, and let you know.

Cheers,

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-15T05:58:20Z

On Sat, Aug 15, 2009 at 1:58 AM, Taylor
Gautier<tgautier@...> wrote:

> I would add serialization of messages to the list. Serializing should
> provide big improvements to throughput and messages behave more like
> messages and not distributed memory.

That's definitely a great idea: I'll put it on top of my list.

Talking about the serialized object, would it be better (for
increasing throughput) to serialize and share it in terracotta as a
string, or as a byte array?

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-14T17:00:34Z

yeah

2 modes. serialization-based vs. identity-based.

--Ari

On Aug 14, 2009, at 4:58 PM, Taylor Gautier wrote:

> I would add serialization of messages to the list. Serializing
> should provide big improvements to throughput and messages behave
> more like messages and not distributed memory. I think the latter is
> useful of course but I think there's also a use for the former.
>
> On Aug 14, 2009, at 10:13 AM, Alex Miller
> <amiller@...> wrote:
>
>> Those all sound like cool features to me although I have little feel
>> for which of them are actually most in need.
>>
>> I'm cc'ing some folks that might have a better feel on the needs of
>> actual tim-messaging and tim-pipes users. Sergio, maybe it would be
>> good to put these ideas up where people could discuss? Like your
>> blog
>> or our forums. I'm sure we could point a little traffic your way
>> somehow.
>>
>>
>> On Aug 14, 2009, at 12:04 PM, Sergio Bossa wrote:
>>
>>> Hi guys,
>>>
>>> some time has passed since the latest Tim-Messaging 2.0 release, and
>>> I'm now starting to think about new features for next releases.
>>> Here are a few new features I was thinking at:
>>>
>>> 1) Given that data-affinity is more and more import, it may be
>>> good to
>>> improve affinity-routing for tim-masterworker.
>>> 2) It may be cool to add a json-over-http interface to tim-pipes,
>>> providing restful access to topologies and pipes.
>>> 3) It may be even cooler to add a restful interface to
>>> tim-masterworker, implementing a scalable, fault-tolerant, rest-
>>> based
>>> master/worker server.
>>>
>>> What do you think?
>>> Do you have any other particular idea/feature/suggestion?
>>>
>>> Thanks,
>>> Cheers!
>>>
>>> Sergio B.
>>>
>>> --
>>> Sergio Bossa
>>> Software Passionate and Open Source Enthusiast.
>>> URL: http://www.linkedin.com/in/sergiob
>>> _______________________________________________
>>> tc-forge-dev mailing list
>>> tc-forge-dev@...
>>> http://lists.terracotta.org/mailman/listinfo/tc-forge-dev
>>
>> _______________________________________________
>> tc-forge-dev mailing list
>> tc-forge-dev@...
>> http://lists.terracotta.org/mailman/listinfo/tc-forge-dev

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-14T16:58:26Z

I would add serialization of messages to the list. Serializing should
provide big improvements to throughput and messages behave more like
messages and not distributed memory. I think the latter is useful of
course but I think there's also a use for the former.

On Aug 14, 2009, at 10:13 AM, Alex Miller
<amiller@...> wrote:

> Those all sound like cool features to me although I have little feel
> for which of them are actually most in need.
>
> I'm cc'ing some folks that might have a better feel on the needs of
> actual tim-messaging and tim-pipes users. Sergio, maybe it would be
> good to put these ideas up where people could discuss? Like your blog
> or our forums. I'm sure we could point a little traffic your way
> somehow.
>
>
> On Aug 14, 2009, at 12:04 PM, Sergio Bossa wrote:
>
>> Hi guys,
>>
>> some time has passed since the latest Tim-Messaging 2.0 release, and
>> I'm now starting to think about new features for next releases.
>> Here are a few new features I was thinking at:
>>
>> 1) Given that data-affinity is more and more import, it may be good
>> to
>> improve affinity-routing for tim-masterworker.
>> 2) It may be cool to add a json-over-http interface to tim-pipes,
>> providing restful access to topologies and pipes.
>> 3) It may be even cooler to add a restful interface to
>> tim-masterworker, implementing a scalable, fault-tolerant, rest-based
>> master/worker server.
>>
>> What do you think?
>> Do you have any other particular idea/feature/suggestion?
>>
>> Thanks,
>> Cheers!
>>
>> Sergio B.
>>
>> --
>> Sergio Bossa
>> Software Passionate and Open Source Enthusiast.
>> URL: http://www.linkedin.com/in/sergiob
>> _______________________________________________
>> tc-forge-dev mailing list
>> tc-forge-dev@...
>> http://lists.terracotta.org/mailman/listinfo/tc-forge-dev
>
> _______________________________________________
> tc-forge-dev mailing list
> tc-forge-dev@...
> http://lists.terracotta.org/mailman/listinfo/tc-forge-dev

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: [tc-forge-dev] New features for next Tim-Messaging releases

2009-08-14T10:13:55Z

Those all sound like cool features to me although I have little feel
for which of them are actually most in need.

I'm cc'ing some folks that might have a better feel on the needs of
actual tim-messaging and tim-pipes users. Sergio, maybe it would be
good to put these ideas up where people could discuss? Like your blog
or our forums. I'm sure we could point a little traffic your way
somehow.

On Aug 14, 2009, at 12:04 PM, Sergio Bossa wrote:

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

New features for next Tim-Messaging releases

2009-08-14T10:04:24Z

Hi guys,

some time has passed since the latest Tim-Messaging 2.0 release, and
I'm now starting to think about new features for next releases.
Here are a few new features I was thinking at:

1) Given that data-affinity is more and more import, it may be good to
improve affinity-routing for tim-masterworker.
2) It may be cool to add a json-over-http interface to tim-pipes,
providing restful access to topologies and pipes.
3) It may be even cooler to add a restful interface to
tim-masterworker, implementing a scalable, fault-tolerant, rest-based
master/worker server.

What do you think?
Do you have any other particular idea/feature/suggestion?

Thanks,
Cheers!

Sergio B.

--
Sergio Bossa
Software Passionate and Open Source Enthusiast.
URL: http://www.linkedin.com/in/sergiob
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Changes in some common TIMs for 3.1

2009-07-15T15:19:13Z

As a part of our upcoming 3.1 release, I wanted to mention that we
have renamed a bunch of TIMs on the Terracotta Forge. We'll be
talking more about these in the release notes and in the docs when 3.1
comes out but consider this a preview if you're on the bleeding edge.

tim-concurrent-collections
====================

This TIM is basically a holder for the ConcurrentStringMap we've had
since 2.7.2 or so. This data structure continues to be a key focus
for us as the cornerstone of map-based components and has been
substantially updated in 3.1 to improve performance, reduce memory,
and make it more generic. In particular, this data structure is no
longer limited to String keys.

The new and improved version has been renamed and put in a new package:
org.terracotta.collections.ConcurrentDistributedMap

The prior class
(org.terracotta.modules.concurrent.collections.ConcurrentStringMap)
still exists and is just a shell subclassing
ConcurrentDistributedMap. This class will still exist in 3.1 but is
now deprecated. We intend to remove it in the next major release.

tim-map-evictor
============

This TIM used to use a clustered ConcurrentHashMap and added a simple
evictor that could provide cache-like functionality and eviction for
TTI or TTL. This code has also been substantially rewritten and
upgraded to serve as the backing data structure for the Terracotta
Second Level Cache for Hibernate.

The TIM itself has been renamed to:
tim-distributed-cache

The interface (DistributedMap) and builder (DistributedMapBuilder)
have been moved to a new package and renamed:
org.terracotta.cache.DistributedCache
org.terracotta.cache.DistributedCacheBuilder

tim-hibernate
==========

For a long time we have had a Hibernate TIM that provided support for
a) clustered detached Hibernate entities and b) supporting clustered
second level cache providers such as Ehcache. Due to our Hibernate
focus in this release and the new Hibernate second level cache, we
have killed the old name and there are now a number of forge top-level
project Hibernate TIMs. Many of these are actually containers for TIM
flavors supporting Hibernate 3.2 or 3.3.

- tim-hibernate-concurrency - an *internal* TIM holding Hibernate
concurrency fixes used by the other tims - you should never need to
specify this directly
- tim-hibernate-entity - prior support for Hibernate clustered
detached entities
- tim-hibernate-cache-deprecated - prior support for Hibernate with
clustered ehcache second level cache.
- tim-hibernate-cache - the brand new better than nachos Terracotta
Hibernate second level cache!

There is much more to say about the new cache and a new deployment
mode that does not require a boot jar but I'll leave that for the
release!

Hope this is useful for some of you out there in user land...we're
shooting for the first stable version of 3.1 around the end of the
month. All of the forge changes above are there now in the 3.1
snapshots.

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Tim-Messaging 2.0.0 released!

2009-07-04T07:55:59Z

Awesome, Sergio. I just added it to the community highlights page and
on the homepage. It'll get pushed out on Wednesday or Friday.

In addition to crediting you in the description, do you want me to
provide a link to your website?

--Orion

On Jul 4, 2009, at 3:47 AM, Sergio Bossa wrote:

> - Announcing Tim-Messaging 2.0.0 -
>
> Tim-Messaging 2.0.0 has been released, providing to Terracotta 3.0.x
> users several fixes, important new features and improved documentation
> and samples.
>
> - How to get and know more -
>
> See Tim-Messaging web site on Terracotta Forge at:
> http://forge.terracotta.org/releases/projects/tim-messaging
>
> - What's new -
>
> Here's a list of the most important features for the two Tim-Messaging
> sub-modules:
>
> Tim-Pipes 2.0.0
>
> * Simplified Router APIs.
>
> Tim-MasterWorker 2.0.0
>
> * Completely dynamic, transparent, management of master/worker
> instances for both WorkManager and Executor APIs.
> * Master-to-Master fail-over.
> * Worker fail-over, with automatic work re-scheduling.
> * Advanced APIs for implementing data-affinity routing.
> * Improved documentation and samples.
>
> ... enjoy!
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Tim-Messaging 2.0.0 released!

2009-07-04T03:47:55Z

- Announcing Tim-Messaging 2.0.0 -

Tim-Messaging 2.0.0 has been released, providing to Terracotta 3.0.x
users several fixes, important new features and improved documentation
and samples.

- How to get and know more -

See Tim-Messaging web site on Terracotta Forge at:
http://forge.terracotta.org/releases/projects/tim-messaging

- What's new -

Here's a list of the most important features for the two Tim-Messaging
sub-modules:

Tim-Pipes 2.0.0

* Simplified Router APIs.

Tim-MasterWorker 2.0.0

* Completely dynamic, transparent, management of master/worker
instances for both WorkManager and Executor APIs.
* Master-to-Master fail-over.
* Worker fail-over, with automatic work re-scheduling.
* Advanced APIs for implementing data-affinity routing.
* Improved documentation and samples.

... enjoy!
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Just an early heads up for 3.1 on api jar

2009-07-01T07:34:19Z

Some background is in this jira:
http://jira.terracotta.org/jira/browse/FORGE-456

In 3.0, we have an artifact with coordinates org.terracotta.api:api
that contains the cluster event and data locality apis for
Terracotta. We put the same jar with the same name in the kit. Due
to Maven naming conventions, the name is something like
api-1.0.0.jar. Users may be using this jar to get access to these
apis in their classpath, but it's been noted that just naming a jar
"api" is not particularly helpful or unique.

So the coordinates changed yesterday to org.terracotta.api:terracotta-
api and the jar will now called terracotta-api-1.1.0.jar for 3.1. At
this point the kit and (I think) all forge projects that depended on
it (tim-async, tim-map-evictor, tim-messaging) have been updated.

Let me know if you have any questions...

Alex
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Max server object count

2009-06-03T01:22:29Z

Since we dont share anything between the L2s other than control data, it should be able to handle 4 billion objects. But
there are some gotchas, like you cant have 1 shared collection in the system with more than 2 billion entries, which is
anyway not possible with current java collections. Also the L1s connect to both the L2s and fault the shared graph as
needed. We dont restrict the size of the faulted graph, its a function of available memory at the L1. So as long as the
L1 doesnt try to fault more than 2 billion objects at the same time, it should be fine.

All this is theoretical limit though, not sure if I am overlooking something.

Artyom Sokolov wrote:

> What about 2 active L2 with striping enabled? Would be there 4 billion
> objects or still 2 billions?
>
> Thanks.
>
> On Tue, Jun 2, 2009 at 2:06 PM, Saravanan Subbiah
> <ssubbiah@...> wrote:
>> Currently at various places in our code base we use java collections to store/operate on the list of shared objects in
>> the system. As you know java collections return an int for getSize() (and many uses int for internal index pointers
>> too). So theoretically it can only handle Integer.MAX_VALUE elements in the collection. This is ok for java collections
>> as this is already a high number (2 Billion) and there is probably not enough memory to hold that many elements in the
>> collection anyways. (This is becoming untrue fast with 64bit VMs)
>>
>> But since TC can page objects in/out from disk, it is possible for us to handle 2+ billion objects, if we fix certain
>> areas of our code base to not use java collections and use some special datastructures or fix the code logic to operate
>> on the list in chunks. Anyways this is not yet done, so the word of warning in the release note.
>>
>> That being said, this limit is for the current live objects in the system and the limit is 2 billion. So its unlikely
>> that most people will ever hit that limit.
>>
>> Artyom Sokolov wrote:
>>> http://www.terracotta.org/web/display/docs/Release+Notes says that
>>> "Max server object count capped by int. There could be some unexpected
>>> behavior if the database has more than max int/2 objects in it."
>>>
>>> It would be appreciated if someone describes what can happen in this
>>> case and why.
>>>
>>> Thanks.
>>> _______________________________________________
>>> tc-users mailing list
>>> tc-users@...
>>> http://lists.terracotta.org/mailman/listinfo/tc-users
>> _______________________________________________
>> tc-users mailing list
>> tc-users@...
>> http://lists.terracotta.org/mailman/listinfo/tc-users
>>
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Max server object count

2009-06-02T02:27:42Z

What about 2 active L2 with striping enabled? Would be there 4 billion
objects or still 2 billions?

Thanks.

On Tue, Jun 2, 2009 at 2:06 PM, Saravanan Subbiah
<ssubbiah@...> wrote:

> Currently at various places in our code base we use java collections to store/operate on the list of shared objects in
> the system. As you know java collections return an int for getSize() (and many uses int for internal index pointers
> too). So theoretically it can only handle Integer.MAX_VALUE elements in the collection. This is ok for java collections
> as this is already a high number (2 Billion) and there is probably not enough memory to hold that many elements in the
> collection anyways. (This is becoming untrue fast with 64bit VMs)
>
> But since TC can page objects in/out from disk, it is possible for us to handle 2+ billion objects, if we fix certain
> areas of our code base to not use java collections and use some special datastructures or fix the code logic to operate
> on the list in chunks. Anyways this is not yet done, so the word of warning in the release note.
>
> That being said, this limit is for the current live objects in the system and the limit is 2 billion. So its unlikely
> that most people will ever hit that limit.
>
> Artyom Sokolov wrote:
>> http://www.terracotta.org/web/display/docs/Release+Notes says that
>> "Max server object count capped by int. There could be some unexpected
>> behavior if the database has more than max int/2 objects in it."
>>
>> It would be appreciated if someone describes what can happen in this
>> case and why.
>>
>> Thanks.
>> _______________________________________________
>> tc-users mailing list
>> tc-users@...
>> http://lists.terracotta.org/mailman/listinfo/tc-users
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users
>

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Max server object count

2009-06-02T02:06:15Z

Currently at various places in our code base we use java collections to store/operate on the list of shared objects in
the system. As you know java collections return an int for getSize() (and many uses int for internal index pointers
too). So theoretically it can only handle Integer.MAX_VALUE elements in the collection. This is ok for java collections
as this is already a high number (2 Billion) and there is probably not enough memory to hold that many elements in the
collection anyways. (This is becoming untrue fast with 64bit VMs)

But since TC can page objects in/out from disk, it is possible for us to handle 2+ billion objects, if we fix certain
areas of our code base to not use java collections and use some special datastructures or fix the code logic to operate
on the list in chunks. Anyways this is not yet done, so the word of warning in the release note.

That being said, this limit is for the current live objects in the system and the limit is 2 billion. So its unlikely
that most people will ever hit that limit.

Artyom Sokolov wrote:

> http://www.terracotta.org/web/display/docs/Release+Notes says that
> "Max server object count capped by int. There could be some unexpected
> behavior if the database has more than max int/2 objects in it."
>
> It would be appreciated if someone describes what can happen in this
> case and why.
>
> Thanks.
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Max server object count

2009-05-31T15:02:11Z

http://www.terracotta.org/web/display/docs/Release+Notes says that
"Max server object count capped by int. There could be some unexpected
behavior if the database has more than max int/2 objects in it."

It would be appreciated if someone describes what can happen in this
case and why.

Thanks.
_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Active/Passive w/two active servers

2009-05-22T11:51:50Z

Yes, the servers are currently in sync, I just check to verify this.
One of the boxes is new, and was out of sync last week, but I believe
that was resolved prior to Monday. I will check with the team that
handles that to make sure they didn't do anything yesterday.

RE the logs, I was too clever for my own good. What I sent weren't
the latest logs. I restarted one of the servers and clients this
morning when I saw the problem, so I think I sent Galileo's ".3" log
file, and Pasteur's ".1" because those were the ones for that time.

So this time I am resending all of the logs back to 5/20, with the
original file names.

Rob

On Fri, May 22, 2009 at 1:55 PM, Manoj Govindassamy
<mgovinda@...> wrote:

> Hi Rob,
>
> Do the servers galileo and pasteur have same system time
> synchronization. The server logs are 2 minutes apart. If they are in
> time sync, please send us the older version (.1) of server logs too.
>
> thanks,
> Manoj
>
>
> On May 22, 2009, at 10:02 PM, Robert Hanson wrote:
>
>> Thanks, logs are attached.
>>
>> This isn't in production yet, so you will see a lot of restarts around
>> 6pm-6:30 while I tweaked the configuration. I believe the error
>> occurred around 9pm. And like I said, this isn't in production, so
>> there was likely no activity on the clients.
>>
>> P.S. - I already talked to a TC sales rep, it is beginning to look
>> like a support contract will be a good thing to have :)
>>
>> Thanks again.
>>
>> Rob
>>
>>
>> On Fri, May 22, 2009 at 11:43 AM, Steven Harris
>> <steve@...> wrote:
>>> Hi,
>>> We could take a look if you attach the logs from all the clients and
>>> servers.
>>> Cheers,
>>> Steve Harris
>>> "Terracotta. It's ten pounds of awesome in a five pound sack."
>>>
>>>
>>>
>>> On May 22, 2009, at 8:39 AM, Robert Hanson wrote:
>>>
>>> So... I think I have everything set up right, but I hope I am missing
>>> something.
>>>
>>> The cluster has 2 servers (active/passive) and two clients
>>> (tomcat6/spring-security tims). The servers are located a couple
>>> thousand miles from each other, and the clients are co-located on the
>>> same boxes as the servers.
>>>
>>> This morning I checked out the TC Dev Console and both servers were
>>> active and only one client was appearing.
>>>
>>> How can I avoid this situation? And I missing something in the
>>> config? I wouldn't be so worried, but it has happened twice in 2
>>> days... and this is a new install, so 2-days basically means every
>>> day. And that worries me a bit.
>>>
>>> Any/all help would be appreciated. Thanks.
>>>
>>>
>>> <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-4.xsd">
>>>
>>> <tc-properties>
>>> <property name="l2.l1reconnect.enabled"
>>> value="true" />
>>> <property name="l2.l1reconnect.timeout.millis"
>>> value="10000"
>>> />
>>> <property
>>> name="l2.objectmanager.fault.logging.enabled" value="true" />
>>> <property name="l2.nha.tcgroupcomm.reconnect.enabled"
>>> value="true" />
>>> <property name="l2.nha.tcgroupcomm.reconnect.timeout"
>>> value="10000" />
>>> </tc-properties>
>>>
>>> <servers>
>>> <server host="1.1.1.1" name="galileo">
>>> <data>/usr/local/terracotta/data/galileo</
>>> data>
>>> <logs>/usr/local/terracotta/logs/galileo</
>>> logs>
>>> <l2-group-port>9530</l2-group-port>
>>> <dso-port>9510</dso-port>
>>> <dso>
>>> <persistence>
>>> <mode>permanent-store</mode>
>>> </persistence>
>>> </dso>
>>> </server>
>>>
>>> <server host="2.2.2.2" name="pasteur">
>>> <data>/usr/local/terracotta/data/pasteur</
>>> data>
>>> <logs>/usr/local/terracotta/logs/pasteur</
>>> logs>
>>> <l2-group-port>9530</l2-group-port>
>>> <dso-port>9510</dso-port>
>>> <dso>
>>> <persistence>
>>> <mode>permanent-store</mode>
>>> </persistence>
>>> </dso>
>>> </server>
>>>
>>> <ha>
>>> <mode>networked-active-passive</mode>
>>> <networked-active-passive>
>>> <election-time>5</election-time>
>>> </networked-active-passive>
>>> </ha>
>>>
>>> <update-check>
>>> <enabled>true</enabled>
>>> </update-check>
>>> </servers>
>>>
>>> <clients>
>>> <logs>/usr/local/terracotta/logs/client-logs</logs>
>>>
>>> <statistics>/usr/local/terracotta/data/%(tc.node-name)/client-
>>> statistics</statistics>
>>> <modules>
>>> <module name="tim-tomcat-6.0"
>>> version="1.0.1" />
>>> <module name="tim-spring-security-2.0"
>>> version="1.1.1" />
>>> </modules>
>>> </clients>
>>>
>>> <application>
>>> <dso>
>>> <instrumented-classes>
>>> <include>
>>>
>>> <class-expression>com.company.sensor.remoting.model.*</class-
>>> expression>
>>> </include>
>>> <include>
>>>
>>> <class-expression>com.company.calendar.model.*</class-expression>
>>> </include>
>>> <include>
>>>
>>> <class-expression>com.company..shared..*</class-expression>
>>> </include>
>>> </instrumented-classes>
>>>
>>> <web-applications>
>>> <web-application>ROOT</web-
>>> application>
>>> </web-applications>
>>> </dso>
>>> </application>
>>>
>>> </tc:tc-config>
>>> _______________________________________________
>>> tc-users mailing list
>>> tc-users@...
>>> http://lists.terracotta.org/mailman/listinfo/tc-users
>>>
>>>
>>> _______________________________________________
>>> tc-users mailing list
>>> tc-users@...
>>> http://lists.terracotta.org/mailman/listinfo/tc-users
>>>
>>>
>>> <logs.zip>
>> _______________________________________________
>> tc-users mailing list
>> tc-users@...
>> http://lists.terracotta.org/mailman/listinfo/tc-users
>
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users
>

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

tc-logs.zip (319K) Download Attachment

Re: Active/Passive w/two active servers

2009-05-22T10:55:54Z

Hi Rob,

Do the servers galileo and pasteur have same system time
synchronization. The server logs are 2 minutes apart. If they are in
time sync, please send us the older version (.1) of server logs too.

thanks,
Manoj

On May 22, 2009, at 10:02 PM, Robert Hanson wrote:

> Thanks, logs are attached.
>
> This isn't in production yet, so you will see a lot of restarts around
> 6pm-6:30 while I tweaked the configuration. I believe the error
> occurred around 9pm. And like I said, this isn't in production, so
> there was likely no activity on the clients.
>
> P.S. - I already talked to a TC sales rep, it is beginning to look
> like a support contract will be a good thing to have :)
>
> Thanks again.
>
> Rob
>
>
> On Fri, May 22, 2009 at 11:43 AM, Steven Harris
> <steve@...> wrote:
>> Hi,
>> We could take a look if you attach the logs from all the clients and
>> servers.
>> Cheers,
>> Steve Harris
>> "Terracotta. It's ten pounds of awesome in a five pound sack."
>>
>>
>>
>> On May 22, 2009, at 8:39 AM, Robert Hanson wrote:
>>
>> So... I think I have everything set up right, but I hope I am missing
>> something.
>>
>> The cluster has 2 servers (active/passive) and two clients
>> (tomcat6/spring-security tims). The servers are located a couple
>> thousand miles from each other, and the clients are co-located on the
>> same boxes as the servers.
>>
>> This morning I checked out the TC Dev Console and both servers were
>> active and only one client was appearing.
>>
>> How can I avoid this situation? And I missing something in the
>> config? I wouldn't be so worried, but it has happened twice in 2
>> days... and this is a new install, so 2-days basically means every
>> day. And that worries me a bit.
>>
>> Any/all help would be appreciated. Thanks.
>>
>>
>> <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-4.xsd">
>>
>> <tc-properties>
>> <property name="l2.l1reconnect.enabled"
>> value="true" />
>> <property name="l2.l1reconnect.timeout.millis"
>> value="10000"
>> />
>> <property
>> name="l2.objectmanager.fault.logging.enabled" value="true" />
>> <property name="l2.nha.tcgroupcomm.reconnect.enabled"
>> value="true" />
>> <property name="l2.nha.tcgroupcomm.reconnect.timeout"
>> value="10000" />
>> </tc-properties>
>>
>> <servers>
>> <server host="1.1.1.1" name="galileo">
>> <data>/usr/local/terracotta/data/galileo</
>> data>
>> <logs>/usr/local/terracotta/logs/galileo</
>> logs>
>> <l2-group-port>9530</l2-group-port>
>> <dso-port>9510</dso-port>
>> <dso>
>> <persistence>
>> <mode>permanent-store</mode>
>> </persistence>
>> </dso>
>> </server>
>>
>> <server host="2.2.2.2" name="pasteur">
>> <data>/usr/local/terracotta/data/pasteur</
>> data>
>> <logs>/usr/local/terracotta/logs/pasteur</
>> logs>
>> <l2-group-port>9530</l2-group-port>
>> <dso-port>9510</dso-port>
>> <dso>
>> <persistence>
>> <mode>permanent-store</mode>
>> </persistence>
>> </dso>
>> </server>
>>
>> <ha>
>> <mode>networked-active-passive</mode>
>> <networked-active-passive>
>> <election-time>5</election-time>
>> </networked-active-passive>
>> </ha>
>>
>> <update-check>
>> <enabled>true</enabled>
>> </update-check>
>> </servers>
>>
>> <clients>
>> <logs>/usr/local/terracotta/logs/client-logs</logs>
>>
>> <statistics>/usr/local/terracotta/data/%(tc.node-name)/client-
>> statistics</statistics>
>> <modules>
>> <module name="tim-tomcat-6.0"
>> version="1.0.1" />
>> <module name="tim-spring-security-2.0"
>> version="1.1.1" />
>> </modules>
>> </clients>
>>
>> <application>
>> <dso>
>> <instrumented-classes>
>> <include>
>>
>> <class-expression>com.company.sensor.remoting.model.*</class-
>> expression>
>> </include>
>> <include>
>>
>> <class-expression>com.company.calendar.model.*</class-expression>
>> </include>
>> <include>
>>
>> <class-expression>com.company..shared..*</class-expression>
>> </include>
>> </instrumented-classes>
>>
>> <web-applications>
>> <web-application>ROOT</web-
>> application>
>> </web-applications>
>> </dso>
>> </application>
>>
>> </tc:tc-config>
>> _______________________________________________
>> tc-users mailing list
>> tc-users@...
>> http://lists.terracotta.org/mailman/listinfo/tc-users
>>
>>
>> _______________________________________________
>> tc-users mailing list
>> tc-users@...
>> http://lists.terracotta.org/mailman/listinfo/tc-users
>>
>>
>> <logs.zip>
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

Re: Active/Passive w/two active servers

2009-05-22T09:32:45Z

Thanks, logs are attached.

This isn't in production yet, so you will see a lot of restarts around
6pm-6:30 while I tweaked the configuration. I believe the error
occurred around 9pm. And like I said, this isn't in production, so
there was likely no activity on the clients.

P.S. - I already talked to a TC sales rep, it is beginning to look
like a support contract will be a good thing to have :)

Thanks again.

Rob

On Fri, May 22, 2009 at 11:43 AM, Steven Harris
<steve@...> wrote:

> Hi,
> We could take a look if you attach the logs from all the clients and
> servers.
> Cheers,
> Steve Harris
> "Terracotta. It's ten pounds of awesome in a five pound sack."
>
>
>
> On May 22, 2009, at 8:39 AM, Robert Hanson wrote:
>
> So... I think I have everything set up right, but I hope I am missing
> something.
>
> The cluster has 2 servers (active/passive) and two clients
> (tomcat6/spring-security tims). The servers are located a couple
> thousand miles from each other, and the clients are co-located on the
> same boxes as the servers.
>
> This morning I checked out the TC Dev Console and both servers were
> active and only one client was appearing.
>
> How can I avoid this situation? And I missing something in the
> config? I wouldn't be so worried, but it has happened twice in 2
> days... and this is a new install, so 2-days basically means every
> day. And that worries me a bit.
>
> Any/all help would be appreciated. Thanks.
>
>
> <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-4.xsd">
>
>        <tc-properties>
>                <property name="l2.l1reconnect.enabled" value="true" />
>                <property name="l2.l1reconnect.timeout.millis" value="10000"
> />
>                <property
> name="l2.objectmanager.fault.logging.enabled" value="true" />
>                <property name="l2.nha.tcgroupcomm.reconnect.enabled"
> value="true" />
>                <property name="l2.nha.tcgroupcomm.reconnect.timeout"
> value="10000" />
>        </tc-properties>
>
>        <servers>
>                <server host="1.1.1.1" name="galileo">
>                        <data>/usr/local/terracotta/data/galileo</data>
>                        <logs>/usr/local/terracotta/logs/galileo</logs>
>                        <l2-group-port>9530</l2-group-port>
>                        <dso-port>9510</dso-port>
>                        <dso>
>                                <persistence>
>                                        <mode>permanent-store</mode>
>                                </persistence>
>                        </dso>
>                </server>
>
>                <server host="2.2.2.2" name="pasteur">
>                        <data>/usr/local/terracotta/data/pasteur</data>
>                        <logs>/usr/local/terracotta/logs/pasteur</logs>
>                        <l2-group-port>9530</l2-group-port>
>                        <dso-port>9510</dso-port>
>                        <dso>
>                                <persistence>
>                                        <mode>permanent-store</mode>
>                                </persistence>
>                        </dso>
>                </server>
>
>                <ha>
>                        <mode>networked-active-passive</mode>
>                        <networked-active-passive>
>                                <election-time>5</election-time>
>                        </networked-active-passive>
>                </ha>
>
>                <update-check>
>                        <enabled>true</enabled>
>                </update-check>
>        </servers>
>
>        <clients>
>                <logs>/usr/local/terracotta/logs/client-logs</logs>
>
> <statistics>/usr/local/terracotta/data/%(tc.node-name)/client-statistics</statistics>
>                <modules>
>                        <module name="tim-tomcat-6.0" version="1.0.1" />
>                        <module name="tim-spring-security-2.0"
> version="1.1.1" />
>                </modules>
>        </clients>
>
>        <application>
>                <dso>
>                        <instrumented-classes>
>                                <include>
>
> <class-expression>com.company.sensor.remoting.model.*</class-expression>
>                                </include>
>                                <include>
>
> <class-expression>com.company.calendar.model.*</class-expression>
>                                </include>
>                                <include>
>
> <class-expression>com.company..shared..*</class-expression>
>                                </include>
>                        </instrumented-classes>
>
>                        <web-applications>
>                                <web-application>ROOT</web-application>
>                        </web-applications>
>                </dso>
>        </application>
>
> </tc:tc-config>
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users
>
>
> _______________________________________________
> tc-users mailing list
> tc-users@...
> http://lists.terracotta.org/mailman/listinfo/tc-users
>
>

_______________________________________________
tc-users mailing list
tc-users@...
http://lists.terracotta.org/mailman/listinfo/tc-users

logs.zip (95K) Download Attachment