Hello,

I am trying to modify an existing application to make use of the asynchronous processing capabilities.
I have created wrapper components around existing ones that call a generic asynchronous processing gateway.

My problem is that the first call to the gateway fails with the message:
"Error invoking CFC for gateway AsynchronousProcessor: Event Handler Exception. An exception occurred when invoking a event handler method from Application.cfc The method name is: onSessionStart."
All subsequent call succeed (but I fear that when new gateway threads are created they will also fail the first time).

The Application.cfc does not contain onSessionStart method but it manages sessions. I think because the old components remained in the same directory structure they "see" an Application.cfc file. The session tries to get initialized the first time the call is made. Question is... why does it fail the first time?
Another thing is that I'm not accessing any session variables in those components (all parameters are passed as arguments), I only need some of the configuration in the application scope.

In this context, is there a way to call the gateway without it trying to initialize a session? Or at least not fail?
If not... what is my best option?
1. Move old components into new directories that don't see the original Application.cfc file and create a copy of that without the session management? (Don't like this very much as I would need to duplicate the configuration parameters)
2. Or pass all configuration parameters as arguments to the methods that need to execute? (Don't like this either as it can create a lot of arguments for the methods)
3. Something else?

Best regards,
Mihai Manuta ----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).

An archive of the CFCDev list is available at www.mail-archive.com/[email protected]

Reply via email to