Wildfire can''t work with Oracle 9i

I’'m using Wildfire 3.0.1 in Win2000 server and Oracle 9i Database

I use wildfire_oracle.sql to create table in Oracle

In “Wildfire Setup”, when I reset admin New Password,it show message

“There were errors when updating the admin account. Please see below.”

“There was an unexpected error encountered when setting the new admin information. Please check your error logs and try to remedy the problem.”


“Could not find UserManager”

there are nothing in error.log


the JIVEUSER table is a very simple table so I wonder what should go wrong there.

“UserManager” is a Wildfire class so I wonder why it should not be found. Does this work with the embedded database?

Do you see errors in Oracles alert.log?


O, why???

It is ok on my pc.

but this problem occur at the server,this server run WebLogic 8.1,Oracle 9i and a Workflow Engine, I don’’ know whether this affect the wildfire

i got exactly the same a while ago. problem was the update sql script not doing a commit after it was run, so ran successfully and then forgot all the data.

this was on an older version of Wildfire, so don’'t know if its been fixed or you still need to do a manual commit???

maybe worth a go. error message was identical.


2006.09.30 16:55:56 [org.jivesoftware.wildfire.filetransfer.ProxyConnectionManager$1.run(ProxyConne ctionManager.java:89)

] Error creating server socket

java.net.BindException: Address already in use: JVM_Bind

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(Unknown Source)

at java.net.ServerSocket.bind(Unknown Source)

at java.net.ServerSocket.(Unknown Source)

at org.jivesoftware.wildfire.filetransfer.ProxyConnectionManager$1.run(ProxyConnec tionManager.java:86)

at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)

at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

at java.util.concurrent.FutureTask.run(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

Maybe some port is already in use


as Oracles web server likes port 7777 a lot this may be indeed the case. You can change the file transfer port or disable the service completely on http://localhost:9090/file-transfer-proxy.jsp .