Invocation service only processing on a single node (Coherence 3.4).

Question

I'm trying to run a task on each node using the invocation service. The task should return a list of report files from each node.
The service is setup as follows:<b>
    <invocation-scheme>
        <scheme-name>agents</scheme-name>
        <service-name>agents</service-name>
        <serializer>com.tangosol.io.DefaultSerializer</serializer>
    </invocation-scheme></b>
And accessed as follows, using the deprecated getInvocationService method:<b>
    InvocationService service = CacheFactory.getInvocationService("agents");
    Map<Member, List<String>> reportQuery = service.query(new ReportFilesnameAgent(), null);</b>
When I access it in this way, the ReportFilesnameAgent only runs on a single node, despite the following listing both cluster nodes:<b>
    Set memberSet = service.getCluster().getMemberSet();</b>
I even tried to force it to run on all nodes by passing the member set to the query method, but this made no difference:<b>
    Map<Member, List<String>> reportQuery = service.query(new ReportFilesnameAgent(), memberSet);</b>
If I access the service using the recommended (non-deprecated) method:<b>
    InvocationService service = (InvocationService) CacheFactory.getService("agents");</b>
Coherences throws the following:<b>
    Caused by: java.lang.IllegalArgumentException: Missing scheme for service: "agents"</b>
Any ideas?
Many thanks in advance,
Cormac.
Edited by: user1744133 on Dec 21, 2009 4:15 AM

Answer 1

Hi,
I'm trying this invocation-schema with Version 3.5.2/463a and a pof serializer and it fails with the below stack trace suggesting that my nodes run of different configurations.
I can see them loading the same cache-config and the same config though.
Any ideas?
many thanks,
Christoph.
The new invocation conig:
     <invocation-scheme>
          <scheme-name>agents</scheme-name>
          <service-name>agents</service-name>
          <serializer>
               <class-name>
                    com.tangosol.io.pof.SafeConfigurablePofContext
          </class-name>
               <init-params>
                    <init-param>
                         <param-type>string</param-type>
                         <param-value>
                              orion-pof-config.xml
          </param-value>
                    </init-param>
               </init-params>
          </serializer>          
          <autostart>true</autostart>
     </invocation-scheme>
the stackt trace:
2010-02-15 15:37:37.286/5.469 Oracle Coherence GE 3.5.2/463 <D5> (thread=Invocation:agents, member=2): Service agents joined the cluster with senior service member 1
2010-02-15 15:37:37.333/5.516 Oracle Coherence GE 3.5.2/463 <Error> (thread=Invocation:agents, member=2): The service "agents" is configured to use serializer com.tangosol.io.DefaultSerializer {loader=sun.misc.Launcher$AppClassLoader@17590db}, which appears to be different from the serializer used by Member(Id=1, Timestamp=2010-02-15 15:37:20.268, Address=165.2.93.118:18001, MachineId=64118, Location=site:EMEA.AD.JPMORGANCHASE.COM,machine:LLDNCFI5SZW83J,process:2360, Role=TmpMain).
java.io.StreamCorruptedException: invalid type: 78
     at com.tangosol.util.ExternalizableHelper.readObjectInternal(ExternalizableHelper.java:2231)
     at com.tangosol.util.ExternalizableHelper.readObject(ExternalizableHelper.java:2219)
     at com.tangosol.io.DefaultSerializer.deserialize(DefaultSerializer.java:60)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.readObject(Service.CDB:4)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$ServiceConfigMap.readObject(Grid.CDB:1)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid$MemberConfigResponse.read(Grid.CDB:13)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:123)
     at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
     at java.lang.Thread.run(Thread.java:619)
Stopping the agents service.
2010-02-15 15:37:37.333/5.516 Oracle Coherence GE 3.5.2/463 <D5> (thread=Invocation:agents, member=2): Service agents left the cluster
2010-02-15 15:37:37.333/5.516 Oracle Coherence GE 3.5.2/463 <Error> (thread=main, member=2): Error while starting service "agents": java.lang.RuntimeException: Failed to start Service "agents" (ServiceState=SERVICE_STOPPED)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.start(Service.CDB:38)
     at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.start(Grid.CDB:38)
     at com.tangosol.coherence.component.util.SafeService.startService(SafeService.CDB:28)
     at com.tangosol.coherence.component.util.SafeService.ensureRunningService(SafeService.CDB:27)
     at com.tangosol.coherence.component.util.SafeService.start(SafeService.CDB:14)
     at com.tangosol.net.CacheFactory.getInvocationService(CacheFactory.java:943)
     at com.tmp.InvocationClient.main(InvocationClient.java:37)