Steve Souza

I don't know how to close it, so probably for the squirrel admin to resolve though I opened it and it was resolved to my satisfaction.

Is the screen snapshot from your running instance? If so , it looks like jamon is wired up correctly. I see SQL stats, and garbage collection stats so that is good. Your problem is probably the most common one that I see (almost 100%). If your code is executing and not throwing exceptions that means it is finding the jamon jar, but you probably have the jamon jar deployed twice 1. Your application is writing to one jamon jar (yourapp->jamonjar1) 2. The jamon web app is reading from a different jamon...

Sorry, for the ridiculously late/pointless response, but thought I would answer in case others look. I hope to update all the libraries jamon uses including hazelcast relatively soon. If you don't have hazelcast jars in your classpath it won't call any of the hazelcast code. You can also explicitly configure the jamonpersister in the jamon properties file to ensure hazelcast code is not called. If you would like you can safely remove all hazelcast classes from the jar. I could work with you on t...

awesome!

Thanks so much for your input. Over the years I haven't had much input from my user community, and so your post is welcome. First, do you realize that the "donate" button on the sourceforge site here fails? No. I put it up a long time ago and never really got donations so more or less forgot about it. I will look into that - who knows I may be leaving millions on the table :). Second, as indicated in one of the reviews (and I've heard it from others), some struggle with finding more on the tool....

Sorry for the delay in responding. I must have missed the email sourceforge sent me. Good suggestion. I hope to update the older libraries jamon uses soon, so I will put this on the list. Thanks for the references.

That class is one of the first loaded and is in jamon-2.82.jar. So it sounds like the jar is not being found by tomcat. Can you give a few more details? 1. What version of tomcat are you using? 2. Where did you put jamon-2.82.jar? 3. Did you do any other configuration steps such as those specified here: https://jamonapi.sourceforge.net/http_monitoring.html Thanks, Steve

Absolutely can be closed. Your solution of moving away from log4j in general is totally acceptable. I didn’t realize I had to close it. Is that something you want me to do? Or you can certainly feel free to close it. Thanks for your help. On Mon, Feb 27, 2023 at 6:29 AM sfst sfst@users.sourceforge.net wrote: I understand you kept this open, so other people can find the solution, but now after one year it can be closed? [feature-requests:#606] Plans for Squirrel to move from EOL log4j 1.x to log4j...