powered by Jive Software

Wildfire 3.2.3 disabling STUN service errors

Errors are below. So i see STUN is launching on startup and then Wildifre tries to disable it. But i dont need STUN, neither Media Proxy, File Transfer service, Server-to-Server, HTTP Binding. So i have disabled all these. And i thought they are not bugging my server while it’‘s launching. Couldnt it be done this way? What’'s disabled - that never even launches at startup.

2007.03.20 10:21:45 org.jivesoftware.wildfire.stun.STUNService.startServer(STUNService.java:136) Disabling STUN server

java.net.BindException: Address already in use

at java.net.PlainDatagramSocketImpl.bind0(Native Method)

at java.net.PlainDatagramSocketImpl.bind(PlainDatagramSocketImpl.java:82)

at java.net.DatagramSocket.bind(DatagramSocket.java:368)

at java.net.DatagramSocket.(XMPPServer.java:148)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessor Impl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructor AccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

at java.lang.Class.newInstance0(Class.java:355)

at java.lang.Class.newInstance(Class.java:308)

at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.java:93)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.java:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.install4j.runtime.Launcher.main(Unknown Source)


P.S. not related probably, warn.log is always filled with

2007.03.19 16:09:17 Could not route packet

2007.03.20 10:21:57 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.

2007.03.20 10:21:57 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.