1 2 Previous Next 15 Replies Latest reply on Apr 2, 2004 6:29 PM by Sherman Wood

    Attempting to eval Nukes

    pdohara Newbie

      I have downloaded Nukes and am attempting to get it running using the HSQL DB that is embedded in JBoss. After unziping the 1.0 dist and starting it up, I get errors that tables are missing. I have been able to startup the HSQL Database Manager, but I am unsure what connect string to use (any path seems to work just fine), and I have not been able to find the schema file, there is the nukes.script that sets up various things, but no table.

      I have searched the Nukes forum and not found anything about HSQL. It seems that most people are using MySQL. Is there a reason?

        • 1. Re: Attempting to eval Nukes
          Viet Master

          have you already a JBOSS_HOME env variable that would point to another jboss distribution ?

          • 2. Re: Attempting to eval Nukes
            jae Master

            if nukes is successfully connecting to the hsqldb, then you need to manually create the tables for everything to work correctly.

            in each component's output/resources directory, you can find setup.ddl files that can be used to create the tables. some components also have beanshell scripts (my favorite) that you can just drop into the deploy directory to create the tables.

            • 3. Re: Attempting to eval Nukes
              pdohara Newbie

              I was not able to find the "output/resources" directories. Ina src bundle I was able to find the file "nukes-hsqldb-setup.bsh" which seems to have the ddl code within java code. I am unsure why this is in a file with a bsh extention, and I suspect this is the wrong file. Still I opened the HSQL Manager pointing it at the connect string "jdbc:hsql:./server/default/data/nukes", and I ran the SQL I was able to extract. The result seems to be the correct table names, etc. JBOSS does not see these tables however, so I assume that the connect URL is incorrect and the tables are being created in the wrong place.

              • 4. Re: Attempting to eval Nukes
                jae Master

                are you compiling from source at all? the output/resources dir only appears if you ran through a build.

                the .bsh files are beanshell scripts. they can be dropped into the deploy directory and then they will create the tables.

                what does your nukes-ds.xml deployment file have in the connection-url element?

                nukes by default is geared to run w/ mysql as the default database. if you want to run w/ hsqldb, then you need to do the following:

                1) copy the "local.properties-example" file from build/etc into build and rename it "local.properties"
                2) edit that file and change the database from mysql to hsqldb
                3) execute "build.sh(bat)" in the build directory.

                that will create the "output" directories in the components and you can find the .ddl files there.

                4) create the db tables (either use the ddls, or the .bsh scripts)
                5) execute "build.sh(bat) deploy" in the build directory.

                that will go through and deploy nukes and you should be good to go.

                • 5. Re: Attempting to eval Nukes
                  pdohara Newbie

                  No I am not building from source, I downloaded rel 1.0. I moved the bean script into the deploy directory and recieved the following error on startup:

                  2004-03-31 13:13:25,488 INFO [org.jboss.nukes.core.modules.block.BlockModule] Started

                  2004-03-31 13:13:25,488 INFO [org.jboss.nukes.core.modules.core.CoreModule] Starting

                  2004-03-31 13:13:25,488 INFO [org.jboss.nukes.core.Main] Added handler nukes.modules:name=core

                  2004-03-31 13:13:25,528 INFO [org.jboss.nukes.core.modules.core.CoreModule] Started

                  2004-03-31 13:13:25,528 INFO [org.jboss.nukes.core.modules.profile.ProfileModule] Starting

                  2004-03-31 13:13:25,528 WARN [org.jboss.system.ServiceController] Problem starting service nukes.modules:name=profile

                  javax.naming.NameNotFoundException: PropertyValue not bound

                  at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)

                  at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)

                  at org.jnp.server.NamingServer.getObject(NamingServer.java:509)

                  at org.jnp.server.NamingServer.lookup(NamingServer.java:282)

                  at org.jnp.server.NamingServer.lookup(NamingServer.java:256)

                  at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:528)

                  at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)

                  at javax.naming.InitialContext.lookup(InitialContext.java:345)

                  at org.jboss.nukes.core.modules.profile.ProfileModule.start(ProfileModule.java:87)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.interceptor.ObjectReferenceInterceptor.invoke(ObjectReferenceInterceptor.java:59)

                  at org.jboss.mx.interceptor.MBeanAttributeInterceptor.invoke(MBeanAttributeInterceptor.java:43)

                  at org.jboss.mx.interceptor.PersistenceInterceptor2.invoke(PersistenceInterceptor2.java:93)

                  at org.jboss.nukes.mx.LifeCycleInterceptor.transition(LifeCycleInterceptor.java:172)

                  at org.jboss.nukes.mx.LifeCycleInterceptor.start(LifeCycleInterceptor.java:134)

                  at org.jboss.nukes.mx.LifeCycleInterceptor.invoke(LifeCycleInterceptor.java:64)

                  at org.jboss.mx.server.MBeanInvoker.invoke(MBeanInvoker.java:76)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)

                  at $Proxy14.start(Unknown Source)

                  at org.jboss.system.ServiceController.start(ServiceController.java:394)

                  at org.jboss.system.ServiceController.start(ServiceController.java:411)

                  at org.jboss.system.ServiceController.start(ServiceController.java:411)

                  at org.jboss.system.ServiceController.start(ServiceController.java:411)

                  at org.jboss.system.ServiceController.start(ServiceController.java:411)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)

                  at $Proxy34.start(Unknown Source)

                  at org.jboss.ejb.EjbModule.startService(EjbModule.java:331)

                  at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)

                  at $Proxy14.start(Unknown Source)

                  at org.jboss.system.ServiceController.start(ServiceController.java:394)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)

                  at $Proxy12.start(Unknown Source)

                  at org.jboss.ejb.EJBDeployer.start(EJBDeployer.java:544)

                  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)

                  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:824)

                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)

                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)

                  at $Proxy6.deploy(Unknown Source)

                  at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)

                  at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:476)

                  at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)

                  at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)

                  at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)

                  at $Proxy0.start(Unknown Source)

                  at org.jboss.system.ServiceController.start(ServiceController.java:394)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)

                  at $Proxy4.start(Unknown Source)

                  at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)

                  at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)

                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)

                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)

                  at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)

                  at java.lang.reflect.Method.invoke(Native Method)

                  at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)

                  at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)

                  at $Proxy5.deploy(Unknown Source)

                  at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)

                  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)

                  at org.jboss.Main.boot(Main.java:150)

                  at org.jboss.Main$1.run(Main.java:395)

                  at java.lang.Thread.run(Thread.java:479)

                  2004-03-31 13:13:25,538 INFO [org.jboss.nukes.core.modules.index.IndexModule] Starting

                  2004-03-31 13:13:25,538 INFO [org.jboss.nukes.component.Component.index] Uses the dir : C:\src\jboss-3.2.3RC1\server\default\data\nukes\index

                  2004-03-31 13:13:25,678 INFO [org.jboss.nukes.component.Component.index] Add nukes.modules:name=index to indices

                  2004-03-31 13:13:25,808 INFO [org.jboss.nukes.core.modules.index.IndexModule] Started

                  2004-03-31 13:13:25,808 INFO [org.jboss.nukes.core.modules.core.blocks.MenuBlock] Starting

                  2004-03-31 13:13:25,848 ERROR [org.jboss.nukes.core.modules.index.Index.index] Cannot open index writer

                  java.io.IOException: Lock obtain timed out

                  at org.apache.lucene.store.Lock.obtain(Lock.java:97)

                  at org.apache.lucene.index.IndexWriter.(IndexWriter.java:173)

                  at org.apache.lucene.index.IndexWriter.(IndexWriter.java:160)

                  at org.jboss.nukes.core.modules.index.Index.getWriter(Index.java:350)

                  at org.jboss.nukes.core.modules.index.Index.access$200(Index.java:36)

                  at org.jboss.nukes.core.modules.index.Index$WriterTask.run(Index.java:540)

                  at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:88)

                  at java.lang.Thread.run(Thread.java:479)

                  2004-03-31 13:13:25,908 INFO [org.jboss.nukes.core.modules.core.blocks.MenuBlock] Started

                  2004-03-31 13:13:25,908 INFO [org.jboss.nukes.core.modules.core.blocks.WhosOnlineBlock] Starting

                  2004-03-31 13:13:25,918 INFO [org.jboss.nukes.core.modules.core.blocks.WhosOnlineBlock] Started

                  2004-03-31 13:13:25,918 INFO [org.jboss.nukes.core.themes.seabreeze.SeaBreezeTheme] Starting

                  2004-03-31 13:13:25,948 INFO [org.jboss.nukes.core.themes.seabreeze.SeaBreezeTheme] Started


                  I am going to try removing the beanscript (as I assume it has already run) and restart nukes.

                  • 6. Re: Attempting to eval Nukes
                    pdohara Newbie

                    Tried that and am getting the same error. Do I need to get the latest code from CVS and do the build?

                    • 7. Re: Attempting to eval Nukes
                      jae Master

                      you don't need the latest code, but in order for you to be able to use hsqldb, you're going to want to do a build against the source.

                      use this link: http://prdownloads.sourceforge.net/jboss/nukes-1.0.0-src.zip?download

                      once you've got the source, follow the instruction i posted before. one thing i realize i forgot to mention is that you will need the nukes-ds.xml file deployed in order for the beanshell scripts to work.

                      you could accomplish this by executing "build deploy" and then manually removing the nukes.ear file from the deploy directory (leaving only the nukes-ds.xml) file.

                      if this still doesn't work, could you post a step-by-step list of the steps you are taking so i can provide better support?

                      • 8. Re: Attempting to eval Nukes
                        pdohara Newbie

                        Cool, it now works (building from source, etc). However I am now faced witht he end of the documentation. The comment is goto http://localhost:8080/nukes and enjoy. What I get at that URL is uninspiring. Where do I go to start making changes to the content?

                        • 9. Re: Attempting to eval Nukes
                          jae Master

                          if you are logged in as the "admin" user, there should be an "edit" link at the top of the page that will allow you to change the contents.

                          • 10. Re: Attempting to eval Nukes
                            pdohara Newbie

                            When I go to http://localhost:8080/nukes, I get a blue bar across the top, and then the message "The file id is not indicated". I also get the error :
                            20:33:29,920 INFO [Server] JBoss (MX MicroKernel) [3.2.3RC1 (build: CVSTag=JBos
                            s_3_2_3_RC1 date=200311101720)] Started in 43s:665ms
                            20:38:27,733 ERROR [index] Cannot open index writer
                            java.io.IOException: Lock obtain timed out
                            at org.apache.lucene.store.Lock.obtain(Lock.java:97)
                            at org.apache.lucene.index.IndexWriter.(IndexWriter.java:173)
                            at org.apache.lucene.index.IndexWriter.(IndexWriter.java:160)
                            at org.jboss.nukes.core.modules.index.Index.getWriter(Index.java:350)
                            at org.jboss.nukes.core.modules.index.Index.access$200(Index.java:36)
                            at org.jboss.nukes.core.modules.index.Index$WriterTask.run(Index.java:540)
                            at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:88)
                            at java.lang.Thread.run(Thread.java:534)


                            Any ideas?

                            • 11. Re: Attempting to eval Nukes
                              jae Master

                              use this as the url:

                              http://localhost:8080/nukes/

                              gotta have the trailing "/" (that should be fixed).

                              i am not sure what is causing that exception however (lucene is trying to get a lock on something, but i don't know what). are there any deployment errors before that?

                              • 12. Re: Attempting to eval Nukes
                                pdohara Newbie

                                Yes, the trailing slash "fixed" the screen. I do not have any links on the page, it describes what is coming in this realease and in future releases. I still get the failed to obtain lock exception.

                                How do I login?

                                • 13. Re: Attempting to eval Nukes
                                  jae Master

                                  you need to execute the following command in the nukes/nukes directory:

                                  build deploy-components

                                  that will deploy the menu-block, etc. i'm not sure why you're still getting the "lock exception" - do the logs offer any more information?

                                  • 14. Re: Attempting to eval Nukes
                                    pdohara Newbie

                                    It is now working completely. Thanks again. Is it documented anywhere that the default admin password is admin?

                                    I don't see any other errors in the log. There is one thing I did that I did not mention. I created a directory called nukes under server/default. Prior to doing that I was getting an IOException over and over. There never seems to be anything in the dir, so I assume it is a work dir.

                                    Thanks again for all your help getting up an running, now I just have to figure out how to use it :-)

                                    1 2 Previous Next