facebook

Error with MyEclipse 6.0.1 when running JBoss 3.2.2

💡
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 15 total)
  • Author
    Posts
  • #280372 Reply

    pradeep1231
    Member

    This message has not been recovered.

    #280377

    Loyal Water
    Member

    What was the optional agrument you set ? Did you set it under the connector or in the eclipse.ini file ?

    11:23:25,859 ERROR [general] Cannot deserialize EmployeeTree: java.io.FileNotFoundException: c:\jboss-3.2.2\server\default\conf\cp.dev\serialize\employee_tree.dat (The system cannot find the path specified)

    Is this the error that you are referring to ?

    #280491

    pradeep1231
    Member

    Hi,
    I have set the heap size parameters(-Xms512m Xmx1024m) in at Arguments in the connector.

    I am referring to the following error not the one you referred.

    11:23:46,043 INFO [audit] Loading performance management data…
    11:26:12,655 ERROR [STDERR] java.lang.OutOfMemoryError

    Thanks in Advance,
    Pradeep

    #280508

    Loyal Water
    Member

    Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

    Can you add this line to your eclipse.ini file and check if the error goes away –

    
    -vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=128M 
    
    #280578

    pradeep1231
    Member

    Hi,
    Please find the Installation details as follows.

    ———————————————————-
    *** Date:
    Friday, January 11, 2008 2:47:14 PM GMT+05:30

    ** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    Eclipse Platform

    Version: 3.3.1.R33x_r20070911-_19UEkpF-B7Uh2hKy75y
    Build id: M20070921-1145

    Eclipse RCP

    Version: 3.3.1.R33x_r20070802-8y8eE8sEV3Fz0z0GlHJrXvTAUS
    Build id: M20070921-1145

    Eclipse Java Development Tools

    Version: 3.3.1.r331_v20070629-7o7jE72EDlXAbqAcnbmyg1rf8RIL
    Build id: M20070921-1145

    Eclipse Plug-in Development Environment

    Version: 3.3.1.R33x_r20070802-7N7M3D1VIA_52JsDFsEC
    Build id: M20070921-1145

    Eclipse Project SDK

    Version: 3.3.1.R33x_r20070802-7M7J78_mu1mnlRa7A4Ns52XeZ6D0
    Build id: M20070921-1145

    Eclipse Graphical Editing Framework

    Version: 3.3.1.v20070814
    Build id: 20070814-1555

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\MyEclipse\eclipse\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\MyEclipse\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.1.R33x_v20070828\eclipse_1020.dll
    -startup
    C:\MyEclipse\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
    -exitdata
    ca4_74
    -vm
    C:\MyEclipse\jre\bin\javaw.exe

    ————————————————————————————————

    my eclipse.ini file already contains

    -showsplash
    com.genuitec.myeclipse.product
    –launcher.XXMaxPermSize
    256m
    -vmargs
    -Xms128m
    -Xmx512m
    -Duser.language=en
    -XX:PermSize=128M
    -XX:MaxPermSize=256M

    Looking forward for your solution.

    Thanks & Regards,
    Pradeep

    #280600

    Loyal Water
    Member

    Notice in connectors there are the “optional program arguments” and “optional vm arguments”.

    You will have to set them in the VM args, not the Program args. Can you make this change and test again.

    #280640

    pradeep1231
    Member

    When I am setting the optional vm arguments. It is throwing the error in the console “Unrecognized option: -vmargs”. popup error message is “Could not create java virtual machine”.

    Could you plz guide me towards the solution?

    Thanks & Regards,
    Pradeep

    #280669

    Loyal Water
    Member

    You done have to append -vmargs before your arguments. Just enter them without “-vmargs”.
    http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp

    #280743

    pradeep1231
    Member

    When I copy the content with out -vmargs at MyEclipse–>Servers–>JBoss 3.x–>Launch–>Runmode–>Create Launch Configuration–>(x)=Arguments–>VM Arguments and apply and run the server..

    The same Error(java.lang.OutOfMemory) still coming..

    When I look back to the VM Arguments the line I copied(-Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=128m) is not there..

    Thanks
    Pradeep

    #280748

    Loyal Water
    Member

    Pradeep,
    You dont have to create a lanch configuration and enter the arguments. This is what I would like you to do:-

    1. Go to Windows > Prefs > MyEclipse > Servers > JBoss > JBoss 3.x and confiure your connector to look like this:-
    https://www.genuitec.com/forums/topic/jboss-3-2-what-does-a-configured-connector-look-like/

    2. Go to Windows > Prefs > MyEclipse > Servers > JBoss > JBoss 3.x > JDK and set the JBoss JDK to your JDK 1.5.

    3. Go to Windows > Prefs > MyEclipse > Servers > JBoss > JBoss 3.x > JDK and enter your memory arguments in the “Optional Java VM arguments” test box without -vmargs.

    Let me know if the problem persists.

    #280749

    pradeep1231
    Member

    Ya Now I am able to run the server..

    Thanks a lottttt Nipun.

    Regards,
    Pradeep

    #280775

    pradeep1231
    Member

    Hi Nipun,

    After deployment the application server is getting restarted automatically. Is there any way that we can avoid restarting of application server after every deployment??

    Thanks & Regards,
    Pradeep

    #280790

    Loyal Water
    Member

    Pradeep,
    That should not happen. How do you know the server is restarting ? From the console messages ?

    #280813

    pradeep1231
    Member

    Hi Nipun,

    Yes, I am able to see that the server getting restarted through Console only.

    Thanks & Regards,
    Pradeep

    #280947

    Loyal Water
    Member

    I think you mean the *Context* is restarting, not the entire server. JBoss embeds Tomcat, and Tomcat, by default, will reload it’s context each time a file changes.

    You can turn this off by using the “reloadable=false” argument in the <context> arg in Tomcat.

    Please refer to the Tomcat or JBoss docs for more information.

Viewing 15 posts - 1 through 15 (of 15 total)
Reply To: Error with MyEclipse 6.0.1 when running JBoss 3.2.2

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