Profiling Flex/Java Web App

[Oleg Konovalov <ol...@gmail.com>]

Hi,

I have a large Flex+Java app (Flex 4.5.1).

Created a new complicated screen (with 3 ADGs) and WindowTitle popup
to edit a row with 2 sets of children (each is a DataGroup with Renderer,
one is a few TextInputs (with 2 way binding),
another is 2 dropdownlists (2nd gets a list based on 1st one selection, so
there is a call to stored proc), checkbox and a button.

It seems that if there are 100s of these children, it takes >35secs for
that popup
to come up in Edit mode.

I tried to profile it using FlashBuilder 4.5.1 on Tomcat 6.0,
but when I bring up profiler, it shows me popup "No activity happened in
the past 60 seconds
after connection was established with the application"  and only after that
app comes up.

Debugger works fine, and I can run that app without any problems.


Is there way to fix it?

I have seen lots of posts showing similar error, but no solution so far.


Please help!

-- 
Thank you,
Oleg.

Re: Profiling Flex/Java Web App

[Alex Harui <ah...@adobe.com>]

Not sure if I’ve used every version of the profiler, but I’ve used the
profiler quite often and it works for me.

I would reboot and don’t start up any apps except Flash Builder
(especially, no browsers, PDF utilities, or AIR apps).  I’ve seen other
SWFs running on the system connect to the profiler instead of the intended
SWF.  If that doesn’t work for your hello world app, the link here [1]
says the profiler defaults to socket port 9999.  Make sure it isn’t
blocked by firewalls and other security software, and that there are no
other processes or services using that port already.

[1] 
http://help.adobe.com/en_US/flashbuilder/using/WS6f97d7caa66ef6eb1e63e3d11b
6c4d0d21-7e46.html
 
On 4/13/15, 6:36 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:

>I tried to create brand new HelloWorld,
>but got the same exact error in FB4.5.1.
>A lot of people on the net got the same.
>Did that profiler ever worked?
>On Apr 10, 2015 14:17, "Alex Harui" <ah...@adobe.com> wrote:
>
>> Did you try profiling a really simple “Hello World” type of application?
>> There could be some issue with how the profiler talks to the SWF.  I
>>think
>> it uses a Socket.  Maybe something else is using that socket.
>>
>> -Alex
>>
>> On 4/10/15, 11:03 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>>
>> >I don't think that is the issue.
>> >
>> >I tried profiling simple application (showing a graph with few nodes,
>> >using
>> >RaVis library - sample of what we have on one screen),
>> >and got exactly the same error popup "No activity happened in the past
>>60
>> >seconds
>> >after connection was established with the application"  and only after
>> >that
>> >app came up.
>> >
>> >Is there anything I need to do to configure FB Profiler to run it?
>> >(i haven't done that in Flex before....)
>> >
>> >
>> >On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <ah...@adobe.com> wrote:
>> >
>> >>
>> >>
>> >> On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>> >>
>> >> >Alex,
>> >> >
>> >> >That profiler problem happens much before I reach my heavy duty
>>popup
>> >>with
>> >> >many children,
>> >> >on initial screen.
>> >> >We are making calls to about 30 Stored Procs to get proper
>>permissions
>> >>and
>> >> >load static data.
>> >> >(can probably turn off some of them and only use data relevant to
>> >>screen
>> >> >with popup we need,although it might take time to investigate).
>> >> >
>> >> >As I said, Debugger is running fine, no timeouts whatsoever.
>> >> >
>> >> >Is Profiler more demanding than Debugger?
>> >>
>> >> Yes, the profiler is logging data for every line of code and every
>> >>memory
>> >> allocation.  So if there is too much work to get the app up and
>>running
>> >> you can have this sort of problem.
>> >>
>> >> I’ve never actually dealt with this situation myself.  IMO, it is an
>> >> indicator that you could refactor the app and defer some of the work
>>and
>> >> see faster startup time and allow the profiler to do its thing.
>> >>
>> >> One thing you could try is to call pauseSampling() in a preinitialize
>> >> handler in the app.  That might shutdown the logging and allow the
>>app
>> >>to
>> >> start up faster.  Then call startSampling at the right moment to
>>start
>> >> collecting the data you need.  Here’s the doc:
>> >>
>> >>
>> >>
>> 
>>http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/
>> >>sa
>> >> mpler/package.html#pauseSampling()
>> >>
>> >> -Alex
>> >>
>> >>
>> >
>> >
>> >--
>> >Thank you,
>> >Oleg.
>>
>>

Re: Profiling Flex/Java Web App

[manish sharma <mi...@gmail.com>]

Hi,

I have also faced this issue that was due to update of flash player.
Neither I am able to debug nor profiling and one more issue with profiler,
if your application take time to load likewise it is loading data from
server then my machine got hanged or profiling does not working. To resolve
this issue I have created local data resources and my profiler worked
properly.

For profiling you should have a valid license of flash builder.

Regards,
Manish
I tried to create brand new HelloWorld,
but got the same exact error in FB4.5.1.
A lot of people on the net got the same.
Did that profiler ever worked?
On Apr 10, 2015 14:17, "Alex Harui" <ah...@adobe.com> wrote:

> Did you try profiling a really simple “Hello World” type of application?
> There could be some issue with how the profiler talks to the SWF.  I think
> it uses a Socket.  Maybe something else is using that socket.
>
> -Alex
>
> On 4/10/15, 11:03 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>
> >I don't think that is the issue.
> >
> >I tried profiling simple application (showing a graph with few nodes,
> >using
> >RaVis library - sample of what we have on one screen),
> >and got exactly the same error popup "No activity happened in the past 60
> >seconds
> >after connection was established with the application"  and only after
> >that
> >app came up.
> >
> >Is there anything I need to do to configure FB Profiler to run it?
> >(i haven't done that in Flex before....)
> >
> >
> >On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
> >>
> >> >Alex,
> >> >
> >> >That profiler problem happens much before I reach my heavy duty popup
> >>with
> >> >many children,
> >> >on initial screen.
> >> >We are making calls to about 30 Stored Procs to get proper permissions
> >>and
> >> >load static data.
> >> >(can probably turn off some of them and only use data relevant to
> >>screen
> >> >with popup we need,although it might take time to investigate).
> >> >
> >> >As I said, Debugger is running fine, no timeouts whatsoever.
> >> >
> >> >Is Profiler more demanding than Debugger?
> >>
> >> Yes, the profiler is logging data for every line of code and every
> >>memory
> >> allocation.  So if there is too much work to get the app up and running
> >> you can have this sort of problem.
> >>
> >> I’ve never actually dealt with this situation myself.  IMO, it is an
> >> indicator that you could refactor the app and defer some of the work
and
> >> see faster startup time and allow the profiler to do its thing.
> >>
> >> One thing you could try is to call pauseSampling() in a preinitialize
> >> handler in the app.  That might shutdown the logging and allow the app
> >>to
> >> start up faster.  Then call startSampling at the right moment to start
> >> collecting the data you need.  Here’s the doc:
> >>
> >>
> >>
> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/
> >>sa
> >> mpler/package.html#pauseSampling()
> >>
> >> -Alex
> >>
> >>
> >
> >
> >--
> >Thank you,
> >Oleg.
>
>

Re: Profiling Flex/Java Web App

[Oleg Konovalov <ol...@gmail.com>]

I tried to create brand new HelloWorld,
but got the same exact error in FB4.5.1.
A lot of people on the net got the same.
Did that profiler ever worked?
On Apr 10, 2015 14:17, "Alex Harui" <ah...@adobe.com> wrote:

> Did you try profiling a really simple “Hello World” type of application?
> There could be some issue with how the profiler talks to the SWF.  I think
> it uses a Socket.  Maybe something else is using that socket.
>
> -Alex
>
> On 4/10/15, 11:03 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>
> >I don't think that is the issue.
> >
> >I tried profiling simple application (showing a graph with few nodes,
> >using
> >RaVis library - sample of what we have on one screen),
> >and got exactly the same error popup "No activity happened in the past 60
> >seconds
> >after connection was established with the application"  and only after
> >that
> >app came up.
> >
> >Is there anything I need to do to configure FB Profiler to run it?
> >(i haven't done that in Flex before....)
> >
> >
> >On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <ah...@adobe.com> wrote:
> >
> >>
> >>
> >> On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
> >>
> >> >Alex,
> >> >
> >> >That profiler problem happens much before I reach my heavy duty popup
> >>with
> >> >many children,
> >> >on initial screen.
> >> >We are making calls to about 30 Stored Procs to get proper permissions
> >>and
> >> >load static data.
> >> >(can probably turn off some of them and only use data relevant to
> >>screen
> >> >with popup we need,although it might take time to investigate).
> >> >
> >> >As I said, Debugger is running fine, no timeouts whatsoever.
> >> >
> >> >Is Profiler more demanding than Debugger?
> >>
> >> Yes, the profiler is logging data for every line of code and every
> >>memory
> >> allocation.  So if there is too much work to get the app up and running
> >> you can have this sort of problem.
> >>
> >> I’ve never actually dealt with this situation myself.  IMO, it is an
> >> indicator that you could refactor the app and defer some of the work and
> >> see faster startup time and allow the profiler to do its thing.
> >>
> >> One thing you could try is to call pauseSampling() in a preinitialize
> >> handler in the app.  That might shutdown the logging and allow the app
> >>to
> >> start up faster.  Then call startSampling at the right moment to start
> >> collecting the data you need.  Here’s the doc:
> >>
> >>
> >>
> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/
> >>sa
> >> mpler/package.html#pauseSampling()
> >>
> >> -Alex
> >>
> >>
> >
> >
> >--
> >Thank you,
> >Oleg.
>
>

Re: Profiling Flex/Java Web App

[Alex Harui <ah...@adobe.com>]

Did you try profiling a really simple “Hello World” type of application?
There could be some issue with how the profiler talks to the SWF.  I think
it uses a Socket.  Maybe something else is using that socket.

-Alex

On 4/10/15, 11:03 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:

>I don't think that is the issue.
>
>I tried profiling simple application (showing a graph with few nodes,
>using
>RaVis library - sample of what we have on one screen),
>and got exactly the same error popup "No activity happened in the past 60
>seconds
>after connection was established with the application"  and only after
>that
>app came up.
>
>Is there anything I need to do to configure FB Profiler to run it?
>(i haven't done that in Flex before....)
>
>
>On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <ah...@adobe.com> wrote:
>
>>
>>
>> On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>>
>> >Alex,
>> >
>> >That profiler problem happens much before I reach my heavy duty popup
>>with
>> >many children,
>> >on initial screen.
>> >We are making calls to about 30 Stored Procs to get proper permissions
>>and
>> >load static data.
>> >(can probably turn off some of them and only use data relevant to
>>screen
>> >with popup we need,although it might take time to investigate).
>> >
>> >As I said, Debugger is running fine, no timeouts whatsoever.
>> >
>> >Is Profiler more demanding than Debugger?
>>
>> Yes, the profiler is logging data for every line of code and every
>>memory
>> allocation.  So if there is too much work to get the app up and running
>> you can have this sort of problem.
>>
>> I’ve never actually dealt with this situation myself.  IMO, it is an
>> indicator that you could refactor the app and defer some of the work and
>> see faster startup time and allow the profiler to do its thing.
>>
>> One thing you could try is to call pauseSampling() in a preinitialize
>> handler in the app.  That might shutdown the logging and allow the app
>>to
>> start up faster.  Then call startSampling at the right moment to start
>> collecting the data you need.  Here’s the doc:
>>
>> 
>>http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/
>>sa
>> mpler/package.html#pauseSampling()
>>
>> -Alex
>>
>>
>
>
>-- 
>Thank you,
>Oleg.

Re: Profiling Flex/Java Web App

[Oleg Konovalov <ol...@gmail.com>]

I don't think that is the issue.

I tried profiling simple application (showing a graph with few nodes, using
RaVis library - sample of what we have on one screen),
and got exactly the same error popup "No activity happened in the past 60
seconds
after connection was established with the application"  and only after that
app came up.

Is there anything I need to do to configure FB Profiler to run it?
(i haven't done that in Flex before....)


On Thu, Apr 9, 2015 at 3:46 PM, Alex Harui <ah...@adobe.com> wrote:

>
>
> On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>
> >Alex,
> >
> >That profiler problem happens much before I reach my heavy duty popup with
> >many children,
> >on initial screen.
> >We are making calls to about 30 Stored Procs to get proper permissions and
> >load static data.
> >(can probably turn off some of them and only use data relevant to screen
> >with popup we need,although it might take time to investigate).
> >
> >As I said, Debugger is running fine, no timeouts whatsoever.
> >
> >Is Profiler more demanding than Debugger?
>
> Yes, the profiler is logging data for every line of code and every memory
> allocation.  So if there is too much work to get the app up and running
> you can have this sort of problem.
>
> I’ve never actually dealt with this situation myself.  IMO, it is an
> indicator that you could refactor the app and defer some of the work and
> see faster startup time and allow the profiler to do its thing.
>
> One thing you could try is to call pauseSampling() in a preinitialize
> handler in the app.  That might shutdown the logging and allow the app to
> start up faster.  Then call startSampling at the right moment to start
> collecting the data you need.  Here’s the doc:
>
> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/sa
> mpler/package.html#pauseSampling()
>
> -Alex
>
>


-- 
Thank you,
Oleg.

Re: Profiling Flex/Java Web App

[Alex Harui <ah...@adobe.com>]

On 4/9/15, 8:59 AM, "Oleg Konovalov" <ol...@gmail.com> wrote:

>Alex,
>
>That profiler problem happens much before I reach my heavy duty popup with
>many children,
>on initial screen.
>We are making calls to about 30 Stored Procs to get proper permissions and
>load static data.
>(can probably turn off some of them and only use data relevant to screen
>with popup we need,although it might take time to investigate).
>
>As I said, Debugger is running fine, no timeouts whatsoever.
>
>Is Profiler more demanding than Debugger?

Yes, the profiler is logging data for every line of code and every memory
allocation.  So if there is too much work to get the app up and running
you can have this sort of problem.

I’ve never actually dealt with this situation myself.  IMO, it is an
indicator that you could refactor the app and defer some of the work and
see faster startup time and allow the profiler to do its thing.

One thing you could try is to call pauseSampling() in a preinitialize
handler in the app.  That might shutdown the logging and allow the app to
start up faster.  Then call startSampling at the right moment to start
collecting the data you need.  Here’s the doc:

http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/sa
mpler/package.html#pauseSampling()

-Alex

Re: Profiling Flex/Java Web App

[Oleg Konovalov <ol...@gmail.com>]

Alex,

That profiler problem happens much before I reach my heavy duty popup with
many children,
on initial screen.
We are making calls to about 30 Stored Procs to get proper permissions and
load static data.
(can probably turn off some of them and only use data relevant to screen
with popup we need,although it might take time to investigate).

As I said, Debugger is running fine, no timeouts whatsoever.

Is Profiler more demanding than Debugger?


On Thu, Apr 9, 2015 at 12:25 AM, Alex Harui <ah...@adobe.com> wrote:

> First, try a small test app to make sure everything really does work.
>
> Then, in your case, if you can control the number of children, instead of
> profiling 100, profile 50.  The same hotspots should show up.
>
> Or do 50 and then 20 and see if you see a trend.
>
> -Alex
>
> On 4/8/15, 3:25 PM, "Oleg Konovalov" <ol...@gmail.com> wrote:
>
> >Hi,
> >
> >I have a large Flex+Java app (Flex 4.5.1).
> >
> >Created a new complicated screen (with 3 ADGs) and WindowTitle popup
> >to edit a row with 2 sets of children (each is a DataGroup with Renderer,
> >one is a few TextInputs (with 2 way binding),
> >another is 2 dropdownlists (2nd gets a list based on 1st one selection, so
> >there is a call to stored proc), checkbox and a button.
> >
> >It seems that if there are 100s of these children, it takes >35secs for
> >that popup
> >to come up in Edit mode.
> >
> >I tried to profile it using FlashBuilder 4.5.1 on Tomcat 6.0,
> >but when I bring up profiler, it shows me popup "No activity happened in
> >the past 60 seconds
> >after connection was established with the application"  and only after
> >that
> >app comes up.
> >
> >Debugger works fine, and I can run that app without any problems.
> >
> >
> >Is there way to fix it?
> >
> >I have seen lots of posts showing similar error, but no solution so far.
> >
> >
> >Please help!
> >
> >--
> >Thank you,
> >Oleg.
>
>


-- 
Thank you,
Oleg.

Re: Profiling Flex/Java Web App

[Alex Harui <ah...@adobe.com>]

First, try a small test app to make sure everything really does work.

Then, in your case, if you can control the number of children, instead of
profiling 100, profile 50.  The same hotspots should show up.

Or do 50 and then 20 and see if you see a trend.

-Alex

On 4/8/15, 3:25 PM, "Oleg Konovalov" <ol...@gmail.com> wrote:

>Hi,
>
>I have a large Flex+Java app (Flex 4.5.1).
>
>Created a new complicated screen (with 3 ADGs) and WindowTitle popup
>to edit a row with 2 sets of children (each is a DataGroup with Renderer,
>one is a few TextInputs (with 2 way binding),
>another is 2 dropdownlists (2nd gets a list based on 1st one selection, so
>there is a call to stored proc), checkbox and a button.
>
>It seems that if there are 100s of these children, it takes >35secs for
>that popup
>to come up in Edit mode.
>
>I tried to profile it using FlashBuilder 4.5.1 on Tomcat 6.0,
>but when I bring up profiler, it shows me popup "No activity happened in
>the past 60 seconds
>after connection was established with the application"  and only after
>that
>app comes up.
>
>Debugger works fine, and I can run that app without any problems.
>
>
>Is there way to fix it?
>
>I have seen lots of posts showing similar error, but no solution so far.
>
>
>Please help!
>
>-- 
>Thank you,
>Oleg.