<@&987246554085740594> please have a look, thanks.
#Docker, compose.yml and a JDBC/Ressource Issue
modern hareBOT
I uploaded your attachments as Gist. This makes them more accessible, for example to mobile users.
little dock
Hey,
I ve been stuck on this error forever. I am currently doing a project for my university. This is my first time working with Docker so I have had help from AI. When first deploying my containers on my own, without compose.yml and configurring the JDBC/Ressource for payara on the admin site by myself. The application worked. As soon as I tried to automate by compose.yml so that my group members dont have to configure anything, I got this error. Since my english is not to good and precise and I dont have enough technical depth, I ve asked Gemini to summariye. Please help me.
I've been trying to get a simple 3-tier application running for over 8 hours and I'm completely stuck on a java.lang.RuntimeException: Invalid resource : jdbc/ausschreibungsscannerpm error during deployment.
I'm using Docker Compose to run Postgres, Payara 6, and a Svelte frontend. I'm using Payara's modern environment variable feature to create the JDBC pool.
What I've tried and what I know for sure:
My persistence.xml has <property name="hibernate.hbm2ddl.auto" value="none" />. I know that value="update" causes this pm error, so I have explicitly set it to none.
I have proved (by unzip-ing the final .war file inside the Docker build) that the persistence.xml with value="none" is correctly packaged inside the ausschreibungssc-ejb.jar (which is inside the final .war).
I have completely cleaned my Docker environment with docker system prune -a --volumes and deleted all old target folders and config "ghost" folders from my local machine. The build is 100% clean.
Despite all this, the __pm error persists. It's a logical contradiction: the .war is correct, but Payara acts as if it's incorrect.
quaint cave
Hey,
I ve been stuck on this error forever. I am currently doing a project for m...
Can you share the entire docker-compose.yml? Also share the entire stack trace error
modern hareBOT
I uploaded your attachments as Gist. This makes them more accessible, for example to mobile users.
little dock
@quaint cave did you have a moment to take a look 😬
quaint cave
<@166201094857293824> did you have a moment to take a look 😬
I dont have much experience with payara - so I cant really advise much 😅 perhaps someone more knowledgable about payara/glassfish can help
I found these articles which I think probably relate to the issue.
From what I can briefly read relating to those errors they all seem to mention stuff like best bet is using a <data-source/> element in web.xml or a @DataSourceDefinition annotation, and mapping the DS to the java:app/ namespace. something something about persistence.xml being fucked
little dock
@quaint cave Thank you very much! For your time and effort