Siebel Webservices Connection Not Working - Search Very Slow (Doc ID 1676505.1)

Last updated on JANUARY 03, 2017

Applies to:

Oracle Knowledge - Version 8.4.2.1 and later
Information in this document applies to any platform.

Goal

Siebel search relies on a working Siebel Webservices Connection from each Oracle Knowledge Search runtime.  The webservices and the Siebel connection information are set up at install time.  If the connection is not working the search will be very slow because the connection is timing out.  In the runtime instance logs you will find these messages.

On Demand Session Refresh Start @Fri May 23 09:30:00 CEST 2014
On Demand Session Refresh End @Fri May 23 09:30:00 CEST 2014
[GC 578025K->296482K(1339584K), 0.0193014 secs]
*** WARNING: Referenced IM document (TR144:TROUBLESHOOTERS/@TITLE) wasn't found for specified language (English)!  Cause = Could not authenticate user with the supplied information. Information supplied may be incorrect or user account may be locked or inactive
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
On Demand Session Refresh Start @Fri May 23 09:35:00 CEST 2014
On Demand Session Refresh End @Fri May 23 09:35:00 CEST 2014
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
- I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect
- Retrying request
- Unable to sendViaPost to url[https://<seibel_test_environment>/eai_enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute&UserName=*****&Password=*******]
java.net.ConnectException: Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:550)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

What connection information has to be set up for Siebel search to work?
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms