All, We solved the problem. As it turned out there was a discrepancy in the directory naming conventions between what we created and the image in DockerHub.
Jon, my team appreciates your willingness to jump on the problem. Thanks, Rod. On 12/8/20, 7:40 AM, "Jonathan Gallimore" <[email protected]> wrote: Nationwide Information Security Warning: This is an EXTERNAL email. Use CAUTION before clicking on links, opening attachments, or responding. (Sender: [email protected]) ------------------------------------------------------------------------------ That's awesome, thanks Rod. I'll keep an eye for the mail on the users list. Jon On Tue, Dec 8, 2020 at 1:28 PM Jenkins, Rodney J (Rod) < [email protected]> wrote: > Jon, > > Thank you for the response. I did not jump straight to bug. I figured I > missed something in the building of our image. > > I have passed along the request for the exception and a reproducer. We > cannot share the actual code base, but I did ask for something that will > reproduce the error. I am working on the stack trace now. > > Also, I will have the user email all of this to the users mailing list. I > think it is more fitting there. > > Thanks again, > Rod. > > > On 12/7/20, 3:38 PM, "Jonathan Gallimore" <[email protected]> > wrote: > > Nationwide Information Security Warning: This is an EXTERNAL email. > Use CAUTION before clicking on links, opening attachments, or responding. > (Sender: [email protected]) > > > ------------------------------------------------------------------------------ > > > Let's get a view on the exception and a reproducer. Sounds like a bug > we'd > want to iron out. > > Jon > > On Mon, Dec 7, 2020 at 4:59 PM Jenkins, Rodney J (Rod) < > [email protected]> wrote: > > > All, > > > > Would anyone know what differences between the drop in WAR vs the > full > > install? I am working with someone who is using our internally built > > Docker image. Our image is built with the drop in WAR. If they use > the > > public container pulled from Dockerhub (built on the full TomEE > version), > > everything works fine. > > > > I am having them do a write up to send to the users list for some > > support. The email to the user list will have the stack trace and > > additional information. However, I was hoping for someone provide > an idea > > as to what would be different. The high level issue is: > > javax.naming.NameNotFoundException > > > > > > Thanks for any initial ideas, > > Rod. > > > > > > >
