Symptoms of multiple browsertabs usage

Our web client does not support multitabbing, as parallel sessions can overlap. This can lead to unexpected behaviour and data conflicts. If a second tab was opened by accident, both need to be closed to prevent a cascading effect.

When multiple tabs have been used in your BOC product, the following entries can be found in your log files:

 

2025-02-21 18:10:10,040 INFO [catalina-exec-51] [*] [1465374097:224647] ACTIVATE CLIENT view (handle:id224630 created:3 active:2) - com.boc.axw.core.client.SessionClientHandles.logInfo(SessionClientHandles.java:186)

02-21 18:10:10,040 WARN [catalina-exec-51] [*] [1465374097:224647] MULTIPLE CLIENT HANDLES for this session. This most likely implies multiple tab usage! - com.boc.axw.core.client.SessionClientHandles.activateHandle(SessionClientHandles.java:100)

Symptoms

Randomly missing objects in the model editor / Checked object is undefined / Error while saving

• Those errors happen because one tab occupies the session from the other.
• If there are changes being made, and they haven't been saved, they can't be saved any more because of the missing session that is now active in another tab.

Previously worked on model is distorted

• This happens when the same model has been worked on parallel in several tabs

Copy and paste in multiple tabs

• Having a model opened in multiple tabs causes the webserver to react twice when triggering an action, what happened is that the user seems to have cut/copied & pasted some model elements and then created a relation to this element.
  Since the paste is done twice, the first paste action is done properly on the aserver, but the second time is skipped since it was detected that the pasted object is already contained, leading to the following warning in the logs:

2025-02-21 17:50:30,910 INFO  [catalina-exec-53] [*] [1465374097:223309]
Propagating 1 actions to AServer...

2025-02-21 17:50:30,975 WARN  [catalina-exec-53] [*] [1465374097:223309]
No paste atom available...

• This internally causes two states in the webserver:
  One where the object exists in the model and one where it does not.
  When then a relation is created to this object it again reacts twice, for the first state it is fine, the object exists but for the second state the object does not exist, and therefore an exception is thrown. 

OrgPortal/Read and Explore is randomly missing the starting page model

• This relates to state filter problem: When a session with a state filter already applied is open, and a new tab is opened where the same filter is applied, some models are filtered. This only affects the read-only state and does not impact editing.