Re: iSphere source file search

Matt,

Can you create a new workspace and execute the steps to get the "The Connection does not exist" error and send it as a zip file to me?

Please do not use a TCP/IP address for the host name in the remote system connection. Use a DNS name instead. You may consider to use "isphere" and update your hosts file to point to the actual address.

Then I could do the same on my PC in order to keep your workspace unchanged when debugging it.

E.g: c:\Windows\System32\drivers\etc\hosts

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
230.175.10.23 isphere

Please also write down the steps you took to produce the error starting from the point of creating the workspace.

Regards,

Thomas.

Am 19.10.2021 um 16:31 schrieb Matt Hopkins:

Hello,

Well it happened again. I am getting "The Connection does not exist"
message again. I have tried all the tricks.. New workspace, update the
.ini, clear the Xshareclasses: cache, reboot.....

Nothing is working now. I don't know what else to try.

Any other suggestions?

Thanks, Matt

On Wed, Oct 6, 2021 at 12:43 AM Thomas Raddatz <thomas.raddatz@xxxxxx>
wrote:

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:

Hi Matt,

So it worked after having changed the ini file, yesterday? And it is

broken again, today? Strange!

The point is, that iSphere did first get a JDBC connection and could

create a JDBC statement but could not execute it (SearchElement.java:150).

The other errors at SearchElement.java:149 must be a result of the first

error that resetted (I assume closed) the connection.

Did you already try (testwise) a new workspace with a new connection? If

not, may you try that?

Thomas.