Hi there Donal,
Good question. No, the ClassLoaderService does not need to be persisted. The
type of Service (Modular or Default) is determined at start up and passed in.
This way we can run the Geode code ClassLoaderIsolated or “normal” depending on
what ClassLoaderService we decide to pass in
Sounds good to me. One question though: is it likely that the
ClassLoaderService configuration will need to be persisted at all? For example,
would it be reasonable to provide a user with the ability to specify a new
ClassLoaderService implementation to be used upon cluster restart (via GFSH or
Right - I'm aware of that directory in Geode, just not sure this belongs
there... yet(?). I'll submit a PR for the native repo, and if I or someone
else eventually adapts it for the Java client (low probability IMO), it can be
moved easily.
Thanks,
Blake
On 9/11/20, 2:11 PM, "Dan Smith" wr
Hi there Apache Geode Devs, (try 2)
Please find attached a proposal for a ClassLoaderService. Please review and
ponder on it.
https://cwiki.apache.org/confluence/display/GEODE/Introduction+of+ClassLoaderService+into+Geode
All comments are please to be made in this mail thread.
—Udo
Hi there Apache Geode Devs,
Please find
Hi,
This problem is usually seen only on 1 server. The other servers metrics and
bucket count looks fine. Another symptom of this issue is that the
max-connections limit is reached on the problematic server if we have a client
that tries to reconnect after the server restart. Clients simply ge
