Bug 977231
| Summary: | java.lang.ClassNotFoundException: org.bouncycastle.jce.provider.BouncyCastleProvider during server startup | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Pavel Macik <pmacik> | ||||||
| Component: | EAP | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Len DiMaggio <ldimaggi> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 | CC: | ganandan, ldimaggi, soa-p-jira | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 6.1.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2025-02-10 03:28:00 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Pavel Macik
2013-06-24 06:36:22 UTC
The SOA version is 6.0.0.DR6 Created attachment 764457 [details]
Full server log
Attached the server log.
I've asked Eric to take a quick look and see what steps are missing as it seems to be related to the SSO. It doesn't look like this is a direct consequence of the SSO integration, taking it back to investigate Marking this as Alpha2 Blocker - not due to immediate functional impact - but we need to understand the impact before we ship alpha2 I have been trying to reproduce this locally and have failed using JDK 6 and JDK 7. What environment was this seen in? From the log it would appear to be a linux system running jdk1.7.0_25-x86_64. I was only able to reproduce this problem by setting the logging level to DEBUG - even though the log messages related to BoucnyCastle are at the ERROR level. See attached server.log This was on RHEL6 with OpenJDK 1.7 Created attachment 766277 [details]
Server log - DEBUG level
This comes from the picketlink codebase and can be ignored by SOA. The error message is also misleading as it is logged at ERROR level even though it is guarded by a check for DEBUG.
In ProvidersUtil.ensure
addJceProvider("BC", "org.bouncycastle.jce.provider.BouncyCastleProvider");
In ProvidersUtil.addJceProvider
try {
// Class<? extends Provider> clazz = Loader.loadClass(className, false, Provider.class);
Class<? extends Provider> clazz = Class.forName(className).asSubclass(Provider.class);
Provider provider = clazz.newInstance();
return addJceProvider(name, provider);
} catch (Throwable t) {
if (logger.isDebugEnabled()) {
logger.jceProviderCouldNotBeLoaded(name, t);
}
return null;
}
In PicketLinkLoggerMessages
@LogMessage(level = Level.ERROR)
@Message(id = 259, value = "The provider %s could not be added")
void jceProviderCouldNotBeLoaded(String name, @Cause Throwable t);
I forgot the comment from the ensure method
// register BC provider if available (to have additional encryption algorithms, etc.)
addJceProvider("BC", "org.bouncycastle.jce.provider.BouncyCastleProvider");
Reported in PicketLink/EAP This should not be an Alpha2 blocker Kevin will verify if it's in the current release or not. Fixed in PicketLink 2.5.3.Final This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |