search

baloise / digital-signature

a digital signature confluence macro
https://marketplace.atlassian.com/1217404
Apache License 2.0
8 stars 8 forks source link

Error on some digital signature macros #68

Closed williamtanner17 closed 3 years ago

williamtanner17 commented 3 years ago

We are seeing errors on some digital signature macros, while others work fine. We even have the same page with the same macro in our Test and Production environments, and the macro works in Test, but not in prod. The error we see on the page is:

Error rendering macro 'signature'

com.baloise.confluence.digitalsignature.Signature cannot be cast to com.baloise.confluence.digitalsignature.Signature digital-signature-error-log.txt

Tiliavir commented 3 years ago

Hi @williamtanner17

Very interesting - which version of digital-signature and confluence are you using?

java.lang.ClassCastException: com.baloise.confluence.digitalsignature.Signature cannot be cast to com.baloise.confluence.digitalsignature.Signature
    at com.baloise.confluence.digitalsignature.DigitalSignatureMacro.sync(DigitalSignatureMacro.java:294)
    at com.baloise.confluence.digitalsignature.DigitalSignatureMacro.execute(DigitalSignatureMacro.java:97)

Best regards Markus

williamtanner17 commented 3 years ago

Hello Markus,

We are on Confluence Data Center 7.10.1. We just updated digital-signature to version 7.0.3.

Regards,

Bill

From: Markus Lindenmann @.> Sent: Thursday, April 15, 2021 1:48 PM To: baloise/digital-signature @.> Cc: TANNER, WILLIAM (CTR) @.>; Mention @.> Subject: Re: [baloise/digital-signature] Error on some digital signature macros (#68)

CAUTION: This email originated from outside of DHS. DO NOT click links or open attachments unless you recognize and/or trust the sender. Contact your component SOC with questions or concerns.

Hi @williamtanner17https://urldefense.us/v3/__https:/github.com/williamtanner17__;!!BClRuOV5cvtbuNI!VL5QCu0qn0MiB49mMPnFOXbTTQiaCWUM4HXdDAQQQ2QE4hU-QNFrWdpLzN9tWiLRfi09QWCJ4kxJGck$

Very interesting - which version of digital-signature and confluence are you using?

java.lang.ClassCastException: com.baloise.confluence.digitalsignature.Signature cannot be cast to com.baloise.confluence.digitalsignature.Signature

    at com.baloise.confluence.digitalsignature.DigitalSignatureMacro.sync(DigitalSignatureMacro.java:294)

    at com.baloise.confluence.digitalsignature.DigitalSignatureMacro.execute(DigitalSignatureMacro.java:97)

Best regards Markus

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/baloise/digital-signature/issues/68*issuecomment-820616374__;Iw!!BClRuOV5cvtbuNI!VL5QCu0qn0MiB49mMPnFOXbTTQiaCWUM4HXdDAQQQ2QE4hU-QNFrWdpLzN9tWiLRfi09QWCJEbfaFHk$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/ASRTY7TDNWZB2WBGHLOZRSDTI4RGFANCNFSM426P3AYQ__;!!BClRuOV5cvtbuNI!VL5QCu0qn0MiB49mMPnFOXbTTQiaCWUM4HXdDAQQQ2QE4hU-QNFrWdpLzN9tWiLRfi09QWCJ6er_x7Y$.

Tiliavir commented 3 years ago

Hi @williamtanner17

It seems your deployment state is somehow corrupted. The error from the log file you provided indicates, that you are still on version 7.0.2, cause in 7.0.3 line 294 is empty:

Can you verify that the deployment was successful?

Best regards Markus

TrooperNo5 commented 3 years ago

Hello there,

we encounter the same behavior. Confluence (Server) is on version 7.10.1 (since January 2021) and the macro says it is on version 7.0.3. How can we verify that the deployment was successful?

Best regards Christian

williamtanner17 commented 3 years ago

We resolved the problem by uninstalling the plugin, clearing the plugin cache, and reinstalling the plugin. A restart of each node is also required as part of clearing the plugin cache.

TrooperNo5 commented 3 years ago

@williamtanner17 Thanks for the hint. It was sufficient for us to clear the plugin cache and restart Confluence. Problem is solved for now.

Best regards Christian

Tiliavir commented 3 years ago

Thank you very much for the update @williamtanner17 and @TrooperNo5!

Glad that the issue is resolved for both of you - I will keep the task open, I think that is worth some kind of documentation in particular since we want to test data center compatibility with #59.

FYI: @culmat