# Websocket max message size exceeded in Perspective when lots of alarms in Alarm Status Table

**URL:** <https://forum.inductiveautomation.com/t/websocket-max-message-size-exceeded-in-perspective-when-lots-of-alarms-in-alarm-status-table/78095>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 18, 2023, 6:15pm UTC](https://forum.inductiveautomation.com/t/websocket-max-message-size-exceeded-in-perspective-when-lots-of-alarms-in-alarm-status-table/78095 "2023-08-18T18:15:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Ar](https://avatars.discourse-cdn.com/v4/letter/k/b4bc9f/32.png) [@Kevin\_Ar](https://forum.inductiveautomation.com/u/Kevin_Ar)\
**Post date:** [August 18, 2023, 6:15pm UTC](https://forum.inductiveautomation.com/t/websocket-max-message-size-exceeded-in-perspective-when-lots-of-alarms-in-alarm-status-table/78095/1 "2023-08-18T18:15:34Z")

</div>

I'm building a Perspective screen with an alarm status table for a large system with lots of alarms. I am simulating the devices for now using the built-in device simulator in Ignition so a lot of alarms are triggered at the same time.

When the alarms come in, I get a "Lost Connection to gateway" message in the designer and in the perspective client. The error message is below:

![image](https://us1.discourse-cdn.com/inductiveautomation/optimized/3X/5/4/54d938746cd43c3775d5b1b574d02debd1116159_2_690x16.png)

I found a post for a similar issue, but am wondering if there is some way to optimize the alarm status table so that I don't need to increase the websocket max message size. I have the pager setting on the alarm status table enabled already. Is the websocket shared for all the views or does each view get it's own websocket (i.e. if one view exceeds the max message size, will that impact other views)?

> [@Gateway Crashing when passing view parameter](https://forum.inductiveautomation.com/t/gateway-crashing-when-passing-view-parameter/41392/25):
>
> As my colleague @cmallonee mentioned, for those who need steps to add/modify the websocket max message size for Perspective, you will need to do the following to add the JVM parameter to Ignition: Open the ignition.conf file that is located in the data folder that’s found in your Ignition installation path Open the ignition.conf with any text editor Within the ignition.conf file, scroll down to where it says # Java Additional Parameters; This is the location where JVM parameters are added into…

---

<div class="post-metadata">

**Author:** ![edward.fowler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/edward.fowler/32/24179_2.png) [@edward.fowler](https://forum.inductiveautomation.com/u/edward.fowler)\
**Post date:** [June 19, 2024, 1:55pm UTC](https://forum.inductiveautomation.com/t/websocket-max-message-size-exceeded-in-perspective-when-lots-of-alarms-in-alarm-status-table/78095/2 "2024-06-19T13:55:23Z")

</div>

I had a similar issue, the alarm status table had about 1000 unacknowledged alarms. The issue cleared up after acknowledging them. It took some time as I kept losing the connection, but it improved as more and more alarms were acknowledged.

Another note on this, it also happened on views that didn't include the alarm status table, just some alarm counts in the north-doc header (query driven).