[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
12:27 a.m.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.SP1, 2.1.0.GA
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is
actually around 25ms. Anything smaller than that, it gets rounded up.
Also, using
timer to set response callback are inherently flawed IMO. There's always going to be
some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem to
have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing code
on the server. If the breakpoint is inserted, everything is good. But when I removed the
breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:22 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak commented on JBSEAM-3721:
--------------------------------------
So do you have a workaround?
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:24 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak updated JBSEAM-3721:
---------------------------------
JBoss Forum Reference: (was: https://jira.jboss.org/jira/browse/JBSEAM-3716)
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Paul Chan commented on JBSEAM-3721:
-----------------------------------
Unfortunately no. I only know why it happens, but I have no idea how it can be solved
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:47 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Eric Jung updated JBSEAM-3721:
------------------------------
Attachment: remote.js.diff
Patch attached. It's inspired from the Yahoo! Interface Library (YUI)'s
YAHOO.util.Connect, an XHR wrapper. The YUI source code, connection.js, is here:
http://developer.yahoo.com/yui/docs/connection.js.html. Specifically, the
YAHOO.util.Connect.handleReadyState() function polls the XHR object every 50 msecs for its
readyState. The XHR.onreadystatechange property is *not* used at all, thereby avoiding the
race condition described in this bug. When the XHR.readyState has reached 4 (all data has
been received), the user-defined callback function, if defined, is invoked.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:52 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Eric Jung updated JBSEAM-3721:
------------------------------
Attachment: remote.js.diff
Oops, the first patch was missing a couple of items. Please use this one instead.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:42 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Stephen Jones commented on JBSEAM-3721:
---------------------------------------
This means Seam Remoting is broken for over 50% of the web browser market! Please verify
Eric's excellent patch and incorporate into Seam ASAP.
Thanks Eric!
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:53 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Eric Jung commented on JBSEAM-3721:
-----------------------------------
My fix has been available for over 7 months. Could a committer please review it, comment
on it, commit it or... anything? :)
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:15 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak commented on JBSEAM-3721:
--------------------------------------
Not that I don't trust Yahoo, but I haven't seen this technique used by another
library besides them (e.g. Prototype, GWT). Can you confirm that this technique works
flawlessly in regards to concurrency (with multiple concurrent requests being processed),
on all major browsers?
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Colette Massey commented on JBSEAM-3721:
----------------------------------------
I am seeing this problem with Firefox 3.0.x and 3.5.x and Seam 2.1.1.
I am temporarily resolving this issue by putting sleeps on the server side methods that
are too fast--but that's a pretty bad hack.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:34 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Eric Jung commented on JBSEAM-3721:
-----------------------------------
Not that I don't trust Yahoo, but I haven't seen this
technique used by another library besides them (e.g. Prototype, GWT). Can you confirm that
this technique works flawlessly > in regards to concurrency (with multiple concurrent
requests being processed), on all major browsers?
No, I don't have the time or resources to do that kind of testing.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:36 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Samuel Mendenhall updated JBSEAM-3721:
--------------------------------------
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:13 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Paul Chan commented on JBSEAM-3721:
-----------------------------------
Can we assume someone from the Seam Team is looking into integrating this fix into the
next release? I am thinking alot of people are seeing this problem as well. I apologize
if i seem a bit eager, but this is a major issue that I am sure many users would like to
see fixed as soon as possible.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:38 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak commented on JBSEAM-3721:
--------------------------------------
Could someone please confirm that the latest version of remote.js
(http://fisheye.jboss.org/browse/Seam/branches/community/Seam_2_2/src/remo...)
still exhibits the issue originally described? The latest version seems to conform with
similar changes made to GWT to fix the same issue:
http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thr...
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:07 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Paul Chan commented on JBSEAM-3721:
-----------------------------------
Looking at version 10195 of remote.js, it still seems to exhibit the same problem that I
have discovered from 9months ago.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is
actually around 25ms. Anything smaller than that, it gets rounded up.
Also, using
timer to set response callback are inherently flawed IMO. There's always going to be
some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem to
have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing code
on the server. If the breakpoint is inserted, everything is good. But when I removed the
breakpoint, the problem appears again.
--------
Eric Jung's fix might resolve this issue since it utilizes a tid array lookup with no
timer to expire.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:03 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak commented on JBSEAM-3721:
--------------------------------------
This doesn't quite make sense to me - the setTimeout() call is only being used to set
onreadystatechange to an empty function, and not to set the response callback. Take a
look at the following code from remote.js (line 650 onward):
asyncReq.onreadystatechange = function()
{
if (asyncReq.readyState == 4)
{
var inScope = typeof(Seam) == "undefined" ? false : true;
if (inScope) Seam.Remoting.hideLoadingMessage();
window.setTimeout(function() {
asyncReq.onreadystatechange = function() {};
}, 0);
if (asyncReq.status == 200)
{
if (inScope) Seam.Remoting.log("Response packet:\n" +
asyncReq.responseText);
if (callback)
{
// The following code deals with a Firefox security issue. It reparses the XML
// response if accessing the documentElement throws an exception
try
{
asyncReq.responseXML.documentElement;
//Seam.Remoting.processResponse(asyncReq.responseXML);
callback(asyncReq.responseXML);
}
catch (ex)
{
try
{
// Try it the IE way first...
var doc = new ActiveXObject("Microsoft.XMLDOM");
doc.async = "false";
doc.loadXML(asyncReq.responseText);
callback(doc);
}
catch (e)
{
// If that fails, use standards
var parser = new DOMParser();
//Seam.Remoting.processResponse(parser.parseFromString(asyncReq.responseText,
"text/xml"));
callback(parser.parseFromString(asyncReq.responseText, "text/xml"));
}
}
}
As you can see from the above code, the setTimeout() call is only invoked after receiving
a successful response. Could you try commenting out the window.setTimeout() line from
this code to see if it makes a difference? Another option may be to move the setTimeout()
code to after when the callback is invoked.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:08 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak commented on JBSEAM-3721:
--------------------------------------
Actually I may have spoke too soon - I would still try commenting out the
window.setTimeout() method (from what I remember it's only there to clean up a memory
leak anyway) however I suspect the correct fix would be to move it into the following
block:
if (asyncReq.status == 200)
{
window.setTimeout(function() {
asyncReq.onreadystatechange = function() {};
}, 0);
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:33 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Paul Chan commented on JBSEAM-3721:
-----------------------------------
Shane, I tried the fix as recommended by you and it seems to work in firefox as always. I
can't test it in internet explorer however, so i don't know whether it would work
or not. This is using remoting.js in Seam 2.2 with the fix you recommended above.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:23 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3721) Seam Remoting Callback not set before server response comes back
[
https://jira.jboss.org/jira/browse/JBSEAM-3721?page=com.atlassian.jira.pl...
]
Shane Bryzak closed JBSEAM-3721.
--------------------------------
Fix Version/s: 2.2.1.CR1
Resolution: Done
I've committed this change to the 2.2 branch - I'm going to assume that it's
fixed the problem (as I can't reproduce it myself) but if anyone is still experiencing
it after this update please re-open this issue.
Seam Remoting Callback not set before server response comes back
----------------------------------------------------------------
Key: JBSEAM-3721
URL: https://jira.jboss.org/jira/browse/JBSEAM-3721
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.1.0.GA, 2.1.0.SP1
Environment: XP SP3, VMWARE 3.5i ESX, 2GB RAM, DualCore AMD 3800+
Reporter: Paul Chan
Assignee: Shane Bryzak
Fix For: 2.2.1.CR1
Attachments: remote.js.diff, remote.js.diff
Original Issue
===========
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
Problem found with the above fix
============================
I have found a bug in this fix.
If the server response comes back before the "window.setTimeout(xxx,0) expires, it
will drop it.
From reading the javascript specs, the minimum timeout value is actually around 25ms.
Anything smaller than that, it gets rounded up.
Also, using timer to set response callback are inherently flawed IMO. There's always
going to be some sort of race condition.
This problem seems to happen on internet explorer, and safari. Firebox doesn't seem
to have a problem with it though.
I discovered this problem when I set a break point on the incoming request processing
code on the server. If the breakpoint is inserted, everything is good. But when I removed
the breakpoint, the problem appears again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5391
days inactive
5706
days old
18 comments
6 participants
participants (6)
-
Colette Massey (JIRA) -
Eric Jung (JIRA)
-
Paul Chan (JIRA)
-
Samuel Mendenhall (JIRA)
-
Shane Bryzak (JIRA)
-
Stephen Jones (JIRA)