weasis 3.8 timestamp error on dcm4chee2.18

27 views
Skip to first unread message

AKS

unread,
Jul 6, 2025, 5:30:13 AM7/6/25
to dcm4che
Dear All,
Any workaround for solving the repeated error coming on the following setup.
It starts as an info but overtime the manifest file stops getting generated.
Any idea what could be causing this??

RHEL 7.9
Dcm4chee 2.18
Weasis 3.8.1 (not standalone. as war in server)
Java "1.8.0_211" 64 bit

Error:

[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weasis]] org.tuckey.web.filters.urlrewrite.substitution.VariableReplacer ERROR: function ${build.timestamp} type 'build.timestamp' not a valid type

 [STDOUT] INFO  o.w.s.JnlpLauncher        Build JNLP from template = weasis.jnlp and with arguments = [cdb=http://xx.xx.xx.xx:8080/weasis, substance.version=1.9.2, src=file:dcm4chee/server/default/tmp/deploy/tmp5284457198731213000weasis-pacs-connector-exp.war/weasis.jnlp, patientID=[Ljava.lang.String;@679963bc, accessionNumber=[Ljava.lang.String;@1d755065, svr=http://xx.xx.xx.xx:8080, app.version=3.8.1, ihs=128m, felix.framework.version=7.0.3, jnlp.jar.version=true, mhs=768m, cdb-ext=http://xx.xx.xx.xx:8080/weasis-ext]
[STDOUT] ERROR o.w.s.RequestManifest     Building Manifest Exception [id=4256]
java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:205)
at org.weasis.servlet.RequestManifest.doGet(RequestManifest.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

AKS

unread,
Jul 6, 2025, 6:14:49 AM7/6/25
to dcm4che
Find attached the urlrewrite.xml of the version
urlrewrite.xml
Reply all
Reply to author
Forward
0 new messages