babeolz.blogg.se

The server is not reachable sonicwall netextender
The server is not reachable sonicwall netextender











the server is not reachable sonicwall netextender

As of Spark 2.0, Spark no longer uses SSL but uses its more advanced but less prevalent cousin TLS. We’‘re using Wildfire 3.01 behind a firewall as an internal chat server but we have been allowing server to server connections, have the pyAIMt gateway installed and working, and were allowing SSL client connections also through the firewall.

the server is not reachable sonicwall netextender

I’‘ll share what we learned here and with any luck it will help some other folks out there. So, I consider this problem with jvm flag settings on the serverĬharley and I worked extensively on this today to undestand it in our environment. I restarted the server and I didn’'t had this problem anymore.Īlso, there was this file stderr.log on the server with the following content:Įxception in thread “Thread-5” : Java heap spaceĮxception in thread “AWT-EventQueue-0” : Java heap space At the time of problem the memory usage was 75,716 KB Similarly, Wildfired.exe process at startup uses: 43,772 KB. At the time of problem the memory usage was 88,176 KB. Wildfire.exe process at startup uses: 11,644 KB.

the server is not reachable sonicwall netextender

So I realized that the problem is with the server and not client. I noticed that the client is showing Invalid Username / password error when the server is not responding after waiting for certain time. To understand the problem, I ran the Spark application from my MyEclipse IDE.













The server is not reachable sonicwall netextender