Discussion on:

5
Comments

Join the conversation!

Follow via:
RSS
Email Alert
0 Votes
+ -
Not sure if openfire has come along farther then they where. But, years ago I tried to set up openfire with Active Directory and had tons of problems and the forums where horrible for help. Not sure if it any better these days? I will give it a try again and see what happens.
"...what if you could have an internal-only chat server that would allow for faster communication and better collaboration?"

What if we could? My limited experience hasn't shown me the value of this tool in the workplace, even though we've been running MS Communicator in limited deployment for a couple of years I still don't know the advantages of chat over telephone or e-mail, or under what circumstances it would be the tool of choice. It just seems slower to me to type than speak in urgent situations, and clumsier to edit and use than e-mail in cases where a response isn't time-sensitive.
In the Fall 2011 I set up an internal Openfire server to replace an old jabber server. Things went smoothly until the server reached an uptime of about two weeks. By this point JVM memory usage reached very high levels and once the Openfire daemon's uptime reached about sixteen days the thing freaked out (corrupting an Openfire database table in the process).

Anyone looking to set up Openfire should watch JVM memory usage (on the main dashboard when you log into the web UI) and consider disabling PEP if memory usage gets high. Since I disabled PEP (a feature we didn't use) memory usage is mighty low now and even recedes from time to time.
From Openfire's site:

Openfire up to and including version 3.6.4 (and looks like 3.7.0 too) suffers from a memory leak in its PEP component. If your Openfire server is crashing with OutOfMemoryExceptions, you might be having this problem.

As a workaround, you can disable PEP, by setting the Openfire property xmpp.pep.enabled to false.


Using HTTP _clear text_ is a thing of the past when any web server has HTTPS enabled! Openfire Web UI with SSL ... https://ADDRESS_TO_SERVER:9091/

My upgrade from Openfire 3.7.0 to 3.7.1 went smoothly as well.

Shared rosters are awesome to push out new employees the existing list and to add new employees to everyone else's list! There's quite a nice feature list that Jack hardly touched on (he'd have quite a few pages if he did). Java or not, Openfire is a nice xmpp/jabber daemon.
0 Votes
+ -
I get 404 errors
I have successfully configure openfire for local chat, now I want to configure openfire with WAN how to achieve this ?

1. How to achieve if I am having static ip address.
2. How to achieve if I am not having static ip address.

Kindly take in count that I have enabled port forwarding (from router) for port 9090, 9091, 5223, 5223 and 5229 to my server's internal LAN ip address. Though I can't able to connect to openfire from external IP or static ip.

Please help
Keyboard Shortcuts:
Prev
Next
Toggle
Join the conversation
Formatting +
BB Codes - Note: HTML is not supported in forums
  • [b] Bold [/b]
  • [i] Italic [/i]
  • [u] Underline [/u]
  • [s] Strikethrough [/s]
  • [q] "Quote" [/q]
  • [ol][*] 1. Ordered List [/ol]
  • [ul][*] · Unordered List [/ul]
  • [pre] Preformat [/pre]
  • [quote] "Blockquote" [/quote]

Join the TechRepublic Community and join the conversation! Signing-up is free and quick, Do it now, we want to hear your opinion.