Rhythmyx 6.7 Upgrade Experiences

Rhythmyx
1

This thread is meant to serve as a repository for users to post their experiences upgrading to Rx 6.7 from various other versions of the product. Please feel free to post thoughts, suggestions, or even questions about upgrading to Rx 6.7 if you have any.

2

We have upgraded from 6.5 to 6.6 and then 6.7 and there were no major issues. We had a few problems upgrading our Dev environment to 6.7 (installation process would not finish), but no issues upgrading the production environment to 6.7.

If you are using PSOToolkit, be aware that “PSOAncestorFolderSlotContentFinder” does not work. Also I just noticed that publishing the absolute URL using siteBase is not working correctly (that might be an issue with the Context Variables for our site though)

3

We have upgraded from 6.5 to 6.7 with no major issues. We had a couple of issues during first phase testing on development regarding content lists, however that issue was fixed with the latest patch.

4

We’re in the process of upgrading to 6.7 at the moment, and have patch: 15949
installed.

We’ve noticed an issue when publishing an incremental edition which can contain a large number of items (>4000)
Whilst in the Current state: “Queueing content”, users are locked out of the content explorer.

Is this intentional or is this a bug?

5

Hi all.

We have upgraded from 6.5.2 to 6.7 and we cannot start the server.

As far as I can see in the ‘server.log’ we’re meeting the following errors:

  1. ERROR [org.jboss.deployment.MainDeployer] Could not create deployment: file:/C:/Rhythmyx/AppServer/server/rx/deploy/rx-ds.xml
    org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=jdbc/RhythmyxData

  2. ERROR [com.percussion.servlets.PSAppServlet] Unexpected error during initialization: Error creating bean with name ‘sys_quartzScheduler’ defined in ServletContext resource [/WEB-INF/config/spring/beans.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn’t clean volatile data: Invalid object name ‘rhythmyx.dbo.PSX_QTRIGGERS’. [See nested exception: java.sql.SQLException: Invalid object name ‘rhythmyx.dbo.PSX_QTRIGGERS’.]]
    org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘sys_quartzScheduler’ defined in ServletContext resource [/WEB-INF/config/spring/beans.xml]: Invocation of init method failed; nested exception is org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Couldn’t clean volatile data: Invalid object name ‘rhythmyx.dbo.PSX_QTRIGGERS’. [See nested exception: java.sql.SQLException: Invalid object name ‘rhythmyx.dbo.PSX_QTRIGGERS’.]]

  3. ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

— Incompletely deployed packages —
org.jboss.deployment.DeploymentInfo@7b04c00b { url=file:/C:/Rhythmyx/AppServer/server/rx/deploy/rx-ds.xml }
deployer: org.jboss.deployment.XSLSubDeployer@2d0483
status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=jdbc/RhythmyxData
state: FAILED
watch: file:/C:/Rhythmyx/AppServer/server/rx/deploy/rx-ds.xml
altDD: null
lastDeployed: 1261409265265
lastModified: 1261409265234
mbeans:

…soon after the error #3 the system is shutting down…

  • INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-9991
  • INFO [org.jboss.system.server.Server] LifeThread.run exits!
  • INFO [org.jboss.system.server.Server] Shutting down the JVM now!
    2009-12-21 15:28:29,984 INFO [org.jboss.system.server.Server] Runtime shutdown hook called, forceHalt: true
  • INFO [org.jboss.system.server.Server] JBoss SHUTDOWN: Undeploying all packages
  1. ERROR [org.apache.tomcat.util.net.PoolTcpEndpoint] Socket error caused by remote host /172.17.0.110
    java.net.SocketException: Connection reset

Any clues about what’s going on?
I’m not an expert but I’ve always managed environment cloning & change of settings…

Thanks in advance.

6

Just a guess here which could be way off but I’d have a look at the rx-ds.xml file and see if there are multiple “local-tx-datasource” entries with the same name (jdbc/RhythmyxData). It could just be as simple as removing any duplicates…

7

Happy new year everyone.

Unfortunately I have only one “local-tx-datasource” in the rx-ds.xml file, and the system worked correctly using it before the upgrade.

It’s pretty weird what’s happening…

8

After upgrading we can no longer authenticate to our ldap server. The error in the console log mentioned a simple bind exception so we thought we might need to re-import our certificates into the keystore. We found two cacerts files in the /cms/Rhythmyx/JRE/lib/security folder, one was identical to our production system with a .6 appended to the file name, the other was much larger and seemed to be added during the upgrade so we backed up the certs and replaced them with the copy from production. After replacing the cacerts and restarting the server we are getting a generic ldap exception during authentication, “invalid credentials”.

Was there anything changed during the upgrade related to ldap authentication? I think I remember reading a detailed summary of changes somewhere but I can’t find it anywhere since.

9

Stephen,

Please contact Tech Support for assistance with your issue.

RLJII

10

After upgrading the Rhythmyx server to version 6.7 the Ephox editor does not work when editing a page (screenshot: noEphox.gif). I checked our configuration file but it doesn’t appear to have been overwritten as I thought it would have during the upgrade. When I attempt to edit the text field that is normally managed by the Ephox editor, all of the text is removed when the changes are submitted. I traced the page using httpfox and it appears that all of the normal calls are being made to the Ephox editor.

Thanks,

Steve

11

I am testing Active Assembly in 6.7 and many of my content types receive the error message:

ERROR [PSAssemblyServlet] Problem assembling item (3541): Couldn’t break page into sections for AA

Any ideas?

12

We experienced a series of “JDBC connection closed” error during the publishing of an edition on upgarded 6.7. The same edition on 6.5.2 runs fine without any problem. The error occurred in the middle of the publishing. Once it occurred on one item, all subsequent items failed due to the same “connection closed” error.

2010-07-23 18:28:08,830 ERROR [PSPublishHandler] 1-101-39649
org.hibernate.InstantiationException: Could not instantiate entity: com.percussion.services.filter.data.PSItemFilterRuleDef

Caused by: org.springframework.transaction.TransactionSystemException: Could not commit Hibernate transaction; nested exception is org.hibernate.TransactionException: JDBC commit failed

Caused by: org.hibernate.TransactionException: JDBC commit failed

Caused by: java.sql.SQLException: Invalid state, the Connection object is closed.
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.checkOpen(ConnectionJDBC2.java:1634)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.setAutoCommit(ConnectionJDBC2.java:2139)
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:362)
at org.jboss.resource.adapter.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:514)
at org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:330)
at org.hibernate.transaction.JDBCTransaction.commitAndResetAutoCommit(JDBCTransaction.java:139)
at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:115)
… 72 more