Problem in pixel graphic rendering

[Former Member]

Hello everybody,

We have updated our Java Version to J2RE 1.4.2 IBM build j9xa64142ifx-20090728 (SR13) recently and since this update I get an error message when I try to render a pixel graphic from an svg file using an animation renderer action block. In the web page the error message is

javax.imageio.ImageTypeSpecifier (initialization failure)

When I run the transaction directly I get the following error immediately after starting the transaction.

[ERROR]: Server returned HTTP response code: 500 for URL: http://mitdb01a.egger.com:50000/XMII/Runner

Any idea how to get rid of this?

Kind Regards,

Matthias

[Former Member · Accepted solution]

Do you have a monitor and graphics system active on this server? If not, you might need to use the Java "headless" VM option...Google around for it.

[Former Member · Accepted solution]

Hello Rick,

we have already had an issue with the headless option quite some time ago; this option is (still) set properly. I'm a bit puzzled because of the second error message when I run the transaction in the workbench. How does the runner service come in when calling a transaction directly in the workbench?

Kind Regards,

Matthias

[Former Member · Accepted solution]

Hi, Matthias.

Assuming that it runs the same way it did when I was involved with MII, the Workbench saves a temporary copy of the transaction on the server, then invokes it and captures the log. We originally did this so that all of the logic runs from the "server" point of view (e.g. file paths, proxy servers, etc...).

It definitely sounds like some type of JVM/configuration issue, or perhaps even a JVM bug.

Rick

[Former Member · Accepted solution]

Hello Rick.

Thank you for your additional information. I have created an SAP support message to get further information on this issue, I'll post further details as soon as they are available.

Best Regards,

Matthias

[Former Member · Accepted solution]

Hello everybody,

this was a strange issue caused by the update of the java version. Finally, a restart solved the problem.

Best Regards,

Matthias