stlecho wrote:
> Saliya,
>
> I've noticed this message only when I change the log level to DEBUG. The ESB
> is starting up and working without any problem, so I think it can be safely
> ignored.
>
> Output of "java -version":
> java version "1.6.0_07"
> Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
> Java HotSpot(TM) Client VM (build 10.0-b23, mixed mode, sharing)
>
> Regards, Stefan.
>
> Saliya Ekanayake-2 wrote:
>
>> Hi,
>>
>> Can you please provide your Java working environment details?
>>
>> Thanks,
>> Saliya
>>
>> stlecho wrote:
>>
>>> Hi,
>>>
>>> When starting v1.7.1 of ESB, I'm receiving a
>>> "java.lang.ClassNotFoundException:
>>> org.apache.tomcat.util.net.jsse.JSSE15Factory". Can this be ignored or is
>>> it
>>> a real problem ?
>>>
>>> 2008-08-26 17:37:05,533 [192.168.13.175-INFOR2] [WrapperSimpleAppMain]
>>> DEBUG
>>> JSSEImplementation Error getting factory:
>>> org.apache.tomcat.util.net.jsse.JSSE15Factory
>>> java.lang.ClassNotFoundException:
>>> org.apache.tomcat.util.net.jsse.JSSE15Factory
>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
>>> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:164)
>>> at
>>> org.apache.tomcat.util.net.jsse.JSSEImplementation.<init>(JSSEImplementation.java:53)
>>> at
>>> org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:70)
>>> at
>>> org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:47)
>>> at
>>> org.apache.tomcat.util.net.SSLImplementation.getInstance(SSLImplementation.java:63)
>>> at
>>> org.apache.coyote.http11.Http11BaseProtocol.checkSocketFactory(Http11BaseProtocol.java:732)
>>> at
>>> org.apache.coyote.http11.Http11BaseProtocol.init(Http11BaseProtocol.java:123)
>>> at
>>> org.apache.catalina.connector.Connector.initialize(Connector.java:1016)
>>> at org.apache.catalina.startup.Embedded.start(Embedded.java:826)
>>> at org.wso2.esb.TomcatServer.start(TomcatServer.java:107)
>>> at org.wso2.esb.ServiceBus.main(ServiceBus.java:62)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:585)
>>> at
>>> org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
>>> at java.lang.Thread.run(Thread.java:595)
>>>
>>>
>>>
>> _______________________________________________
>> Esb-java-user mailing list
>> [email protected]
>> http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>>
>>
>>
>
>
Hi Stefan,
It is recommended to use jdk 1.5.x when running the wso2 esb as
there is currently a known issue with script mediator support which will
be resolved with the next major release. Other than that there should
not be any issues though we have not tested under the jdk 1.6
environment. But from the next release we are planning on fully
supporting jdk 1.6 environment.
Regards,
Dinuka
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
