rmi

What could cause RMI method calls to fail intermittently?

家住魔仙堡 提交于 2019-12-22 10:37:23
问题 Long story short, I have an RMI Server and Client. The Server and Client are capable of making RMI calls on each other. After the Client connects to the Server, the Server may make many hundreds of method calls in quick succession on the Client. The problem is this - towards the end of a huge batch of Server-to-Client method calls, some will fail because RMI claims it cannot establish a connection from Server-to-Client, even though hundreds of calls before it will succeed. I can't post any

RMI Server vs. RMI Registry

吃可爱长大的小学妹 提交于 2019-12-22 10:36:36
问题 On Oracle's FAQ page about Java RMI, it says: While the Java Remote Method Invocation (Java RMI) server can theoretically be on any host, it is usually the same host as that on which the registry is running, and on a different port. Even if the server is mistaken about its hostname or IP address (or has a hostname that simply isn't resolvable by clients), it will still export all of its objects using that mistaken hostname, but you will see an exception every time you try to receive one of

RMI and JMX Socket Factories

醉酒当歌 提交于 2019-12-22 09:34:58
问题 I'm trying to start an embedded JMX server in my java app. I want to use the same port for the RMI Registry and for the actual RMI traffic (or JMX traffic if you like). Apparently this is possible since the RMI Registry is merely a Remote Object itself. The added difficulty is that I need to use Socket Factories because I need to bind to a specific NIC. I start off by: int registryPort = 3012; int jmxPort = 3012; // use the same port and here's my server socket factory. Pretty straight

RMI and JMX Socket Factories

旧巷老猫 提交于 2019-12-22 09:33:15
问题 I'm trying to start an embedded JMX server in my java app. I want to use the same port for the RMI Registry and for the actual RMI traffic (or JMX traffic if you like). Apparently this is possible since the RMI Registry is merely a Remote Object itself. The added difficulty is that I need to use Socket Factories because I need to bind to a specific NIC. I start off by: int registryPort = 3012; int jmxPort = 3012; // use the same port and here's my server socket factory. Pretty straight

How to enable WebDAV in Adobe AEM?

走远了吗. 提交于 2019-12-22 07:57:20
问题 I am trying to access Adobe AEM via WebDAV, however, I cannot get it to work. I am running the out-of-the-box crx-quickstart, so I am using port 4502 and the default workspace. I am using Windows Explorer as the WebDAV client, which I use to connect to Sharepoint without difficulty. These seem to be the only instructions for connecting to AEM via WebDAV. http://dev.day.com/docs/en/crx/current/how_to/webdav_access.html The instructions imply that you just point your WebDAV client at the

RMI Threads prevent JVM from exiting after main() completes

可紊 提交于 2019-12-22 04:08:17
问题 To make a long story short, I'm having trouble getting a couple of Java RMI's non-daemon threads to close out after my application no longer needs RMI. This prevents the JVM from exiting when main() completes. I understand that exporting UnicastRemoteObject s will cause RMI to leave threads open until you successfully call UnicastRemoteObject.unexportObject(Object o,boolean force) . Here's an example (run without modification and the JVM will exit normally - remove the call to unexportObject

How to improve the performance of Client-Server Architecture Application?

瘦欲@ 提交于 2019-12-21 21:16:00
问题 We have a product built on the Client-Server architecture. Some details about the technology stack used. Client - Java Swing Server - RMI Java Database - Oracle The clients are located at different parts of the world but the java server & the oracle database are located on the same machine in Sweden. Because of this there is a lot of network latency. The clients located at distant locations have terrible performance. The application is used for processing files with the size over 50MB. Each

Why RMI registry is ignoring the java.rmi.server.codebase property

旧城冷巷雨未停 提交于 2019-12-21 12:07:13
问题 I am running a Hello World example for java RMI 1) I run the registry in an empty folder motta@motta-laptop ~/tmp $ rmiregistry 2) I start the HTTP server to retrieve the classes at runtime. The download folder contains the remote interface for the client-server motta@motta-laptop ~/download $ java NanoHTTPD 8080 3) I start the server passing the java.rmi.server.codebase property as suggested in the java RMI tutorial motta@motta-laptop ~/server $ java -Djava.rmi.server.codebase="http:/

Bad idea to chain exceptions with RMI?

霸气de小男生 提交于 2019-12-21 06:05:25
问题 Is it a bad idea to use exception chaining when throwing RemoteExceptions? We have an RMI server that does something like this: public Object doSomething() throws RemoteException { try { return getData(); } catch (CustomException ex) { throw new RemoteException(ex); } } I'm getting UnmarshallException caused by a ClassNotFoundException in my client. On the plus side, it turns out that CustomException itself IS exported. Unfortunately, another exception deep inside this guy is NOT exported,

How Fast Might RMI Be?

∥☆過路亽.° 提交于 2019-12-21 05:21:15
问题 I have seen the question: Communication between two separate Java desktop applications (answer: JGroups) and I'm thinking about implementing something with JavaGroups or straight RMI but speed is of the essence. I'm not sending large amounts of data around (content of MIDI Messages, so 3 bytes each, no more than say two messages every three milliseconds) and this will be all on the same machine. Is it daft to think that RMI/JGroups on the same physical machine will be slow? (My thought is