Weasis deployment failed on dcm4chee-arc 5.16.1 Wildfly 16

[leogrande]

Ubuntu 18.04

Wildfly 16.0

Keycloak 5.0.0.

Weasis 3.0.4

dcm4chee-arc-5.16.1-psql-secure-ui

Deployment of weasis.war and weasis-pacs-connector.war failed

Only weasis-i18n.war was successfully deployed.

[leogrande]

Is it only me?

Hey, developers!

My dcm4chee-arc deployment depends on Weasis, I can't move on with upgrades.

It would be nice to hear from you.

Thanks.

[vrinda...@j4care.com]

Issue is not reproducible.

10:39:08,583 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "dcm4chee-arc-ear-5.16.1-psql-secure-ui.ear" (runtime-name : "dcm4chee-arc-ear-5.16.1-psql-secure-ui.ear")
10:39:15,701 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/vrinda/work/wildfly-16.0.0.Final/standalone/data/content/73/ffb26fe8cb88b47f9b4590a313a796755d8b38/content
10:39:15,704 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "weasis-pacs-connector.war" (runtime-name: "weasis-pacs-connector.war")
10:39:15,957 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,957 [ead Pool -- 196] INFO  o.w.s.ManifestManager     Start the manifest manager running as a background process
10:39:15,959 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,959 [ead Pool -- 196] INFO  o.w.s.ManifestManager     Server info: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) - 2.0.19.Final
10:39:15,961 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,961 [ead Pool -- 196] INFO  o.w.s.ManifestManager     Default configuration: vfs:/content/weasis-pacs-connector.war/WEB-INF/classes/weasis-connector-default.properties
10:39:15,963 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,962 [ead Pool -- 196] INFO  o.w.s.ManifestManager     Archive configuration: vfs:/content/weasis-pacs-connector.war/WEB-INF/classes/dicom-dcm4chee.properties
10:39:15,963 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,963 [ead Pool -- 196] INFO  o.w.s.ManifestManager     Default jnlp template: file:/home/vrinda/work/wildfly-16.0.0.Final/standalone/tmp/vfs/temp/temp54dc8f17bb416df5/content-80fff3ecc6b7db48/weasis.jnlp
10:39:15,965 INFO  [stdout] (ServerService Thread Pool -- 196) 2019-04-23 10:39:15,965 [ead Pool -- 196] INFO  o.w.s.ManifestManager     ManifestManagerThread configuration (maxLifeCycle=300s, cleanFrequency=60s)
10:39:15,966 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 196) WFLYUT0021: Registered web context: '/weasis-pacs-connector' for server 'default-server'
10:39:15,978 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "weasis-pacs-connector.war" (runtime-name : "weasis-pacs-connector.war")
10:39:22,770 INFO  [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /home/vrinda/work/wildfly-16.0.0.Final/standalone/data/content/8a/731d2e936a96bf2694cb595d6378ea7323f042/content
10:39:22,773 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "weasis.war" (runtime-name: "weasis.war")
10:39:23,128 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 196) WFLYUT0021: Registered web context: '/weasis' for server 'default-server'
10:39:23,138 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "weasis.war" (runtime-name : "weasis.war")

What do you see in the server.log?

[leogrande]

I have sent  a server.log privately.

That was Oracle OpenJDK environment.

[vrinda...@j4care.com]

Didn't receive any! You may attach the log here too.

[leogrande]

I have just successfully deployed Weasis on Wildfly 16 after switching to Oracle Java JDK 1.8

It looks like OpenJDK caused these problems.

So now, I guess, I need to prepare for Oracle Java JDK subscription.

[Nicolas Roduit]

In my opinion, there is no reason to install the Oracle JDK instead of the OpenJDK.

[leogrande]

This is what I have experienced. I do not recommend anything to anyone. What I know is that my 5.16.0 stopped working after some OpenJDK upgrade. Switching back to Oracle JDK 8 helped me with both, 5.16.0 deployment then and Weasis on 5.16.1 now.

It doesn't look very encouraging when an application in production depends on Java updates which can easily ruin it. Again, it is what I have experienced.

In my experience, Oracle JDK never caused any issues (and nevertheless, I still hate their new licensing).

[Gunter Zeilinger]

Compare the build number of your Oracle JDK 8 and OpenJDK. I remember some issues with 8u181 on Debian - but deployment never failed.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at https://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[leogrande]

Oracle JDK 1.8.0_201-b09 - works

OpenJDK 11.0.2+9-3ubuntu1~18.04.3 - doesn't work

It looks like this OpenJDK upgrade/update caused deployment issues:

The latest package that worked was:

10.0.2+13-Ubuntu-1ubuntu0.18.04.4

it was upgraded (automatically) to:

11.0.2+9-Ubuntu-3ubuntu118.04.3  - which failed

I will try an official OpenJDK 12 package for the test purposes only, the distro's package would be preferable (easy updates, not like one described in this post, of course :)).

So this is the reason why I will be using Oracle Java, at least for now.

On Wednesday, April 24, 2019 at 7:51:07 AM UTC-4, gunterze wrote:

Compare the build number of your Oracle JDK 8 and OpenJDK. I remember some issues with 8u181 on Debian - but deployment never failed.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm...@googlegroups.com.

[Gunter Zeilinger]

I successfully tested OpenJDK build 11.0.2+9 on Ubuntu 18.10 and Debian 9.8.

On Wed, Apr 24, 2019 at 11:36 PM leogrande <leon....@gmail.com> wrote:

Oracle JDK 1.8.0_201-b09 - works

OpenJDK 11.0.2+9-3ubuntu1~18.04.3 - doesn't work

It looks like this OpenJDK upgrade/update caused deployment issues:

The latest package that worked was:

10.0.2+13-Ubuntu-1ubuntu0.18.04.4

it was upgraded (automatically) to:

11.0.2+9-Ubuntu-3ubuntu118.04.3  - which failed

I will try an official OpenJDK 12 package, though the distro's package would be preferable (updates).

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.

[leogrande]

I have just test OpenJDK 12.0.1 from the official package.

I have set java, javac, jre alternatives to openjdk-12.0.1

After initial wildfly restart I got these errors:

2019-04-25 09:20:27,785 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-1) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task org.dcm4chee.arc.ian.scu.IANScheduler@72a3ab26 as container is suspended
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:164)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:835)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:85)

2019-04-25 09:20:27,836 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-2) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task org.dcm4chee.arc.export.mgt.impl.ExportScheduler@11e9abbb as container is suspended
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:164)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:835)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:85)

2019-04-25 09:20:27,928 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-1) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task org.dcm4chee.arc.audit.AuditScheduler@524c272f as container is suspended
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.ControlPointUtils$ControlledScheduledRunnable.run(ControlPointUtils.java:164)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.access$201(ManagedScheduledThreadPoolExecutor.java:383)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.internal.ManagedScheduledThreadPoolExecutor$ManagedScheduledFutureTask.run(ManagedScheduledThreadPoolExecutor.java:534)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:835)
    at org.glassfish.javax.enterprise.concurrent//org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250)
    at org.jbo...@16.0.0.Final//org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:85)

I do not know whether these errors are deployment related or not, at least they are listed after:

2019-04-25 09:19:27,989 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-1) Start TCP Listener on /0.0.0.0:2575
2019-04-25 09:19:28,024 INFO  [org.dcm4che3.net.Connection] (EE-ManagedExecutorService-default-Thread-2) Start TCP Listener on /0.0.0.0:11112

But after several subsequent restarts those errors were not recorded.

It looks good for now, let's see what happens.

Gunter, I do not know which package have you tested:

openjdk-11.0.2_linux-x64_bin.tar.gz (official)

or

OpenJDK 11.0.2+9-3ubuntu1~18.04.3 (Canonical)

I am not an expert and can't say for sure that they are different. But anyway, I will stick with OpenJDK 12 from the official package. At least, I will not depend on Canonical guys.

Although those above mentioned errors make me a little bit nervous. I will keep Oracle JDK as a reliable backup.

[Gunter Zeilinger]

I am using

ii  openjdk-11-jdk:amd64                           11.0.2+9-3ubuntu1~18.10.3    amd64                        OpenJDK Development Kit (JDK)
ii  openjdk-11-jdk-headless:amd64                  11.0.2+9-3ubuntu1~18.10.3    amd64                        OpenJDK Development Kit (JDK) (headless)
ii  openjdk-11-jre:amd64                           11.0.2+9-3ubuntu1~18.10.3    amd64                        OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-11-jre-headless:amd64                  11.0.2+9-3ubuntu1~18.10.3    amd64                        OpenJDK Java runtime, using Hotspot JIT (headless)

provided by Ubuntu 18.10.

2019-04-25 09:20:27,836 ERROR [org.jboss.as.ee] (EE-ManagedScheduledExecutorService-default-Thread-2) WFLYEE0110: Failed to run scheduled task: java.lang.IllegalStateException: WFLYEE0111: Cannot run scheduled task org.dcm4chee.arc.export.mgt.impl.ExportScheduler@11e9abbb as container is suspended

=> Wildfly is going down, caused by a previous event/failure.

To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.