tracker issue : CF-4033856

Benoit, I am not able to observe the "Application.cfc/default DSN" issue with CF 11 update 06 (on Win 7 x64) Can you pls. share the relevant code with which you can observe the issue. I used the code below: -------------------- Application.cfc ---------------------------------- component output="false" displayname="" { THIS.name= "default-app-dsn-test"; THIS.datasource = "cfartgallery"; THIS.customtagpaths = "#expandpath("./")#..\mytags"; } -------------------- ../myTags/greetings.cfm --------------- <cfparam name="Attributes._name" default="Earthling"> <cfoutput>Greetings from Mars, #Attributes._name#!<br></cfoutput> -------------------------- test.cfm --------------------------- <cfquery name="_qry"> SELECT firstname FROM artists WHERE lastname='Kim' </cfquery> <cfoutput>#application.applicationname#</cfoutput><br> <cf_greetings _name = _qry.firstname > -------------------------- output ----------------------------------- default-app-dsn-test Greetings from Mars, Elicia!

Comment by Piyush K.

Hi Piyush, Perhaps CF-3634391 wasn't completely fixed. Please see my Sep 3, 2015 comment on that ticket. Thanks!, -Aaron

Comment by External U.

Hi Piyush, your code look ok to me, the problem is that i don't have a simple process to reproduce the issue, i'm merely only aware of the issue because of an error handler in my Application.cfc that e-mail me every error triggered on the production serveur with all details.

Comment by External U.

Benoit, Can you share the stack traces from your CF exception.log files from the time corresponding to the error notification emails you received. Let us see if we see something akin to what Aaron is suspecting in there. Aaron. Thanks for your input. I think we can raise a separate bug for the CME exceptions you observed in case Benoit here, unearths something different in the logs. Bug #CF-3634391 fixed an NPE. The new CME error could possibly be related to that fix.

Comment by Piyush K.

Latest one attached, too big to come in note. NB: Strangely enough the location pointed in the error message is always wrong, it seem to be a mix of the first file triggered, with the position of the error on the last file on the stack

Comment by External U.

Benoit, Can you share the defaulting cfc indicated in the log file you shared: /var/www/sidysv2/_ws/vente/bc.cfc You can share just the relevant part of the component here, or if you are not comfortable sharing it here you can mail it to pnayak@adobe.com

Comment by Piyush K.

I am closing this. We can revisit the issue if there is a reliable reproducible test case for this.

Comment by Piyush K.

I've recently found that the application had two extra "Application.cfm" (but with same application name) lurking in different path to override some of the settings/processing originaly done in the root's Application.cfm file. Requesting a file from within thoses path seem to be the missing trigger of the problem, it look like it reset the application setting "in flight" of the currently running pages, so that two requests on the same page will react differently (first one can work while the second one fail for missing the default datasource setting). I'm in process of fixing this on our application, however wouldn't it be a bit better to "fix" application settings for the current processing ? ie have some kind of local copy of the application structure made at request initialisation, that can't be modified "live" by the other requests ?

Comment by External U.