Applets get Hung up very often

[sidnooradarsh]

Hi,

We have JRE 1.5 and IE 6 running on the client machines.

And we are facing some serious problems like after some hours like 1-2 hrs ( No specific time intervals) the applets hang up and all the charts and grids just blank out showing just black color i mean the whole grid or chart blacken up thats it and we cannot do anything then we need to kill the process from task manager or logoff or restart the machine to bring back the portal

and restart the application again.

This has never happened earlier.

Please anyone guide me

1) what might be the possible causes for Hanging up?

2) Is it the memory issue?

3) Does the java version we are using has the problems?

4) Is it the problem with IE 6 we are using?

4) Something other than these problems?

Thanks,

Adarsh

[Former Member · Accepted solution]

You probably have an infinite loop caused by appletA updating appletB which has an updateevent that updates appletA that updates appletB which...

Or, you are trying to reference an applet via a body onLoad js event when the applet has not fully rendered yet.

[sidnooradarsh · Accepted solution]

Ryan,

I guess you may be right.

But it doesn't happen all the time.

When we close the application and restart It works fine

but gradually after sometime at some point it gets hung up.

Is it the problem with the network or IE 6 or JRE( we are using JRE1.5 update 14) used by us or anything else.

Please provide some suggestions as what are the things we need to ensure or any solution to fix this issue.

Regards,

Adarsh

[Former Member]

When I was in the early stages of my learning xMII, I would have problems like this as well. Personally, I have found if you are over complicating your queries or, in Xacute, over complicating your transactions, this could be a cause. What I mean is look at the original query. If the origin of the query resides in SQL, check the design of the view or the procedure. I personally prefer to point to tables and create the calculations in Xacute to minimize the hang ups.

A good way to see this problem is by remoting into the xMII server and view the processes. Start your transaction and you will see the java percentage spike and then the memory usage will stay at the 100,000 mark or higher. Your system will not recover unless you restart the services. This is a good indication that the transaction or queries you are trying to execute are not performing well.

Edited by: Chip Pyles on Apr 14, 2008 10:01 PM

[jcgood25]

Have you monitored the Sun Java Console for any insightful error messages?

It appears to be a client issue, but are you seeing any server side errors at the time the client is 'hung'.?

Have you considered that application logic may be part of the issue?

Is the situation related to elapsed client time and activity or is influenced by time of day?

If it is repeatable then have you tried a client running a 1.4.2 or 1.6 version of the JRE?

[sidnooradarsh]

1) When the applets get hung up the whole application gets hung up and we are not able to open Java console also.

But we have enabled Applet tracers, Show exception and error logs thru Java control panel or console.

2) No we are not looking at the server side when client gets hung up because earlier we went live on 4 machines and we never faced this issue at all. But now we have went live on nearly 10 machines and i am wondering may be has got something to get hung up.

3) This issue is not specific to any time part of the day.

it happens randomly at any point of time

4) And we have not checked with 1.4.2 or 1.6 we are using 1.5 on client machines and we are using IE 6 and windows XP platform. but on server we are using 1.4.2

[Former Member]

>

> 
> 4) And we have not checked with 1.4.2 or 1.6 we are using 1.5 on client machines and we are using IE 6 and windows XP platform. but on server we are using 1.4.2

Adarsh,

Can you be more specific as to which JRE you are running on the client machines? I had significant issues with 1.5.0_9 (similar non-repeatable seemingly random issues), which went away when I moved the client to 1.5.0_12.

Also, I setup a prototype environment running xMII 11.5 on a VMWare virtual server, which caused similar unpredictable applet results on the client side. This probably doesn't relate to your issue, but I wanted to throw it out there in case anyone else contemplates setting up a virtual server.

Regards,

Rod Hoffman

[agentry_src]

Which version of xMII are you running? And what JRE do you have running on the xMII server?

[sidnooradarsh]

We are using SAP xMII 11.5.3 b66 version

and we are using java 1.4.2 upadate 13.