Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 11 total
Thread TLink: URL property or "window.location.href"
Tue, Mar 26 2013 3:23 PMPermanent Link

Alvaro

Hi all:

I have an application written on EWB 1.01b5 with EWB Server and ElevateDB 2.12b2 Unicode.
The application has a main application and three sub-applications with different options.
Since the principal application for use 3 TLink URL call to each of the three sub-applications.
To complete each sub-application, use a TLINK to call the main application via URL.
For two or three days of intensive use, everything works OK.
But then, begin to malfunction calls to the main URL from the sub-applications when trying to close them.
From the main application to sub-applications (using TLink URL), never had problem.

The only way to reverse this is down the server, delete the folder where the applications, modules, images, etc and recopy everything again and newly re-run the server.
The URL invokes the listening port in the Web Server, is the 8089.

Why it works well for some time and the only way to get it working again is to do all the steps mentioned?
It can be a problem in the Web Server or may be a problem with the hosting?

Probe into the OnClick event, put:
  window.location.href: = 'http://xxxxxx.xxx.xxxxr:8089/subsystem1/';
And it is exactly the same issue.

Thanks in advance.
Alvaro
Tue, Mar 26 2013 3:39 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alvaro,

<< But then, begin to malfunction calls to the main URL from the
sub-applications when trying to close them. >>

What do you mean by "malfunction" ?  Please elaborate on the symptoms that
you're seeing.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Tue, Mar 26 2013 11:21 PMPermanent Link

Alvaro

"Tim Young [Elevate Software]" wrote:

<<What do you mean by "malfunction" ?  Please elaborate on the symptoms that
you're seeing.>>

Tim: I was not clear in describing the error.
Clicking on TLink output to return to the main system, the browser is trying to connect and awaiting response from the server.

Actually that link works because it is the homepage of the project.

Calling the main project:
http://xxxxxxxx.xxx.xxx.xx:8089/

Calling the sub-project:
window.location.href: = 'http://xxxxxxx.xxx.xxx.xxr:8089/subsystem1/';

Leaving the sub-project, this is called the main project:
window.location.href: = 'http://xxxx.xxxxxx.xx:8089/';

The original test was completing URL property TLink component with the URL that I mentioned earlier.

At some point we talked about having all the options in a single project, to speed in a single download the entire project.
I have not yet defined the sub-projects to incorporate and how great it will be, so I started to assemble thus separated.
However I have in mind what you recommended and also commented in great detail Claudia Borsel forum.

Returning to l issue in question ....
For two or three days works Ok.
Suddenly the browser is looking for the call to the main project and the only way to return to the main menu by pressing the browser back.
It happens in all browsers that probe: FF, IE9, Chrome, Opera and Safari.
I copied privately user and pass for you to check the behavior.
thanks
Alvaro
Wed, Mar 27 2013 1:14 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alvaro,

<< Clicking on TLink output to return to the main system, the browser is
trying to connect and awaiting response from the server. >>

It works fine in IE, but not in FF, which appears to be this issue:

http://www.elevatesoft.com/incident?action=viewrep&category=ewb&release=1.01&incident=3716

Are you sure that you're using the latest build of the EWB Web Server ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Mar 27 2013 1:36 PMPermanent Link

Alvaro

"Tim Young [Elevate Software]" wrote:

<<Are you sure that you're using the latest build of the EWB Web Server ?>>

Tim:
I check the version and I have installed 1.01b5.
Just probe again with IE9, but does not work.
Just in 7 or 8 hours, could reinstall everything again on the server to check that after the reinstatement works Ok, even with FF.

My question is if I clear the cache in some way, by repeating many times access to the URL and therefore remains on hold.
Currently I am not doing anything about it. I just make the call to the URL for every click a user makes on TLink component.
This idea of clearing the cache would explain in part because reinstalling everything, then it works.
thanks
Alvaro
Thu, Mar 28 2013 7:54 PMPermanent Link

Alvaro

Tim: Tested. Just could the entire site, TLink now works fine. FF works well sometimes. Half of them is waiting for the response from the server.
What is striking is that all browsers start having problems after two or three days.
Leave the session available for you to try if needed.

And a funny thing: I have to copy the entire site, if I copy only index.html and the corresponding Java application, also I have the same behavior.

Have any explanation need to copy the entire site to work properly? (images folder, folder modules, themes folder, sub-systems folder, main application with their respective images)

That's all for now.
regards
Alvaro
Fri, Mar 29 2013 2:11 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alvaro,

<< Tim: Tested. Just could the entire site, TLink now works fine. FF works
well sometimes. Half of them is waiting for the response from the server.
What is striking is that all browsers start having problems after two or
three days. Leave the session available for you to try if needed. >>

What does FireBug (F12/Net Panel) say under FF when you have the issue ?  It
should indicate which file it is waiting on.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Fri, Mar 29 2013 3:13 PMPermanent Link

Alvaro

"Tim Young [Elevate Software]" wrote:

<<What does FireBug (F12/Net Panel) say under FF when you have the issue ?  It
should indicate which file it is waiting on.>>

Tim:
By the order in which each subsystem is loaded, the first thing that transfers the server is the theme. In the screenshot I sent you in private, to choose the option subsytem2 first and then load up the application. Returning to the main menu, the theme also loaded first and then the application.
When I want to load subsytem1, fails to load anything, so we can assume that has problems loading the theme.
I could not recreate the problem in reverse, because now subsytem1 failure load.
Be a problem with the theme?
thanks
Alvaro
Mon, Apr 1 2013 5:22 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alvaro,

<< When I want to load subsytem1, fails to load anything, so we can assume
that has problems loading the theme.  >>

We can't *assume* anything. Smile Did FireBug indicate that it was having
trouble loading the theme CSS file ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Apr 10 2013 3:52 PMPermanent Link

Alvaro

Tim:
Finally I found what was the problem of the server machine.
The staff makes technical maintenance on PC's in the hospital, installed on the PC's NOD32 antivirus.
(coincides with the time when the problems started).
After all this time, I decided to leave everything uninstalled and start to install what I needed.
In the midst of all this, I was doing tests until after removing the NOD32, the application started working.
It is not my task to configure the antivirus. I install Avast Free and everything was working Ok. This does not discredit NOD32, just I have no time to study as configured.
Sometime'll check and configure NOD32.
Now it's working fine.
Thanks again for advising me on this issue.
Best Regards
Alvaro
Page 1 of 2Next Page »
Jump to Page:  1 2
Image