javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial

Atlassian JIRA | Nigel Owen | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Untared atlassian-bamboo-1.0.3-standalone.tar.gz Changed webapp/WEB-INF/classes/bamboo-init.properties to bamboo.home=/argon/Bamboo Edited bamboo.sh export BAMBOO_INSTALL=/argon/Bamboo export JAVA_HOME=/argon/jdk1.5.0_11 and added -Dbamboo.home=/argon/Bamboo/ to the RUN_CMD variable As root ./bamboo.sh start Noticed when doing a ps -efwww the process is sourcing jdk1.4.2 somewhere root 14981 1 94 18:55 pts/0 00:00:34 java -Djava.ext.dirs=/usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/jre/lib/ext -Xms256m -Xmx512m -XX:MaxPermSize=256m -Djava.awt.headless=true -classpath /argon/jdk1.5.0_11/lib/tools.jar:..... And from bamboo.log 2007-04-01 19:00:25,202 INFO [main] [HttpServer] Version Jetty/5.1.4 2007-04-01 19:00:25,278 INFO [main] [Credential] Checking Resource aliases 2007-04-01 19:01:05,159 WARN [main] [WebApplicationContext] Configuration error on ./webapp javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(libgcj.so.7) at javax.naming.InitialContext.getDefaultInitCtx(libgcj.so.7) at javax.naming.InitialContext.getURLOrDefaultInitCtx(libgcj.so.7) at javax.naming.InitialContext.lookup(libgcj.so.7) at org.mortbay.jetty.plus.PlusWebAppContext.initialize(PlusWebAppContext.java:167) at org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:463) at org.mortbay.jetty.plus.PlusWebAppContext.doStart(PlusWebAppContext.java:150) at org.mortbay.util.Container.start(Container.java:73) at org.mortbay.http.HttpServer.doStart(HttpServer.java:753) at org.mortbay.jetty.plus.Server.doStart(Server.java:154) at org.mortbay.util.Container.start(Container.java:73) at com.atlassian.bamboo.server.Server.main(Server.java:60) 2007-04-01 19:01:05,196 INFO [main] [SocketListener] Started SocketListener on 0.0.0.0:8085 Exception in thread "main" java.lang.RuntimeException: org.mortbay.util.MultiException[javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial] at com.atlassian.bamboo.server.Server.main(Server.java:79) Caused by: org.mortbay.util.MultiException[javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial] at org.mortbay.http.HttpServer.doStart(HttpServer.java:731) at org.mortbay.jetty.plus.Server.doStart(Server.java:154) at org.mortbay.util.Container.start(Container.java:73) at com.atlassian.bamboo.server.Server.main(Server.java:60) root@alice:/argon/Bamboo/logs#

    Atlassian JIRA | 1 decade ago | Nigel Owen
    javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial
  2. 0

    Untared atlassian-bamboo-1.0.3-standalone.tar.gz Changed webapp/WEB-INF/classes/bamboo-init.properties to bamboo.home=/argon/Bamboo Edited bamboo.sh export BAMBOO_INSTALL=/argon/Bamboo export JAVA_HOME=/argon/jdk1.5.0_11 and added -Dbamboo.home=/argon/Bamboo/ to the RUN_CMD variable As root ./bamboo.sh start Noticed when doing a ps -efwww the process is sourcing jdk1.4.2 somewhere root 14981 1 94 18:55 pts/0 00:00:34 java -Djava.ext.dirs=/usr/lib/jvm/java-1.4.2-gcj-4.1-1.4.2.0/jre/lib/ext -Xms256m -Xmx512m -XX:MaxPermSize=256m -Djava.awt.headless=true -classpath /argon/jdk1.5.0_11/lib/tools.jar:..... And from bamboo.log 2007-04-01 19:00:25,202 INFO [main] [HttpServer] Version Jetty/5.1.4 2007-04-01 19:00:25,278 INFO [main] [Credential] Checking Resource aliases 2007-04-01 19:01:05,159 WARN [main] [WebApplicationContext] Configuration error on ./webapp javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(libgcj.so.7) at javax.naming.InitialContext.getDefaultInitCtx(libgcj.so.7) at javax.naming.InitialContext.getURLOrDefaultInitCtx(libgcj.so.7) at javax.naming.InitialContext.lookup(libgcj.so.7) at org.mortbay.jetty.plus.PlusWebAppContext.initialize(PlusWebAppContext.java:167) at org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:463) at org.mortbay.jetty.plus.PlusWebAppContext.doStart(PlusWebAppContext.java:150) at org.mortbay.util.Container.start(Container.java:73) at org.mortbay.http.HttpServer.doStart(HttpServer.java:753) at org.mortbay.jetty.plus.Server.doStart(Server.java:154) at org.mortbay.util.Container.start(Container.java:73) at com.atlassian.bamboo.server.Server.main(Server.java:60) 2007-04-01 19:01:05,196 INFO [main] [SocketListener] Started SocketListener on 0.0.0.0:8085 Exception in thread "main" java.lang.RuntimeException: org.mortbay.util.MultiException[javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial] at com.atlassian.bamboo.server.Server.main(Server.java:79) Caused by: org.mortbay.util.MultiException[javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial] at org.mortbay.http.HttpServer.doStart(HttpServer.java:731) at org.mortbay.jetty.plus.Server.doStart(Server.java:154) at org.mortbay.util.Container.start(Container.java:73) at com.atlassian.bamboo.server.Server.main(Server.java:60) root@alice:/argon/Bamboo/logs#

    Atlassian JIRA | 1 decade ago | Nigel Owen
    javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial
  3. 0

    db:: 4.88::twiddle usage 8a

    hivmr.com | 1 year ago
    org.jboss.util.NestedRuntimeException: Can't find property: java.naming.factory.initial; - nested throwable: (javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    prototype-standalone.war 独立运行出错

    GitHub | 3 years ago | flanliulf
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
  6. 0

    jta-data-source breaks generation

    GitHub | 3 years ago | rkorn86
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. javax.naming.NoInitialContextException

    Can't find property: java.naming.factory.initial

    at javax.naming.spi.NamingManager.getInitialContext()
  2. Java RT
    InitialContext.lookup
    1. javax.naming.spi.NamingManager.getInitialContext(libgcj.so.7)
    2. javax.naming.InitialContext.getDefaultInitCtx(libgcj.so.7)
    3. javax.naming.InitialContext.getURLOrDefaultInitCtx(libgcj.so.7)
    4. javax.naming.InitialContext.lookup(libgcj.so.7)
    4 frames
  3. org.mortbay.jetty
    PlusWebAppContext.initialize
    1. org.mortbay.jetty.plus.PlusWebAppContext.initialize(PlusWebAppContext.java:167)
    1 frame
  4. Jetty Server
    WebApplicationContext.doStart
    1. org.mortbay.jetty.servlet.WebApplicationContext.doStart(WebApplicationContext.java:463)
    1 frame
  5. org.mortbay.jetty
    PlusWebAppContext.doStart
    1. org.mortbay.jetty.plus.PlusWebAppContext.doStart(PlusWebAppContext.java:150)
    1 frame
  6. Jetty Util
    Container.start
    1. org.mortbay.util.Container.start(Container.java:73)
    1 frame
  7. org.mortbay.http
    HttpServer.doStart
    1. org.mortbay.http.HttpServer.doStart(HttpServer.java:753)
    1 frame
  8. org.mortbay.jetty
    Server.doStart
    1. org.mortbay.jetty.plus.Server.doStart(Server.java:154)
    1 frame
  9. Jetty Util
    Container.start
    1. org.mortbay.util.Container.start(Container.java:73)
    1 frame
  10. com.atlassian.bamboo
    Server.main
    1. com.atlassian.bamboo.server.Server.main(Server.java:60)
    1 frame