Hi Mark ,
I don't think we should suspect the custom class loader here as its very old
code and works fine across all application servers e.g. IBM WebSphere and JBoss
EAP 7.X. The custom class loader is required as our java classes are part of
the Database which we need to load and hence required.
It works in Tomcat 7.X as well but when we moved to 8.x or 9.x in both it
failed.
RegardsDinesh
On Monday, December 12, 2022 at 06:33:56 PM GMT+5:30, Mark Thomas
<ma...@apache.org> wrote:
The JNDI binding code is unchanged (apart from the removal of some
deprecated methods) between 7.0.x and 9.0.x (and beyond that range). I
think you'll need to do some debugging to figure out exactly why this
isn't working but I suspect the custom class loader is at least a part
of the reason.
There may be better options that using a custom class loader. What are
the requirements that mean you need to use one?
Mark
On 12/12/2022 12:42, dineshk wrote:
> Hi ,
> We are trying to deploy our application on tomcat 9.0.70. Before the
> hibernate bootstraps in our application , we do change the "Current Thread
> Context Class Loader " in the running thread to our "Custom class loader"
> which is required.
> Changing the "Current Thread Context Class Loader " fails the JNDI look up
> for data source done by hibernate.
> if the "Current Thread Context Class Loader " is not changed than JNDI look
> up works.
> We have also deployed the same application with the same configurations on
> apache-tomcat-7.0.57 and it works fine there , no issues with JNDI look up.
> We have not faced this issues on IBM WebSphere and JBoss EAP but
> apache-tomcat-7.0.57 onwards.
> It will be great help if we could get a solution for this.
>
> RegardsDinesh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
