Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delay in broadcasting data #1168

Closed
rekhahindlekar opened this issue Jun 29, 2013 · 1 comment
Closed

Delay in broadcasting data #1168

rekhahindlekar opened this issue Jun 29, 2013 · 1 comment

Comments

@rekhahindlekar
Copy link

Hi,

We are using the Atmosphere API version 1.0.12. In our setup, the Server receives data from an application, and broadcasts these data to client, that are suspended on a HTTP connection, which receives these data in real-time. This set-up has been working for the last 18 months.
2 days back, we had an issue, where the clients started getting delayed data i.e data that was broadcasted nearly 30 minutes back were received by the clients. We stopped the application which was sending the data to the server, but still the clients were receiving the data. It seemed as if the data broadcasted by Server was getting cached up and the clients were receiving the data from the cache.

We are sure that the Server broadcast was at real time, since just before the data is broadcasted, it is also stored in a container on the Server, which is then writen back to the database by a parallel thread. The container data as welll as the database data synced with the data being received by the Server from the application. Only the data received by the client was delayed.
We even started a fresh client connection and still it received the delayed data.There were no errors shown in any of the log files.

Can anyone help us out, regarding what can be the cause of this issue. The Application Server used is JBoss 7.1.1 and we have used the HeaderBroadcasterCache, specified in the web.xml as shown below :

<servlet>

     <description>AtmosphereServlet</description>   

     <servlet-name>AtmosphereServlet</servlet-name>

<servlet-class>org.atmosphere.cpr.AtmosphereServlet</servlet-class>

    <init-param>
        <param-name>org.atmosphere.useBlocking</param-name>
        <param-value>false</param-value>
    </init-param>

    <init-param>
        <param-name>org.atmosphere.cpr.broadcasterCacheClass</param-name>
        <param-value>org.atmosphere.cache.HeaderBroadcasterCache</param-value>
    </init-param>

    <load-on-startup>0</load-on-startup>
    <async-supported>true</async-supported>

Regards,
Rekha Hindlekar

@jfarcand
Copy link
Member

@rekhahindlekar What you are asking is professionnal service. Please visit async-io.org and buy professional services or subscriptions. This is clearly not a bug in Atmosphere, but somewhere in your system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants