This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
build 200706180000 jdk1.6b105 glassfish v2 b50 1) Create CustomerCMP sample 2) Run it. Run fails with following messages in log (snip) Deploying application in domain failed; Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment Error Code: 0 C:\Documents and Settings\Dan Kolar\My Documents\NetBeansProjects\CustomerCMP\nbproject\build-impl.xml:185: Deployment error: The module has not been deployed. See the server log for details. BUILD FAILED (total time: 1 minute 28 seconds)
Reproduced on Mac OS X and Windows XP Product Version: NetBeans IDE 6.0M10 (build 200706272201) Java: 1.5.0_11; Java HotSpot(TM) Client VM 1.5.0_11-b03 System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb) Can't deploy Customer CMP Application to server.
For me deployment also fails, but the reason could be different, here is a log from the App Server: ADM1006:Uploading the file to:[/private/tmp/s1astempdomain1server-1727147590/CustomerCMP.ear] Unable to create client jar: null com.sun.enterprise.deployment.backend.IASDeploymentException at com.sun.enterprise.deployment.backend.ClientJarMakerThread.createClientJar(ClientJarMakerThread.java:143) at com.sun.enterprise.deployment.backend.ClientJarMakerThread.run(ClientJarMakerThread.java:80) Caused by: java.util.zip.ZipException: ZIP file must have at least one entry at java.util.zip.ZipOutputStream.finish(ZipOutputStream.java:291) at com.sun.enterprise.deployment.deploy.shared.OutputJarArchive.closeEntry(OutputJarArchive.java:163) at com.sun.enterprise.deployment.backend.ApplicationClientJarMaker.create(ApplicationClientJarMaker.java:123) at com.sun.enterprise.deployment.backend.ClientJarMakerThread.createClientJar(ClientJarMakerThread.java:134) ... 1 more Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException: javax.naming.NameNotFoundException: test not found
So should this be assigned to the Appserver plugin? Any justification for changing the priority from P3 to P1?
hitting also this on my solaris-sparc with 200706270000 & GF v2 b52. adding myself in cc (nouar38) got the error at deployment: Deploying application in domain failed; Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment Error Code: 0 ... ** Under Services/DataBase: can connect to jdbc:derby://localhost/CustomerCMP [app on APP] but Tables/Views/Procedures are empty. ** Is there any sql script setup to create the tables ? could not find any with the created project. ** in my server.log has an exception: TopLink, version: Oracle TopLink Essentials - 2.0 (Build b52-rc (06/20/2007)) Server: unknown RAR7010: Pool not reachable. RAR5114 : Error allocating connection : [This pool is not registered with the runtime environment] Exception occured in J2EEC Phase com.sun.enterprise.deployment.backend.IASDeploymentException: Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment Error Code: 0 at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:305) at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:150) at oracle.toplink.essentials.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:185) at oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:552) at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:233) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:227) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:93) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:126) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:120) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:91) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.loadPersistenceUnitBundle(PersistenceProcessor.java:513) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.createTablesInDB(PersistenceProcessor.java:353) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processAppBundle(PersistenceProcessor.java:219) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:146) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122) at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79) at com.sun.enterprise.deployment.backend.AppDeployer.postDeploy(AppDeployer.java:392) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:251) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223)
Yes I think it should go to appserver plugin, there hasn't been any changes in the sample during the last couple of months and I don't understand the cause of this problem. The issue sounds like a P2 to me, unless the problem is more generic (reproducible in user projects)
NB 6.0 200707020000 & GF v2 b53 on solaris-sparc: with the Roster EE application (javaeetutorial) there is no problem as it uses jdbc/__default data source. I've made a similar example of this EE application + dep and changed the persistence unit to use a new db created (jdbc:derby://localhost:1527/app1DB [nouar on Nouar]) and "test" data source like CustomerCMP, and hit the problem at deployment. sun-resource.xml: ------------------ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE resources PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Resource Definitions //EN" "http://www.sun.com/software/appserver/dtds/sun-resources_1_3.dtd"> <resources> <jdbc-resource enabled="true" jndi-name="test" object-type="user" pool-name="derby_netPool"/> <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="org.apache.derby.jdbc.ClientDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="derby_netPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false"> <property name="serverName" value="localhost"/> <property name="PortNumber" value="1527"/> <property name="DatabaseName" value="app1DB"/> <property name="User" value="nouar"/> <property name="Password" value="nouar"/> </jdbc-connection-pool> </resources> persistence.xml: ------------------ <?xml version="1.0" encoding="UTF-8"?> <persistence version="1.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd"> <persistence-unit name="em" transaction-type="JTA"> <provider>oracle.toplink.essentials.PersistenceProvider</provider> <jta-data-source>test</jta-data-source> <properties> <property name="toplink.ddl-generation" value="drop-and-create-tables"/> </properties> </persistence-unit> </persistence>
This appears to be an issue with when the server is recognizing/deploying the sun-resources.xml and when it loads the persistence.xml. Investigating to identify it it is a server issue.
The error is because the resource that the persistence.xml is looking for is not present. Workaround : Delete the server-resources.xml file from under Server Resources node. Manually create required JDBC resource on server via admin-gui. Then deploy.
verified the WA:all done with Admin Console. ** create JDBC Connection Pool derby_netPool with: DatabaseName=CustomerCMP vendor=derby, type=javax.sql.DataSource user/password=app ** create JDBC resource jndi-name=test with Pool=derby_netPool with IDE: ** remove the sun-resource.xml file ** build/Undeploy & Deploy & Run: all are ok, can create Customer Id/search it/add subscription, ...etc.
On deploying an ejb module containing persistence.xml, in the server the persistence.xml seems to be loaded/executed before the sun-resources.xml is loaded and hence required resources are not found. Deploying the app containing persistence.xml but without the sun-resources.xml succeeds if resources are pre-registered on the server. Deploying the app containing sun-resources.xml but without the persistence.xml succeeds and the resources defined in the sun-resources.xml are successfully registered. Filed an issue against the appserver. https://glassfish.dev.java.net/issues/show_bug.cgi?id=3317
http://deadlock.netbeans.org/fisheye/changelog/netbeans/serverplugins/sun?cs=MAIN:vkraemer:20070724180412
Reproducible on build 200707260000 jdk1.5.0.7 Mac
dkolar: Did you create a new project or were you re-opening an existing project? Could you attach the "verbose" ant output that you get when you run the project?
Created a new one.
Every build that I tried to use after build "netbeans-6.0-nightly-200707230000" give me the follows error: ----------------------------------------------------------------- Start registering the project's server resources Finished registering server resources moduleID=patient-service deployment started : 0% Deploying application in domain failed; The resource jdbc/canarsie is having a conflict with resource defined in domain.xml. The resource jdbc/benson is having a conflict with resource defined in domain.xml. The resource canarsie_sqlpool is having a conflict with resource defined in domain.xml. The resource jdbc/midwood is having a conflict with resource defined in domain.xml. The resource benson_sqlpool is having a conflict with resource defined in domain.xml. The resource avez_sqlpool is having a conflict with resource defined in domain.xml. The resource midwood_sqlpool is having a conflict with resource defined in domain.xml. The resource jdbc/avez is having a conflict with resource defined in domain.xml. D:\SPS\project\patient-service\nbproject\build-impl.xml:191: Deployment error: The module has not been deployed. --------------------------------------------------------------- I have sun-resources.xml and persistence.xml. My environment: NetBeans IDE Dev (Build 200707260000) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: Windows XP version 5.1 running on x86;
forgot to mention that I'm running glassfish build 57
I am also having this problem. I do not believe this is a glassfish problem. My reasoning: The same project, same build procedure, same EAR, will deploy fine with NB 5.5.1, NB 6.0M10, will deploy fine when using the admin console and uploading the EAR file, will deploy fine when copying the EAR file to the autodeploy directory. The only place it will not deploy fine is from within the latest builds of NB6.0. I have tested this with glassfish build 43, build 50g and build 57. All work find when using NB 5.5.1 and NB 6.0M10.
See also: Issue 111185
See also: http://www.netbeans.org/servlets/BrowseList?list=nbusers&by=thread&from=801506
Just some clarification on the sun-resources.xml feature in the various releases , (1)Module with sun-resources.xml in 5.5.1 - will work to the extent supported by the appserver. The 5.5.1 plugin does not register resources in sun-resources.xml. The resources file in 5.5.1 had a different extension *.sun-resource (2)Module with sun-resources.xml in NB6 M10 - will work since the plugin does not attempt to register the resources and is deferring to the packaging mechanism placing the sun0resources.xml in the archive and appserver handling the resource registration (3)Module with sun-resources.xml in NB6 latest builds - The plugin is registering the resources as part of the deploy. If the sun-resources.xml is also in the archive that is getting deployed, there will be resource conflict issues as the appserver's sun-resources.xml registration feature cannot handle duplicate resources. Also, I am investigating an ordering issue raised by Brett in the context of his application that might be causing errors in addition to the above scenario(3)
Filed IZ 111853 for problem faced by brettbergquist. Once user upgraded to latest IDE and ensured that the project was built fresh, the error regarding resource conflicts is not reproducible. I am unable to reproduce this issue with the latest IDE and creating a new CustomerCMP sample project. dkolar, Do you still see this issue? If you are, can you attach your project to this issue.
Issue cannot be reproduced. Marking Fixed. Please reopen with complete steps and attach project if you see issue again.
Reproducible in standard build 200708210000 jdk1.6.0_02 I'll attach project
Created attachment 46973 [details] CustomerCMP.zip
reproduced on solaris-sparc with jdk 1.6u1 and NB 6.0 200708200000/GF v2 b58b bundled: in two cases Case1: happens if another jdbc-resource (mydata1) over the same JDBC CP (derby_netPool) is still deployed by another project before deploying the CustomerCMP that has the "test" jdbc-resource sharing the same JDBC CP. easy to solve: delete remaining resources and deploy again Case2: happens if the new CustomerCMP project is created after doing the following cleanup procedure from a previous run: managed to solve twice but could not describe how ? **** undeploy the EAR CustomerCMP project **** remove CP resource : derby_netPool (delete in Services) **** delete the 4 projects CustomerCMP* **** delete in Services/Databases the entry of the CustomerCMP DB node (jdbc:derby://....) **** stop the DB server **** remove the /.netbeans-derby/CustomerCMP directory +++>>> at creation of CustomerCMP in the wizard: Name and Location will see org.netbeans.api.db.explorer.DatabaseException.java.net.ConnectException: Error connection port 1527 with message Connecio.... +++>>> the DB server is started +++>>> the projects created as expected, the CustomerCMP DB node (jdbc:derby://....) is added +++>>> at deploy: in GF log: RAR7010: Pool not reachable. RAR5114 : Error allocating connection : [This pool is not registered with the runtime environment] JDO76611: Cannot connect to database via JNDI name 'CustomerCMP': java.sql.SQLException: This pool is not registered with the runtime environment. TopLink, version: Oracle TopLink Essentials - 2.0 (Build b58b-rc3 (08/15/2007)) Server: unknown RAR7010: Pool not reachable. RAR5114 : Error allocating connection : [This pool is not registered with the runtime environment] Internal Exception: java.sql.SQLException: This pool is not registered with the runtime environment Error Code: 0 at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:305) at oracle.toplink.essentials.jndi.JNDIConnector.connect(JNDIConnector.java:150) at oracle.toplink.essentials.sessions.DatasourceLogin.connectToDatasource(DatasourceLogin.java:184) at oracle.toplink.essentials.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:582) at oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:280) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:229) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:93) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:126) at oracle.toplink.essentials.internal.ejb.cmp3.base.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:120) at oracle.toplink.essentials.internal.ejb.cmp3.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:91) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.loadPersistenceUnitBundle(PersistenceProcessor.java:513) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.createTablesInDB(PersistenceProcessor.java:353) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processAppBundle(PersistenceProcessor.java:219) at com.sun.jdo.spi.persistence.support.ejb.ejbc.PersistenceProcessor.processApplication(PersistenceProcessor.java:146) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processApplication(DeploymentEventListenerImpl.java:211) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.processEvent(DeploymentEventListenerImpl.java:172) at com.sun.jdo.spi.persistence.support.ejb.ejbc.DeploymentEventListenerImpl.notifyDeploymentEvent(DeploymentEventListenerImpl.java:122) at com.sun.enterprise.deployment.backend.DeploymentEventManager.notifyDeploymentEvent(DeploymentEventManager.java:79) at com.sun.enterprise.deployment.backend.AppDeployer.postDeploy(AppDeployer.java:392) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:251) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:788) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223) <<< this does not happen all the time: RAR5038:Unexpected exception while creating resource RAR5058: Error while Resizing pool. .... many times and after the node for CustomerCMP DB disappears from Services/Databases. the Apache Derby Network Server is shutdown >>> nouar.
The project has the server resource files in the old format ie. *.sun-resource Plugin has logic to create the new sun-resources.xml for these resources, but they are not being triggered during a two step create - deploy action. Investigating. Nouar, Case1: What is the error you see in case 1. I didn't understand. Case 2: is because of what I described above.
Fixed issue with sun-resources.xml not getting created. Checking in appsrv/src/org/netbeans/modules/j2ee/sun/ide/sunresources/beans/ResourceUtils.java; /cvs/serverplugins/sun/appsrv/src/org/netbeans/modules/j2ee/sun/ide/sunresources/beans/ResourceUtils.java,v <-- ResourceUtils.java new revision: 1.27; previous revision: 1.26 done Checking in appsrv81/src/org/netbeans/modules/j2ee/sun/ide/j2ee/ModuleConfigurationImpl.java; /cvs/serverplugins/sun/appsrv81/src/org/netbeans/modules/j2ee/sun/ide/j2ee/ModuleConfigurationImpl.java,v <-- ModuleConfigurationImpl.java new revision: 1.21; previous revision: 1.20 Keeping IZ open for Nouar's update on the first issue that she noticed.
In my two platforms got the sun-resources.xml generated as was able to deploy and run. After deleting the projects, and creating again got also the file generated. when a sun-resources.xml is generated, do we have a temporary file generated somewhere on the system (for ex. in /tmp, /var/tmp .. etc) ? so I can remove in case the generation/copy is not done, before starting again. This point may explain why got "case 1" with "mydata1" name, trying to reproduce again.
was able again to do the deployment of CustomerCMP on solaris-sparc recreated as a new project again. In the server logs: found how mydata1 resource get into the server. In july, kept ServletStateless project (for issue 110547) on which I've added jdbc data resource tests using sample db and derby_netPool jndi-name. in my server log: found the same exception that I've described in case2. could not reproduce with ServletStateless, as deleted/created again with IDE/samples after the test this week. will try again to create a similar project with resource injection, as with a new war project that just has the data resource added cannot break the deployment. will attach my server.log file
Created attachment 47089 [details] GF v2 b58b domain1 log file
Nouar will open a separate issue if she is able to reproduce/isolate behavior she noticed.
NB 6.0 200708261200 & windows-xp & jdk 1.6u1: no CustomerCMP project, no CustomerCMP db GlassFish V2 started (b58c) 1) Create CustomerCMP project (don't expand any dep project) 2) Run it. is OK on windows only once, as doing again: 3) "Undeploy & Deploy" on project will fail, problem is not related to resources. joining the output for build.xml
Created attachment 47464 [details] build.xml for second deploy on windows
NB 6.0 200708261200 & jdk 1.6u1: solaris-sparc Can "Run" new CustomerCMP project many times with no problem.
i can run this project without error on ubuntu & NetBeans IDE Dev (Build 200709031200) Java: 1.6.0_02-ea;
CustomerCMP run with success over windows/xp (jdk 1.6 u1) & build 200709030000 and solaris-sparc (jdk1.6u1) & build 200709040000 (GF v2, personal developer domain and personal cluster domain)
v.