June 20, 2017 at 10:37 pm #527550
I would like to know if MyEclipse Blue can deploy to WebSphere Liberty.
Below is the MyEclipse Blue installation summary.123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566*** Date:Wednesday, June 21, 2017 11:33:34 AM SGT** System properties:OS=WindowsVistaOS version=6.1.0Java version=1.6.0_13*** MyEclipse details:MyEclipse Blue EditionVersion: 10.0 BlueBuild id: 10.0-Blue-20111028*** Eclipse details:MyEclipse Blue EditionVersion: 10.0 BlueBuild id: 10.0-Blue-20111028Eclipse PlatformVersion: 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0fBuild id: I20110613-1736Eclipse Java Development ToolsVersion: 3.7.0.v20110520-0800-7z8gFchFMTdFYKuLqBLqRja9B15BBuild id: I20110613-1736Eclipse Plug-in Development EnvironmentVersion: 3.7.0.v20110504-0800-7b7qFVpFEx2XnmYtj_9RfO7Build id: I20110613-1736Eclipse Graphical Editing Framework GEFVersion: 3.7.0.v20110425-2050-777D-81B2Bz0685C3A6E34272Build id: 201105020958Eclipse RCPVersion: 3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgYBuild id: I20110613-1736Eclipse startup command=-oswin32-wswin32-archx86-showsplash-launcherC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\myeclipse-blue.exe-nameMyeclipse-blue--launcher.libraryC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll-startupC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar-installC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10-configurationC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\configuration-vmC:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dllJune 21, 2017 at 10:08 am #527612
The connector for Websphere Liberty profile is not available in MyEclipse 10.x. Please note that versions earlier than MyEclipse 2016 are no longer fully supported. Websphere support is improved drastically in our newer releases and I recommend you upgrade to working with MyEclipse 2017, our latest release based on Eclipse Neon.
The MyEclipse 2017 installer is available for download here : https://www.genuitec.com/products/myeclipse/download/
You can install MyEclipse 2017 to a different folder alongside your existing MyEclipse 10.x installation and use your current license. Right click in the Servers view, select New > Server and you will find the connector for Websphere Liberty Profile v8.5.
Please refer to this tutorial for detailed instructions about configuring application servers in newer versions of MyEclipse : https://www.genuitec.com/products/myeclipse/learning-center/deploy/myeclipse-application-server-connectors/
Let us know if you have any questions or if you see any issues upgrading to MyEclipse 2017.
MyEclipse SupportJune 29, 2017 at 4:49 am #528542
The validation is taking very long. I think more than 30 mins. See attached image.
June 29, 2017 at 8:57 am #528559
- This reply was modified 10 months, 3 weeks ago by hahagal.
Can you please clarify if the validation problem is in MyEclipse 10.x or in MyEclipse 2017?
Does the project have large number of XHTML/HTML files?
If you are still working with MyEclipse 10.x, then I suggest you check in MyEclipse 2017 as there are significant performance improvements in the newer releases when compared to MyEclipse 10.x
MyEclipse SupportJune 29, 2017 at 7:50 pm #528589
MyEclipse 10.x no issue. Validation issue is in MyEclipse 2017 Stable 1.0 (64-bits). Yes, we have more than 600 XHTML files.
June 30, 2017 at 3:19 am #528646
- This reply was modified 10 months, 3 weeks ago by hahagal.
Can you please send us 3-4 thread dumps from the time when the validation is taking too long?
Also send us the log file located at workspace dir/.metadata/.log.
Here is Eclipse page on how to get thread dump: https://wiki.eclipse.org/How_to_report_a_deadlock . Preferably use jstack [pid] > thread_dump.txt.
Please let me know if you have trouble getting the thread dump.
Apologies for inconvenience caused.
MyEclipse SupportJune 30, 2017 at 4:31 am #528649
I am using Windows. How should I get the thread dump using jstack [pid] > thread_dump.txt?
hahagalJune 30, 2017 at 8:46 am #528664
You can get the PID for the MyEclipse process from the Task Manager. Switch to the Details tab in the Task Manager and look for ‘eclipse.exe’ (MyEclipse shows up as ‘eclipse.exe’) and get the respective PID.
JStack comes along with JDK kit. If you are working with the JDK that is shipped with MyEclipse 2017 Stable, then the jstack command is available here :
Go to the command prompt and run the jstack command with the process id:
I suggest you write the thread dump to a file and share with us.
Example : jstack -l processid > D:\Test\kklog.txt
Hope this helps.
MyEclipse SupportJuly 5, 2017 at 9:55 pm #529353
I encountered some errors when collecting jstack logs.
jstack -l 3308 > C:\Belsize\Logfile\meb\jstack\log1.txt
jstack -F -l 3308 > C:\Belsize\Logfile\meb\jstack\log1.txt
hahagalJuly 5, 2017 at 10:01 pm #529355
Aside from the validation taking very long, after I deployed the projects, I am not able to associate shared libraries from WebSphere admin console.
Noticed some differences when projects deployed from MyEclipse 10.x and MyEclipse 2017 Stable 1.0:
1) Module name
2) Not OK button
hahagalJuly 6, 2017 at 4:27 am #529363
Regarding the jstack problem, we weren’t clear on which version of Windows you’re running MyEclipse. From your screenshots, it looks like the myeclipse.exe task isn’t the one to use for the process id in the jstack command. Look for a javaw.exe task (if there is more than one, it’s probably the one with the very high CPU utilization). Please use the PID for the javaw.exe process ID in the jstack command.July 6, 2017 at 5:15 am #529368
Regarding the shared libraries issue, this is because it is not support when deploying with “in-workspace” mode, which is the default for the Websphere connector. Refer the this document for further configuring the Websphere connector, including deployment modes.
However, you can also specify shared libraries with an EAR (enterprise application project), which will work for both deployment modes. Detailed instructions are mentioned in this topic reply.July 6, 2017 at 8:45 pm #529493
I left it to validate since yesterday about 10.30am until now it is still validating. Looks like its hang. I have collected the jstack and workspace logfile. Pls see attached.
Attachments:You must be logged in to view attached files.July 6, 2017 at 9:07 pm #529502
Regarding not able to add shared libraries, you are right, I am on “In-workspace” mode. After I set to “Classic” mode, works fine now.
Btw, we cannot choose “Classic” mode when we add the server? In MyEclipse 10.x we can do that. But in MyEclipse 2017, I need to add the server first then double click on it to set to “Classic” mode.
hahagalJuly 7, 2017 at 1:21 am #529524
In-workspace mode was experimental in release 10.x. Once it reached a stable implementation, it seemed sensible to make it the default as it is so much quicker for deployment and hot code updates. As you have seen, the server connector architecture has changed significantly since release 2015, hence the need to edit the configuration in a different way.
Thanks for the dumps and the log file; we’ll respond when we’ve had a chance to analyze them.