java - Hazelcast keep running after application stops on Weblogic (and also Tomcat) -

I'm playing to get what Hazelcast offers now. There are only a few things in the use of hazelkast in the celebration

On weblogic server 10.3.6, I noticed that there is something wrong in one of the maps. This was an exception to the class certainty error, although it is running more than a few days without the problem. Then I stopped the application on running Oracle weblogic on 8 nodes, I had closed the Hajalcast clusters / instances, but even though the application closed on all the nodes of the weblogic, but I saw hazelcast merge exceptions on logs (throwing).

I also test on the basis of my spring application on Tomcat 7, even if I close the application, opposes the closure of the Hazelcast in some way.

Is this normal behavior?

Note that when my application begins, then I call Hajjalkast, there is no special client, only Weblogic Server has only 8 nodes.

> Edit: The Stacktrace of the Migration Issue is Here

  SEVERE: Datasheel Eligible, Problems while Reading Namespace: 0, ID: 0, Class: 'com.hazelcast .partition.impl.MigrationRequestOperation ', exception: com.hazelcast.partition.impl.MigrationRequestOperation com.hazelcast.nio.serialization.HazelcastSerializationException: 0, ID :: 0, class: DataSerializable, namespace reading problems while' com.hazelcast. partition.impl.MigrationRequestOperation ', exceptions to com on com.hazelcast.nio.serialization.DataSerializer.read (DataSerializer.java:120) on com.hazelcast.nio.serialization.DataSerializer.read (DataSerializer.java:39) com .hazelcast.partition.impl.MigrationRequestOperatio. Hazelcast.nio.serialization.StreamSerializerAdapter.toObject (StreamSerializerAdapt er.java:65) com.hazelcast.nio.serialization.SerializationServiceImpl.toObject (SerializationServiceImpl.java:260) com.hazelcast.spi.impl.NodeEngineImpl.toObject (NodeEngineImpl.java : com.hazelcast.spi.impl.BasicOperationService $ OperationPacketHandler.handle (BasicOperationService.java:621) on com on .impl.BasicOperationService $ OperationPacketHandler.loadOperation (BasicOperationService.java:638) at 186) on com.hazelcast.spi. hazelcast.spi.impl.BasicOperationService $ OperationPacketHandler.access com.hazelcast.spi.impl $ 1500 (BasicOperationService.java:614) com Acjhelkast on com.Hazelcast.spi.impl on. Basic Operation Services $ Basic DispatcherIIPP DISAPTCH (Basic Operation Sewer.Java TTS66). Basic OperationSecular $ OperationTrade. Process (Basic Operation Centelligence .java script) com.hazelcast.spi.impl.basicOperationScheduler $ OperationThread.doRun on com.hazelcast.spi.impl.BasicOperationScheduler $ OperationThread.processPriorityMessages (BasicOperationScheduler.java:480) (BasicOperationScheduler.java 457) caused by Elcast.spi.impl.BasicOperationScheduler $ OperationThread.run (BasicOperationScheduler.java:432): java.lang.ClassNotFoundException: com.hazelcast.partition.impl.MigrationRequest classes on Veblogikkutton. Classloaders GenericClassLoader.findLocalClass (GenericClassLoader.java: 297) on weblogic.utils.classloaders .java.lang.ClassLoader.loadClass on weblogic.utils.classloaders.ChangeAwareClassLoader.findClass (ChangeAwareClassLoader.java:64) on GenericClassLoader.findClass (GenericClassLoader.javaumer70) (ClassLoader.java: 306) java.lang.ClassLoader.loadClass (ClassLoader.javaailand47) weblogic.utils.classloaders.GenericClassLoader.loadClass (GenericClassLoader.java:179) on weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass (ChangeAwareClassLoader .java: 43 on) com.hazelcast.nio.ClassLoaderUtil.tryLoadClass (ClassLoaderUtil.java:124) com.hazelcast.nio.ClassLoaderUtil.loadClass (ClassLoaderUtil.java:113) on com.hazelcast.nio.ClassLoaderUtil.newInstance ( ClassLoaderUtil.java at: 66) com.hazelcast.nio.serialization.DataSerializer.read (DataSerializer.java:109) ... 12 and 16 March 2015 5:31:29 Prime com.haz Elcast.spi.OperationService  

Reliable says:

< P> As the last step, if you have done it with your customer, you can stop it as shown below, it will discard all used resources and close the connection with the cluster.

  client.shutdown ();  

that your code should be called in the delete () method:

  public class ExampleBean applicable disposable bean {public Zero Blast () {Client.shutdown (); }}  

The exception that you have pasted is due to the fact that your app class loader is destroyed when your app is closed.