Topic
2 replies Latest Post - ‏2013-01-14T19:47:06Z by SystemAdmin
jkent
jkent
3 Posts
ACCEPTED ANSWER

Pinned topic SEVERE: javaAccessorNotSet - com.ibm.ws.naming.java.javaURLContextFactory

‏2008-03-24T12:13:57Z |
Does anyone know how to make this message go away? I'm doing web services in WDSC7 with WebSphere 6.1 and although the message is marked as "SEVERE" it is not causing any problems. It would be nice to supress it somehow. Thanks!

Message was edited by: jkent
Updated on 2013-01-14T19:47:06Z at 2013-01-14T19:47:06Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    659 Posts
    ACCEPTED ANSWER

    Re: SEVERE: javaAccessorNotSet - com.ibm.ws.naming.java.javaURLContextFactory

    ‏2008-06-11T15:51:16Z  in response to jkent
    Hi Kent

    Did you solve this issue. I am also facing the same problem. In my case, I am calling a Web Service from a job scheduled using Quartz.

    AS Nair
  • SystemAdmin
    SystemAdmin
    659 Posts
    ACCEPTED ANSWER

    Re: SEVERE: javaAccessorNotSet - com.ibm.ws.naming.java.javaURLContextFactory

    ‏2013-01-14T19:47:06Z  in response to jkent
    Hi I am also getting same message. Using websphere portal 6.1
    " Error message"

    Jan 14, 2013 2:42:05 PM com.ibm.ws.naming.java.javaURLContextFactory
    SEVERE: javaAccessorNotSet
    log4j:WARN No appenders could be found for logger (com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager).
    log4j:WARN Please initialize the log4j system properly.
    Exception in thread "main" java.lang.NoClassDefFoundError: org.eclipse.core.runtime.CoreException

    Could you suggest me any solution?