- This topic has 13 replies, 6 voices, and was last updated 11 years, 9 months ago by support-swapna.
-
AuthorPosts
-
dadelcasMemberHello. I’m migrating my projects from MyEclipse 9.1 to MyEclipse 10. I’m using Tomcat 5.5 to deploy during the development and Maven for the PLC. The hot deployment feature is not working in the MyEclipse 10 and I haven’t found a work around this problem. Any advice?
support-swapnaModeratordadelcas ,
Sorry that you are seeing this issue with MyEclipse.
Can you answer some more questions for us ?
1) Can you share the Build ID from Help > About MyEclipse Enterprise Edition > Build ID ? Also share your OS and version details.
2) Can you clarify if you are using exploded deployment, that you are starting the server in Debug mode ? If you are using the Servers view to launch Tomcat and are selecting “Run”, you need to stop it and select “Debug”… the server has to be running in Debug mode.
3) Can you switch to a new workspace, create a new project with sample java files and check if the hot deployment is working ? It might also be a workspace/cache issue.
4) Can you also check the .log file which is located at <workspace dir>/.metadata/.log for any errors of interest ? If yes then paste the errors here for us to investigate further.
dadelcasMemberHi,
1) MyEclipse
MyEclipse Enterprise Workbench
Version: 10.0
Build id: 10.0-20111028OS
Windows 7 Professional 32-bit + Service Pack 1
Processor Intel Xeon X5550 @ 2.67 GHz
RAM 3.0 GB2) The web server is Apache Tomcat 5.5.34 with launch mode Debug and started in Debug mode as well. The folder WEB-INF/classes is empty – jar files were not exploded into the working directory.
3) I’ll do it and come back to you later.
4) I didn’t see anything of interest in the log file, no exceptions indeed.
After restarting and redeploying the .project multiple times, WEB-INF/classes was populated with the exploded packages and hot deployment seems to work now. It might have been a cache problem but how can it be solved? We need to migrate the dev environment of multiple developers.
Thanks!
support-swapnaModeratordadelcas ,
Glad that it is working.
1) What exactly is your concern now that the hot deployment is working ?
2) Are you worried about switching workspaces if the problem ever occurs again?
dadelcasMemberThe problem is I’m testing before migrating the projects because the whole team will have to switch to version 10 once everything is working well but we cannot afford wasting time cleaning, rebuilding and going over again – I spent 3 days trying to get it working and I still don’t know what has solved it. We are 10 people currently using version 9.1
Cheers
support-tonyKeymasterdadelcas,
Is it possible for you to try migrating another of your team as a further test? These odd problems are often specific to an individual’s set up. It’s not unusual to see a problem reported that can’t be replicated by other members of a team, even if the systems appear to be identical.
As you’ve probably seen, both 9.1 and 10.0 can exist on the same machine and can use the same workspace (though you may want to back it up, for safety). So it need not be a one-way migration if any members do encounter problems that can’t be sorted quickly.
nayeemtpMemberI too faced the same problem but I m getting the following exception whenever i change the source code file
Exception log from .log file
!ENTRY com.genuitec.eclipse.ast.deploy.core 1 0 2012-04-12 12:37:56.136
!MESSAGE Unable to set deployment errorMarker
!STACK 1
org.eclipse.core.internal.resources.ResourceException: The resource tree is locked for modifications.
at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:116)
at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2282)
at org.eclipse.core.internal.resources.Marker.setAttribute(Marker.java:234)
at com.genuitec.eclipse.ast.deploy.core.Deployment.addErrorMarker(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.Deployment.setUptoDate(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.setUptoDate(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.EARDeployment.resourceChanged(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor$C.�(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor$C.visit(Unknown Source)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at com.genuitec.eclipse.ast.deploy.core.DeployedResourceEventProcessor.resourceChanged(Unknown Source)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:395)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1530)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:156)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
!SUBENTRY 1 org.eclipse.core.resources 4 380 2012-04-12 12:37:56.136
!MESSAGE The resource tree is locked for modifications.
support-swapnaModeratornayeemtp ,
Sorry that you are seeing this issue.
1. Can you please share the installation details from MyEclipse > Installation Summary > Installation Details ? Paste them here for us.
2. Which editor are you using at the time of the error ?
3. Can you switch to a new workspace, create a new project and check if you see the issue?
nayeemtpMemberHi Swapna,
1. Installation Summary
*** Date:
Tuesday, 17 April, 2012 4:32:06 PM IST** System properties:
OS=Linux
OS version=2.6.32
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 10.0
Build id: 10.0-20111028*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 10.0
Build id: 10.0-20111028Eclipse startup command=-os
linux
-ws
gtk
-arch
x86
-showsplash
-launcher
/home/nayeem/Genuitec/MyEclipse 10/myeclipse
-name
Myeclipse
–launcher.library
/home/nayeem/Genuitec/MyEclipse 10//../Common/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.100.v20110505/eclipse_1407.so
-startup
/home/nayeem/Genuitec/MyEclipse 10//../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
–launcher.overrideVmargs
-exitdata
21800b
-install
/home/nayeem/Genuitec/MyEclipse 10
-configuration
/home/nayeem/Genuitec/MyEclipse 10/configuration
-vm
/home/nayeem/Genuitec/Common/binary/com.sun.java.jdk.linux.x86_1.6.0.013/bin/java2. MyEclipse JavaEditor
3. Cant do it now
support-swapnaModeratorNayeem ,
Thank you for the details.
Can you please update to the latest release 10.1 and check if you still see the issue?
Go to Help > MyEclipse Configuration Center > Software > Software Updates Available. Select MyEclipse Enterprise Edition 10.1, apply the changes,follow the wizard and restart the IDE when it prompts.
Let us know how it works for you.
miguelmuMemberI’m too facing this issue. I’m using In-Workspace mode with WAS6.1 . I’m able to see changes to jsp,html,js files without having to reload the application but the Java hot code replace is not working. Is this a known issue?
I’m using version 10.1
support-swapnaModeratormiguelmu ,
Sorry that you are seeing this issue. I could not replicate it at my end.
Can you answer some more questions for us ?
1. Can you please give the installation details from MyEclipse > Installation Summary > Installation Details ? Paste them here.
2. Is this project imported from elsewhere or created in MyEclipse itself ?
3. Can you create a simple EAR project and check if you are seeing the same issue?
4. Clear the contents of the .log file which is located at <workspace dir>/.metadata/.log.Delete the contents of the deployment log, now try deploying the application and paste the deployment log for us.
5. Also check the .log file for any errors of interest and paste them here for us.
CheckingMemberI too facing this issue. I’m using In-Workspace mode with IBM websphere7.0 . I’m able to see changes to jsp,html files without having to reload the application but the Java hot code replace is not working.
The project was creating in RAD.
Installation details are
*** Date:
Thursday, January 17, 2013 8:45:59 AM IST*** System properties:
OS=WindowsXP
OS version=5.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.6.0_13
Workspace=file:/C:/MobileDrugPricing/
VM Args=-Xmx512m
-XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
-Dosgi.nls.warnings=ignore
-Djava.class.path=C:\PROGRA~1\MYECLI~1\MYECLI~1\../Common/plugins/OR02A7~1.JAR*** Subscription information
Product Id: E3MB (MyEclipse Blue Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20130124
Number of users: 9*** Eclipse details:
MyEclipse Blue EditionVersion: 10.1 Blue
Build id: 10.1-Blue-20120316Blueprint: MyEclipse Blue Edition 10
com.genuitec.myeclipse.blue.feature – 10.1.0.me201203170059
com.genuitec.myeclipse.database – 10.1.0.me201203170059
com.genuitec.myeclipse.db2 – 10.1.0.me201203170059
com.genuitec.myeclipse.desktop – 10.1.0.me201203170059
com.genuitec.myeclipse.editor – 10.1.0.me201203170059
com.genuitec.myeclipse.geronimo – 10.1.0.me201203170059
com.genuitec.myeclipse.glassfish – 10.1.0.me201203170059
com.genuitec.myeclipse.icefaces.feature – 10.1.0.me201203170059
com.genuitec.myeclipse.iedebugger – 10.1.0.me201203170059
com.genuitec.myeclipse.imageeditor – 10.1.0.me201203170059
com.genuitec.myeclipse.jboss – 10.1.0.me201203170059
com.genuitec.myeclipse.jetty – 10.1.0.me201203170059
com.genuitec.myeclipse.jonas – 10.1.0.me201203170059
com.genuitec.myeclipse.jrun – 10.1.0.me201203170059
com.genuitec.myeclipse.jsf – 10.1.0.me201203170059
com.genuitec.myeclipse.matisse – 10.1.0.me201203170059
com.genuitec.myeclipse.maven – 10.1.0.me201203170059
com.genuitec.myeclipse.oracle – 10.1.0.me201203170059
com.genuitec.myeclipse.orion – 10.1.0.me201203170059
com.genuitec.myeclipse.persistence – 10.1.0.me201203170059
com.genuitec.myeclipse.pulse – 10.1.0.me201203170059
com.genuitec.myeclipse.reports – 10.1.0.me201203170059
com.genuitec.myeclipse.resin – 10.1.0.me201203170059
com.genuitec.myeclipse.struts – 10.1.0.me201203170059
com.genuitec.myeclipse.sun – 10.1.0.me201203170059
com.genuitec.myeclipse.tomcat – 10.1.0.me201203170059
com.genuitec.myeclipse.uml2 – 10.1.0.me201203170059
com.genuitec.myeclipse.visualvm – 10.1.0.me201203170059
com.genuitec.myeclipse.visualvm.server – 10.1.0.me201203170059
com.genuitec.myeclipse.weblogic – 10.1.0.me201203170059
com.genuitec.myeclipse.ws – 10.1.0.me201203170059
com.genuitec.myeclipse.ws.blue – 10.1.0.me201203170059
org.eclipse.birt – 2.6.1.me201203170059
org.eclipse.datatools.connectivity.feature – 1.9.0.me201203170059
org.eclipse.datatools.enablement.feature – 1.9.0.me201203170059
org.eclipse.datatools.modelbase.feature – 1.9.0.v201106031100-77078CcNBHCBYKYEbNV
org.eclipse.datatools.sqldevtools.feature – 1.9.0.me201203170059
org.eclipse.emf – 2.7.0.v20110606-0949
org.eclipse.gef – 3.7.0.v20110425-2050-777D-81B2Bz0685C3A6E34272
org.eclipse.graphiti.feature – 0.8.0.v20110607-1252
org.eclipse.jpt.jpa.feature – 3.0.0.me201203170059
org.eclipse.jpt.jpadiagrameditor.feature – 1.0.0.me201203170059
org.eclipse.jst.common.fproj.enablement.jdt – 3.3.0.me201203170059
org.eclipse.jst.enterprise_ui.feature – 3.3.0.me201203170059
org.eclipse.jst.server_adapters.ext.feature – 3.3.0.me201203170059
org.eclipse.jst.server_adapters.feature – 3.2.100.me201203170059
org.eclipse.jst.server_ui.feature – 3.3.0.me201203170059
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201203170059
org.eclipse.m2e.feature – 1.0.0.me201203170059
org.eclipse.sapphire.platform – 0.3.0.201106221325
org.eclipse.wst.common.fproj – 3.3.0.me201203170059
org.eclipse.wst.server_adapters.feature – 3.2.100.me201203170059
org.eclipse.xsd – 2.7.0.v20110606-0949
org.springframework.ide.eclipse.feature – 2.7.1.me201203170059com.android.ide.eclipse.adt – 20.0.3.v201208082019-427395
com.android.ide.eclipse.ddms – 20.0.3.v201208082019-427395
com.android.ide.eclipse.hierarchyviewer – 20.0.3.v201208082019-427395
com.android.ide.eclipse.traceview – 20.0.3.v201208082019-427395
com.collabnet.subversion.merge.feature – 2.2.4
fr.obeo.acceleo.bridge.feature – 2.6.0.200906261742
org.eclipse.cvs – 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C
org.eclipse.draw2d – 3.7.0.v20110425-2050-46-7w3122153603161
org.eclipse.equinox.p2.core.feature – 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129
org.eclipse.equinox.p2.extras.feature – 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO
org.eclipse.equinox.p2.rcp.feature – 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO
org.eclipse.equinox.p2.user.ui – 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl
org.eclipse.help – 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
org.eclipse.jdt – 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
org.eclipse.jsf.feature – 3.3.0.me201203170059
org.eclipse.ocl – 3.1.0.v20110606-1427
org.eclipse.pde – 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E–0
org.eclipse.platform – 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q
org.eclipse.rcp – 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272
org.tigris.subversion.clientadapter.feature – 1.6.12
org.tigris.subversion.clientadapter.javahl.feature – 1.6.17
org.tigris.subversion.clientadapter.svnkit.feature – 1.6.15
org.tigris.subversion.subclipse – 1.6.18
org.tigris.subversion.subclipse.graph.feature – 1.0.9
org.tigris.subversion.subclipse.mylyn – 3.0.0Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_4.2.0.v201201111650\eclipse_4201.dll
-startup
C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-install
C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10
-configuration
C:\Program Files\MyEclipse Blue Edition\MyEclipse Blue Edition 10\configuration
-vm
C:\Program Files\MyEclipse Blue Edition\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll
support-swapnaModeratorChecking,
Hot swap depends on the type of change made. This isn’t something controlled by MyEclipse but really just depends on the WAS and the JVM being used to run it. On our side, we make sure the re-compiled classes are placed in the correct location.
Whether hot swap works (or not) depends on the type of change you are making – some changes will be automatically picked up, but some may not. For example, could you try a simple dummy method with a String return value? If you change this return value to something else and save the file, this should certainly work. However, adding new methods, changing signatures and adding or removing classes will typically not work. What changes are you trying to make?
Can you also please update to the latest version of MyEclipse 10.7, switch to a new workspace, import the RAD project, enhance it to work with MyEclipse and check if the issue exists ?
You can download the installer for 10.7 and install it to a different location while keeping the 10.1 intact.
Let us know how it works for you.
-
AuthorPosts