dcm4chee-arc-light 5.10.1 released

349 views
Skip to first unread message

gunterze

unread,
Apr 27, 2017, 11:04:01 AM4/27/17
to dcm4che

Antonio Gomez

unread,
Apr 27, 2017, 2:39:55 PM4/27/17
to dcm4che
Hi, I have upgraded to this version, but when I deploy gives an error:

[standalone@localhost:9990 /] deploy /opt/dcm4chee-arc-5.10.1-mysql-secure-ui/deploy/dcm4chee-arc-ear-5.10.1-mysql-secure-ui.ear
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"dcm4chee-arc-ear-5.10.1-mysql-secure-ui.ear\".\"dcm4chee-arc-service-5.10.1.jar\".component.ArchiveServiceImpl.START" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"dcm4chee-arc-ear-5.10.1-mysql-secure-ui.ear\".\"dcm4chee-arc-service-5.10.1.jar\".component.ArchiveServiceImpl.START: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
    Caused by: java.lang.IllegalStateException: WFLYEE0042: Failed to construct component instance
    Caused by: javax.ejb.EJBException: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.dcm4chee.arc.impl.ArchiveDeviceProducer.init() on org.dcm4chee.arc.impl.ArchiveDeviceProducer@4b217668
    Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke private void org.dcm4chee.arc.impl.ArchiveDeviceProducer.init() on org.dcm4chee.arc.impl.ArchiveDeviceProducer@4b217668
    Caused by: java.lang.reflect.InvocationTargetException
    Caused by: javax.enterprise.inject.CreationException
    Caused by: org.dcm4che3.conf.api.ConfigurationException: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]
    Caused by: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.subunit.\"dcm4chee-arc-ear-5.10.1-mysql-secure-ui.ear\".\"dcm4chee-arc-service-5.10.1.jar\".component.ArchiveServiceImpl.START"],"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined}}}


El jueves, 27 de abril de 2017, 17:04:01 (UTC+2), gunterze escribió:

Release 5.10.1

gunterze

unread,
Apr 27, 2017, 2:54:43 PM4/27/17
to dcm4che
Caused by: org.dcm4che3.conf.api.ConfigurationException: javax.naming.AuthenticationException: [LDAP: error code 49 - Invalid Credentials]

=> The value of java.naming.security.principal=<ldap-user> or java.naming.security.credentials=<ldap-password> in $DCM4CHEE_HOME/standalone/configuration/dcm4chee-arc/ldap.properties does not match user/password of your LDAP server.

Paolo Marcheschi

unread,
Apr 28, 2017, 8:22:20 AM4/28/17
to dcm4che
Great,
Thank you

It's time to try the docker  upgrade process !!

Paolo

On Thursday, April 27, 2017 at 5:04:01 PM UTC+2, gunterze wrote:

Release 5.10.1

Márcio Farias

unread,
Apr 30, 2017, 11:34:13 AM4/30/17
to dcm4che
I have this error

12:25:32,569 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 87) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./dcm4chee-arc/ui: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./dcm4chee-arc/ui: java.lang.RuntimeException: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.run(FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)
    at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: java.lang.RuntimeException: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    at org.keycloak.adapters.KeycloakDeploymentBuilder.internalBuild(KeycloakDeploymentBuilder.java:67)
    at org.keycloak.adapters.KeycloakDeploymentBuilder.build(KeycloakDeploymentBuilder.java:142)
    at org.keycloak.adapters.undertow.KeycloakServletExtension.handleDeployment(KeycloakServletExtension.java:135)
    at io.undertow.servlet.core.DeploymentManagerImpl.handleExtensions(DeploymentManagerImpl.java:255)
    at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:159)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100)
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
    ... 6 more
Caused by: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    at org.keycloak.common.util.PemUtils.decodePublicKey(PemUtils.java:84)
    at org.keycloak.adapters.KeycloakDeploymentBuilder.internalBuild(KeycloakDeploymentBuilder.java:63)
    ... 12 more
Caused by: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    at org.bouncycastle.jcajce.provider.asymmetric.util.BaseKeyFactorySpi.engineGeneratePublic(Unknown Source)
    at org.bouncycastle.jcajce.provider.asymmetric.rsa.KeyFactorySpi.engineGeneratePublic(Unknown Source)
    at java.security.KeyFactory.generatePublic(KeyFactory.java:328)
    at org.keycloak.common.util.DerUtils.decodePublicKey(DerUtils.java:66)
    at org.keycloak.common.util.PemUtils.decodePublicKey(PemUtils.java:82)
    ... 13 more


12:25:39,288 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "dcm4chee-arc-ear-5.10.1-mysql-secure-ui.ear")]) - failure description: {
    "WFLYCTL0080: Failed services" => {"jboss.undertow.deployment.default-server.default-host./dcm4chee-arc/ui" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./dcm4chee-arc/ui: java.lang.RuntimeException: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    Caused by: java.lang.RuntimeException: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    Caused by: org.keycloak.common.util.PemException: java.security.spec.InvalidKeySpecException: encoded key spec not recognised
    Caused by: java.security.spec.InvalidKeySpecException: encoded key spec not recognised"},
    "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.deployment.default-server.default-host./dcm4chee-arc/ui"],

    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined


12:25:40,798 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 64027ms - Started 2674 of 3145 services (3 services failed or missing dependencies, 813 services are lazy, passive or on-demand)



Em quinta-feira, 27 de abril de 2017 12:04:01 UTC-3, gunterze escreveu:

Release 5.10.1

Marko

unread,
May 13, 2017, 7:01:50 AM5/13/17
to dcm4che
I have the same problem.
I have changed the content of ldap.properties however I still get the ldap authentication error. 
The content of the file is:

cat /opt/dcm4chee-arc-light/wildfly-10.1.0.Final/standalone/configuration/dcm4chee-arc/ldap.properties 

java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory
java.naming.ldap.attributes.binary=dicomVendorData
java.naming.provider.url=ldap://localhost:389/dc=dcm4che,dc=org
java.naming.security.principal=cn=admin,dc=dcm4che,dc=org
java.naming.security.credentials=mypassword

I'm able to connect to LDAP from various clients using this credentials.

Marko

unread,
May 13, 2017, 2:18:17 PM5/13/17
to dcm4che
I restarted a clean install and is working ok
I think it was because weasis.war and weasis-pacs-connector.war were in the deploy directory
Reply all
Reply to author
Forward
0 new messages