JavaEE in netbeans giving BUILD FAILED error on deployment

Question

When I try to run my Java EE program in Netbeans, consisting of servlets (java pages), JSP, beans (java pages), and HTML pages, I get this error in the output:

In-place deployment at C:\Users\Derek\Documents\NetBeansProjects\EJBProject\EJBProject-war\build\web Initializing... deploy?path=C:\Users\Derek\Documents\NetBeansProjects\EJBProject\EJBProject-war\build\web&name=EJBProject-war&force=true failed on Personal GlassFish v3 Domain C:\Users\Derek\Documents\NetBeansProjects\EJBProject\EJBProject-war\nbproject\build-impl.xml:611: The module has not been deployed. BUILD FAILED (total time: 1 second) 

And then on the command line, when I run asant run in the appropriate directory, I get:

C: \ Users \ Derek \ Documents \ NetBeansProjects \ EJBProject \ nbproject \ build-impl.xml: 19: Class org.apache.tools.ant.taskdefs.condition.Not does not support the nested element "antversion".

Do you know why this would be? Why don't netbeans deploy my application so I can run and test it?

EDIT: ant version actually came up with ...

Apache Ant version 1.6.5 compiled June 2, 2005

Fiberglass logs say:

 SEVERE: Exception while loading the app java.lang.RuntimeException: EJB Container initialization error at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:219) at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:197) at org.glassfish.ejb.startup.EjbDeployer.load(EjbDeployer.java:63) at org.glassfish.internal.data.ModuleInfo.load(ModuleInfo.java:175) at org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:216) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:338) at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183) at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272) at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320) at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176) at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235) at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224) at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365) at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204) at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166) at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100) at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:245) at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791) at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693) at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954) at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170) at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102) at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88) at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76) at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53) at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57) at com.sun.grizzly.ContextTask.run(ContextTask.java:69) at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330) at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.RuntimeException: Error while binding JNDI name x.results#x.results for EJB : resultsBean at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:1530) at com.sun.ejb.containers.StatefulSessionContainer.initializeHome(StatefulSessionContainer.java:214) at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:161) at org.glassfish.ejb.startup.EjbApplication.loadContainers(EjbApplication.java:207) ... 32 more Caused by: javax.naming.NameAlreadyBoundException: Use rebind to override at com.sun.enterprise.naming.impl.TransientContext.doBindOrRebind(TransientContext.java:275) at com.sun.enterprise.naming.impl.TransientContext.bind(TransientContext.java:214) at com.sun.enterprise.naming.impl.SerialContextProviderImpl.bind(SerialContextProviderImpl.java:79) at com.sun.enterprise.naming.impl.LocalSerialContextProviderImpl.bind(LocalSerialContextProviderImpl.java:81) at com.sun.enterprise.naming.impl.SerialContext.bind(SerialContext.java:586) at com.sun.enterprise.naming.impl.SerialContext.bind(SerialContext.java:602) at javax.naming.InitialContext.bind(InitialContext.java:404) at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.publishObject(GlassfishNamingManagerImpl.java:206) at com.sun.enterprise.naming.impl.GlassfishNamingManagerImpl.publishObject(GlassfishNamingManagerImpl.java:187) at com.sun.ejb.containers.BaseContainer$JndiInfo.publish(BaseContainer.java:5484) at com.sun.ejb.containers.BaseContainer.initializeHome(BaseContainer.java:1515) 

EDIT: It seems to be about my "session" bean session, since when I delete it, it works fine.

Answer 1

My best guess is that you downloaded and installed the GlassFish Server 3 web profile or created a web application with a deployment descriptor that forces the server to treat it like Java EE 5 (or even J2EE 1.4), and then created EJB in this web application ... which is likely to lead to similar errors.

Answer 2

It seems you have several fields in a bean state session that can have the same name as other fields of the Sessionful Session bean. This is just a hunch. There is a lot of information about your EJBS to do in-depth analysis. Hope this helps.