Editing this file:/usr/IBM/WebSphere/AppServer/java/8.0/jre/lib/security/java.securityAs described in the link above solved it.

Apparently this can be solved by adding MD5 on java:That's why you asked the jdk version?Re: JsafeJCE provider is disabled

Java version = 1.8.0_151, Java Runtime Version = 8.0.5.7 - pap6480sr5fp7-20171216_01(SR5 FP7), Java Compiler = j9jit29, Java VM name = IBM J9 VMIt's running on Websphere 9.It's the JEE version

Hello,app server:cluster, topology2 application servers, 1 clusterdb:DB2 V11.1OS:AIX 7200-02-01-1731When invoking the SignatureService I get the following error:Error Calling SignatureServicecom.adobe.livecycle.signatures.service.impl.DSSConfigurationHelper (initialization failure)java.lang.Security...

increasing to 300k improved perfomance, now it runs under the 12 minutes...  it is a single document with 51 pages.but still a lot slower than server 2...I found that the CPU is different, could be the cause. I'm not the one who configured the servers... so that came as a surprise...

will change to 307k and check what happens.we have a clustered environment with one application target each. I'm invoking via webservice a process that uses the OutputService.found out a moment ago that server 1 is much slower than the server 2... server 1 takes at least twice the time...it runs sus...

Found this:Performance Tuning Tips for Faster LiveCycle Output | Adobe LiveCycle BlogWill try to increase the max document inline size and see what happens.I already have the BMC.POOL_MAX configured

Hello,I'm trying to improve the OutputService performance.last month I had a problem that was solved by increasing timeout to 420, but this month I have a document to generate who is a ~50% bigger than the last one.I increased to 720 seconds, It is taking longer than 720 seconds. I could keep increa...

it worked thanks

It worked thanks