8 Replies Latest reply on Nov 16, 2006 3:45 PM by Brandon Olivares

    Trouble starting up JBoss

    Brandon Olivares Newbie

      Hi,

      I've just recently installed JBoss, and the eclipse ide with the jboss plugins.

      I'm having trouble getting JBoss started though. When I installed it, I used the jems installation package, and specified the ejb3-clustered install. It doesn't seem the "all" option includes ejb3, and I wanted ejb3.

      I specified MySQL for the datasource, and put the appropriate .jar file in server/default/lib

      When I try to start JBoss from within Eclipse, it says it fails. The console contains the following:

      13:59:07,921 INFO [Server] Starting JBoss (MX MicroKernel)...
      13:59:07,921 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)
      13:59:07,937 INFO [Server] Home Dir: C:\Program Files\jboss-4.0.5.GA
      13:59:07,937 INFO [Server] Home URL: file:/C:/Program Files/jboss-4.0.5.GA/
      13:59:07,937 INFO [Server] Patch URL: null
      13:59:07,937 INFO [Server] Server Name: default
      13:59:07,937 INFO [Server] Server Home Dir: C:\Program Files\jboss-4.0.5.GA\server\default
      13:59:07,937 INFO [Server] Server Home URL: file:/C:/Program Files/jboss-4.0.5.GA/server/default/
      13:59:07,937 INFO [Server] Server Log Dir: C:\Program Files\jboss-4.0.5.GA\server\default\log
      13:59:07,937 INFO [Server] Server Temp Dir: C:\Program Files\jboss-4.0.5.GA\server\default\tmp
      13:59:07,937 INFO [Server] Root Deployment Filename: jboss-service.xml
      13:59:08,312 INFO [ServerInfo] Java version: 1.6.0-rc,Sun Microsystems Inc.
      13:59:08,312 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-rc-b104,Sun Microsystems Inc.
      13:59:08,312 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      13:59:08,734 INFO [Server] Core system initialized
      13:59:10,109 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      13:59:11,031 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://127.0.0.1:3873/]
      13:59:11,406 INFO [AspectDeployer] Deployed AOP: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/ejb3-interceptors-aop.xml
      13:59:15,015 INFO [AspectDeployer] Deployed AOP: file:/C:/Program Files/jboss-4.0.5.GA/server/default/deploy/tc5-cluster.sar/tc5-cluster.aop
      13:59:15,625 INFO [DefaultPartition] Initializing
      13:59:15,859 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is localhost:1390 (additional data: 14 bytes)
      -------------------------------------------------------
      13:59:18,046 INFO [DefaultPartition] Number of cluster members: 1
      13:59:18,046 INFO [DefaultPartition] Other members: 0
      13:59:18,046 INFO [DefaultPartition] Fetching state (will wait for 30000 milliseconds):
      13:59:18,046 INFO [DefaultPartition] State could not be retrieved (we are the first member in group)
      13:59:18,109 INFO [HANamingService] Started ha-jndi bootstrap jnpPort=1100, backlog=50, bindAddress=localhost/127.0.0.1
      13:59:18,125 INFO [DetachedHANamingService$AutomaticDiscovery] Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI address=127.0.0.1:1100
      13:59:18,296 INFO [WebService] Using RMI server codebase: http://localhost:8083/
      13:59:18,453 WARN [TreeCache] Using deprecated config element CacheLoaderFetchPersistentState. This element will be removed in future, please use CacheLoaderConfiguration instead.
      13:59:18,453 WARN [TreeCache] Using legacy cache loader config mechanisms.
      13:59:18,453 WARN [TreeCache] Using deprecated config element CacheLoaderFetchTransientState. This element will be removed in future, replaced with FetchInMemoryState.
      13:59:18,453 WARN [TreeCache] Calls to setFetchStateOnStartup are ignored; configure state transfer using setFetchInMemoryState and any cache loader's FetchPersistentState property
      13:59:18,453 WARN [TreeCache] Using deprecated config element CacheLoaderClass. This element will be removed in future, please use CacheLoaderConfiguration instead.
      13:59:18,468 WARN [TreeCache] Using deprecated config element CacheLoaderConfig(Properties). This element will be removed in future, please use CacheLoaderConfiguration instead.
      13:59:18,468 WARN [TreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
      13:59:18,500 WARN [TreeCache] Using deprecated configuration element 'EvictionPolicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases.
      13:59:18,562 INFO [InterceptorChainFactory] interceptor chain is:
      class org.jboss.cache.interceptors.CallInterceptor
      class org.jboss.cache.interceptors.EvictionInterceptor
      class org.jboss.cache.interceptors.PessimisticLockInterceptor
      class org.jboss.cache.interceptors.CacheLoaderInterceptor
      class org.jboss.cache.interceptors.UnlockInterceptor
      class org.jboss.cache.interceptors.ReplicationInterceptor
      class org.jboss.cache.interceptors.CacheStoreInterceptor
      class org.jboss.cache.interceptors.TxInterceptor
      class org.jboss.cache.interceptors.CacheMgmtInterceptor
      13:59:18,781 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is localhost:1397
      -------------------------------------------------------
      13:59:20,781 INFO [TreeCache] TreeCache local address is localhost:1397
      13:59:20,781 INFO [TreeCache] viewAccepted(): [localhost:1397|0] [localhost:1397]
      13:59:20,781 INFO [TreeCache] State could not be retrieved (we are the first member in group)
      13:59:22,171 INFO [InterceptorChainFactory] interceptor chain is:
      class org.jboss.cache.interceptors.CallInterceptor
      class org.jboss.cache.interceptors.PessimisticLockInterceptor
      class org.jboss.cache.interceptors.UnlockInterceptor
      class org.jboss.cache.interceptors.ReplicationInterceptor
      class org.jboss.cache.interceptors.TxInterceptor
      class org.jboss.cache.interceptors.CacheMgmtInterceptor
      13:59:22,203 WARN [TreeCache] Using deprecated configuration element 'EvictionPolicyProvider'. This is only provided for 1.2.x backward compatibility and may disappear in future releases.
      13:59:22,203 INFO [InterceptorChainFactory] interceptor chain is:
      class org.jboss.cache.interceptors.CallInterceptor
      class org.jboss.cache.interceptors.EvictionInterceptor
      class org.jboss.cache.interceptors.PessimisticLockInterceptor
      class org.jboss.cache.interceptors.UnlockInterceptor
      class org.jboss.cache.interceptors.ReplicationInterceptor
      class org.jboss.cache.interceptors.TxInterceptor
      class org.jboss.cache.interceptors.CacheMgmtInterceptor
      13:59:22,312 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is localhost:1406
      -------------------------------------------------------
      13:59:24,437 INFO [TreeCache] viewAccepted(): [localhost:1406|0] [localhost:1406]
      13:59:24,437 INFO [TreeCache] TreeCache local address is localhost:1406
      13:59:24,453 INFO [TreeCache] State could not be retrieved (we are the first member in group)
      13:59:24,453 INFO [TreeCache] parseConfig(): PojoCacheConfig is empty
      13:59:24,484 INFO [STDOUT]
      -------------------------------------------------------
      GMS: address is localhost:1414
      -------------------------------------------------------
      13:59:26,484 INFO [TreeCache] TreeCache local address is localhost:1414
      13:59:26,484 INFO [TreeCache] viewAccepted(): [localhost:1414|0] [localhost:1414]
      13:59:26,484 INFO [TreeCache] State could not be retrieved (we are the first member in group)
      13:59:26,781 INFO [Embedded] Catalina naming disabled
      13:59:26,859 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
      13:59:26,859 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
      13:59:27,265 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
      13:59:27,265 INFO [Catalina] Initialization processed in 406 ms
      13:59:27,265 INFO [StandardService] Starting service jboss.web
      13:59:27,265 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.20
      13:59:27,312 INFO [StandardHost] XML validation disabled
      13:59:27,328 INFO [Catalina] Server startup in 63 ms
      13:59:27,437 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
      13:59:27,796 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
      13:59:28,140 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp15130jbossws-context-exp.war/
      13:59:28,390 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
      13:59:29,093 INFO [MailService] Mail Service bound to java:/Mail
      13:59:29,406 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
      13:59:29,562 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
      13:59:29,640 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
      13:59:29,656 INFO [QuartzResourceAdapter] start quartz!!!
      13:59:29,734 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
      13:59:29,765 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      13:59:29,765 INFO [RAMJobStore] RAMJobStore initialized.
      13:59:29,765 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
      13:59:29,765 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      13:59:29,765 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
      13:59:30,281 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      13:59:30,718 INFO [A] Bound to JNDI name: queue/A
      13:59:30,718 INFO [B] Bound to JNDI name: queue/B
      13:59:30,734 INFO [C] Bound to JNDI name: queue/C
      13:59:30,734 INFO [D] Bound to JNDI name: queue/D
      13:59:30,734 INFO [ex] Bound to JNDI name: queue/ex
      13:59:30,750 INFO [testTopic] Bound to JNDI name: topic/testTopic
      13:59:30,750 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
      13:59:30,750 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
      13:59:30,765 INFO [testQueue] Bound to JNDI name: queue/testQueue
      13:59:30,781 INFO [UILServerILService] JBossMQ UIL service available at : localhost/127.0.0.1:8093
      13:59:30,828 INFO [DLQ] Bound to JNDI name: queue/DLQ
      13:59:31,000 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      13:59:31,031 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      13:59:31,218 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
      13:59:31,312 INFO [ChannelSocket] JK: ajp13 listening on localhost/127.0.0.1:8009
      13:59:31,328 INFO [JkMain] Jk running ID=0 time=0/63 config=null
      13:59:31,359 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 23s:422ms
      


      I don't know what those warnings are from. I see no errors, though.

      Any ideas what could be going wrong?

      Any help much appreciated.

        • 1. Re: Trouble starting up JBoss
          VisolveGroup Novice

          Hello,

          From the Server log that you have given denotes that there is no problem in starting of JBoss. The warnings are clearly stated that, its come from deprecated configuration environment and it will be disappear in future releases.

          And, It seems you need ejb3 but you have installed ejb3-clustering configuration from jems.

          1. Try to select ejb3 server configuration then install it using jems installer jar and not the ejb3-clustering(unless you need ejb3 - clustering server configuration).

          2. Now start the jboss server with ejb3 Server configuration.

          Hope, this may help you.

          • 2. Re: Trouble starting up JBoss
            Brandon Olivares Newbie

            hi,

            Thanks for the response. I reinstalled, with the "all" configuration. Is this supposed to support EJB3? i thought I read somewhere it should, but I am not sure.

            Anyway, now when I start, i get something like this at the end:

            --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
            ObjectName: jboss:service=Naming
             State: FAILED
             Reason: java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
             java.net.BindException: Address already in use: JVM_Bind
             I Depend On:
             jboss.system:service=ThreadPool
             Depends On Me:
             jboss.ws:service=WebServiceClientDeployer
             jboss.cache:service=TomcatClusteringCache
             jboss:service=DefaultPartition
             jboss:service=HASessionState
             jboss:service=invoker,type=jrmpha
             jboss:service=invoker,type=pooledha
             jboss:service=CorbaORB
             jboss:service=invoker,type=iiop
             jboss:service=CorbaNaming
             jboss.mq:service=DestinationManager
             jboss.mq:service=Invoker
             jboss.mq:service=InvocationLayer,type=UIL
             jboss.mq:service=InvocationLayer,type=UILXA
             jboss.mq:service=InvocationLayer,type=UIL2,alias=UIL2ConnectionFactory
             jboss.mq:service=InvocationLayer,type=UIL2XA,alias=UIL2XAConnectionFactory
             jboss.jms:alias=QueueConnectionFactory
             jboss.jms:alias=TopicConnectionFactory
             jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
             jboss.jmx:alias=jmx/rmi/RMIAdaptor
             jboss:service=TransactionManager
            
            ObjectName: jboss.jca:service=RARDeployment,name='jms-ra.rar'
             State: NOTYETINSTALLED
             Depends On Me:
             jboss.jca:service=ManagedConnectionFactory,name=JmsXA
            
            ObjectName: jboss.jca:service=RARDeployment,name='jboss-local-jdbc.rar'
             State: NOTYETINSTALLED
             Depends On Me:
             jboss.jca:service=ManagedConnectionFactory,name=DefaultDS
            
            
            23:54:14,156 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 10s:188ms
            


            It says njboss.naming was already started, and then that other things seemed not to have been installed. Not sure why this would be, though, since it should have installed everything.

            • 3. Re: Trouble starting up JBoss
              VisolveGroup Novice

              Hello,

              With 'all' server configuration, you can't able to run the EJB3.

              So, For running EJB3 Applications, you should install 'EJB3' Server Configuration while you are selecting the Server Configuration at the time of Installation by using jems installer jar.

              The error denotes, the ports are already bound. Are you running more than one jboss server at a time??

              If so, stop all the jboss servers and start only one instance of jboss.

              • 4. Re: Trouble starting up JBoss
                Brandon Olivares Newbie

                OK, I installed the EJB3 configuration.

                I figured out that the port 1098 was being used due to some process on my computer. I stopped the process and then got no more of those errors.

                Now it looks like it is starting fine; it is like my original post, minus the warnings. But, in the JBos server view, in the event log, after the successful start of the server i see a bunch of messages like:

                Twiddle Launch: Server is down


                Then after a good 25 of those:

                [quoteServer failed to start

                • 5. Re: Trouble starting up JBoss
                  Brandon Olivares Newbie

                  Hi,

                  I found a twiddle.log in the bin directory of JBoss.

                  It contains the following:

                  [code08:54:06,562 DEBUG [Twiddle] args[0]=-s
                  08:54:06,562 DEBUG [Twiddle] args[1]=localhost:1099
                  08:54:06,562 DEBUG [Twiddle] args[2]=-a
                  08:54:06,562 DEBUG [Twiddle] args[3]=jmx/rmi/RMIAdaptor
                  08:54:06,562 DEBUG [Twiddle] args[4]=get
                  08:54:06,562 DEBUG [Twiddle] args[5]=jboss.system:type=Server
                  08:54:06,562 DEBUG [Twiddle] args[6]=Started
                  08:54:06,562 DEBUG [Twiddle] Command name: get
                  08:54:06,578 DEBUG [Twiddle] Command arguments: jboss.system:type=Server,Started
                  08:54:06,578 DEBUG [Twiddle] command proto type properties: jar:file:/C:/Program%20Files/jboss-4.0.5.GA/bin/twiddle.jar!/org/jboss/console/twiddle/commands.properties
                  08:54:06,578 DEBUG [Twiddle] Adding command 'jsr77'; proto: org.jboss.console.twiddle.command.JSR77Command@133f1d7
                  08:54:06,578 DEBUG [Twiddle] Adding command 'xmbean'; proto: org.jboss.console.twiddle.command.XMBeanCommand@a01335
                  08:54:06,578 DEBUG [Twiddle] Adding command 'info'; proto: org.jboss.console.twiddle.command.InfoCommand@bf32c
                  08:54:06,578 DEBUG [Twiddle] Adding command 'get'; proto: org.jboss.console.twiddle.command.GetCommand@f81843
                  08:54:06,578 DEBUG [Twiddle] Adding command 'invoke'; proto: org.jboss.console.twiddle.command.InvokeCommand@c4bcdc
                  08:54:06,578 DEBUG [Twiddle] Adding command 'create'; proto: org.jboss.console.twiddle.command.CreateCommand@128e20a
                  08:54:06,578 DEBUG [Twiddle] Adding command 'setattrs'; proto: org.jboss.console.twiddle.command.SetAttrsCommand@e4f972
                  08:54:06,578 DEBUG [Twiddle] Adding command 'unregister'; proto: org.jboss.console.twiddle.command.UnregisterCommand@1bf52a5
                  08:54:06,578 DEBUG [Twiddle] Adding command 'query'; proto: org.jboss.console.twiddle.command.QueryCommand@10b9d04
                  08:54:06,593 DEBUG [Twiddle] Adding command 'set'; proto: org.jboss.console.twiddle.command.SetCommand@1404536
                  08:54:06,593 DEBUG [Twiddle] Adding command 'serverinfo'; proto: org.jboss.console.twiddle.command.ServerInfoCommand@7d8483
                  08:54:06,593 DEBUG [GetCommand] processing arguments: jboss.system:type=Server,Started
                  08:54:06,593 DEBUG [GetCommand] mbean name: jboss.system:type=Server
                  08:54:06,593 DEBUG [GetCommand] adding attribute name: Started
                  08:54:06,593 DEBUG [GetCommand] attribute names: [Started]
                  08:54:06,953 DEBUG [GetCommand] as string[]: Started
                  08:54:06,953 DEBUG [SecurityAssociation] Using ThreadLocal: false
                  08:54:06,984 ERROR [Twiddle] Exec failed
                  java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
                  at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
                  at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
                  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                  at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                  at java.lang.reflect.Method.invoke(Unknown Source)
                  at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
                  at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
                  at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
                  at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
                  at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
                  at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
                  at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
                  at java.lang.reflect.Method.invoke(Unknown Source)
                  at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
                  at sun.rmi.transport.Transport$1.run(Unknown Source)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at sun.rmi.transport.Transport.serviceCall(Unknown Source)
                  at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
                  at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
                  at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                  at java.lang.Thread.run(Unknown Source)
                  at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
                  at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
                  at sun.rmi.server.UnicastRef.invoke(Unknown Source)
                  at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
                  at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
                  at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
                  at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
                  at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
                  at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
                  at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
                  at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
                  at $Proxy0.getAttributes(Unknown Source)
                  at org.jboss.console.twiddle.command.GetCommand.execute(GetCommand.java:168)
                  at org.jboss.console.twiddle.Twiddle.main(Twiddle.java:305)

                  • 6. Re: Trouble starting up JBoss
                    Brandon Olivares Newbie

                    Just another update:

                    I saw in other parts of the forum that people had this same problem, and fixed it by just using the zip download instead of the jar installer. I tried the same, and it worked.

                    But the problem is that this doesn't include EJB3. Is there a way I can include EJB3 in it? Apparently there is some problem with the installer.

                    • 7. Re: Trouble starting up JBoss
                      Peter Johnson Master

                      To get EJB3 support, download the source tar.gz file, unpack it (if you are on Windows, WinZip can do this), abd build it using a 5.0 JDK. The build creates both the standard binary distribution and an EJB3 variation.

                      To built it, set JAVA_HOME, go to the build directory, and run build.bat or build.sh. The binary appears in the build/output directory.

                      • 8. Re: Trouble starting up JBoss
                        Brandon Olivares Newbie

                        Hi,

                        Thanks for the reply. I downloaded jboss-ejb3 rc9, and according to the install.html I'm supposed to use ant to build and install into jboss. so I ran

                        ant -f install.xml -Djboss.server.config=default[/coe]
                        
                        And it looks like it worked. I've not tested it but it looks like it.
                        
                        Now hopefully this'll work. :D Thanks to everyone who replied.