Hey all,
Since we’‘re getting quite close to the official 2.1.0 beta, I’'m going to start publishing Windows (exe) builds in the nightly builds area. We hope this makes it easier for people to test out the lastest stuff and to provide feedback. The builds use the new installer, which supports deploying as a Windows service.
http://www.jivesoftware.org/nightly.jsp
Regards,
Matt
Is the following error okay: “This executable was created with an evaluation version of install4j”
Also, would this evaluation cause the service to stop without any errors?
Is the following error okay: "This executable was
created with an evaluation version of install4j"
You’‘re using a slightly older binary build. If you try out the latest, it shouldn’'t have that message.
Also, would this evaluation cause the service to stop
without any errors?
Yep – the service stopped after 30 mins since it was an eval version of the installer. That should now be resolved too.
Regards,
Matt
Yo!
I had 2.0.1 installed in a D:\Program Files\ subdirectory. I shut that off and installed the most recent windows build to D:\Program Files\JiveBETA.
It installed fine and I picked service also. I restarted the machine just cause I like to do that heh.
Anyway, i see the MESSEN~1.EXE service there.
I try to use the Admin and it’'s bringing up a blank screen on the loopback:9090 html.
This is a windows 2003 box.
I miss something? Sorry if i did
Can you check to see if the service is started?
Regards,
Matt
Newer build fixed the problem, now if only Group edit would function…
Newer build fixed the problem, now if only Group edit
would function…
Trying to get that in today.
-Matt
Another thing I noticed is that you have to stop the java process in order for the install to compete without error. I found the installation gets stuck at copying a few DLL’'s unless you kill the java process in task manager.
Another thing I noticed is that you have to stop the
java process in order for the install to compete
without error. I found the installation gets stuck
at copying a few DLL’'s unless you kill the java
process in task manager.
We haven’'t seen that issue before. What version of Windows are you using? Can you reproduce the issue or does it only happen once?
Regards,
Matt
Windows 2003 Standard Server
This happened with both 2.1 beta executables I installed. Each time there was a java process running that I had to kill. The process would start up again after a few seconds or two. Let me see what application the process is attached to.
Looks like the wrapper is whats running the java process. Even after stopping the Jive service, and making sure the jive console is closed, the wrapper is still running…
from matt
Can you check to see if the service is started?
Yes, jive messenger shows as Started.
Ok,
I went from OUTSIDE the box…
and did an http://myip:9090/login.jsp and the settings came up… however i started on the server with messengerd.exe instead… maybe something funked in the service?
Got some other weird errors… think I’'ll look at this more before posting any rants. Thanx!
One more since i got 3 in a row!
Can you install these builds OVER current installs or do they need to be fresh subdirectory installs? Thanx!
One more since i got 3 in a row!
Can you install these builds OVER current installs or
do they need to be fresh subdirectory installs?
Thanx!
Not tested installing over 2.0.1, but you can install new nightly builds over old ones.
-Matt
I installed the most current build over my exisitng installation (I’‘m using MySQL as the backend). Seems to work fine, however it does require to run through the setup again (this doesn’'t seem to affect the DB). Other than the problems with the earlier build, it seems to function just fine on my server.
FYI…I just installed over the top of my old one… 2.0.1
Can you install these builds OVER current installs or
do they need to be fresh subdirectory installs?
Not tested installing over 2.0.1, but you can install new >nightly builds over old ones.
-Matt
users are still there… new features appear there… I’'ll play around a little more heh
users are still there… new features appear there… I’'ll >>play around a little more heh
Some problems in the chat room create… some errors about room already existing and then…
org.jivesoftware.messenger.muc.ConflictException
at org.jivesoftware.messenger.muc.spi.IQOwnerHandler.processConfigurationForm(IQOw nerHandler.java:358)
at org.jivesoftware.messenger.muc.spi.IQOwnerHandler.handleDataFormElement(IQOwner Handler.java:308)
at org.jivesoftware.messenger.muc.spi.IQOwnerHandler.handleIQ(IQOwnerHandler.java: 87)
at org.jivesoftware.messenger.admin.muc_002droom_002dedit_002dform_jsp._jspService (muc_002droom_002dedit_002dform_jsp.java:252)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:427)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:816)
at org.jivesoftware.util.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingF ilter.java:41)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:807)
at org.jivesoftware.admin.AuthCheckFilter.doFilter(AuthCheckFilter.java:76)
at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplica tionHandler.java:807)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler. java:488)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:569)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.ja va:624)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1434)
at org.mortbay.http.HttpServer.service(HttpServer.java:896)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:366)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
wheee?
users are still there… new features appear
there… I’'ll >>play around a little more heh
Some problems in the chat room create… some errors
about room already existing and then…
org.jivesoftware.messenger.muc.ConflictException
at
t
Did you upgrade your database? Database upgrade scripts are now in CVS. Otherwise, we’'d recommend using a fresh database for now.
We’'re hoping to integrate a database upgrade process into the setup wizard for the final release.
Regards,
Matt