Skip to Main Content
Forums

Java Security

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ClassNotFoundException: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl

1001382Apr 5 2013 — edited Apr 15 2013
I updated JDK from 6 to 7 and our application is broken as show in the exception below. As I found out that in JDK7, jsse.jar did repackage com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl was repackaged to com.sun.net.ssl.SSLSocketFactoryImpl and that is why cause ClassNotFoundException. My code (in highlight) did not reference the class directly. Any advise on fixing this issue will be appreciated.



Exception naming Exception = fidVirtualDir-QA.fmr.com:2491null
Exception naming Exception = fidVirtualDir-QA.fmr.com:2491java.net.SocketException: java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
javax.naming.CommunicationException: fidVirtualDir-QA.fmr.com:2491 [Root exception is java.net.SocketException: java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl]
at com.sun.jndi.ldap.Connection.<init>(Connection.java:214)
at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:136)
at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1600)
at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2698)
at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:316)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:193)
at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:211)
at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:154)
at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:84)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
at javax.naming.InitialContext.init(InitialContext.java:242)
at javax.naming.InitialContext.<init>(InitialContext.java:216)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:101)
at fmtc.common.util.DirAuthService.ldapBind(DirAuthService.java:103)
at com.pyramis.security.acl.internal.FMTCUser.basicAuthentication(FMTCUser.java:297)
at com.pyramis.security.acl.internal.FMTCUser.authenticate(FMTCUser.java:283)
at com.pyramis.security.realm.JDBCRealm.authentication(JDBCRealm.java:199)
at com.pyramis.security.realm.JDBCRealm.getUser(JDBCRealm.java:189)
at com.pyramis.security.service.PSECServicesBean.authenticate(PSECServicesBean.java:226)
at com.pyramis.security.service.PSECServicesBean.authenticate(PSECServicesBean.java:276)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:203)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:162)
at com.pyramis.security.advice.MethodProfilingInterceptor.invoke(MethodProfilingInterceptor.java:85)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:51)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:209)
at com.sun.proxy.$Proxy22.authenticate(Unknown Source)
at fmtc.security.ws.FSECWebServiceImpl.authenticate(FSECWebServiceImpl.java:125)
at fmtc.security.ws.FSECWebService.authenticate(FSECWebService.java:111)
at fmtc.security.ws.FSECWebService$$FastClassByCGLIB$$e89c62e8.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:191)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:714)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:162)
at com.pyramis.security.advice.MethodProfilingInterceptor.invoke(MethodProfilingInterceptor.java:85)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.adapter.AfterReturningAdviceInterceptor.invoke(AfterReturningAdviceInterceptor.java:51)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:53)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:185)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:652)
at fmtc.security.ws.FSECWebService$$EnhancerByCGLIB$$faaea86b.authenticate(<generated>)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.java:246)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:471)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135)
at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129)
at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160)
at com.sun.xml.ws.transport.http.servlet.WSSpringServlet.doPost(WSSpringServlet.java:52)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:606)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.net.SocketException: java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
at javax.net.ssl.DefaultSSLSocketFactory.throwException(SSLSocketFactory.java:198)
at javax.net.ssl.DefaultSSLSocketFactory.createSocket(SSLSocketFactory.java:211)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:331)
at com.sun.jndi.ldap.Connection.<init>(Connection.java:201)
... 83 more
Caused by: java.lang.ClassNotFoundException: com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at javax.net.ssl.SSLSocketFactory.getDefault(SSLSocketFactory.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:287)
... 84 more

Comments

Gbenga Ajakaye 
The Oracle materials seem to favor RAC databases being created as Policy-Managed.  In the real world however I noticed many of my colleagues creating them as Admin-Managed.

Remember that your colleagues shop is different from your environment. Have you ever asked any of your colleagues why they decide to implement ADMIN Managed over Policy Managed?

I'll suggest you start here: Oracle Database 12c: Why and How You Should Be Using Policy-Managed Oracle RAC Databases.

It should help to dispel you think and give you insight about why it's best to use Policy Managed over Admin Managed.

In addition:

Deploying Policy-Managed Databases

When you deploy a policy-managed database you must first determine the services and their required sizing, taking into account that services cannot span server pools. If you are going to collocate this database with other databases, then you should factor in its CPU requirements relative to the other hosted databases, and also factor in the value of its CPU_COUNT attribute for instance caging, so that you can size the database both vertically and horizontally in one or more server pools.
If you are going to collocate the server pools for this database with other server pools, then consider configuring the server pools to adjust the server pool sizes on a calendar or event basis to optimize meeting demand and business requirements. Once you have determined the sizes of the server pools, and configured the appropriate values for the MIN_SIZE and MAX_SIZE server pool attributes, you can then determine the relative importance of each server pool. Managing a policy-managed database requires less configuration and reconfiguration steps than an administrator-managed one with respect to creation, sizing, patching, and load balancing. Also, because any server in the server pools within the cluster can run any of the databases, you do not have to create and maintain database instance-to-node-name mappings. You can perform maintenance tasks such as patching by relocating servers into the Free pool or by adjusting the server pool minimum and maximum sizes, thereby retaining required availability.

Admin Manager database

For administrator-managed databases, you must ensure that the database software is deployed on the nodes on which you plan to run the respective database instances. You must also ensure that these nodes have access to the storage in which you want to store the database files. Oracle recommends that you select Oracle ASM during database installation to simplify storage management. Oracle ASM automatically manages the storage of all database files within disk groups. If you plan to use Oracle Database Standard Edition to create an Oracle RAC database, then you must use Oracle ASM to store all of the database files.
For policy-managed databases, you must ensure that the database software is deployed on all nodes on which database instances can potentially run, given your active server pool setup. You must also ensure that these nodes have access to the storage in which you want to store the database files. Oracle recommends using Oracle ASM, as previously described for administrator-managed databases.

You can get the detail in the official documentation: https://docs.oracle.com/database/121/RACAD/admcon.htm#RACAD8895

In addition, I'll also suggest you read over this Oracle before deciding whether to use Policy or Managed http://www.nocoug.org/download/2013-05/NoCOUG_201305_Why_and_How_Using_Policy_Managed_Databases.pdf

MaryY

Sincere thanks for the detailed response.

As all my posts, prior to posting I search Oracle docs, Google and these forums.  When I am still missing puzzle pieces or have not found how to make the theory practical...I post here.  I am thinking of adding this to my signature line.  :-)

What do YOU  do in the real world production environments you work in concerning creating RAC database for this topic.  Do you create them as Policy or Admin managed and why?

What are the key attributes that you found that made you choose one over the other?

Thanks.

BPeaslandDBA

I create mine as admin-managed. I've never had a reason to use policy-managed, at least not yet.

Cheers,
Brian

Robin.A-Oracle

Hi Mary


How many nodes you have in your cluster?If you are on a basic 2 node cluster,then it doesn't matter Admin or policy managed.

But say if you have 8 node RAC ,it would help in the effective use of resources  if you create a policy-managed database with associated  server pools.

Also you can configure new features like QoS

Regards

Robin

Hemant K Chitale
Answer

Admin managed for DBAs who have been working with earlier versions and need to maintain control of the configuration.  The Real World.

Policy managed for DBAs trained by Oracle !   The Imaginary World.

Hemant K Chitale

Marked as Answer by MaryY · Sep 27 2020
2 people found this helpful
Levi Pereira 
When I am still missing puzzle pieces or have not found how to make the theory practical...I post here.  I am thinking of adding this to my signature line.  :-)

To think use it you need go into  Oracle Database QoS Management.

Oracle Database QoS Management is an automated, policy-based product that monitors the workload requests for an entire system. Oracle Database QoS Management manages the resources that are shared across applications and adjusts the system configuration to keep the applications running at the performance levels needed by your business. Oracle Database QoS Management responds gracefully to changes in system configuration and demand, thus avoiding additional oscillations in the performance levels of your applications.

https://docs.oracle.com/database/121/APQOS/apqos_intro.htm#APQOS109

Here a pratical example:

https://www.youtube.com/watch?v=H8I69nyiwdw

BPeaslandDBA

LOL!!!

Policy managed for DBAs trained by Oracle ! The Imaginary World.

I would also add...Policy managed are for those who have unlimited checkbooks or don't care about the money the company spends. If I have an extra node in the cluster "just sitting there" waiting to be added to support my RAC database at a moments noticed, that extra node needs to be licensed for Oracle EE and RAC! If I licensed that node, it ain't going to be sitting there idle. I'm gonna be using it!

Cheers,

Brian

1 - 7
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 13 2013
Added on Apr 5 2013
#authentication, #java-secure-socket-extension-jsse, #security, #ssl
1 comment
27,287 views