Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 14 Jul 2016 15:46:20 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12989496.1468511135000.29368.1468511180574@Atlassian.JIRA>
In-Reply-To: <JIRA.12989496.1468511135000@Atlassian.JIRA>
References: <JIRA.12989496.1468511135000@Atlassian.JIRA> <JIRA.12989496.1468511135347@arcas>
Subject: [jira] [Created] (IGNITE-3483) Regression: service is being
 deployed on the client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 14 Jul 2016 15:46:22 -0000

Denis Magda created IGNITE-3483:
-----------------------------------

             Summary: Regression: service is being deployed on the client
                 Key: IGNITE-3483
                 URL: https://issues.apache.org/jira/browse/IGNITE-3483
             Project: Ignite
          Issue Type: Bug
            Reporter: Denis Magda


Seems that we got a regression. Presently if to start a service (defined in the configuration of the server node) then it will be automatically deployed on client nodes as well. 

I got the following exception on the client 

{code}
[14:44:45,074][SEVERE][srvc-deploy-#41%null%][GridServiceProcessor] Failed to initialize service (service will not be deployed): FileLoaderServiceImpl
class org.apache.ignite.binary.BinaryInvalidTypeException: be.ing.tds.shielding.core.service.FileLoaderServiceImpl
	at org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:636)
	at org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1452)
	at org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
	at org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1119)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1040)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1662)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1352)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:106)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1319)
	at org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1709)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: be.ing.tds.shielding.core.service.FileLoaderServiceImpl
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)
	at org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8263)
	at org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
	at org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:627)
	... 15 more
{code}

Attaching the test. Run {{testNoDeployOnClient}} test to see the issue. Present test check that {{ServiceDescriptors.topologySnapshot}} is 0 for a client node. However it's 1. 

I've checked previous version and saw that {{ServiceDescriptors.topologySnapshot}} is not 0 as well. However after debugging the sources I saw that no deploying happens on the client in any case meaning that this {{ServiceDescriptors.topologySnapshot}}  is broken as well.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)