EDIS is working Very Slow

[Sree]

Dear All,

Any idea why the EDIS is working very slow.

Regards,
Srikant

[Wasim Naffar]

Hi Srikant,

Actually, EDIS is working well without any delay or freezing from our side. But keep in mind for every action like select Patient from list or refresh the list every secondes makes hits and transactions between the browser and the server, so there is a hidden transactions between the application (browser) and the server(i.e data transactions between browser , web-server tomcat & VistALink).
in addition EDIS uses Media Flash, which is slower than HTML sometimes, depend on the application.

Anyway, I suggest to check & monitor your connections between Application-Server(Tomcat or Jetty) and VistALink.

There is no specific tool or fixes that I can send to you for these testing.
But in case you face any error something like "Refresh Log Selector failed: Error# 1085" I can send you some hints that may help.

BTW, What is the Application Server (Container) that you already use? Tomcat or Jetty ...!!!

Regards,
Wasim

--
You received this message because you are subscribed to the Google Groups "VistA Emergency Room" group.
To post to this group, send email to vista-emer...@googlegroups.com.
To unsubscribe from this group, send email to vista-emergency-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/vista-emergency-room?hl=en.

[Sree]

Dear Wasim,

Thanks a lot for your support.
I use Tomcat7 and sometimes i faced the issue "Refresh Log Selector
failed: Error# 1085"
Please suggest me the hints for that.(I resolved the issue by
commenting few Exception lines)

Can it will run fast in case i switch from Tomcat7 to jetty?
Which Application server you are using?

Regards,
Srikant

[Wasim Naffar]

Fine!
The "Refresh Log Selector failed: Error# 1085" happens because the server has a security issue to limit the number of connections per IP.
This security defined in the configuration file for the VistALink in the xinetd, so you need to edit this configuration file to be something like below:
per_source = UNLIMITED
instances = UNLIMITED

and that will solve this Error# 1085.

As you know it is not enough and not right to comment any Exception lines from the source code.

I use Tomcat6, but i think there is no problem if you use Tomcat7 or Jetty, so don't worry about Application-Server now.

Regards,
Wasim

[Sree]

Dear Wasim,

I have changed the file "/etc/xinetd.conf" as per ur instruction
like

# Define access restriction defaults
#
# no_access =
# only_from =
# max_load = 0
cps = 50 10
instances = UNLIMITED
per_source = UNLIMITED

But still the problem is there.


Note( I am not able to start the VistALink port from the Foundation
Manager menu Options
so am starting the VistALink port using the Command J
LISTENER^XOBVTCPL(8011))


Regards,
Srikant

On Feb 13, 12:58 pm, Wasim Naffar <w0795930...@gmail.com> wrote:
> Fine!
> The "Refresh Log Selector failed: Error# 1085" happens because the server
> has a security issue to limit the number of connections per IP.

> This security defined in the configuration file for the VistALink in the *
> xinetd*, so you need to edit this configuration file to be something like
> below:
> per_source = *UNLIMITED*
> instances = *UNLIMITED*