[Ejbca-develop] Problem with the installation of version 6.3.1.1

[Andreas K. <ku...@tr...>]

Hi Folks,

after migrating to the latest version I detected an error in the jboss
server log:

18:18:28,794 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4)
MSC00001: Failed to start service jboss.web.connector.httpspub:
org.jboss.msc.service.StartException in service
jboss.web.connector.httpspub: Failed to start service
    at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
    at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[rt.jar:1.7.0_79]
    at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[rt.jar:1.7.0_79]
    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: java.lang.NoClassDefFoundError:
org/bouncycastle/jce/spec/ECPublicKeySpec
    at
org.bouncycastle.jcajce.provider.asymmetric.ec.KeyFactorySpi.engineGeneratePublic(Unknown
Source)

After switching the version from 6.2.0 to 6.3.1.1 in my provisioning
script and setting up clean system from scratch the mentioned error
occurs. My quick guess is that the BC package in the ejbca.ear is not
yet visible to the https engine? In the old days I usually placed crypto
provider in the endorsed directory of the server ...

Greetings,

Andreas

-- 
Andreas Kühne 
phone: +49 177 293 24 97 
mailto: ku...@tr...

Trustable Ltd. Niederlassung Deutschland Ströverstr. 18 - 59427 Unna Amtsgericht Hamm HRB 5868

Directors Andreas Kühne, Heiko Veit

Company UK Company No: 5218868 Registered in England and Wales