|
I'm just an amused user, not an Atlassian support person.
1.0-rc1 worked with GCJ - in fact I hadn't noticed I was using it. Hi Allen,
This problem is happening because Jetty is starting up but for some reason or other, cannot find the property specifying the java naming InitialContextFactory. Unfortunately, we can't replicate this one here locally just yet. From what I can see, this problem could be due to the introduction of the new wrapper services as part of rc2, or, as Ben has alluded to something on the JVM side, or even both. Out of curiosity, have you changed any of the configurations for Bamboo? e.g. try to set up JNDI mail server via jetty.xml? Or changed the wrapper.conf file? Thanks, My datapoint is that I didn't change anything (apart from adjusting my start script to find the start-bamboo script and have the argument "console")
My install process is unpack distribution, update main directory symlink (I have bamboo.home set via an env variable), restart server and wait for errors - not a huge process fraught with risks. But I'm all fine and dandy now, so you can return to eating your candy. My install process was: unpack, edit bamboo.home in bamboo-init.properties, and then run "start-bamboo console".
bamboo-init.properties was the only file I edited. For the record, I have a patched libwrapper wrapper executeable from Hi guys
Sorry, I completely missed your comments in this issue. From I can see, it looks as if though Wrapper might be incompatibility with the Java Service Wrapper. However, as of Bamboo 1.0.1, we have again moved off a default Wrapper startup (given all the issues we have had). Would you like to give 1.0.1 a try and see if that's working? Cheers, I appear to be getting the same problem:
Again, this is Fedora Core 4, 64-bit, running gcj instead of sun's java [root@zeus Bamboo]# ./bamboo.sh console Starting Bamboo: 2007-03-07 11:30:20,686 INFO [main] [HttpServer] Version Jetty/Mort Bay Consulting, Pty. Ltd. 2007-03-07 11:30:20,741 INFO [main] [Credential] Checking Resource aliases 2007-03-07 11:30:21,985 WARN [main] [WebApplicationContext] Configuration error on ./webapp javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial at javax.naming.spi.NamingManager.getInitialContext(java.util.Hashtable) (/usr/lib64/libgcj.so.6.0.0) at javax.naming.InitialContext.getDefaultInitCtx() (/usr/lib64/libgcj.so.6.0.0) at javax.naming.InitialContext.getURLOrDefaultInitCtx(java.lang.String) (/usr/lib64/libgcj.so.6.0.0) at javax.naming.InitialContext.lookup(java.lang.String) (/usr/lib64/libgcj.so.6.0.0) at org.mortbay.jetty.plus.PlusWebAppContext.initialize() (Unknown Source) at org.mortbay.jetty.servlet.WebApplicationContext.doStart() (Unknown Source) at org.mortbay.jetty.plus.PlusWebAppContext.doStart() (Unknown Source) at org.mortbay.util.Container.start() (Unknown Source) at org.mortbay.http.HttpServer.doStart() (Unknown Source) at org.mortbay.jetty.plus.Server.doStart() (Unknown Source) at org.mortbay.util.Container.start() (Unknown Source) at com.atlassian.bamboo.server.Server.main(java.lang.String[]) (Unknown Source) at .main (/usr/lib64/libgij.so.6.0.0) at .__libc_start_main (/lib64/libc-2.3.6.so) 2007-03-07 11:30:22,052 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(java.lang.String[]) (Unknown Source) at .main (/usr/lib64/libgij.so.6.0.0) at .__libc_start_main (/lib64/libc-2.3.6.so) Caused by: org.mortbay.util.MultiException[javax.naming.NoInitialContextException: Can't find property: java.naming.factory.initial] at org.mortbay.http.HttpServer.doStart() (Unknown Source) at org.mortbay.jetty.plus.Server.doStart() (Unknown Source) at org.mortbay.util.Container.start() (Unknown Source) at com.atlassian.bamboo.server.Server.main(java.lang.String[]) (Unknown Source) ...2 more When I start bamboo using sun's jdk, everything works fine:
[root@zeus Bamboo]# PATH=/usr/java/jre/bin/:$PATH ./bamboo.sh console Starting Bamboo: 2007-03-07 10:46:33,025 INFO [main] [HttpServer] Version Jetty/5.1.4 2007-03-07 10:46:33,091 INFO [main] [Credential] Checking Resource aliases 2007-03-07 10:46:34,129 INFO [main] [Container] Started org.mortbay.jetty.servlet.WebApplicationHandler@7d26f75b 2007-03-07 10:46:34,496 INFO [main] [CollectionFactory] JDK 1.4+ collections available 2007-03-07 10:46:34,507 INFO [main] [CollectionFactory] Commons Collections 3.x available 2007-03-07 10:46:34,536 INFO [main] [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [applicationContextBootstrap.xml] 2007-03-07 10:46:34,661 INFO [main] [ClassPathXmlApplicationContext] Bean factory for application context [org.springframework.context.support.ClassPathXmlApplicationContext;hashCode=424167941]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [homeLocator,applicationConfig,setupPersister,upgradeManager,bootstrapManager,hibernateConfig,hibernateConfigurator,bambooLicenseManager,sidManager]; root of BeanFactory hierarchy 2007-03-07 10:46:34,781 INFO [main] [ClassPathXmlApplicationContext] 9 beans defined in application context [org.springframework.context.support.ClassPathXmlApplicationContext;hashCode=424167941] 2007-03-07 10:46:34,789 INFO [main] [ClassPathXmlApplicationContext] Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource@bd10a5c] 2007-03-07 10:46:34,791 INFO [main] [ClassPathXmlApplicationContext] Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster@6d3f7281] 2007-03-07 10:46:34,792 INFO [main] [DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [homeLocator,applicationConfig,setupPersister,upgradeManager,bootstrapManager,hibernateConfig,hibernateConfigurator,bambooLicenseManager,sidManager]; root of BeanFactory hierarchy] 2007-03-07 10:46:34,973 INFO [main] [lifecycle] Real path of servlet context: /mnt/store/bamboo/Bamboo/webapp 2007-03-07 10:46:35,111 INFO [main] [lifecycle] Starting Bamboo 1.0.1 (build #210) 2007-03-07 10:46:35,120 INFO [main] [UpgradeLauncher] Checking if upgrade required 2007-03-07 10:46:35,120 INFO [main] [UpgradeLauncher] UpgradeLauncher not performed since the application has not been setup yet. 2007-03-07 10:46:35,140 INFO [main] [FlushingSpringSessionInViewFilterForHibernate] Initializing filter 'sessioninview' 2007-03-07 10:46:35,157 INFO [main] [FlushingSpringSessionInViewFilterForHibernate] Filter 'sessioninview' configured successfully 2007-03-07 10:46:35,195 INFO [main] [DefaultConfiguration] Loading global messages from com.atlassian.bamboo.ww2.BambooActionSupport 2007-03-07 10:46:35,198 INFO [main] [DispatcherUtils] Could not load portlet-api, disabling webwork's portlet support. 2007-03-07 10:46:35,381 INFO [main] [Bamboo] [CompressingFilter/1.4] CompressingFilter has initialized 2007-03-07 10:46:35,388 INFO [main] [Bamboo] org.tuckey.web.filters.urlrewrite.utils.Log ERROR: logLevelConf: null 2007-03-07 10:46:35,454 INFO [main] [Bamboo] org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok) 2007-03-07 10:46:35,550 INFO [main] [Container] Started WebApplicationContext[/,Bamboo] 2007-03-07 10:46:35,561 INFO [main] [SocketListener] Started SocketListener on 0.0.0.0:8085 2007-03-07 10:46:35,561 INFO [main] [Container] Started com.atlassian.bamboo.server.Server@721cdeff **************************************************************** * * * You can see Bamboo by visiting http://localhost:8085/ * * **************************************************************** Hi Allen,
Yes - after more investigation, we have found that there are compatibility issues between gcj and Bamboo. I will close this issue for now. Please let us know if you have any other issues or queries. Regards, |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
Java error on startup
BAM-851, Ben Walding made the following comment:gcj is the default java install for Fedora machines, and gcj works just fine for the JIRA installation running on the same box.