Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corda RPC: A hot observable returned from an RPC was never subscribed to #63

Open
cdesch opened this issue Nov 2, 2021 · 0 comments
Open

Comments

@cdesch
Copy link

cdesch commented Nov 2, 2021

I'm getting the error

RPCClientProxyHandler.onRemoval - A hot observable returned from an RPC was never subscribed to. This wastes server-side resources because it was queueing observations for retrieval. It is being closed now, but please adjust your code to call .notUsed() on the observable to close it explicitly. (Java users: subscribe to it then unsubscribe). If you aren't sure where the leak is coming from, set -Dnet.corda.client.rpc.trackRpcCallSites=true on the JVM command line and you will get a stack trace with this warning.

Following this example template, and making calls with SignedTransaction result = proxy.startTrackedFlowDynamic(ExampleFlow.Initiator.class, amount,otherParty).getReturnValue().get();

This SO says that the Observable needs to be subscribed and unsubscribed to. How is that supposed to be done properly given the example?

ashutoshmeher-r3 pushed a commit that referenced this issue Jan 30, 2022
update log4j version and upgrade corda version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant