Genuitec » All Posts Wed, 16 Jan 2019 06:45:25 +0000 en-US <![CDATA[Reply To: WAS 8.5 Application Deployment Won\'t Start (ADMA0116W) with MyEclipse 2018.12]]> Wed, 16 Jan 2019 10:36:38 +0000 support-swapna Steve,

Thank you for the details. The error in the log points to a problem with default servlet mapping.
Caused by: SRVE0303E: Servlet name for the servlet mapping /rest/* could not be found.

Similar issue is discussed here :

If you are still seeing the problem then please share with us the complete server log file, SystemOut.log which is located in your WAS server install directory :
WebSphere 8.5\profiles\profilename\logs\servername\SystemOut.log. You can change the extension on the file to .txt and attach it here to help us investigate further. Also please share with us your workspace log file which is located in your workspace dir/.metadata/.log.

Regarding the error when starting MyEclipse 2018 using 2017 JVM, it could be a result of trying to point to 32 bit JVM on a 64 bit version of MyEclipse 2018. Please point to a 64 bit version of Java 8 and check.

Genuitec Support

]]> <![CDATA[Reply To: WAS 8.5 Application Deployment Won\'t Start (ADMA0116W) with MyEclipse 2018.12]]> Wed, 16 Jan 2019 06:02:17 +0000 stevebradford Clarification as requested:
1. The application deploys to WAS 8.5 successfully (classic/packaged options)
2. The application always fails to start under MyEclipse 2018 (never worked for 2018 but 2017 does)
3. MyEclipse 2018 deploys and starts the EAR OK on WAS 7
4. Building the EAR artefact outside of ME 2018 always results in a successful deployment & start on WAS 8.5
eg Manual installation of Jenkins build
5. See the attached the start-up error dump. It isn’t helpful to determine the jar causing the error (frameworks are wonderful!)
6. I tried running ME 2018 using the 2017 JVM but both javaw.exe and jvm.dll errored (but do run 2017)
7. I started ME 2018 using the WAS 8.5 JVM, it started but then gave me a security integrity alert and quit

Other 1.8 JVMs also fail



You must be logged in to view attached files.
]]> <![CDATA[Reply To: DEMO]]> Wed, 16 Jan 2019 02:40:10 +0000 xuelinr

You must be logged in to view attached files.
]]> <![CDATA[Reply To: DEMO]]> Wed, 16 Jan 2019 02:40:09 +0000 xuelinr

You must be logged in to view attached files.
]]> <![CDATA[DEMO]]> Wed, 16 Jan 2019 02:39:31 +0000 xuelinr ASDVASDV

]]> <![CDATA[iniciando]]> Wed, 16 Jan 2019 02:22:17 +0000 fgulfo iniciando con CodeMix

]]> <![CDATA[]]> Wed, 16 Jan 2019 02:21:26 +0000 wsh8115385 <![CDATA[Reply To: WAS 8.5 Application Deployment Won\'t Start (ADMA0116W) with MyEclipse 2018.12]]> Tue, 15 Jan 2019 20:45:43 +0000 Brian Fernandes Steve,

There haven’t been changes to MyEclipse 2018 in the WAS deployment area, so seeing it fail in 2018 when it works in 2017 is surprising.

Just a couple of questions in addition to Swapna’s above:

6) Research I’ve done suggests it’s a java reflection class load problem of a different JAR version to what is expected
Can you share the name and version of the JAR involved?

7) MyEclipse 2018 runs with Java 10, while 2017 runs with Java 8. Of course, this should not matter much as your server should be starting with an IBM JDK (as Swapna asked in #4 above) but, being a major difference between 2018 and 2017, you might want to try running MyEclipse 2018 with a Java 8 JDK instead (you can use the VM from the binary folder in your 2017 install) and see if that works. You need to change the -vm argument in your myeclipse.ini file to achieve this, please let us know if you need help.

8) brute-force idea is to export an EAR from MyEclipse 2017 and from 2018 using the File > Export > Java EE > EAR option, and then extract both EARs. If you do a file system diff over the extracted contents, it may be easy to spot a key difference, which will help us figure out what is going wrong.

Hope we’re able to get you deploying with 2018 in short order!

]]> <![CDATA[Reply To: Cannot disable DevStyle preference page]]> Tue, 15 Jan 2019 14:21:44 +0000 support-swapna Hi,

Thank you for the details and the screenshots. I could replicate the problem at my end with the missing ECT page with DevStyle disabled. I have filed a bug for the dev team to look into it. We will keep you posted when the fix is out.

Apologies for inconvenience caused. Thank you for reporting it.

Genuitec Support

]]> <![CDATA[Reply To: How to checkout from Git repository]]> Tue, 15 Jan 2019 09:05:57 +0000 support-swapna hahagal,

Glad that you are working with a newer release of MyEclipse. MyEclipse CI 2018.12.0 is the latest.Yes, you can apply the same instructions as the Git functionality in MyEclipse is coming from the EGit plugin which is shipped along with MyEclipse.

Let us know if you have any further questions.

Genuitec Support

]]> <![CDATA[Reply To: WAS 8.5 Application Deployment Won\'t Start (ADMA0116W) with MyEclipse 2018.12]]> Tue, 15 Jan 2019 08:45:29 +0000 support-swapna Steve,

Sorry that you are seeing this issue.

Can you please give us some more details to help us investigate further?

1. It is not clear what exactly you mean by the deployment does not start. Is the deployment itself failing or the deployed application does not run? Please clarify.
2. Are you seeing this problem only recently? Did this project ever work fine in MyEclipse 2018 post updating from MyEclipse 2017?
3. If you are seeing this problem only recently, then can you please let us know if there has been any changes to the MyEclipse IDE or the application or the WAS server (applied a fix patch,upgraded to latest version etc)
4. Is the WAS 8.5 configured to run with the IBM JDK? You can verify the same by double clicking on the WAS server entry in the Servers view to open the Overview page and then click on ‘Runtime Environment’ link and verify the configured JDK.
5. Please share with us the full stacktrace of the ADMA0116W error.

Apologies for inconvenience caused.

Genuitec Support

]]> <![CDATA[Reply To: How to checkout from Git repository]]> Tue, 15 Jan 2019 07:48:41 +0000 hahagal Hi Swapna,

I have another later My Eclipse CI version. Do I apply using the same instruction above?

*** Date:
Tuesday, January 15, 2019 at 3:47:39 PM Singapore Standard Time

*** System properties:
OS version=6.1.0
OS arch=amd64
Profile arch=x86_64
Window system=win32
Java version=10.0.1
VM Args=-Xms256m
C:\Users\admin\AppData\Local\MyEclipse CI\\plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar

*** Subscription information
Product Id: E3MB (MyEclipse Blue Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20190515
Number of users: 3

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: CI 2018.9.0
Build id: 16.0.0-20180903 – 14.0.0.me201808311557
com.genuitec.myeclipse.database – 15.0.1.me201808311557
com.genuitec.myeclipse.db2 – 15.0.1.me201808311557
com.genuitec.myeclipse.desktop – 14.0.0.me201808311557
com.genuitec.myeclipse.enterprise.workbench – 14.0.0.me201808311557
com.genuitec.myeclipse.icefaces.feature – 14.0.0.me201808311557
com.genuitec.myeclipse.imageeditor – 14.0.0.me201808311557
com.genuitec.myeclipse.jsf – 14.0.0.me201808311557
com.genuitec.myeclipse.maven – 14.0.0.me201808311557
com.genuitec.myeclipse.persistence – 14.0.0.me201808311557
com.genuitec.myeclipse.reports – 14.0.0.me201808311557
com.genuitec.myeclipse.struts – 14.0.0.me201808311557
com.genuitec.myeclipse.uml2 – 14.0.0.me201808311557
com.genuitec.myeclipse.visualvm – 14.0.0.me201808311557 – 14.0.0.me201808311557 – 14.0.0.me201808311557
com.skyway.myeclipseforspring.feature – 15.0.1.me201808311557
org.eclipse.birt – 4.8.0.me201808311557
org.eclipse.datatools.connectivity.feature – 1.14.1.me201808311557
org.eclipse.datatools.enablement.feature – 1.14.1.me201808311557
org.eclipse.datatools.modelbase.feature –
org.eclipse.datatools.sqldevtools.feature – 1.14.1.me201808311557
org.eclipse.emf – 2.14.0.v20180529-1144
org.eclipse.gef –
org.eclipse.graphiti.feature –
org.eclipse.jpt.jpa.feature – 3.5.101.me201808311557
org.eclipse.jpt.jpadiagrameditor.feature – 1.2.300.me201808311557
org.eclipse.jst.common.fproj.enablement.jdt – 3.10.0.me201808311557
org.eclipse.jst.enterprise_ui.feature – 3.9.2.me201808311557
org.eclipse.jst.server_adapters.ext.feature – 3.3.602.me201808311557
org.eclipse.jst.server_adapters.feature – 3.2.500.me201808311557
org.eclipse.jst.server_ui.feature – 3.4.300.me201808311557 – 1.1.301.me201808311557
org.eclipse.m2e.feature – 1.9.0.me201808311557
org.eclipse.sapphire.platform –
org.eclipse.wst.common.fproj – 3.7.1.me201808311557
org.eclipse.wst.server_adapters.feature – 3.2.700.me201808311557
org.eclipse.xsd – 2.14.0.v20180127-0547
org.springframework.ide.eclipse.feature – 3.9.5.me201808311557

angularjs-eclipse-feature – 1.2.0.me201808311557
angularjs-eclipse-jsp-feature – 1.2.0.me201808311557
angularjs-eclipse-php-feature – 1.2.0.me201808311557
com.eclipsesource.j2v8.feature –
com.github.eclipsecolortheme.feature – 1.0.0.me201808311557
com.vmware.vfabric.ide.eclipse.tcserver – 3.9.5.me201808311557
com.vmware.vfabric.ide.eclipse.tcserver.insight – 3.9.5.me201808311557
fr.obeo.acceleo.bridge.feature – 2.6.0.me201808311557
io.emmet.eclipse – 14.0.0.me201808311557
jdt-codemining-feature –
net.jeeeyul.pdetools.feature – 1.2.6.me201808311557
net.jeeeyul.swtend.feature – 2.2.5.me201808311557
org.chromium.debug –
org.chromium.sdk –
org.chromium.sdk.wipbackends –
org.dadacoalition.yedit.feature –
org.eclipse.buildship – 2.2.1.v20180125-1441
org.eclipse.cvs – 1.4.500.v20180611-0500
org.eclipse.draw2d –
org.eclipse.e4.rcp – 1.6.100.v20180611-0422
org.eclipse.ecf.core.feature – 1.5.0.v20180426-1936
org.eclipse.ecf.core.ssl.feature – 1.1.100.v20180301-0201
org.eclipse.ecf.filetransfer.feature – 3.14.0.v20180306-0429
org.eclipse.ecf.filetransfer.httpclient4.feature – 3.14.0.v20180301-0132
org.eclipse.ecf.filetransfer.httpclient4.ssl.feature – 1.1.100.v20180301-0132
org.eclipse.ecf.filetransfer.ssl.feature – 1.1.100.v20180301-0132
org.eclipse.egit –
org.eclipse.epp.mpc – 1.7.1.v20180628-1155
org.eclipse.equinox.p2.core.feature – 1.5.0.v20180515-1348
org.eclipse.equinox.p2.discovery.feature – 1.2.0.v20180512-1128
org.eclipse.equinox.p2.extras.feature – 1.4.0.v20180515-1348
org.eclipse.equinox.p2.rcp.feature – 1.4.0.v20180515-1348
org.eclipse.equinox.p2.user.ui – 2.4.0.v20180515-1348 – 2.2.200.v20180611-0500
org.eclipse.jdt – 3.14.0.v20180611-0500
org.eclipse.jet – 1.1.1.v201101271243-5319sC7HCAGERASDK3924
org.eclipse.jet.uml2 – 1.1.0.v201006011447-2-07w311A1A152813
org.eclipse.jgit –
org.eclipse.jsf.feature – 3.10.0.me201808311557
org.eclipse.mylyn.bugzilla_feature – 3.24.1.v20180619-2132
org.eclipse.mylyn.commons – 3.24.1.v20180619-2131
org.eclipse.mylyn.commons.identity – 1.16.0.v20180619-2131
org.eclipse.mylyn.commons.notifications – 1.16.0.v20180619-2131
org.eclipse.mylyn.commons.repositories – 1.16.0.v20180619-2131
org.eclipse.mylyn.context_feature – 3.24.1.v20180619-2131
org.eclipse.mylyn.cvs – 1.16.0.v20170629-1738
org.eclipse.mylyn.discovery – 3.24.1.v20180619-2131
org.eclipse.mylyn.gerrit.feature – 2.15.0.v20180322-1946
org.eclipse.mylyn.git – 1.16.0.v20170629-1738
org.eclipse.mylyn.ide_feature – 3.24.1.v20180619-2131
org.eclipse.mylyn.java_feature – 3.24.1.v20180619-2131
org.eclipse.mylyn.monitor – 3.24.1.v20180619-2131 – 2.15.0.v20180619-2132
org.eclipse.mylyn.tasks.ide – 3.24.1.v20180619-2132
org.eclipse.mylyn.team_feature – 3.24.1.v20180619-2131
org.eclipse.mylyn.versions – 1.16.0.v20170629-1738
org.eclipse.mylyn_feature – 3.24.1.v20180619-2132
org.eclipse.ocl – 3.1.0.v20110606-1427
org.eclipse.pde – 3.13.100.v20180611-0826
org.eclipse.platform – 4.8.0.v20180611-0656
org.eclipse.rcp – 4.8.0.v20180611-0656 – – – – – – 4.3.0.me201808311557
org.eclipse.userstorage – 1.1.0.v20170526-1605
org.eclipse.wb.core.feature – –
org.eclipse.wb.core.ui.feature –
org.eclipse.wb.core.xml.feature –
org.eclipse.wb.doc.user.feature – –
org.eclipse.wb.rcp.SWT_AWT_support –
org.eclipse.wb.rcp.doc.user.feature –
org.eclipse.wb.rcp.feature –
org.eclipse.wb.swing.doc.user.feature –
org.eclipse.wb.swing.feature –
org.eclipse.wb.swt.feature –
org.eclipse.wb.xwt.feature –
org.sonatype.m2e.mavenarchiver.feature –
tern-feature –
tern-jsdt-feature –
tern-linters-feature –
tern-server-nodejs-feature –
tern.eclipse.ide.server.nodejs.embed –

Eclipse startup command=-os
C:\Users\admin\AppData\Local\MyEclipse CI\myeclipse.exe
C:\Users\admin\AppData\Local\MyEclipse CI\\plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.700.v20180518-1200\eclipse_1705.dll
C:\Users\admin\AppData\Local\MyEclipse CI\\plugins/org.eclipse.equinox.launcher_1.5.0.v20180512-1130.jar
C:\Users\admin\AppData\Local\MyEclipse CI\configuration
C:\Users\admin\AppData\Local\MyEclipse CI
C:\Users\admin\AppData\Local\MyEclipse CI\binary\\bin\javaw.exe

]]> <![CDATA[Reply To: How to checkout from Git repository]]> Tue, 15 Jan 2019 04:34:27 +0000 support-swapna hahagal,

Welcome back 🙂
Please check this tutorial about working with Git in Eclipse :
The wizards are the same in MyEclipse as well.

I see you are still working with an outdated version of MyEclipse i.e 10.x. It is highly recommended to upgrade to the latest release of MyEclipse i.e MyEclipse 2018.

Hope this helps.

Genuitec Support

]]> <![CDATA[How to checkout from Git repository]]> Tue, 15 Jan 2019 03:03:15 +0000 hahagal Is there any guide on how to checkout from Git repository? I am using the below version.

*** Date:
Tuesday, January 15, 2019 11:02:46 AM SGT

** System properties:
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Blue Edition
Version: 10.0 Blue
Build id: 10.0-Blue-20111028

*** Eclipse details:
MyEclipse Blue Edition

Version: 10.0 Blue
Build id: 10.0-Blue-20111028

Eclipse Platform

Version: 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f
Build id: I20110613-1736

Eclipse Java Development Tools

Version: 3.7.0.v20110520-0800-7z8gFchFMTdFYKuLqBLqRja9B15B
Build id: I20110613-1736

Eclipse Plug-in Development Environment

Version: 3.7.0.v20110504-0800-7b7qFVpFEx2XnmYtj_9RfO7
Build id: I20110613-1736

Eclipse Graphical Editing Framework GEF

Version: 3.7.0.v20110425-2050-777D-81B2Bz0685C3A6E34272
Build id: 201105020958

Eclipse RCP

Version: 3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY
Build id: I20110613-1736

Eclipse startup command=-os
C:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\myeclipse-blue.exe
C:\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
C:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
C:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10
C:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\MyEclipse Blue Edition 10\configuration
C:\Users\admin\AppData\Local\Genuitec\MyEclipse Blue Edition 10\Common\binary\\jre\bin\client\jvm.dll

]]> <![CDATA[WAS 8.5 Application Deployment Won\'t Start (ADMA0116W) with MyEclipse 2018.12]]> Tue, 15 Jan 2019 02:47:41 +0000 stevebradford I upgraded MyEclipse from 2017 to 2018 a few months back and now nothing I do can make our EAR deployment start on WAS 8.5.11 (tried every WAS upgrade too)

The web services EAR application is OK on WAS 7 but on WAS 8.5 I always get error ADMA0116W.
(I’m using Classic/Packaged options but have tried everything!)
Research I’ve done suggests it’s a java reflection class load problem of a different JAR version to what is expected.
The stack trace isn’t useful to determine the class.

The same application code works fine on the same WAS 8.5 server deploying from ME 2017.

The EAR application is a set of web services built under JAX-WS & JAX-WS.
It has a bit of Spring usage too but maybe not relevant.

I’ve set up both 2017 & 2018 with the same Maven & JVM configurations
Makes no difference what I try.
Note that the Jenkins built final artefact deployed manually to WAS 8.5 does start properly.

I want to move to Java 8 so will not have WAS 7 any more.
Looks like I’m staying on 2017 unless this problem has been solved.

Anyone have any ideas to try?