Return to Jive Software

Skip navigation
Up to Discussions in Jive Forums
This discussion is archived
4,071 Views 7 Replies Last post: Aug 9, 2005 7:43 AM by dwhale RSS
britchie Jive Employee
britchie
2,054 posts since
Jun 28, 2001
Currently Being Moderated

Jul 7, 2005 3:35 PM

Jive Knowledge Base 1.6.1 Released

The Jive team is proud to announce that Jive Knowledge Base 1.6.1 is url http://www.jivesoftware.com/downloads.jspavailable[/url]. This release includes a variety of bug fixes and one commonly asked for feature - RSS. The full changelog can be see url http://www.jivesoftware.com/builds/docs/kb/ent/1.6.1/changelog.htmlhere[/url].

mrosker Novice
mrosker
23 posts since
Jan 14, 2005
Currently Being Moderated
Jul 19, 2005 1:56 AM in response to: Bruce Ritchie
Re: Jive Knowledge Base 1.6.1 Released

I have a problem upgrading from 1.5.3 to 1.6.1:

 

1. there is no documentation for this upgrade path. the documentation is still at stage of 1.5.x

 

2. after exchanging the jar file with the new one, the following errors occur:

<pre>

com.opensymphony.xwork.config.ConfigurationException: Error loading configuration file xwork.xml

    with nested exception

com.opensymphony.xwork.config.ConfigurationException: Caught exception while loading file jive-webwork-default.xml

    with nested exception

java.lang.Exception: Could not open file jive-webwork-default.xml

     com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init(XmlConfigurationProvider.java:127)

     com.opensymphony.xwork.config.impl.DefaultConfiguration.reload(DefaultConfiguration.java:85)

     com.opensymphony.xwork.config.ConfigurationManager.getConfiguration(ConfigurationManager.java:56)

     com.opensymphony.xwork.DefaultActionProxyFactory.setupConfigIfActionIsCommand(DefaultActionProxyFactory.java:58)

     com.opensymphony.xwork.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:43)

     com.opensymphony.webwork.dispatcher.ServletDispatcher.serviceAction(ServletDispatcher.java:270)

     com.jivesoftware.base.util.JiveWebWorkServlet.service(JiveWebWorkServlet.java:62)

     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

     com.jivesoftware.util.SetResponseCharacterEncodingFilter.doFilter(SetResponseCharacterEncodingFilter.java:53)

     com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:118)

     com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:52)

     com.jivesoftware.kb.util.EntryViewFilter.doFilter(EntryViewFilter.java:64)

     com.jivesoftware.util.SetRequestCharacterEncodingFilter.doFilter(SetRequestCharacterEncodingFilter.java:48)

</pre>

 

I couldn't find either of the mentioned config files.

 

Please advise.

Regards,

Matthias

britchie Jive Employee
britchie
2,054 posts since
Jun 28, 2001
Currently Being Moderated
Jul 20, 2005 8:45 PM in response to: Matthias Rosker
Re: Jive Knowledge Base 1.6.1 Released

Matthias,

 

Replacing the jar file will not be enough - you should completely replace the webapp as quite a few files have changed outside of the jar file. If you've made any skin customizations you should copy them over to the new files and redeploy those.

 

Normal upgrade procedures for point releases is as follows:

 

1. Backup db. We always recommend this for obvious reasons.

2. On a QA server shut down the app server.

3. On the above QA server replace the webapp - either the war or the exploded war - with the corresponding war or exploded war from the point release. Backup the original.

4. Make sure you run the editWar tool or update the jive_init.xml file if you are using that method to set the location of the jiveHome directory (see documentation for alternatives).

5. If you are putting your db's jdbc jar file in the jivekb webapp copy it over now.

6. If you have made any customizations to jsp files, etc, merge them into corresponding files in the new point release.

7. On some app servers such as Tomcat it's best to clean out the work directory to remove any compiled jsp files as it otherwise sometimes will not detect the file change and use the older - possibly incompatible - compiled jsp.

8.  Startup the QA server and verify functionality.

9. Once verification is complete repeat steps on production server.

 

 

Regards,

 

Bruce Ritchie

mrosker Novice
mrosker
23 posts since
Jan 14, 2005
Currently Being Moderated
Jul 21, 2005 1:16 AM in response to: Bruce Ritchie
Re: Jive Knowledge Base 1.6.1 Released

Bruce,

 

in fact I replaced the WAR, not the JAR and redeployed the application.

This way worked fine for Upgrade from 1.5.1 to 1.5.3.

 

Can you please check this error anyway?

 

Regards,

Matthias

britchie Jive Employee
britchie
2,054 posts since
Jun 28, 2001
Currently Being Moderated
Jul 21, 2005 7:58 AM in response to: Matthias Rosker
Re: Jive Knowledge Base 1.6.1 Released

Matthias,

 

I've just downloaded and deploy 1.6.1 pro, 1.6.1 ent and 1.6.1 pro source and deployed all three on Tomcat without any issues whatsoever. The two files mentioned in the error should be within the jivekb.jar file.

 

Can you confirm that you do not have any old jar files lying around in the classpath that could be causing issues? What application server and version are you testing with?

 

 

Regards,

 

Bruce Ritchie

mrosker Novice
mrosker
23 posts since
Jan 14, 2005
Currently Being Moderated
Jul 21, 2005 8:02 AM in response to: Bruce Ritchie
Re: Jive Knowledge Base 1.6.1 Released

Bruce,

 

I also use Tomcat 5.5.7, and redeployed the complete WAR. I'll try again some time and let you know.

 

Regards,

Matthias

greg Jive Employee
greg
2,660 posts since
Jul 20, 2004
Currently Being Moderated
Jul 28, 2005 5:36 PM in response to: Matthias Rosker
Re: Jive Knowledge Base 1.6.1 Released

Hi Matthias,

 

One other note: Tomcat can be funny about cleaning up its "work" directory (usually in TOMCAT_HOME/work/). Try stopping Tomcat, deleting all of the subdirectories in the work directory and restarting Tomcat. Don't worry, the contents of the work directory will be fully replaced by Tomcat.

 

Regards,

Greg

dwhale Novice
dwhale
75 posts since
Apr 29, 2005
Currently Being Moderated
Aug 9, 2005 7:43 AM in response to: Bruce Ritchie
Re: Jive Knowledge Base 1.6.1 Released

Sorry to butt in on this one, but I've just followed bruce and greg's instructions for upgrading 1.5.3 to 1.6.1 and this does indeed work.

 

I've done a partial upgrade on my staging server (haven't re applied any of my JSP skin modifications yet ), just enough to prove that the document edit bug has been fixed (which it indeed has), as this was my reason for upgrading. The patching process is quite complex and manual to apply my skin patches to the JSP's, so I didn't want to do all this work to find the bug still there.

 

Just a couple of notes for when anyone else who needs to do this upgrade, as there are a couple of gotcha's that I fell right into.

 

1) I followed the instructions from bruce and greg to the letter and they worked. Anything else just doesn't work!

 

2) don't get fooled by the upgrade-instructions.html in the distribution - if you have 1.5.3 you don't have to do the database upgrade. This wasn't that clear and I tried the upgrade and it failed - silly me, I should have looked at the version numbers more closely. The tables inserted and modified by the upgrade script are not needed for 1.5.3 as they are already there.

 

3) I have a custom user manager installed, and in order to do a quick "smoke test" of the new release, I just deleted the jiveProperty/userManager.className and jiveProperty.authFactory.className rows in the database as a temporary fix, so that I didn't get class load errors on startup.

 

4) On my first attempt, I tried to login to the admin interface and it wouldn't accept my standard admin user password. I investigated in the tomcat logs and kbServlet had throwed a servlet load error exceptionInInitializer and was whinging about the tangosol cache coherence couldn't find a valid licence key.

 

At this time, I thought "time to contact jive", but surfed the forums and found this thread. That's when I realised that I didn't drop my mysql.jar driver into the jivekb.war file, so that's why login was failing (and I suspect also why tangosol couldn't find its licence).

 

So, to summarise my steps:

- backup the database

- get the jivekb.war and unzip it

- modified jive_init.xml to set jiveHome variable

- added mysql.jar into WEB-INF/lib

- rezipped to a war

- stopped tomcat service

- deleted the tomcat/work/jivekb folder

- replaced jivekb.war in work/manager

- restarted tomcat

- logged in to admin interface and it worked.

 

Hope this helps,

 

David Whale.

More Like This

  • Retrieving data ...

Bookmarked By (0)

To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.