ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » oAuth V2: SSL socket operation / IIB 10.0.0.3

Post new topic  Reply to topic
 oAuth V2: SSL socket operation / IIB 10.0.0.3 « View previous topic :: View next topic » 
Author Message
firoj.badsa
PostPosted: Mon Jun 19, 2017 12:42 pm    Post subject: oAuth V2: SSL socket operation / IIB 10.0.0.3 Reply with quote

Centurion

Joined: 16 Feb 2007
Posts: 104

We are using OAuthV2.0 for client authentication. And the connectivity was working fine for last couple of months. Suddenly we started getting below error in logs. It works intermittently. Sometimes restarting broker fixing the issue.. but it comes back again after some time. Below is the log messages.

using HTTPRequest node, IIB version - 10.0.0.3

( IBNODE.ISERVER ) An error occurred whilst performing an SSL socket operation. Operation: 'connect'. Error Text: 'java.net.ConnectException: Connection timed out: connect'.

This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname or port number.

See the following messages for information pertaining to this error.
( IBNODE.ISERVER ) Socket error detected whilst invoking Web service located at host 'federation-sts.nn.com', port '443', path '/oauth/ls/connect/token'. This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number.
( IBNODE.ISERVER ) An error occurred whilst performing an SSL socket operation. Operation: 'connect'. Error Text: 'java.net.ConnectException: Connection timed out: connect'.

This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname or port number.

See the following messages for information pertaining to this error.
( IBNODE.ISERVER ) Socket error detected whilst invoking Web service located at host 'federation-sts.nn.com', port '443', path '/oauth/ls/connect/token'. This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number.


from console.txt---

[‎19-‎06-‎2017 23:10]
No Title
Exception in thread "Thread-77" 2017-06-19 17:29:44.057 5654 java.net.ConnectException: Connection timed out: connect
2017-06-19 17:29:44.057 5654 at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
2017-06-19 17:29:44.057 5654 at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:97)
2017-06-19 17:29:44.057 5654 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:370)
2017-06-19 17:29:44.057 5654 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:231)
2017-06-19 17:29:44.057 5654 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:213)
2017-06-19 17:29:44.057 5654 at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:192)
2017-06-19 17:29:44.057 5654 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:404)
2017-06-19 17:29:44.057 5654 at java.net.Socket.connect(Socket.java:643)
2017-06-19 17:29:44.057 5654 at com.ibm.broker.imbsslsocket.MbSslSocket.connectTimeoutInternalNoProxy(Unknown Source)
2017-06-19 17:29:44.057 5654 at com.ibm.broker.imbsslsocket.MbSslSocket.connectTimeout(Unknown Source)
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Jun 19, 2017 2:17 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Too heavy traffic? Caching the credentials might help...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
firoj.badsa
PostPosted: Mon Jun 19, 2017 8:17 pm    Post subject: Reply with quote

Centurion

Joined: 16 Feb 2007
Posts: 104

web services used to generate the token used by many application with in the enterprise and no one else has this issue. When all other processes stopped and we try with a single transaction also we see this error.

during debug - I see the control coming out of the failure terminal in less than 60 seconds where the client time-out set as 120 seconds.

we already have a caching mechanism which stores the token for 1 hour to reduce the number of hit to the token web service.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jun 20, 2017 4:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY

Open a PMR
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » oAuth V2: SSL socket operation / IIB 10.0.0.3
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.