Flex 2 Runtime: iviews stuck in 'initializing' phase

[former_member190457]

Hi everybody,

We just patched customer's EP7 VC in order to remove the nasty 32/64k bug with the new Flex 2 runtime.

However what happens now is:

we have several large models developed in SP12/Flex 1.5, they are being correctly deployed to EP SP14/Flex2, but fail to load.

They all hang indefinitely during the initialization phase of the iview, the progress bar stops at about 80%.

Smaller models work ok.

Please help, this issue is endangering my project.

Points will be awarded.

VT

[former_member190457]

let's wait for an official statement

[Former Member]

Hi Folks

Check these threads :-

[Flex error Problem|],

[Some Solutions|]

Cheers!!!

[Former Member]

Hi,

This will happen some times for big models or with modles with more layers.

i am also faced this issue .

Just refresh ur browser and firrst deploy the model useing deploy Button and the run that model by clicking on those deployed links

I think this will solve ur problem and one more if the portal is down then also it will ahppen some times

Regards,

Govindu

[former_member190457]

Hi Govindu, thanks for replying

The portal is definitely up.

As for your other suggestion, I refreshed the VC window, deployed and then run the iview from the link at the bottom with no results.

I tried to refresh the iview browser window, unsuccessfully.

I also tried to run the iview as a preview from portal content, but it didn't work.

Have I correctly applied your suggestion?

Thanks

[former_member190457]

I removed every popup and now it works ok... however I do need popups

any suggestion?

[Former Member]

Hi,

are sure u are useing Flex2 Compiler becuse with flex2 this problem should not happen .

As u told u removed the Poupups and now its working means u r running with Flex not flex2.

Is it correct?

Rerads,

Goivndu

[former_member190457]

Compiler/Runtime is flex 2 (I checked that under options -> compiler, and also during compilation flash (flex2) compiler is invoked).

Also the appearence of the progress bar is different from flex1.5

I verified this behaviour:

if the popup is triggered by a non existing event everything works ok

if the event exists it fails

this is irrespective of the size of the iview

[Former Member]

Hi ,

Ok can u send ZIP File of ur GML of model .I will verify why its happening.

My mail di:govindunagotla@gmail.com

Regards,

Govindu

[former_member190457]

Disabling internet explorer caching solves the problem. I guess this is a bug.

Thanks all the same.

[saranwin]

Hi Govindu,

I'm also phasing the phasing same issue here,

It's giving the error like this, Can u suggest me y it's coming..,

and wat's that FLEX2 Complier.., As a developer can i do anything for this....,

Error Details...

Error in compiling Flex application: Error: A function in the code exceeds the 64K byte limit (actual size = '134236'). Since the problem occurs in the compiler-generated deferred instantiation code, please refactor/componentize portions of this document.

(/usr/sap/ED1/JC01/j2ee/cluster/server0/GUIMachine_Business_Packages/yfiin_gain_22077/FLEX_COMPILATION_FOLEDR/AAD2JT2.mxml:19)

Failed to compile AAD2JT2.mxml

It's Urgent requirement... Help me plz

Regards,

Saran

[Former Member]

Hi,

Flex2 compiler is a new flex compiler developed By SAP to avoid 32K Bug and 62K Bug.

In error it self u can see the resaon for this bugs.

If Code in the function or in a statement exceeds Size 32k bytes or 62k Bytes this problem will come in to picture.

And just see below link for more details:

<https://www.sdn.sap.com/irj/sdn/wiki?path=/display/vc/32k+limitation&>

If helpful awrad ponits

Regards,

Govindu

[Former Member]

Hi,

yes it in development side and it will be avaliable in future SPs .

ok if ur problem solved close this thread.

Regards.

Govindu

[former_member190457]

Sorry cache disabling is not enough.

In order to make it work you have to manually delete your internet explorer cache before each execution and then hit refresh.

I can hardly believe this is a solution.

Let's wait for an official statement before closing this thread.

Thanks