facebook

jboss4.0.2 start error( with myeclipse4.0m2)

💡
Our Forums Have Moved

For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 15 posts - 1 through 15 (of 19 total)
  • Author
    Posts
  • #231658 Reply

    Baby1937
    Member

    I always get this message while i start jboss4.0.2:
    1.
    JVM launcher: could not find main class, program will exit.
    2.
    A configuration error occurred during startup. please verify the preference field with the prompt: java.lang.NoClassDefFoundError:
    Files\jboss-4/0/2\lib\endorsed
    Exception in thread”main”

    i am using eclipse 3.0.2 and myeclipse 4.0 m2,JDK1.5.0_03,how do i solve this problem??

    #231666

    Scott Anderson
    Participant

    Can you try configuring JBoss to launch with a 1.4.2 JDK, since that’s what it’s tested on, by specifying one at:
    Window > Preferences > MyEclipse > JBoss 4 > JDK?

    #232105

    jschweickart
    Member

    I am just setting this up, going through the tutorial for the HelloWorld JSP and getting the same error.

    My environment is Win2K Pro/Eclipse 3.1.0/MyEclipse4.0M2/JDK 1.4.2_08/JBoss 4.0.2

    Also, when deploying the HelloWorld JSP, I chose deploy type of ‘exploded’, but the location was D:\Program Files\jboss-4.0.2\server\default\deploy\HelloWorld.war. I didn’t expect to see the .war, but just a directory.

    TIA,
    Joe

    #232121

    Riyad Kalla
    Member

    Guys I couldn’t reproduce this, on a brand new installs of 3.1 and MyEclipse 4M2 and JBoss 4.02 I set it up to run with JDK 1.5.0_04 and hit start and got this:

    08:16:36,875 INFO [Server] Starting JBoss (MX MicroKernel)…
    08:16:36,875 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
    08:16:36,875 INFO [Server] Home Dir: D:\Java\jboss-4.0.2
    08:16:36,875 INFO [Server] Home URL: file:/D:/Java/jboss-4.0.2/
    08:16:36,875 INFO [Server] Library URL: file:/D:/Java/jboss-4.0.2/lib/
    08:16:36,875 INFO [Server] Patch URL: null
    08:16:36,875 INFO [Server] Server Name: default
    08:16:36,875 INFO [Server] Server Home Dir: D:\Java\jboss-4.0.2\server\default
    08:16:36,875 INFO [Server] Server Home URL: file:/D:/Java/jboss-4.0.2/server/default/
    08:16:36,890 INFO [Server] Server Data Dir: D:\Java\jboss-4.0.2\server\default\data
    08:16:36,890 INFO [Server] Server Temp Dir: D:\Java\jboss-4.0.2\server\default\tmp
    08:16:36,890 INFO [Server] Server Config URL: file:/D:/Java/jboss-4.0.2/server/default/conf/
    08:16:36,890 INFO [Server] Server Library URL: file:/D:/Java/jboss-4.0.2/server/default/lib/
    08:16:36,890 INFO [Server] Root Deployment Filename: jboss-service.xml
    08:16:36,890 INFO [Server] Starting General Purpose Architecture (GPA)…
    08:16:37,281 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc.
    08:16:37,281 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_04-b05,Sun Microsystems Inc.
    08:16:37,281 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86
    08:16:37,796 INFO [Server] Core system initialized
    08:16:39,312 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
    08:16:39,406 INFO [WebService] Using RMI server codebase: http://rkalla:8083/
    08:16:39,609 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
    08:16:43,265 INFO [Embedded] Catalina naming disabled
    08:16:43,718 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
    08:16:43,718 INFO [Catalina] Initialization processed in 375 ms
    08:16:43,718 INFO [StandardService] Starting service jboss.web
    08:16:43,734 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
    08:16:43,875 INFO [StandardHost] XML validation disabled
    08:16:43,921 INFO [Catalina] Server startup in 203 ms
    08:16:44,046 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/D:/Java/jboss-4.0.2/server/default/deploy/http-invoker.sar/invoker.war/
    08:16:44,343 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
    08:16:45,125 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/D:/Java/jboss-4.0.2/server/default/tmp/deploy/tmp12209jboss-ws4ee-exp.war/
    08:16:45,312 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/D:/Java/jboss-4.0.2/server/default/deploy/jbossweb-tomcat55.sar/ROOT.war/
    08:16:45,578 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/D:/Java/jboss-4.0.2/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
    08:16:48,015 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/D:/Java/jboss-4.0.2/server/default/deploy/management/console-mgr.sar/web-console.war/
    08:16:48,859 INFO [MailService] Mail Service bound to java:/Mail
    08:16:49,328 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/jboss-ha-local-jdbc.rar
    08:16:49,484 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/jboss-ha-xa-jdbc.rar
    08:16:49,593 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/jboss-local-jdbc.rar
    08:16:49,734 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/jboss-xa-jdbc.rar
    08:16:49,859 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/jms/jms-ra.rar
    08:16:49,968 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/D:/Java/jboss-4.0.2/server/default/deploy/mail-ra.rar
    08:16:50,718 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager ‘jboss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name ‘java:DefaultDS’
    08:16:51,062 INFO [A] Bound to JNDI name: queue/A
    08:16:51,062 INFO [B] Bound to JNDI name: queue/B
    08:16:51,062 INFO [C] Bound to JNDI name: queue/C
    08:16:51,062 INFO [D] Bound to JNDI name: queue/D
    08:16:51,062 INFO [ex] Bound to JNDI name: queue/ex
    08:16:51,093 INFO [testTopic] Bound to JNDI name: topic/testTopic
    08:16:51,109 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
    08:16:51,109 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
    08:16:51,109 INFO [testQueue] Bound to JNDI name: queue/testQueue
    08:16:51,156 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093
    08:16:51,203 INFO [DLQ] Bound to JNDI name: queue/DLQ
    08:16:51,453 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager ‘jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name ‘java:JmsXA’
    08:16:51,500 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/D:/Java/jboss-4.0.2/server/default/deploy/jmx-console.war/
    08:16:52,109 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
    08:16:52,296 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
    08:16:52,312 INFO [JkMain] Jk running ID=0 time=0/47 config=null
    08:16:52,328 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 15s:438ms

    #232813

    Tarry Singh
    Member

    Ok rkalla then enlighten here please how did you set it up.
    My situation is same as above
    OS= win xp sp2
    JDK = 1.5.0_03
    Just bought the MyEclipse 🙂
    Already had Eclipsefinal 3.1

    Funny thing is that my java installed jre’s show’s jre home. I don’t know about others but just to mention that when you install you have jdk and jre installed alongside for instance i have JDK = d:\java\jdk1.5…. and JRE = d:\java\jre1.5….

    So what gives? This is really annoying. 😐

    #232814

    jschweickart
    Member

    rkalla set me straight, but it must have been in a private message. You need to have your jboss root in a directory without any spaces in it. I had mine in c:\program files\jboss, and when I moved it to c:\jboss, it worked fine.

    As for the jdk vs. jre, I had to go to Windows>Preferences>MyEclipse>Application Servers>Jboss 4>JDK and click the Add . . . button. I browsed to the root of the JDK, C:\jsdk1.4.2_08 in my case, and then select that JDK. I followed the instructions from the tutorial, so I don’t really know what happens if you just specify a JRE root here, but the tutorial warned against doing that.

    HTH,
    Joe

    #232815

    Tarry Singh
    Member

    OK dude, mine is in the prog files as well so I’m purty curious. will report pronto! 🙂

    #232819

    Tarry Singh
    Member

    That was indeed the error gents. Thanks for the insight and help.

    –So two things to remember
    Eclipse installation picks the JRE, in the installed JRE’s, change it to JDK
    2. jboss app servers should be put in folders which don’t have spacves in the names like “program files” “apache group”…

    Thx again Joe. 🙂

    Tarry

    #232837

    Riyad Kalla
    Member

    Guys w.r.t. to the spaces-in-the-path issue, it’s not a consistent issue. For example, I can install JBoss/Tomcat/etc. just fine to a path with spaces (C:\Program Files) and it runs on my computer, as well as 2 of our devs, but fails on your setups. It has been reported before by others and at this point until we can figure out what is going on all we can do is give suggested work arounds. We originally thought it was a locale issue, but that didn’t seem to be the case, then we thought it was a Win2K/XP issue, that wasn’t the case either, and I’m on XP 64-bit here so there seems to be no consistency with it except when a system can’t run Java using paths, it won’ work anywhere, quoted or not quoted (we do quote the values).

    #234041

    jlavallet
    Member

    I’m seeing this same error with Tomcat5.5.9. I suspect a corrupted classpath or something else in the java command line. Can I pass an extra argument or set some configuration option so that I can see the java command line when I click the Start menu item?

    #234052

    Riyad Kalla
    Member

    What start menu item are you referring to? How is this related to MyEclipse?

    #234083

    jlavallet
    Member

    Run/Stop MyEclipse Application Servers > Tomcat > Start

    see my other post please.

    #236290

    gilinachum
    Member

    I just had to move the jboss dir out of the “program files” dir.
    I guess it’s a white spaces problem…

    #236291

    Riyad Kalla
    Member

    This should have been fixed with 4.0 GA release, can you confirm you are running this version by checking the Window > Preferenecs > MyEclipse page?

    #236462

    gilinachum
    Member

    My case goes as follows:

    Jboss 4.0 used to lunch ok with the start/stop icon.

    It stop working a couple of days ago (with no resone i can think of) and wrote the message:
    java.lang.NoClassDefFoundError:
    Files\jboss-4/0/2\lib\endorsed
    Exception in thread”main”

    A restart or a removing-adding the server’s myeclipse config didn’t solved anthing.

    I googled for a solution and got to this forum thread.
    I alliminated any white spaces by moving from d:\program files\jboss… to d:\jboss…
    and redefined the server home location in the myeclipse configuration page.

    The Problem was solved.

Viewing 15 posts - 1 through 15 (of 19 total)
Reply To: jboss4.0.2 start error( with myeclipse4.0m2)

You must be logged in to post in the forum log in