Thanks Kai, I've updated my code :-) There is just one change that I noticed which could be improved...if you only specify one (TCP) port in the KerbyClient, it will complain with "port out of range:-1". You have to explicitly disable UDP for this to work. I would suggest that it be better that it should only use either UDP or TCP if the port has been configured.
Colm. On Tue, Jun 30, 2015 at 9:44 AM, Zheng, Kai <[email protected]> wrote: > Colm, > > Recently I made large changes across client, server side and test base > codes. I'm afraid it may break your codes. Please let me know if any issue > I can help with. > > Regards, > Kai > > -----Original Message----- > From: Colm O hEigeartaigh [mailto:[email protected]] > Sent: Monday, June 22, 2015 10:35 PM > To: [email protected] > Subject: Re: Unit test regression > > Thanks, that works. > > Colm. > > On Wed, Jun 10, 2015 at 12:17 PM, Zheng, Kai <[email protected]> wrote: > > > Colm, > > > > With the following change it works. I guess previously timeout setting > > doesn't effect. After it's fixed and works now, 5 is too small because > > client and server are not ensured to be started in sequence in the > > test. > > > > - client.setTimeout(5); > > + client.setTimeout(50); > > > > Regards, > > Kai > > > > -----Original Message----- > > From: Zheng, Kai [mailto:[email protected]] > > Sent: Wednesday, June 10, 2015 6:57 PM > > To: [email protected]; [email protected] > > Subject: RE: Unit test regression > > > > I will look at it later. > > > > Regards, > > Kai > > > > -----Original Message----- > > From: Colm O hEigeartaigh [mailto:[email protected]] > > Sent: Wednesday, June 10, 2015 5:56 PM > > To: [email protected] > > Subject: Unit test regression > > > > Hi all, > > > > One of the unit tests in my github repo has stopped working: > > > > Caused by: java.net.SocketTimeoutException: Read timed out > > at java.net.SocketInputStream.socketRead0(Native Method) > > at java.net.SocketInputStream.read(SocketInputStream.java:152) > > at java.net.SocketInputStream.read(SocketInputStream.java:122) > > at java.net.SocketInputStream.read(SocketInputStream.java:210) > > at java.io.DataInputStream.readInt(DataInputStream.java:387) > > at > > > > > org.apache.kerby.kerberos.kerb.transport.KrbTcpTransport.receiveMessage(KrbTcpTransport.java:54) > > at > > > > > org.apache.kerby.kerberos.kerb.client.impl.DefaultKrbHandler.handleRequest(DefaultKrbHandler.java:40) > > ... 36 more > > > > > > The test-case is here: > > > > > > https://github.com/coheigea/testcases/blob/master/apache/cxf/cxf-kerbe > > ros-kerby/src/test/java/org/apache/coheigea/cxf/kerberos/authenticatio > > n/AuthenticationTest.java > > > > Specially, "unitTest". The GSS interop testcases are all fine. Has > > anything changed with regards to the client API of Kerby that would > > cause this? > > > > Colm. > > > > > > -- > > Colm O hEigeartaigh > > > > Talend Community Coder > > http://coders.talend.com > > > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
