×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
You can go headless, as Pete suggests or load NAWT (native abstract windowing toolkit) as someone else suggested. The DISPLAY environment variable goes with NAWT and specifies which of 99 VNC windows to use. VNC must be running in another job. See
https://www.ibm.com/support/knowledgecenter/mobile/#!/ssw_ibm_i_71/rzaha/nawtinstall14full.htm
POI uses abstract windows to render text and other graphics.
<div>-------- Original message --------</div><div>From: Pete Helgren <pete@xxxxxxxxxx> </div><div>Date:03/21/2016 4:50 PM (GMT-06:00) </div><div>To: Java Programming on and around the IBM i <java400-l@xxxxxxxxxxxx> </div><div>Subject: Re: POI HSSF Windows Server X11 error resolved </div><div>
</div>I can't say for sure but I thought you needed to run them headless when
it is looking for an X Windows entry. Something like:
ADDENVVAR ENVVAR(QIBM_RPG_JAVA_PROPERTIES) +
VALUE('-Djava.awt.headless=true;+
-Dos400.awt.native=true;') +
REPLACE(*YES)
Not sure about your environment but I have used entries like this (in CL
and Shells) to get past the DISPLAY problem.
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
On 3/21/2016 11:58 AM, Darren Strong wrote:
We're currently running the Jakarta POI HSSF Excel generation java methods,
version 3.10.1. I attempted to replace this with the current version,
which is 3.14. Identical programs on different IBM i servers reacted
differently to this upgrade. Some worked as on the previous version, but
our production server blew up on an error about Windows Server X11 could
not be located. I found that some other install had created an environment
variable "DISPLAY" with an attribute of "localhost:10" on the production
server. Removing this environment variable let the new version (3.14) work
correctly. This DISPLAY variable has something to do with defining a
display device to Java, which I presume does not exist for an IBM i job
running in batch.
I'm posting this for someone else that may have experienced a similar
issue, so that it might help you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.