- This topic has 11 replies, 4 voices, and was last updated 11 years, 5 months ago by
.
-
Posts
-
I’m evaluating MyEclipse Blue 10.6 (with JRebel plugin) in our company.
I am getting following error in deployment (classic mode) log when trying to deploy a EAR:————————————————————————————————————————–
MyEclipse: deployment START exploded project: donreEAR server: websphere7Server#AppSrv01 time: Fri Oct 19 15:04:27 BRT 2012
————————————————————————————————————————–
Command line too long.
—————————————————————————————————————
MyEclipse: deployment END project: donreEAR server: websphere7Server#AppSrv01 time: Fri Oct 19 15:04:28 BRT 2012
—————————————————————————————————————I tried the other deployment connections, and both worked.
I want to use the JRebel Plugin, but with it the only deployment connection available is the classic mode.donrere,
Sorry that you are seeing this issue.
Can you answer some more questions for us ?
1. Can you please copy paste the Installation Details from MyEclipse > Installation Summary > Installation Details ? Also give us the OS and version details.
2. Can you please share the installation directory details for Websphere and the details of where your workspace is located.
3. Did you make any changes to the WAS server connector ?
Hello swapna,
Thanks for the reply.
Here are the answers to your questions:1 – Installation Details
OS: Windows 7 Pro @ 32 Bits
*** Date:
Segunda-feira, 22 de Outubro de 2012 14h13min55s BRST*** System properties:
OS=Windows7
OS version=6.1.0
OS arch=x86
Profile arch=x86
Window system=win32
Java version=1.6.0_31
Workspace=file:/C:/Java/workspace-3.7.2/
VM Args=-Xms40m
-Xmx384m
-XX:MaxPermSize=256m
-Djava.class.path=C:\Java\eclipse-3.7.2\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar*** Subscription information
Your 30-day trial period expires on Nov 16, 2012*** Eclipse details:
Eclipse SDKVersion: 3.7.2
Build id: M20120208-0800Blueprint: N/A
com.genuitec.myeclipse.blue.feature – 10.6.0.me201207261914
com.genuitec.myeclipse.desktop – 10.6.0.me201207261914
com.genuitec.myeclipse.jboss – 10.6.0.me201207261914
com.genuitec.myeclipse.persistence – 10.6.0.me201207261914
com.genuitec.myeclipse.struts – 10.6.0.me201207261914
com.genuitec.myeclipse.ws – 10.6.0.me201207261914
com.genuitec.myeclipse.ws.blue – 10.6.0.me201207261914
org.eclipse.datatools.connectivity.feature – 1.9.0.me201207261914
org.eclipse.datatools.enablement.feature – 1.9.0.me201207261914
org.eclipse.datatools.modelbase.feature – 1.9.0.v201106031100-77078CcNBHCBYKYEbNV
org.eclipse.datatools.sqldevtools.feature – 1.9.0.me201207261914
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.me201207261914
org.eclipse.jpt.jpadiagrameditor.feature – 1.0.0.me201207261914
org.eclipse.jst.common.fproj.enablement.jdt – 3.3.0.me201207261914
org.eclipse.jst.enterprise_ui.feature – 3.3.0.me201207261914
org.eclipse.jst.server_adapters.ext.feature – 3.3.0.me201207261914
org.eclipse.jst.server_adapters.feature – 3.2.100.me201207261914
org.eclipse.jst.server_ui.feature – 3.3.0.me201207261914
org.eclipse.jst.ws.axis2tools.feature – 1.1.200.me201207261914
org.eclipse.sapphire.platform – 0.3.0.201106221325
org.eclipse.wst.common.fproj – 3.3.0.me201207261914
org.eclipse.wst.server_adapters.feature – 3.2.100.me201207261914
org.eclipse.xsd – 2.7.0.v20110606-0949
org.zeroturnaround.myeclipse.feature – 1.0.4.RELEASE-201207191833com.microsoft.tfs.client.eclipse.feature – 11.0.0.201208021316
jd.edi.eclipse.feature – 0.1.3
org.eclipse.cvs – 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C
org.eclipse.cvs.source – 1.3.100.v20110520-0800-7B78FHl9VF7BD7KBM4GP9C
org.eclipse.draw2d – 3.7.0.v20110425-2050-46-7w3122153603161
org.eclipse.epp.mpc – 1.1.1.I20110907-0947
org.eclipse.equinox.p2.core.feature – 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129
org.eclipse.equinox.p2.core.feature.source – 1.0.1.v20110906-1605-8290FZ9FVKHVRKtmx3fpNuo02129
org.eclipse.equinox.p2.discovery.feature – 1.0.101.R37x_v20110909-4-8_9oB5885K5B28WKK
org.eclipse.equinox.p2.extras.feature – 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO
org.eclipse.equinox.p2.extras.feature.source – 1.0.1.v20110906-1605-7A4FD4DiVOMap8cHSc6vPuny4gqO
org.eclipse.equinox.p2.rcp.feature – 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO
org.eclipse.equinox.p2.rcp.feature.source – 1.0.1.v20110906-1605-782EqBqNKGVkiV-PUsgz-uny4gqO
org.eclipse.equinox.p2.user.ui – 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl
org.eclipse.equinox.p2.user.ui.source – 2.1.2.R37x_v20110815-1155-6-Bk8pYWZz0qUTX5I15GZWwbXkrl
org.eclipse.help – 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
org.eclipse.help.source – 1.3.0.v20110530-0844-7i7uFFmFFl8nvqbDpEqTvx
org.eclipse.jdt – 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
org.eclipse.jdt.source – 3.7.2.v20120120-1414-7z8gFcuFMP7BW5XTz0jLTnz0l9B1
org.eclipse.pde – 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E–0
org.eclipse.pde.source – 3.7.2.v20120120-1420-7b7rFUOFEx2Xnqafnpz0E–0
org.eclipse.platform – 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q
org.eclipse.platform.source – 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q
org.eclipse.rcp – 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272
org.eclipse.rcp.source – 3.7.2.v20120120-1424-9DB5FmnFq5JCf1UA38R-kz0S0272
org.eclipse.sdk – 3.7.2.r37x_v20111213-7Q7xALDPb32vCjY6UACVPdFTz-icPtJkUadz0lMmk4z-8
org.zeroturnaround.eclipse.feature – 5.0.1.RELEASE-201207191833
org.zeroturnaround.eclipse.wtp.feature – 5.0.0.RELEASE-201207191833Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
C:\Java\eclipse-3.7.2\plugins\org.eclipse.platform_3.7.2.v201202080800\splash.bmp
-launcher
C:\Java\eclipse-3.7.2\eclipse.exe
-name
Eclipse
–launcher.library
C:\Java\eclipse-3.7.2\plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502\eclipse_1406.dll
-startup
C:\Java\eclipse-3.7.2\plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
–launcher.overrideVmargs
-vm
C:\Program Files\Java\jre6\bin\client\jvm.dll2 – Installation Directories
WAS7 – C:\Java\WAS7
Eclipse Workspace – C:\Java\workspace-3.7.2
EAR Sources (EJB+Web) – C:\TFSProjects\Administrative\Donrere\branches\Donrere V01.00.00-00\DES3 – Connector Changed Setttings:
Instance Configuration: Enabled
Name: AppSrv01
Profile Location: C:\Java\WAS7\profiles\AppSrv01
Default Server Launch Mode: Debug mode
Security: Enabled
Deployment connection: Classic Mode
Optional Java VM arguments: -XX:MaxPermSize=512m -Duser.timezone=GMT-02:00donrere,
Thank you for the details. I have escalated it to a dev team member. They will get back to you.
Sorry for inconvenience caused.
donrere,
Apologies for the delay in addressing the issue. The dev team was busy with higher priority issues.They are looking into this issue right away.
Coming to the license issue, on the expired subscription dialog, you will see a button which allows you to extend the subscription.
If you cannot find it, then please email [email protected] with a link to this thread.
Let us know if you see any issues.
donrere,
I hope you had no problems extending your trial licence! I am very sorry to keep you waiting for such a long time. However, I have not been able to reproduce your issue. I suspect that the problem may regard classpath for EJBDeploy tool. I can give you tips, which may solve the issue.
1. Right click on your EAR project in “Package Explorer” and choose “Properties”.
2. Navigate to MyEclipse/EAR property page, and uncheck “Run EJBDeploy tool” listed under “WebSphere Deployment Options”.That way the EJBDeploy tool will not run on each deployment.
If you have EJB 2.x projects in you EAR, you will need to run EJB Deploy tool manually inside MyEclipse before first deployment, and after that, each time you change API of any EJB. To launch it, right click on the EAR project -> MyEclipse -> Run EJBDeploy. On the first run it will ask you to configure target server for each of your EJB projects. EJB stubs will be generated in “.ejbdeploy” folder of each EJB 2.x project. Note that if your RAD project has EJB stubs generated by WAS in one of the source folders, you will need to delete them. The regenerated EJB stubs should be correctly synchronized with the deployment by JRebel.
Let us know if it helped! It would be perfect if you could attach an example project, which fails with that error.
Sorry for the delay in replying.
I was able to solve the problem by adding the following key in donreEAR\.settings\com.genuitec.eclipse.j2eedt.core.prefs file:
C\:\\\TFSProjects\\\Administrative\\\Donrere\\\branches\\\Donrere V01.00.00-00\\\DES\\\donreEAR\\\*.jarSorry, bad copy/paste.
j2ee.deployment.ear.ejbdeploy.buildpath=C\:\\\TFSProjects\\\Administrative\\\Donrere\\\branches\\\Donrere V01.00.00-00\\\DES\\\donreEAR\\\*.jar
This is still a problem with MEB 10.7.1. The project builds and deploys, but never installs correctly on WAS 7.
The workaround described will even work even if j2ee.deployment.ear.ejbdeploy.buildpath has an empty value! It just must be in the file as follows:
EAR project/.settings/com.genuitec.eclipse.j2eedt.core.prefs
j2ee.deployment.ear.ejbdeploy.buildpath=Setting this value deployment and install of the project works perfectly. No “command line is too long”.
Can someone at Genuitec explain how this property changes the command to deploy and install? The same project works perfectly in 10.0.0. This issue appeared first when I upgrade to 10.6.
mjmesiti,
EJB Deploy tool in some cases needs to have an additional classpath provided. Starting with 10.6, ME is passing project’s classpath to the EJB Depoly tool. Apparently, the classpath can be too long in some rare cases – Windows has a problem if command line is too long. That’s why, if user overrides classpath, the process is working fine.
