[support-pradeep]

volodiaL,

Can you please share your Build-id from MyEclipse > Installation summary ?

1) For the deployment issues, can you please answer some more questions for us :
a) Does deployment status for the project show as “OK” under the servers view ? If yes, can you please right click on the project in the servers view and click “browse deployment location” to see the project is deployed.
b) If there are any errors while deploying the project, copy paste the entire error here for us.

2) To quickly navigate to a particular class, you need to click “CTRL+SHIFT+H” for the popup to open.

3) You can change the preferences of Java formatter by going to Window > Preferences > Java > Code style > Formatter. The active profile should be set to “Eclipse [built-in]” you cannot edit this setting. So click on New, in the “profile name” pick a name. The “Initialize setting with the following profile” option should have “Eclipse [built-in]” selected. And the “Open the edit dialog now” should also be selected. Now click “OK” to create your new format settings. You are now presented with the “Profile ‘name you selected’” box. Goto Line Wrapping tab and change the width of “Maximum line width” and click on Apply and OK.

The console preferences can be set using the Window > Preferences > Run/Debug > Console. For more information on console preferences please follow this link : http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/preferences/run-debug/ref-console.htm

4) Regarding navigating from XHTML page to bean, I could not replicate this issue at my end on MyEclipse 10.7. When I CTRL+CLICK on preson.name in the following line, it takes to me to bean class.
<h:inputText required=”true” id=”name” value=”#{person.name}” />

[volodiaL]

Thank you for all replies!

Build id: 10.6-20120727

I am very sorry. Yesterday my project was deployed successfully on Glassfish from MyEclipse, but it was not copied into domain1/applications/ folder about which I asked!
Yesterday I could ciick on ‘Browse deployment location’ and it sent me to domain1/autodeploy/myProjectName.war ! And status was OK, Mode was Exploded

Today in the morning I deployed m project successfully via command line. After that I can’t deploy it again neither via command line nor myeclipse.
The error is :

[#|2012-12-19T14:14:51.296+0200|SEVERE|glassfish3.1.2|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=51;_ThreadName=AutoDeployer;|Exception while preparing the app : Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment : JavaHelpPool
Error Code: 0
Local Exception Stack: 
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment : JavaHelpPool
Error Code: 0
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:309)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:135)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:584)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invokeInternal(EntityManagerFactoryMethodHandler.java:117)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invokeCreateEntityManager(EntityManagerFactoryMethodHandler.java:103)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invoke(EntityManagerFactoryMethodHandler.java:77)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl_$$_javassist_1.createEntityManager(EntityManagerFactoryImpl_$$_javassist_1.java)
    at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
    at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
    at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
    at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
    at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
    at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
    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:555)
    at java.util.TimerThread.run(Timer.java:505)
Caused by: java.sql.SQLException: This pool is not registered with the runtime environment : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1552)
    at com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRuntime.java:564)
    at com.sun.enterprise.connectors.service.ConnectorResourceAdminServiceImpl$MyDataSource.getConnection(ConnectorResourceAdminServiceImpl.java:283)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:132)
    ... 39 more
Caused by: javax.resource.ResourceException: This pool is not registered with the runtime environment : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:669)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1545)
    ... 42 more
Caused by: com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: This pool is not bound in JNDI : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1087)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:628)
    ... 43 more
Caused by: javax.naming.NamingException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming} [Root exc
eption is javax.naming.NameNotFoundException: pools]
    at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
    at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at com.sun.appserv.connectors.internal.api.ResourceNamingService.lookup(ResourceNamingService.java:221)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:870)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1003)
    ... 44 more
Caused by: javax.naming.NameNotFoundException: pools
    at com.sun.enterprise.naming.impl.TransientContext.resolveContext(TransientContext.java:310)
    at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:218)
    at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:219)
    at com.sun.enterprise.naming.impl.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:77)
    at com.sun.enterprise.naming.impl.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:119)
    at com.sun.enterprise.naming
.impl.SerialContext.lookup(SerialContext.java:505)
    ... 50 more
|#]

2012-12-19T14:14:51.296+0200 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
WARNING: [AutoDeploy] Autodeploy failed : C:\glassfish3\glassfish\domains\domain1\autodeploy\JavaHelp.war.

When I click Ctrl+click to navigate to backing bean I get nothing. Bean name is not underlined and I can’t navigate anywhere.
If I have my backing bean registered in faces-config.xml I can see it in content assist when building EL expression. If it is not registered in faces-config but declared with @ManagedBean annotation which is equvalent I don’t have it in content assist at all.
BUT I cannot navigate anywhere by Ctrl+click regardless bean is registered in faces-config or not! I don’t tell about content assist when you build the h:datatable and want to quickly access property of entity which is declared in attribute ‘var’ !
Next I did not create this Maven project with Eclipse at all. I manually created folder which serves as workspace and pasted into that folder my project. Then I started MyEclipse and using Import-‘Existing Maven project’ I imported it !

[volodiaL]

I forgot to mention how I added JSF capabilities to this project.

I could not add JSF capabilities in normal way because it requires Dynamic Web Module 3.0.
Unfortunately by default it was set to 2.2 regardless that my web.xml uses 3.0.
I opened .settings/org.eclipse.wst.common.project.facet.core file generated by IDE
and changed this line :
<installed facet=”jst.web” version=”2.2″/>
to this :
<installed facet=”jst.web” version=”3.0″/>
Then I started IDE and via Properties-MyEclipse-Project Facets I checked ‘Java Server Faces
2.0’. Dynamic Web Module was set to 3.0 .
It is impossible to add JSF capabilities if Dynamic Web Module is 2.2 which I had after import !

[volodiaL]

The error I posted there again disappeared!

Unfortunately new kind of error arised:

2012-12-19T19:26:17.828+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.util
WARNING: RAR8068: Using default datasource : __ds_jdbc_ra for pool : JavaHelpPool
2012-12-19T19:26:18.031+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.jms.util
WARNING: jmsra.upgrade_check_failed
2012-12-19T19:26:18.046+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR8061: failed to load resource-adapter-config or RA [ __ds_jdbc_ra ], com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Unable to get active RA for module __ds_jdbc_ra
2012-12-19T19:26:18.046+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR8060: Unable to lookup pool [ JavaHelpPool ], javax.naming.NamingException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory
.url.pkgs=com.sun.enterprise.naming} [Root exception is javax.naming.NameNotFoundException: pools]
2012-12-19T19:26:18.046+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR6017 : Failed to get connection pool object jdbc/javahelpds via JNDI lookup : com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.cor
ba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}
2012-12-19T19:26:18.046+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.util
WARNING: RAR8068: Using default datasource : __ds_jdbc_ra for pool : JavaHelpPool
2012-12-19T19:26:18.109+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR8061: failed to load resource-adapter-config or RA [ __ds_jdbc_ra ], com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Unable to get active RA for module __ds_jdbc_ra
2012-12-19T19:26:18.109+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR8060: Unable to lookup pool [ JavaHelpPool ], javax.naming.NamingException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory
.url.pkgs=com.sun.enterprise.naming} [Root exception is javax.naming.NameNotFoundException: pools]
2012-12-19T19:26:18.109+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR6017 : Failed to get connection pool object jdbc/javahelpds via JNDI lookup : com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.cor
ba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming}
2012-12-19T19:26:23.421+0200 org.eclipse.persistence.session.file:/C:/glassfish3/glassfish/domains/domain1/applications/JavaHelp/WEB-INF/classes/_com.javahelp_JavaHelp_war_1.0PU14486254
INFO: EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461
2012-12-19T19:26:23.437+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.util
WARNING: RAR8068: Using default datasource : __ds_jdbc_ra for pool : JavaHelpPool
2012-12-19T19:26:23.484+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
SEVERE: RAR8061: failed to load resource-adapter-config or RA [ __ds_jdbc_ra ], com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Unable to get active RA for module __ds_jdbc_ra
2012-12-19T19:26:23.484+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
WARNING: RAR7010: Pool not reachable. 
2012-12-19T19:26:23.484+0200 javax.enterprise.resource.resourceadapter.com.sun.enterprise.connectors.service
WARNING: jdbc.exc_get_conn
[#|2012-12-19T19:26:23.515+0200|SEVERE|glassfish3.1.2|org.eclipse.persistence.session.file:/C:/glassfish3/glassfish/domains/domain1/applications/JavaHelp/WEB-INF/classes/_com.javahelp_JavaHelp_war_1.0PU14486254.ejb|_ThreadID=75;_ThreadName=admin-thread-pool-4848(3);|Local Exception Stack: 
Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment : JavaHelpPool
Error Code: 0
    at org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:309)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:135)
    at org.eclipse.persistence.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:162)
    at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:584)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invokeInternal(EntityManagerFactoryMethodHandler.java:117)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invokeCreateEntityManager(EntityManagerFactoryMethodHandler.java:103)
    at org.zeroturnaround.jrebel.integration.eclipselink.EntityManagerFactoryMethodHandler.invoke(EntityManagerFactoryMethodHandler.java:77)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl_$$_javassist_0.createEntityManager(EntityManagerFactoryImpl_$$_javassist_0.java)
    at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
    at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
    at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
    at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
    at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
    at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
    at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
    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:348)
    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 com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
    at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
    at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
    at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
    at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
    at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
    at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
    at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:860)
    at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:757)
    at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1056)
    at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:229)
    at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
    at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
    at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
    at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
    at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
    at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
    at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
    at java.lang.Thread.run(Thread.java:722)
Caused by: java.sql.SQLException: This pool is not registered with the runtime environment : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1552)
    at com.sun.enterprise.connectors.ConnectorRuntime.getConnection(ConnectorRuntime.java:564)
    at com.sun.enterprise.connectors.service.ConnectorResourceAdminServiceImpl$MyDataSource.getConnection(ConnectorResourceAdminServiceImpl.java:283)
    at org.eclipse.persistence.sessions.JNDIConnector.connect(JNDIConnector.java:132)
    ... 52 more
Caused by: javax.resource.ResourceException: This pool is not registered with the runtime environment : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:669)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnection(ConnectorConnectionPoolAdminServiceImpl.java:1545)
    ... 55 more
Caused by: com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: This pool is not bound in JNDI : JavaHelpPool
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1087)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getUnpooledConnection(ConnectorConnectionPoolAdminServiceImpl.java:628)
    ... 56 more
Caused by: javax.naming.NamingException: Lookup failed for '__SYSTEM/pools/JavaHelpPool' in SerialContext[myEnv={java.naming.factory.initial=com.sun.enterprise.naming.impl.SerialInitContextFactory, java.naming.factory.state=com.sun.corba.ee.impl.presentation.rmi.JNDIStateFactoryImpl, java.naming.factory.url.pkgs=com.sun.enterprise.naming} [Root exc
eption is javax.naming.NameNotFoundException: pools]
    at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:518)
    at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:455)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at com.sun.appserv.connectors.internal.api.ResourceNamingService.lookup(ResourceNamingService.java:221)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolAdminServiceImpl.getConnectorConnectionPool(ConnectorConnectionPoolAdminServiceImpl.java:870)
    at com.sun.enterprise.connectors.service.ConnectorConnectionPoolA
dminServiceImpl.obtainManagedConnectionFactory(ConnectorConnectionPoolAdminServiceImpl.java:1003)
    ... 57 more
Caused by: javax.naming.NameNotFoundException: pools
    at com.sun.enterprise.naming.impl.TransientContext.resolveContext(TransientContext.java:310)
    at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:218)
    at com.sun.enterprise.naming.impl.TransientContext.lookup(TransientContext.java:219)
    at com.sun.enterprise.naming.impl.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:77)
    at com.sun.enterprise.naming.impl.LocalSerialContextProviderImpl.lookup(LocalSerialContextProviderImpl.java:119)
    at com.sun.enterprise.naming.impl.SerialContext.lookup(SerialContext.java:505)
    ... 63 more

I have surved the Internet for that and I did not find solution!
I posted this error at java.net

[volodiaL]

You wont believe it !

I have just deployed the same project successfully only from MyEclipse!
I give my output from Console that corresponds to this deployment

2012-12-19T19:56:00.500+0200 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: [AutoDeploy] Selecting file C:\glassfish3\glassfish\domains\domain1\autodeploy\JavaHelp.war for autodeployment.
2012-12-19T19:56:03.437+0200 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-12-19T19:56:38.546+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:56:38] JRebel: Directory 'D:\meworkspace\JavaHelp\target\classes' will be monitored for changes.
2012-12-19T19:56:38.546+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:56:38] JRebel: Directory 'D:\meworkspace\JavaHelp\target\m2e-jee\web-resources' will be monitored for changes.
2012-12-19T19:56:38.546+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:56:38] JRebel: Directory 'D:\meworkspace\JavaHelp\src\main\webapp' will be monitored for changes.
2012-12-19T19:57:17.890+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:57:17] JRebel-GlassFish: Watching 'com.javahelp.util.JavaHelpMailerBean' for changes
2012-12-19T19:57:18.031+0200 javax.enterprise.system.container.ejb.com.sun.ejb.containers
INFO: EJB5181:Portable JNDI names for EJB JavaHelpMailerBean: [java:global/JavaHelp/JavaHelpMailerBean!com.javahelp.util.JavaHelpMailerBean, java:global/JavaHelp/JavaHelpMailerBean]
2012-12-19T19:57:18.812+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:57:18] JRebel-GlassFish: Watching 'com.sun.faces.config.ConfigureListener' for changes
2012-12-19T19:57:19.515+0200 javax.enterprise.resource.webcontainer.jsf.config
INFO: Initializing Mojarra 2.1.6 (SNAPSHOT 20111206) for context '/JavaHelp'
2012-12-19T19:57:21.500+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:57:21] JRebel-GlassFish: Watching 'com.ocpsoft.pretty.PrettyFilter' for changes
2012-12-19T19:57:21.500+0200 com.ocpsoft.pretty.PrettyFilter
INFO: PrettyFilter starting up...
2012-12-19T19:57:22.359+0200 com.ocpsoft.pretty.PrettyFilter
INFO: PrettyFilter initialized.
2012-12-19T19:57:22.390+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:57:22] JRebel-GlassFish: Watching 'com.javahelp.util.cc.UploadFilter' for changes
2012-12-19T19:57:22.390+0200 javax.enterprise.system.std.com.sun.enterprise.server.logging
INFO: [2012-12-19 19:57:22] JRebel-GlassFish: Watching 'javax.faces.webapp.FacesServlet' for changes
2012-12-19T19:57:22.406+0200 javax.enterprise.system.container.web.com.sun.enterprise.web
INFO: WEB0671: Loading application [JavaHelp] at [/JavaHelp]
2012-12-19T19:57:22.703+0200 javax.enterprise.system.tools.admin.org.glassfish.deployment.admin
INFO: JavaHelp was successfully deployed in 81 563 milliseconds.
2012-12-19T19:57:22.703+0200 javax.enterprise.system.tools.deployment.org.glassfish.deployment.common
INFO: [AutoDeploy] Successfully autodeployed : C:\glassfish3\glassfish\domains\domain1\autodeploy\JavaHelp.war.

UNFORTUNATELY the deployed app is not in domain1/applications folder but only
in domain1/autodeploy folder. Also There is a file ‘JavaHelp.war_deployed’ of unknown type !
The problem is only in fact that it was not copied into folder for deployed projects.

[support-pradeep]

volodiaL,

Glad that you have deployed your application successfully.

In MyEclipse, when you deploy an application to glassfish server, the deployment location will be at <Glassfish home dir>\domains\domain1\autodeploy folder. If you want to change the deployment location, you can create a launch configuration for glassfish server and in launch configuration you can change your deployment location.

Can you please answer some more questions :
1) Can you please let us know whether you can access your application in browser after deploying and running in glassfish server ? If yes, please let us know what exact issue you are facing in detail ?

2) If you cannot access your application in browser then please perform the following steps and let us know :
a) Can you please create a sample application in MyEclipse
b) Run the application in Glassfish server.
c) Now try accessing the application from browser and let us know whether you can access the sample application through browser.

3) If possible, can you please attach your project to help us investigate further ?

[volodiaL]

you can create a launch configuration for glassfish server and in launch configuration you can change your deployment location.

I can’t create launch configuration where I can specify path where to deploy because Myeclipse itself appends to path ‘/autodepoy’. So I can provide only this:
‘/glassfish/domains/domain1’ . Then exploded directory will be given for me by IDE and it is not modifiable ‘/glassfish/domains/domain1/autodeploy’

The problem is: even this siimplest web app which I created to test myeclipse can’t be deployed well with myeclipse. It is really copied only into /autodeploy folder and IDE prints that it is deployed successfully but it is not copied fromm ‘/autodeploy’ into ‘/applications’ where it can be accessed from browser.
BUT I tried also to deploy it via command line and it was deployed well and copied into ‘applications’ folder and it is accessible from browser
I attach this simplest JSF web app.

In that simple webapp I could not use content assist to bind input control to backing bean value!
Also Ctrl+click did not work! I registered this backing bran in faces-config.xml

[support-pradeep]

volodiaL,

I have escalated it to a dev team member. They will get back to you.

Sorry for inconvenience caused.

[support-tony]

volodiaL,

You appear to be using JRebel to deploy the application. Could you please confirm if that is the case? If so, could you please try the deployment without JRebel to see if that is the issue?

[support-tony]

volodiaL,

Further to my previous reply, I’ve managed to replicate your problem and have raised a bug report though it may still be a Glassfish bug. The problem appears to be that an exploded deployment is not being deployed correctly by Glassfish, which is using a context root which is the same name as the exploded directory (that is, the context root with “.war” appended). You should see a marker folder for your application under applications/_internal and be able to execute by using “localhost:8080/JavaHelp.war” in the browser.

When deploying from a different folder (not autodeploy), using the admin console, an exploded deployment does appear to pick up the correct context root.

If you use packaged deployment instead, this should deploy correctly.

Sorry for the inconvenience. We’ll investigate the problem further and, hopefully provide a fix or workaround in a future release.

[support-tony]

volodiaL,

Here is a possible workaround.

You can specify the context root in a glassfish-web.xml file. This file should be in the WEB-INF directory, alongside the web.xml file. Here is a sample, for just setting the context root:

<!DOCTYPE glassfish-web-app PUBLIC "-//GlassFish.org//DTD 
GlassFish Application Server 3.1 Servlet 3.0//EN" 
"http://glassfish.org/dtds/glassfish-web-app_3_0-1.dtd">
<glassfish-web-app>
   <context-root>appname</context-root>
</glassfish-web-app>

I hope this helps.

[Author]

Posts