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

class com.baloise.confluence.digitalsignature.Signature cannot be cast to class #70

Closed
maxiestudies opened this issue May 4, 2021 · 7 comments
Assignees

Comments

@maxiestudies
Copy link

I'm getting this error message when trying to render the signatures:

class com.baloise.confluence.digitalsignature.Signature cannot be cast to class com.baloise.confluence.digitalsignature.Signature (com.baloise.confluence.digitalsignature.Signature is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @5f3f362b; com.baloise.confluence.digitalsignature.Signature is in unnamed module of loader org.apache.felix.framework.BundleWiringImpl$BundleClassLoader @59a0ac3)

The plugin worked fine until today, we didn't do any updates (Confluence or plugin).
We are using the Version 7.0.3 of the plugin and version 7.10.2 for Atlassian Confluence.

@Tiliavir
Copy link
Member

Hi @maxiestudies

Please refer to this Issue: #68.
Are you using the Data Center version as well? In that case you might have to invalidate the plugin cache.

Best regars
Markus

@Tiliavir Tiliavir self-assigned this May 10, 2021
@maxiestudies
Copy link
Author

worked like charm, thank you!

@MarekChladny
Copy link

Hi,
I am having a similar issue with digital-signature. After the Confluence upgrade to the version 7.13.1, all occurrences of the digital-signature display the error:

com.baloise.confluence.digitalsignature.Signature cannot be cast to com.baloise.confluence.digitalsignature.Signature

The version of digital-signature is 7.0.3

I would like to try invalidating the plugin cache. My question is, can I do it only for the digital-signature plugin? Or can I invalidate the cache only for all our Confluence plugins using this method?

Thank you.

Marek

@Tiliavir
Copy link
Member

Hi @MarekChladny

Plugin cache of digital-signature should be sufficient.

Best regards
Markus

@MarekChladny
Copy link

Hi @Tiliavir ,
Would you mind explaining please how to remove the cache of just the digital-signature plugin, and preferably without stopping the Confluence service?
Thanks

Marek

@Tiliavir
Copy link
Member

Hi @MarekChladny

sorry I was wrong with that - just had a look into the Readme and attached issue where it states

Using Confluence Data Center Version
Digital-signature can be used on Confluence Data Center, however it is not yet officially tested and approved. When performing an update you might have to invalidate the plugin cache and restart Confluence. For details refer to #68.

and more importantly this comment on the referenced issue #68 (comment):

williamtanner17 commented on 21 Apr
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.

Sorry for the confusion and inconvenience. Unfortunately we are not (yet) migrated to DC and therefore the urge to push compatibility for this plugin is not too big. Hope I can address this issue with #72

Best regards
Markus

@MarekChladny
Copy link

Hi @Tiliavir ,

We have the server license for Confluence, not the data center. Anyway, I stopped the Confluence service last night, cleared the cache for all plugins and then started the service. The digital-signature plugin then started working just fine.

Thanks for the support.

Have a nice day.
Marek

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

3 participants