Several changes occured in MX that made code that worked in cf5 break (for example, naming variables something.something is illegal in CFMX, without first defining the structure).
You might want to check your error handler for deprecated syntax.
Robert
-----Original Message-----
From: Jeff Waris [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 18, 2004 10:09 A
To: CF-Talk
Subject: RE: Weird CFHTTP Error....
Maybe a little more info may help.
This CFHTTP call is part of a loop over account numbers. It appears that the
first loop passes CFHTTPPARAM's correctly through to the next page. It
writes to my home brew log file the correct 5 variables. As it gets to the
NEXT applicable one in sequence it writes this stuff in its place....
HTTP_ACCEPT:text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
HTTP_CONNECTION:keep-alive
HTTP_HOST:127.0.0.1
HTTP_USER_AGENT:Java1.3.1_03
HTTP_CONTENT_LENGTH:24085
HTTP_CONTENT_TYPE:application/x-www-form-urlencoded,application/x-www-form-u
rlencoded,application/x-www-form-urlencoded,application/x-www-form-urlencode
d,application/x-www-form-urlencod
.....etc
Here is the kicker, on a CF 5.0 seperate server this cfhttp call works
perfectly, now using 6.0 it doesn't seem to be working and I am getting
these errors.
Jeff
-----Original Message-----
From: Bartlett, Robert E. USNUNK NAVAIR 1490, 54-L4
[mailto:[EMAIL PROTECTED]
Sent: Monday, May 17, 2004 4:29 PM
To: CF-Talk
Subject: RE: Weird CFHTTP Error....
Sorry, I meant to post more, and hit send accidentally!
Looks like:
4) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)
"Error","jrpp-237","05/17/04","14:28:08",,"Element SQL is undefined in
ERROR. The specific sequence of files included or processed is:
I:\CFusionMX\wwwroot\WEB-INF\exception\coldfusion\runtime\DatabaseException.
cfm "
coldfusion.runtime.UndefinedElementException: Element SQL is undefined in
ERROR.
Indicates that perhaps your CFERROR page is making a reference to a variable
SQL in the ERROR scope, like perhaps:
#ERROR.SQL#
or something like it.
Without code to look at, its hard to say.
If that is the case, thats not valid, since in the ERROR scope that variable
isn't present.
TRY/CATCH the error page (!), and CFMAIL the CFDUMP of the CFERROR to
yourself.
Robert
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
