|
Hi Matt,
You should be able to put the ini change back to ist original state,
because the problem did not seem to be related to the Java cache issue.
Thomas.
-----Ursprüngliche Nachricht-----
Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Matt
Hopkins
Gesendet: Dienstag, 5. Oktober 2021 19:39
An: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Betreff: Re: [WDSCI-L] iSphere source file search
I hadn’t done that yet, so, yes, a new workspace fixed the issue.
Currently have the ini fix in place. Should I be able to put the ini file
back to it’s original state?
Matt Hopkins
On Oct 5, 2021, at 12:55 PM, Tools/400 <thomas.raddatz@xxxxxxxxxxx>wrote:
broken again, today? Strange!
Hi Matt,
So it worked after having changed the ini file, yesterday? And it is
create a JDBC statement but could not execute it (SearchElement.java:150).
The point is, that iSphere did first get a JDBC connection and could
error that resetted (I assume closed) the connection.
The other errors at SearchElement.java:149 must be a result of the first
not, may you try that?
Did you already try (testwise) a new workspace with a new connection? If
Thomas.
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.