How we can speedup Designer 10.5 version

1

Hi Team,

We are using wM Designer 10.5 version via RDP and nowadays whatever changes we are doing in the flow services changes are not saving and every time it is restoring the session again and again, Can you please let me know how we can fix the below issue -

We are getting below error -

Screenshot 2021-12-01 at 10.40.01 AM
Screenshot 2021-12-01 at 10.40.01 AM742×658 223 KB

Also can you please let me know how we can increase the Designer ‘Heap Size’ and ‘RAM’ or is there a way to speed up the designer?

In the eclipse.ini file, we are using below -
-Xms256m
-Xmx1024m

2

A couple of points.

  1. How frequent are the error messages “read timed out” , it is unclear from the log attached since there are no timestamps. Do you see any error messages in the error log?
    If the designer is in the same machine as the Integration Server, do these Socket exceptions go away?
  2. Regarding speeding up , it sometimes helps to start with a higher memory allocation , but it depends on the exact problem at hand.
    I would suggest raising a support ticket for this issue.

-NP

3

Hi @Nagendra_Prasad -

Below are my comments -

Whenever we are doing the changes in DEV env in any of the flow services it is restoring the session every time and shows the above mentioned error in the screenshot.
We are connecting to WVD and then using the wM Designer 10.5 Version but SAG is installed in a different machine.

Error IS
Error IS1834×1022 70.2 KB

SAG Error
SAG Error3558×1806 150 KB

4

Hi @Yogesh_Maheshwari ,
The error logs on the IS side could have some more information on the error. you can check them in the Admin UI by navigating to Logs->Error , expanding the stacktrace.

There could be genuine network issues, hence would suggest you to try what is mentioned above.
Other than this , I cannot think of anything else here. Would wait if anyone else has any thoughts or would suggest to raise a ticket.

-NP

5

Hi,

is there a firewall involved?
In this case it might be a timeout issue, meaning that the firewall thinks that the connection is no longer used and stops it.
In our environment there is a firewall timeout every 30 minutes which cannot be changed.
But usually Designer tries to reconnect to the server when this happens.

Regards,
Holger

1 Like
6

Hi @Nagendra_Prasad @Holger_von_Thomsen

I can see below logs in Stake Trace -

com.wm.io.comm.CommException: [BAC.0002.0000] Wrapped Exception: java.net.SocketTimeoutException: Read timed out
at com.wm.app.b2b.server.ServerHTTPLink.receive(ServerHTTPLink.java:110)
at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:116)
at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:170)
at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:364)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:745)

7

Good point @Holger_von_Thomsen about the firewall, but I would imagine that a firewall would be set to block at set intervals, In this case the time intervals seem random from the image below.

From the randomness, I cannot rule out network issues.

@Yogesh_Maheshwari , the stack trace is indicative of the communication between Designer and IS , so without more investigation it is not possible to figure out the reason.

-NP

8

Thanks @Nagendra_Prasad @Holger_von_Thomsen for sharing the information, I have checked with our network team and issues were from the network- firewall side.

Later network team made the necessary changes from their side and after that, we are able to save the changes in Designer.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.