× 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.



Hi Kevin,

That are interesting news, because the iSphere Spooled File Search uses SQL to read the list of spooled files from file [ISPHERE_LIBRARY]/SPLF. When I add a breakpoint to the statement where the JDBC connection field is first used and set that variable to null, I get the "%1" result! Sadly I cannot investigate the problem with a true Kerberos connection, because I have no environment using Kerberos at my hands.

So it could be, that the following Java statement does not return a JDBC connection usuable with Kerberos:

jdbcConnection = IBMiConnection.getConnection(getHost()).getJDBCConnection(null, false);

The complete code block looks like this:


public Connection getToolboxJDBCConnection() {
Connection jdbcConnection = null;
try {
jdbcConnection = IBMiConnection.getConnection(getHost()).getJDBCConnection(null, false);
} catch (SQLException e) {
}
return jdbcConnection;
}

Your error log does not contain any iSphere related messages except for that iSphere could not connect to the update server (SourceForge).

Regards,

Thomas.

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Arco Simonse
Gesendet: Freitag, 19. Januar 2018 11:49
An: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Betreff: Re: [WDSCI-L] Is iSphere plugin going to support Kerberos?

Hi Kevin and Thomas,

I do see the same %1 behavior for the iSphere spoolfiles component when Kerberos is activated.
The iSphere Source File Search is also not opening the search window then.
However, iSphere Compare Editor and iSphere Messages do work.

When I switch off Kerberos and restart the workbench all the components do work, Just not with Kerberos.
Below is the RDI errorlog. It is producing the same log entries even if Kerberos is switched on or off.

Best regards,
-Arco


!SESSION 2018-01-19 11:31:36.135
-----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.8.0 IBM J9 2.8 Windows 10 amd64-64 Compressed References 20170722_357405 (JIT enabled, AOT enabled) J9VM - R28_20170722_0201_B357405 JIT - tr.r14.java_20170722_357405
GC - R28_20170722_0201_B357405_CMPRSS
J9CL - 20170722_357405
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en Framework arguments: -product com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ibm.rational.developer.ibmi.product.ide

!ENTRY org.eclipse.core.resources 2 10035 2018-01-19 11:31:39.512 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.jface 2 0 2018-01-19 11:31:41.455 !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2018-01-19 11:31:41.455 !MESSAGE A conflict occurred for CTRL+SHIFT+C:
Binding(CTRL+SHIFT+C,
ParameterizedCommand(Command(com.ibm.etools.rse.ui.compile.category.CompileMultipleCommand,Compile,
,
Category(com.ibm.etools.iseries.rse.ui.keybinding,IBM i,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@c584cde8,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+SHIFT+C,
ParameterizedCommand(Command(org.eclipse.externaltools.compareWithLatest,Compare
With Latest,
,
Category(org.eclipse.externaltools.commandcategory,Compare With Latest,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@493fa8d2,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2018-01-19 11:31:41.455 !MESSAGE A conflict occurred for CTRL+SHIFT+A:
Binding(CTRL+SHIFT+A,
ParameterizedCommand(Command(org.eclipse.pde.ui.openPluginArtifact,Open
Plug-in Artifact,
Open a plug-in artifact in the manifest editor,
Category(org.eclipse.ui.category.navigate,Navigate,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7010ac3,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(CTRL+SHIFT+A,
ParameterizedCommand(Command(com.ibm.etools.iseries.rse.ui.keybinding.openmbr,Open
an IBM i member in editor ,
,
Category(com.ibm.etools.iseries.rse.ui.keybinding,IBM i,null,true),
org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@22d26b4d,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)

!ENTRY com.ibm.etools.iseries.rse.ui 1 0 2018-01-19 11:31:42.439 !MESSAGE Rational Developer for i product plugin version
9.6.1.v20171205_1645

!ENTRY biz.isphere.core 4 4 2018-01-19 11:31:47.618 !MESSAGE Failed to connect to iSphere update server.
!STACK 0
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure at com.ibm.jsse2.k.a(k.java:17) at com.ibm.jsse2.k.a(k.java:3) at com.ibm.jsse2.at.b(at.java:49) at com.ibm.jsse2.at.a(at.java:573) at com.ibm.jsse2.at.i(at.java:73) at com.ibm.jsse2.at.a(at.java:357) at com.ibm.jsse2.at.startHandshake(at.java:723)
at com.ibm.net.ssl.www2.protocol.https.c.afterConnect(c.java:215)
at com.ibm.net.ssl.www2.protocol.https.d.connect(d.java:34)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1561)
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1489)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:491)
at com.ibm.net.ssl.www2.protocol.https.b.getResponseCode(b.java:80)
at
biz.isphere.core.internal.SearchForUpdates.followRedirects(SearchForUpdates.java:182)
at
biz.isphere.core.internal.SearchForUpdates.followRedirects(SearchForUpdates.java:186)
at biz.isphere.core.internal.SearchForUpdates.run(SearchForUpdates.java:85)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY com.ibm.etools.stacktool 0 0 2018-01-19 11:31:47.730 !MESSAGE plugin is early starting...

!ENTRY com.ibm.etools.stacktool 0 0 2018-01-19 11:31:47.740 !MESSAGE Save the stack tool properties file.

!ENTRY org.eclipse.ui 2 2 2018-01-19 11:31:48.097 !MESSAGE Invalid preference category path: modeling.diagram.appearance.misc
(bundle: com.ibm.xtools.rmp.ui.diagram, page:
com.ibm.xtools.rmp.ui.preferences.SelectionFeedbackPreferencePage)

2018-01-13 19:10 GMT+01:00 Tools/400 <thomas.raddatz@xxxxxxxxxxx>:

Kevin,

Honestly I do not know what I should have to do, to make iSphere
supporting Kerberos.

iSphere utilizes IBMiConnection and AS400, which are classes shipped
with RDi/WDSC.

Hence I assumed, that iSphere should be able to support Kerberos, as
long as Kerberos is supported by
"com.ibm.etools.iseries.subsystems.qsys.api.IBMiConnection" and
"com.ibm.as400.access.AS400".

Thomas.


--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.