Hi Mark,
This is my stacktrace:
ResourceLinkFactory.validateGlobalResourceAccess(String) line: 109
ResourceLinkFactory.getObjectInstance(Object, Name, Context,
Hashtable<?,?>) line: 142
NamingManager.getObjectInstance(Object, Name, Context, Hashtable<?,?>)
line: 321
NamingContext.lookup(Name, boolean) line: 847
NamingContext.lookup(Name) line: 158
NamingContext.lookup(Name, boolean) line: 835
NamingContext.lookup(Name) line: 158
NamingContext.lookup(Name, boolean) line: 835
NamingContext.lookup(String) line: 172
validateGlobalResourceAccess function returns false and then getObjectInstance
returns NULL.
Regards,
Chinoy
-----Original Message-----
From: Mark Thomas [mailto:[email protected]]
Sent: Friday, September 30, 2016 5:28 PM
To: Tomcat Users List <[email protected]>
Subject: Re: Unable to access Global JNDI Resource
On 30/09/2016 12:50, Chinoy Gupta wrote:
> I am getting NULL instead of the resource's value. I debugged the
> tomcat code and figured out that in ResourceLinkFactory.java, before
> fetching the resource there is a validation based on current
> classloader. That validation fails and tomcat returns NULL.
The above statement is not correct. If the class loader based validation fails,
Tomcat throws an exception. It does not return null.
Mark
>
> -----Original Message----- From: Mark Thomas [mailto:[email protected]]
> Sent: Friday, September 30, 2016 4:11 PM
> To: Tomcat Users List <[email protected]> Subject: Re: Unable to
> access Global JNDI Resource
>
> On 30/09/2016 11:30, Chinoy Gupta wrote:
>> Hi,
>>
>> I have a web application which runs on tomcat. In server.xml, I
>> provide some resources under "<GlobalNamingResources> section" and
>> then provide a ResourceLink to the same in context.xml. And then I
>> fetch that resource in my application. This was working properly
>> earlier but started breaking with 8.0.37.
>
> Define breaking. Ideally with a stack trace.
>
> Mark
>
>
>> I think the reason is the extra validation check introduced in
>> ResourceLinkFactory class. My application has its own classloader and
>> when I try to fetch the JNDI resource, the Thread's classloader is my
>> custom one rather than the default one. Because of that validation
>> fails and tomcat returns NULL. Is there a way to fix this through
>> configuration or any other means?
>>
>> Regards, Chinoy
>>
>>
>
>
> ---------------------------------------------------------------------
>
>
To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
> ---------------------------------------------------------------------
>
>
To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
