- This topic has 15 replies, 3 voices, and was last updated 17 years, 6 months ago by Riyad Kalla.
-
AuthorPosts
-
a_matijacaMemberHi there,
I am trying to work through the EJB3 Myeclipseide tutorial – I have Eclipse 3.2.2 with 5.5GA and glassfish 2.x (latest version patch 2).
When I try to deploy the EJB Project as an Exploded archive to the …./../…/autodeploy
directory as per your tutorial, the project does NOT get deployed as a EJB module,
but instead as a WEB application (actually 3-4 little web apps — it seems that each
java class ends up becoming it’s own little web app (??)).When I deploy the same project as a JAR archive to the same deployment directory,
everything runs fine, and the app is deployed as a EJB module.So, what is going on?? Is exploded deployment available or NOT available for
glassfish? Or am I doing something wrong — I don’t think I am, since I even went
as far as to download your own ZIP file and imported it as a project into Eclipse..Thanks, Alex.
Riyad KallaMemberWhen I try to deploy the EJB Project as an Exploded archive to the …./../…/autodeploy
directory as per your tutorial, the project does NOT get deployed as a EJB module,
but instead as a WEB application (actually 3-4 little web apps — it seems that each
java class ends up becoming it’s own little web app (??)).That’s the weirdest thing I’ve heard all week.
We’ve been working closely with the Glassfish team getting deployment issues ironed out for 2.0, so let’s dig into this situation and see if we can uncover what’s going on and possibly get it fixed.
I’m going to need some screenshots from you, the best would be to post them in your reply, but if you cannot host them anywhere and link to them using a URL, you can PM them to me (using the PM button under my post) as attachments.
I need a screenshot of:
1) Your project expanded in the package explorer
2) The full version of glassfish you are using (2.0, build what? patch level what? etc.)
3) Full startup message from glassfish as it starts up from the console
4) Screenshot of the EJB modules and Web modules admin page from the Glassfish admin console on port 4848 (http://localhost:4848). Login should be admin/adminadmin I think.
jkratzMember@support-rkalla wrote:
That’s the weirdest thing I’ve heard all week.
Not the weirdest thing I’ve head all week as I’m having the same exact issue. (same release of Glassfish). It tries to autodeploy every class as it’s own web app so I have about 128 copies of the same thing in my j2ee-modules directory :/
Jason
Riyad KallaMemberGuys this is sounding like a Glassfish hickup and the team has really been great fixing issues we ran into so I’d like to get this fixed if possible.
Jason, can you answer some of the same questions I asked Alex?
jkratzMemberI have build b41d (the beta 2 release). Before I post anything else I’m going to try build 48 (from May 23rd) and see if that shows the same problem.
Jason
jkratzMemberGood news. Build 48 works. I do get this error right way though when I start the autodeploy:
INFO: [AutoDeploy] Exception occures while invoking backend deployment service for file : C:\development\tools\glassfish\domains\domain1\autodeploy\ForecastingAdmin.war. — Unrecognized module type for C:\development\tools\glassfish\domains\domain1\autodeploy\ForecastingAdmin.war; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. — Unrecognized module type for C:\development\tools\glassfish\domains\domain1\autodeploy\ForecastingAdmin.war; the archive may be incorrectly constructed, non-existent, or inaccessible from the server.
For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB.
May 30, 2007 2:58:33 PM com.sun.enterprise.deployment.autodeploy.AutoDeployer markFileAfterDeployment
INFO: [AutoDeploy] Autodeploy failed : C:\development\tools\glassfish\domains\domain1\autodeploy\ForecastingAdmin.war.
May 30, 2007 2:58:37 PM com.sun.enterprise.deployment.autodeploy.AutoDeployer deployAfter the deployment finishes it tries again and succeeds. Is that normal behavior? Is it just a matter of tuning the auto-polling in the server admin console?
Thanks,
Jason
Riyad KallaMemberJason,
Very strange… if it fails *then* works with the exactly same war file (meaning you didn’t hit redeploy during that time) then I’d have to say that’s a Glassfish problem. I am glad however to hear that the EJB deployment is fixed.You may want to file this in the Glassfish issue tracker:
https://glassfish.dev.java.net/servlets/ProjectIssuesI did a few searches myself and didn’t get any matches.
jkratzMemberoops. sorry…my issue wasnt EJBs.. It was a standard war file. each class became its own deployment. (in build 41d)
a_matijacaMemberI am back – sorry — I have not been able to reproduce the behavior – now it seems ok. After deploying ONCE as
a jar file. I have since undeployed, and REDPLOYED a number of times as a exploded archive and it seems ok…What it DID do before (when things didn’t work) – it would tell me that
…..\autodploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanClient.class
cannot be found (ClassNotFoundException )- of course
SampleEJBProject.jar\com…. is NOT the name of the class it is
com\myeclipse …
and then, I would see the .class file “deployed” as web app…
I am glad to see that I am not the only one having this problem … Perhaps this will go away with newer
versions of glassfish??So my process seems to be — first deploy once as a deployment jar file, start/stop glassfish, remove
the project, and then just re-deploy as an exploded archive and all is ok…I KNOW THAT THIS DOES NOT MAKE SENSE, but it seems to work…
Thanks, a.m.
Riyad KallaMembera.m.
One of the big things we worked on with the GF team was to make sure that exploded deployments work. With the newer builds you should be able to simple do an exploded deployment and have it work.
a_matijacaMemberso, I have once again, redeployed as exploded archive, and although it seems to have
worked, (no errors on start-up this time), when trying to run the client, I did get
errors, and I have now screen shots that show good (packaged) deployments,
and bad (exploded) deployments…here are the screen shots
http://tinypic.com/view.php?pic=6bcq1y9
http://tinypic.com/view.php?pic=67yz5ew
http://tinypic.com/view.php?pic=543q2yr
http://tinypic.com/view.php?pic=6cfi70z (this one is the most interesting one)
(if these links get garbled, you shoudl be able to search
tinypic.com for keywrod myeclipseide)here are the “good ones” (JARd deployment)
http://tinypic.com/view.php?pic=6ffwd93
http://tinypic.com/view.php?pic=67oeh7d
Thanks for the help…
Alex.
LOG FILE OF BAD START-UP AFTER DEPLOYMENT
2007 10:16:08 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Selecting file C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBean.class for autodeployment.
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBean (type=Web Module) starting
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.annotation.impl.ModuleScanner getElements
WARNING: Cannot load SampleEJBProject.jar.com.myeclipseide.ejb3.MyBean reason : SampleEJBProject.jar.com.myeclipseide.ejb3.MyBean
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.annotation.impl.ModuleScanner getElements
WARNING: Cannot load SampleEJBProject.jar.com.myeclipseide.ejb3.MyBean reason : SampleEJBProject.jar.com.myeclipseide.ejb3.MyBean
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
INFO: deployed with moduleid = SampleEJBProject.jar_com_myeclipseide_ejb3_MyBean
May 31, 2007 10:16:08 AM com.sun.enterprise.web.WebContainer loadWebModule
INFO: WEB0100: Loading web module [SampleEJBProject.jar_com_myeclipseide_ejb3_MyBean] in virtual server [server] at [/MyBean]
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBean (type=Web Module) completed successfully, elapsed time 375 ms
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Successfully autodeployed : C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBean.class.
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Selecting file C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanRemote.class for autodeployment.
May 31, 2007 10:16:08 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanRemote (type=Web Module) starting
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
INFO: deployed with moduleid = SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanRemote
May 31, 2007 10:16:09 AM com.sun.enterprise.web.WebContainer loadWebModule
INFO: WEB0100: Loading web module [SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanRemote] in virtual server [server] at [/MyBeanRemote]
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanRemote (type=Web Module) completed successfully, elapsed time 343 ms
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Successfully autodeployed : C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanRemote.class.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Selecting file C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\IMyBean.class for autodeployment.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_IMyBean (type=Web Module) starting
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
INFO: deployed with moduleid = SampleEJBProject.jar_com_myeclipseide_ejb3_IMyBean
May 31, 2007 10:16:09 AM com.sun.enterprise.web.WebContainer loadWebModule
INFO: WEB0100: Loading web module [SampleEJBProject.jar_com_myeclipseide_ejb3_IMyBean] in virtual server [server] at [/IMyBean]
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_IMyBean (type=Web Module) completed successfully, elapsed time 281 ms
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Successfully autodeployed : C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\IMyBean.class.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Selecting file C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanClient.class for autodeployment.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanClient (type=Web Module) starting
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
INFO: deployed with moduleid = SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanClient
May 31, 2007 10:16:09 AM com.sun.enterprise.web.WebContainer loadWebModule
INFO: WEB0100: Loading web module [SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanClient] in virtual server [server] at [/MyBeanClient]
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanClient (type=Web Module) completed successfully, elapsed time 359 ms
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Successfully autodeployed : C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanClient.class.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Selecting file C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanLocal.class for autodeployment.
May 31, 2007 10:16:09 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo <init>
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanLocal (type=Web Module) starting
May 31, 2007 10:16:10 AM com.sun.enterprise.deployment.phasing.J2EECPhase runPhase
INFO: deployed with moduleid = SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanLocal
May 31, 2007 10:16:10 AM com.sun.enterprise.web.WebContainer loadWebModule
INFO: WEB0100: Loading web module [SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanLocal] in virtual server [server] at [/MyBeanLocal]
May 31, 2007 10:16:10 AM com.sun.enterprise.deployment.phasing.PEDeploymentService$AuditInfo reportEnd
INFO: Deployment by user Unknown of module SampleEJBProject.jar_com_myeclipseide_ejb3_MyBeanLocal (type=Web Module) completed successfully, elapsed time 312 ms
May 31, 2007 10:16:10 AM com.sun.enterprise.deployment.autodeploy.AutoDeployer invokeDeploymentService
INFO: [AutoDeploy] Successfully autodeployed : C:\Sun_glassfish\SDK\domains\domain1\autodeploy\SampleEJBProject.jar\com\myeclipseide\ejb3\MyBeanLocal.class.
Riyad KallaMemberHmmm very odd, I see what you mean. Looks like exploded deployments may have a problem. I’ll contact someone from the Glassfish team.
Riyad KallaMemberAlex,
Can you zip up the contents of the domains/domain1/autodeploy directory (the one that is all screwy) and send it to support@genuitec.com ATTN Riyad? The lead of the GF team wants to take a look at why it’s deploying the EJB as multiple web projects.
Riyad KallaMemberAlex,
After the GF looked into things on their end, it seems that exploded deployments only work with Build 48 and later. Your screenshot looked like you were still using Build 41. I, as well as the GF team, used the EJB Sample project and deployed it successfully in exploded format.If there is another project giving you trouble, we will need that for testing.
Attachments:
You must be logged in to view attached files.
a_matijacaMemberHi,
I just installed release build48 — IT WORKS (exploded deploy) !!
Many thanks, Alex.
-
AuthorPosts