Skip to main content
Question

JAVAX Error When Saving FME Server Automation


pmcpherson
Contributor
Forum|alt.badge.img+9

Am encountering an odd "javax.crypto.IllegalBlockSizeException" error when I try to save an Automation. There seems to be some issue with the associated workflow, however the workflow runs fine by itself, or via a schedule.

Has anyone else encountered something similar?

7 replies

Forum|alt.badge.img+2

Hi @pmcpherson

 

Does the automation save/start if you remove the / from the name?

pmcpherson
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • June 18, 2019

Jennifer,

Am still not sure what the error means exactly, but I was able to relate it to a password published parameter that was not importing correctly from the associated workspace. I was able to get the Automation to save/run by manually overriding that password parameter within the Automation dialog, although it was touchy in that it kept resetting.

Phil


nic_ran
Contributor
Forum|alt.badge.img+16
  • Contributor
  • April 28, 2020

This appears to be a bit of an issue with Automations. From my observations, it would appear that all password entries need to be re-entered any time a change is made to any of the published parameter values for the Automation. So, for example, if I just want to update a non-password parameter, I also need to update all password params. I don't think this should be the default behaviour.


pmcpherson
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • April 28, 2020
nic_ran wrote:

This appears to be a bit of an issue with Automations. From my observations, it would appear that all password entries need to be re-entered any time a change is made to any of the published parameter values for the Automation. So, for example, if I just want to update a non-password parameter, I also need to update all password params. I don't think this should be the default behaviour.

Yes, the problem persists. Hopefully the Safe folks will add it to the bug-fix list for the next release. Thanks for commenting.


jovitaatsafe
Safer
Forum|alt.badge.img+11

Hi @nic_ran and @pmcpherson,

It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads

 

 

Please give that a try and let us know how it goes for you!

pmcpherson
Contributor
Forum|alt.badge.img+9
  • Author
  • Contributor
  • May 5, 2020
jovitaatsafe wrote:

Hi @nic_ran and @pmcpherson,

It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads

 

 

Please give that a try and let us know how it goes for you!

Jovita,

I've upgraded to FME Server 2020.0.1 and so far the error has not reappeared. Will advise if it shows up again. Thanks.

Phil


nic_ran
Contributor
Forum|alt.badge.img+16
  • Contributor
  • May 22, 2020
jovitaatsafe wrote:

Hi @nic_ran and @pmcpherson,

It looks like this error message, tracked in an internal issue as (FMESERVER-14633), has been resolved for FME 2020.0.1 in the latest release, which can be downloaded here: safe.com/downloads

 

 

Please give that a try and let us know how it goes for you!

That's great news. Unfortunately, I don't have simple access to install a newer version of FME Server but will try to test it soon...


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings