[nat101]

After a long time without MyEclipse, I am trying ME out again. (Windows 7 64 bit system, ME 10.x 32 bit ide.) On an existing functional (vanilla eclipse 372 jee) workspace, I ‘upgraded’ several ejb projects to ME, and set the jre to 32 instead of 64 bit. I re-installed the exisitng local Glassfish 312 server via ME’s wizard and Glassfish 312 comes up, BUT:
1. Error on GF startup.
2. Only a very simple 1 entity, 1 bean, test project deploys ok. The others, do NOT deploy as evident in GF logs, but ME reports a-ok with the deployment.

DETAILS:
1. Error on GF startup.
Launching GlassFish on Felix platform
2012-03-28T16:50:42.749-0400 com.sun.enterprise.server.logging.GFFileHandler
INFO: Running GlassFish Version: GlassFish Server Open Source Edition 3.1.2 (build 23)
2012-03-28T16:50:42.984-0400 javax.enterprise.system.core.com.sun.enterprise.v3.services.impl
INFO: Grizzly Framework 1.9.46 started in: 15ms – bound to [0.0.0.0:3700]
2012-03-28T16:50:42.984-0400 javax.enterprise.system.core.com.sun.enterprise.v3.services.impl
INFO: Grizzly Framework 1.9.46 started in: 47ms – bound to [0.0.0.0:8181]
2012-03-28T16:50:42.984-0400 javax.enterprise.system.core.com.sun.enterprise.v3.services.impl
INFO: Grizzly Framework 1.9.46 started in: 63ms – bound to [0.0.0.0:8080]
2012-03-28T16:50:42.984-0400 javax.enterprise.system.core.com.sun.enterprise.v3.services.impl
INFO: Grizzly Framework 1.9.46 started in: 47ms – bound to [0.0.0.0:4848]
2012-03-28T16:50:42.984-0400 javax.enterprise.system.core.com.sun.enterprise.v3.services.impl
INFO: Grizzly Framework 1.9.46 started in: 31ms – bound to [0.0.0.0:7676]
2012-03-28T16:50:43.093-0400 javax.enterprise.system.core.com.sun.enterprise.v3.admin.adapter
INFO: The Admin Console is already installed, but not yet loaded.
2012-03-28T16:50:43.109-0400 org.glassfish.ha.store.spi.BackingStoreFactoryRegistry
INFO: Registered org.glassfish.ha.store.adapter.cache.ShoalBackingStoreProxy for persistence-type = replicated in BackingStoreFactoryRegistry
2012-03-28T16:50:43.639-0400 javax.enterprise.system.container.ejb.com.sun.ejb.containers
INFO: Created EjbThreadPoolExecutor with thread-core-pool-size 16 thread-max-pool-size 32 thread-keep-alive-seconds 60 thread-queue-capacity 2147483647 allow-core-thread-timeout false
2012-03-28T16:50:43.670-0400 javax.enterprise.system.core.security.com.sun.enterprise.security
INFO: SEC1002: Security Manager is OFF.
2012-03-28T16:50:43.889-0400 javax.enterprise.system.core.security.com.sun.enterprise.security
INFO: SEC1010: Entering Security Startup Service
2012-03-28T16:50:43.889-0400 javax.enterprise.system.core.security.com.sun.enterprise.security
INFO: SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
2012-03-28T16:50:43.936-0400 javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm
INFO: SEC1115: Realm [admin-realm] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
2012-03-28T16:50:43.936-0400 javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm
INFO: SEC1115: Realm [file] of classtype [com.sun.enterprise.security.auth.realm.file.FileRealm] successfully created.
2012-03-28T16:50:43.952-0400 javax.enterprise.system.core.security.com.sun.enterprise.security.auth.realm
INFO: SEC1115: Realm [certificate] of classtype [com.sun.enterprise.security.auth.realm.certificate.CertificateRealm] successfully created.
2012-03-28T16:50:43.952-0400 javax.enterprise.system.core.security.com.sun.enterprise.security
INFO: SEC1011: Security Service(s) Started Successfully
2012-03-28T16:50:44.530-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
SEVERE: Exception while visiting com/sun/gjc/common/DataSourceSpec.class of size 3267
java.lang.NullPointerException
at org.glassfish.hk2.classmodel.reflect.impl.TypesImpl.getType(TypesImpl.java:78)
at org.glassfish.hk2.classmodel.reflect.impl.ModelClassVisitor.visit(ModelClassVisitor.java:119)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.glassfish.hk2.classmodel.reflect.Parser$5.on(Parser.java:363)
at org.glassfish.hk2.classmodel.reflect.util.JarArchive.onSelectedEntries(JarArchive.java:125)
at org.glassfish.hk2.classmodel.reflect.Parser.doJob(Parser.java:348)
at org.glassfish.hk2.classmodel.reflect.Parser.access$300(Parser.java:70)
at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:307)
at org.glassfish.hk2.classmodel.reflect.Parser$3.call(Parser.java:296)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
—
Despite this error, it does run normally afterwards, which brings me to the real problem (point 2 ) that it does not deploy the same app which Eclipse 372 JEE deploys. Worth a mention is the fact that ME used the auto deploy scheme, while Eclipse 372 deploys it as a real app. Here is the error:

SEVERE: Archive [Adam] was deployed as a Java EE archive while it does not contain any valid Java EE components. Please check the packaging of the archive.
java.lang.RuntimeException: Archive [Adam] was deployed as a Java EE archive while it does not contain any valid Java EE components. Please check the packaging of the archive.
at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:147)
at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:94)
at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:827)
at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:769)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:368)
at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:353)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
at org.glassfish.deployment.autodeploy.AutoOperation.run(AutoOperation.java:145)
at org.glassfish.deployment.autodeploy.AutoDeployer.deploy(AutoDeployer.java:575)
at org.glassfish.deployment.autodeploy.AutoDeployer.deployAll(AutoDeployer.java:461)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:389)
at org.glassfish.deployment.autodeploy.AutoDeployer.run(AutoDeployer.java:380)
at org.glassfish.deployment.autodeploy.AutoDeployService$1.run(AutoDeployService.java:220)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
2012-03-28T17:21:01.133-0400 javax.enterprise.system.tools.admin.org.glassfish.deployment.admin
SEVERE: Exception while deploying the app [Adam] : Archive [Adam] was deployed as a Java EE archive while it does not contain any valid Java EE components. Please check the packaging of the archive.
2012-03-28T17:21:01.149-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
WARNING: [AutoDeploy] Autodeploy failed : C:\glassfish312\glassfish\domains\domain1\autodeploy\Adam.jar.

—————————————
And to end this post on a good note:) Here is the log of the jee APP that DOES deploy a-ok:
2012-03-28T17:23:39.901-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: Autoundeploying application :Awords
2012-03-28T17:23:39.920-0400 org.eclipse.persistence.session.file:/C:/glassfish312/glassfish/domains/domain1/applications/Awords/_EZWords
INFO: file:/C:/glassfish312/glassfish/domains/domain1/applications/Awords/_EZWords logout successful
2012-03-28T17:23:39.940-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: [AutoDeploy] Successfully autoundeployed : C:\glassfish312\glassfish\domains\domain1\autodeploy\Awords.jar.
2012-03-28T17:23:41.905-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: [AutoDeploy] Selecting file C:\glassfish312\glassfish\domains\domain1\autodeploy\Awords.jar for autodeployment.
2012-03-28T17:23:42.000-0400 javax.enterprise.system.core.classloading.com.sun.enterprise.loader
INFO: ez.awords.db.Aword actually got transformed
2012-03-28T17:23:42.000-0400 org.eclipse.persistence.session.file:/C:/glassfish312/glassfish/domains/domain1/applications/Awords/_EZWords
INFO: EclipseLink, version: Eclipse Persistence Services – 2.3.2.v20111125-r10461
2012-03-28T17:23:42.000-0400 org.eclipse.persistence.session.file:/C:/glassfish312/glassfish/domains/domain1/applications/Awords/_EZWords
INFO: file:/C:/glassfish312/glassfish/domains/domain1/applications/Awords/_EZWords login successful
2012-03-28T17:23:42.047-0400 javax.enterprise.system.container.ejb.com.sun.ejb.containers
INFO: EJB5181:Portable JNDI names for EJB AwordsMain: [java:global/Awords/AwordsMain!ez.awords.server.session.AwordsMainRemote, java:global/Awords/AwordsMain!ez.awords.server.session.AwordsMain]
2012-03-28T17:23:42.047-0400 javax.enterprise.system.container.ejb.com.sun.ejb.containers
INFO: EJB5182:Glassfish-specific (Non-portable) JNDI names for EJB AwordsMain: [ez.awords.server.session.AwordsMainRemote#ez.awords.server.session.AwordsMainRemote, ez.awords.server.session.AwordsMainRemote]
2012-03-28T17:23:42.078-0400 javax.enterprise.system.tools.admin.org.glassfish.deployment.admin
INFO: Awords was successfully deployed in 173 milliseconds.
2012-03-28T17:23:42.078-0400 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: [AutoDeploy] Successfully autodeployed : C:\glassfish312\glassfish\domains\domain1\autodeploy\Awords.jar.
——————–
Thanks;
nat

[support-tony]

nat,

Sorry you’re seeing this problem.

Deployment to glassfish, from a MyEclipse perspective, is just copying files to the autodeploy folder. If that works, the deployment has “worked”. Of course, this doesn’t help if the set of files or archive is not assembled correctly. However, I can’t replicate the problem with simple EJB or Enterprise Application projects. If possible, could you attach, or send us, a project that exhibits the problem, so we can try to replicate it?

Are any of these projects that have been deployed and run successfully outside of MyEclipse and, if so, can you notice any difference between the MyEclipse deployment and the deployment outside of MyEclipse?

[nat101]

Ok. Got it to work.. I made a new ME ejb project, copied the src directory structure, and added libs as needed. When I tried adding ‘Glassfish server runtime’ ME complained that it is not compatible with ME. No sweat, used ME’s Java EE 6 library instead. Also added Eclipselink 2.3 as a lib.
wadda ya know, it deploys….

Thanks
nat

[support-tony]

nat,

I’m glad you got it working. Thanks for letting us know.

[Author]

Posts