Skip to main content

KB: PushNotification broken after upgrading to CFix.65CR1.2201

Yesterday I updated a Connections environment to the latest CFix. In other environments I found that PushNotification Cluster was not started after the update, like described in the knowledge base document PushNotification broken after upgrading to CFix.65CR1.2201. In this update the application and cluster were running, but not working at all. Browser console.log showed the error:

Error connecting to push auth sync service /servic/info: RequestError: Unable to load https://cnx-fqdn/push/service/info status: 500

So I tweaked the workaround from the knowledge base document above. I used the find command with the option -exec which is great for running commands on all found files. So we can search and move the files in one step.

  1. On each Application Server Node, go to this directory:
# <WAS_HOME>/profiles/<profile_name>/installedApps/ConnectionsCell/PushNotification.ear
cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/ConnectionsCell/PushNotification.ear
  1. Move files
# Create a backup directory
mkdir ~/backup_pns
# Find and move the files
find -name \*slf4j\*1.7.5\* -exec mv {} ~/backup_pns \;
  1. Restart the PushNotification application or PushNotification Cluster
Note

PushNotification is very important for the Desktop Plugins, so don’t underestimate the importance of this app.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Change the Connections editor on the fly

·256 words·2 mins
When I test topics with the different Connections editors (CKEditor, Textbox.io and TinyMCE), I always used multiple users in my test environment, installed the editor selector ear and then gave each of the test users a different editor. That’s easy with the different j2ee roles, but I always had to use multiple browsers or sandboxes to see them next to each other.