[GLASSFISH-16575] Object doesn't support this property or method at ... resource/common/js/adminjsf.js line 2091 Created: 06/May/11  Updated: 16/Jun/11  Resolved: 16/Jun/11

Status: Resolved
Project: glassfish
Component/s: admin_gui
Affects Version/s: 3.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: brimimc Assignee: Jason Lee
Resolution: Invalid Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: 3_1-next, 3_1_1-scrubbed

 Description   

Though it seems consistent on some machines, it seems like a timing issue. Line 2091 is

adminggui.ajax.pingHeader()

inside the admingui.ajax.get function

It seems that it's possible for this line of code to be executed prior to the loading of the definition of pingHeader (which is defined at the end of the object's declarations)



 Comments   
Comment by Anissa Lam [ 10/May/11 ]

Can you be more specific on what you are experiencing ?

Comment by brimimc [ 10/May/11 ]

I receive a script error when using the admin gui - the error message is

Object doesn't support this property or method at ... resource/common/js/adminjsf.js line 2091

The method it is complaining about seems to be pingHeader()

It looks like a timing issue, if the page is slow to load, it's possible for this line of code to be executed prior to the complete loading of the adminjsf.js. Since pingHeader is defined at the end of the file it's not yet defined.

Comment by brimimc [ 12/May/11 ]

Is that enough detail or do you need more info?

Comment by Jason Lee [ 17/May/11 ]

What browser and OS? Do you have a set of steps we can follow to reproduce this? I'm not seeing it locally. :|

Comment by brimimc [ 17/May/11 ]

Win7/XP 32 bit IE8 - but we have seen it work on XP 32 bit IE8 as well. I don't think it's a platform issue, but a timing issue (e.g if you machine is slower it's more likely to happen).

I'll try and get a stack trace for you, but you should be able to help it along by adding a bunch of noop code before the definition of pingHeader to delay the loading of the method definition.

Comment by brimimc [ 17/May/11 ]

Also of note this is being displayed in the embedded active x IE component - not sure if this have any relation other than it may be slower than the external browser?

Comment by brimimc [ 18/May/11 ]

This was in the log:

07:59:38.06][ERROR]: SCRIPT ERROR: Object doesn't support this property or method at http://msass4:4848/resource/common/js/adminjsf.js line 2091
[07:59:38.17][ERROR]: Error was in: function() {
admingui.ajax.loadPage(

{ url : url, target: document.getElementById('content'), oldOnClickHandler: oldOnClick, sourceNode: node }

);
return false;
}
[07:59:38.18][INFO]: Received DOM Event: [BID: 0][FPATH: ][TYPE: click][PATH: //A[@id='treeForm:tree:applications:applications_link']][LOC: 594, 160][THINK: 175][URL: http://msass4:4848/common/index.jsf][TAG: A][SUBTAG: ][VALUE: Applications]

Comment by Jason Lee [ 02/Jun/11 ]

I just noticed that you said "this is being displayed in the embedded active x IE component". Does that mean you're NOT using the standalone Internet Explorer application but are, rather, using a third party app that embeds IE via this ActiveX control? If so, what app is that? Is it publicly/freely available? I have not been able to reproduce this issue on my WinXP VM with IE 8.

Comment by Jason Lee [ 02/Jun/11 ]

Can this same user reproduce the issue on the more traditional standalone IE 8 on the same box?

Comment by Jason Lee [ 02/Jun/11 ]

I'm not sure the no-op code would achieve much, because, as I understand things, Javascript is single threaded. When the browser finds a script tag, it loads (either from the page or the specified remote resource) the Javascript source and processes it before moving on to the next element on the page. I've done some searching for a definitive answer on that and haven't found anything to contradict it. If I'm wrong, and you know of a definitive refutation, I'd certainly love to see it.

Comment by brimimc [ 03/Jun/11 ]

No, it does seem limited to the embedded active X component.

In fact we may have found the problem outside of glassfish. I'll verify this and get back to you.

Comment by Anissa Lam [ 15/Jun/11 ]

any update ?
We will close this issue on Friday, 6/17, if we don't hear anything. thanks.

Comment by brimimc [ 15/Jun/11 ]

Yes, go ahead and close it. It was due to xmlhttprequest being hijacked and not a problem in glassfish. Sorry for the bogus case.

Comment by Jason Lee [ 16/Jun/11 ]

Closed per reporter's request.

Generated at Sat Feb 28 05:27:40 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.