1. spring manages hiberante transactions. When setting the cut plane, you must consider all the places that may involve transactions. Otherwise, the cut plane does not involve any database operations, which occupy a lot of resources and cannot be released.
2. when using rmi, if multiple ip addresses exist on the server where the application is deployed, 127.0.0.1 confused connetion will be reported when the client connects to the service. In this case, you need to set the ip address registered by rmi, System parameter, system. setProperty ("java. rmi. server. hostname "," XXX. XXX. XXX. XXX "); of course, this setting should be before rmi registration.
3. rmi traversal is a problem (for example, no route to host), but spring org. springframework. remoting. rmi. rmiServiceExporter provides servicePort attribute settings, that is, to set the service port. rmi uses a port to listen to the Service (registryPort) and a port for Communication (servicePort ), this firewall only needs to open the two ports.