The subject is the error I have been getting on both of the 2.x.x releases. It says authenticating then this pops up. I have tried both the regular server name as well as by ip address. This is working fine with 1.1.4. anyone have any ideas?
Also if in the advanced tab if i change the port from 5222 to 5223 and put in the ip for the host I get an invaid user/password error
I’‘m getting this as well. I’‘m wondering if it’'s an SSL issue? I have SSL enabled to the Wildfire server through the firewall. Used to be you could connect to Wildfire via SSL (Old Port Method) in Spark, up to and including the 2.0 Beta. Starting with the first official 2.0 release this seems to be broken. If the remote users connect to the VPN and use the internal address of the Wildfire server and port 5222 (no SSL) they can log in without a problem.
Message was edited by: jdueltgen
Yes we are also using the alt port ssl although it did not work in the 2.0 beta either. We are also using an old server version(2.2.2)
same here – any ideas/updates?
charley
Hi
I had similar problem. To understand the problem, I ran the Spark application from my MyEclipse IDE. I noticed that the client is showing Invalid Username / password error when the server is not responding after waiting for certain time.
So I realized that the problem is with the server and not client. Wildfire.exe process at startup uses: 11,644 KB. At the time of problem the memory usage was 88,176 KB. Similarly, Wildfired.exe process at startup uses: 43,772 KB. At the time of problem the memory usage was 75,716 KB
I restarted the server and I didn’'t had this problem anymore.
Also, there was this file stderr.log on the server with the following content:
Exception in thread “Thread-5” java.lang.OutOfMemoryError: Java heap space
Exception in thread “AWT-EventQueue-0” java.lang.OutOfMemoryError: Java heap space
Exception in thread “AWT-EventQueue-0” java.lang.OutOfMemoryError: Java heap space
Exception in thread “AWT-EventQueue-0” java.lang.OutOfMemoryError: Java heap space
So, I consider this problem with jvm flag settings on the server
Please comment.
Regards
GS
Charley and I worked extensively on this today to undestand it in our environment. I’‘ll share what we learned here and with any luck it will help some other folks out there. 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. As of Spark 2.0, Spark no longer uses SSL but uses its more advanced but less prevalent cousin TLS. SSL/TLS is often used in one breath so I wasn’‘t really aware of the differences before flogging this problem to death but they ain’‘t the same and although Wildfire supports both, Spark does not anymore. To allow outside clients to connect to our Wildfire server without having to run a VPN client we can open port 5222 and Spark will connect using TLS. We verified with a packet sniffer that the connection is in fact encrypted after the handshake so as long as we open port 5222 and tell Wildfire that Client Connection Security is Required we have a working secure solution for Spark. However, we’‘re a mixed Mac and Windows environment and iChat on the Mac only supports SSL. And, unfortunately, the iChat Agent connection monitor is unstable, at least in conjunction with the loopback NAT/Firewall rules in our SonicWall firewall, and will disconnect from the Wildfire server randomly from inside the network. Because of that, clients that always stay inside the network (not laptops) use the internal address of the Wildfire server and port 5222 without encryption which is rock solid. If we require client security this will break. And that’‘s our current quandry. For now I guess I’'ll recommend other Windows clients that still support SSL like Psi or Pandion for those that need access through the firewall.
Hi GS,
it looks like the default setting Xmx64m. The wildfire.exe process may use much more than 64 MB with this setting as 64 MB are used for the Java heap. The native heap to control the Java threads and the sandbox itself (just-in-time compiler, garbage collector) uses also some memory.
You’'ll need to create a vmoptions file as described in the documentation to set the Java heap to a higher value, e.g. 128 MB.
LG
Hi,
it should be possible to use a connection manager and bind it to the internal IP address and set:
xmpp.multiplex.tls.policy = (required / optional / disabled)
xmpp.multiplex.compression.policy = (optional / disabled)
LG
src: http://www.jivesoftware.org/community/thread.jspa?messageID=123457