Chris,
Seems attachment was not sent properly. Here is the trace
SEVERE: Naming Exception occuredjavax.naming.ServiceUnavailableException:
ldap.atpco.net:636; socket closed; remaining name
'racfid=XXXXX,profiletype=user,cn=RACFLDAP,c=us'
javax.naming.ServiceUnavailableException: ldap.atpco.net:636; socket closed;
remaining name 'racfid=XXXXX,profiletype=user,cn=RACFLDAP,c=us'
at com.sun.jndi.ldap.Connection.readReply(Connection.java:449)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:640)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:563)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1985)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1844)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1769)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:392)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:358)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:341)
at
javax.naming.directory.InitialDirContext.search(InitialDirContext.java:267)
at
net.atpco.tomcat.racf.service.RacfLDAPService.createLdapInitContext(RacfLDAPService.java:98)
at
net.atpco.tomcat.racf.service.TestRacfService.main(TestRacfService.java:14)
Jul 15, 2016 3:24:45 PM net.atpco.tomcat.racf.service.TestRacfService main
INFO: Exception occuredjava.lang.Exception: Naming Exception occured
Thanks
Ambica.
-----Original Message-----
From: Sanka, Ambica [mailto:asa...@atpco.net]
Sent: Friday, July 15, 2016 3:30 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: java
Chris,
Thank you for the quick response. Please see the attached for the stack trace.
Thanks
Ambica.
-----Original Message-----
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Thursday, July 14, 2016 8:59 PM
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: java
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ambica,
On 7/14/16 4:31 PM, Sanka, Ambica wrote:
> Does anyone facing issues with security from jdk1.8.0_51 onwards?
> We wrote a Valve in tomcat that connects to our ldap and gets user
> roles and groups. We connect ldap through ssl certificate. Our ldap
> ssl Certificate is working fine till jdk1.8.0_45. From jdk1.8.0_51 ,
> our applications are failing with below error
>
> SEVERE: Naming Exception occured
> javax.naming.ServiceUnavailableException: ldap.atpco.net:636; socket
> closed; remaining name
>
> I also posted this question in java community. But no response.
Can you post the full stack trace? It also looks like the full error message is
being truncated: "remaining name" looks like it's incomplete.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAleINUUACgkQ9CaO5/Lv0PA/+wCcDpVgXGxY5FCFUn/pWN2SMJbk
2rAAn3/f9EpIvtFAN8v81pwJTTjeNeiY
=Qkh7
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
