no worries!

Mark

On Wed, Jan 7, 2009 at 8:58 AM, Ryan <[email protected]> wrote:
>
> Don't you love it when you spend all day debugging an issue only to
> find out someone else didn't do their job? That popped into my mind as
> well right after I sent the email. Sure enough, the server was still
> on 8.0.0. Upgrading to 8.0.1 fixed it. Thanks again for your spot on
> analysis. Time for a beer. ;)
>
> -Ryan
>
> On Jan 6, 3:49 pm, "Mark Mandel" <[email protected]> wrote:
>> The first thing that pops to mind is - is the server running 8.01 ?
>>
>> Mark
>>
>>
>>
>> On Wed, Jan 7, 2009 at 7:22 AM, Ryan <[email protected]> wrote:
>>
>> > The code for this app ( a large collection application ) works fine on
>> > all our dev boxes. I'm setting up a staging server and deploy this
>> > same code from svn. As I'm getting the server up and running, I notice
>> > that I'm intermittantly getting errors when doing a transfer.save().
>>
>> > The EVENT parameter to the actionAfterDiscardTransferEvent function is
>> > required but was not passed in.
>>
>> > The error occurred in C:\code\cfmx\extensions\components\transfer\com
>> > \TransferObjectProxy.cfc: line 237
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \TransferObjectProxy.cfc: line 130
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \adapter\SoftReferenceAdapter.cfc: line 148
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \collections\AfterDiscardObserverCollection.cfc: line 44
>> > Called from C:\code\cfmx\extensions\components\transfer\com\collections
>> > \AbstractBaseObservable.cfc: line 74
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \EventManager.cfc: line 233
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \EventManager.cfc: line 210
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \Transfer.cfc: line 415
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \Transfer.cfc: line 266
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \Transfer.cfc: line 178
>> > Called from C:\code\apps\butterfly\apps\scratchpad\dsp_scratch.cfm:
>> > line 5
>> > Called from C:\code\apps\butterfly\parsed\scratchpad.go.cfm: line 17
>> > Called from C:\code\cfmx\extensions\components
>> > \fusebox5\Application.cfc: line 228
>> > Called from C:\code\cfmx\extensions\components
>> > \fusebox5\Application.cfc: line 218
>> > Called from C:\code\cfmx\extensions\components\fusebox5\fusebox5.cfm:
>> > line 57
>> > Called from C:\code\apps\butterfly\index.cfm: line 4
>>
>> > Here's the test code in dsp_scratch.cfm:
>>
>> > <cfset t = getBean('Transfer') />
>> > <cfset o = t.get('account.Account', 10000012) />
>> > <cfset o.setName('Bob') />
>> > <cfset t.save(o) />
>> > <cfdump var="#o.getMemento()#" />
>>
>> > Here's the odd thing: 1) It happens with ANY of the objects within the
>> > transfer factory I've tested,  2) it only happens the first time I try
>> > to save an object -- after that it saved successfully and 2) I get
>> > different errors at different times all related to transfers
>> > internals.
>>
>> > I've also seen:
>>
>> > The EVENT parameter to the actionAfterUpdateTransferEvent function is
>> > required but was not passed in.
>>
>> > The error occurred in C:\code\cfmx\extensions\components\transfer\com
>> > \TransferObjectProxy.cfc: line 237
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \TransferObjectProxy.cfc: line 130
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \adapter\SoftReferenceAdapter.cfc: line 100
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \collections\AfterUpdateObserverCollection.cfc: line 44
>> > Called from C:\code\cfmx\extensions\components\transfer\com\collections
>> > \AbstractBaseObservable.cfc: line 74
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \EventManager.cfc: line 233
>> > Called from C:\code\cfmx\extensions\components\transfer\com\events
>> > \EventManager.cfc: line 189
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \Transfer.cfc: line 269
>> > Called from C:\code\cfmx\extensions\components\transfer\com
>> > \Transfer.cfc: line 178
>> > Called from C:\code\apps\butterfly\apps\scratchpad\dsp_scratch.cfm:
>> > line 5
>> > Called from C:\code\apps\butterfly\parsed\scratchpad.go.cfm: line 16
>> > Called from C:\code\cfmx\extensions\components
>> > \fusebox5\Application.cfc: line 228
>> > Called from C:\code\cfmx\extensions\components
>> > \fusebox5\Application.cfc: line 218
>> > Called from C:\code\cfmx\extensions\components\fusebox5\fusebox5.cfm:
>> > line 57
>> > Called from C:\code\apps\butterfly\index.cfm: line 4
>>
>> > and even
>>
>> > The TRANSFER parameter to the equalsTransfer function is required but
>> > was not passed in.
>>
>> > The one thing in common is that they all occurr in
>> > TransferObjectProxy.cfc at line 237.
>>
>> > I'm assuming that this has to do with the environment of the new
>> > machine (Win2K3 Server, CF8, Transfer 1.1, Java 1.6_11) but it is set
>> > up as close as possible to all the dev environments that have never
>> > had this problem.
>>
>> > I'm just wondering if anyone has any ideas what may be causing this
>> > problem. I've tried all the normal stuff, clearing the cache and defs.
>> > Let me know if you think of anything.
>>
>> > Thanks in advance.
>>
>> > -Ryan
>>
>> --
>> E: [email protected]
>> W:www.compoundtheory.com
> >
>



-- 
E: [email protected]
W: www.compoundtheory.com

--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer

You received this message because you are subscribed to the Google Groups 
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to