BrXM v16 not deployable in Bloomreach Cloud

Experience Manager (PaaS/OnPrem)
1

We have successfully upgraded our BrXM implementation from version 15.x to 16.0. The upgraded BrXM v16.0 is running smoothly in our local environment. However, we are experiencing issues with deploying it to the Bloomreach Cloud; the deployment process stalls, and we see errors in the log.

According to the documentation, Bloomreach Cloud was supposed to support BrXM v16 starting from July 12th. (https://xmdocumentation.bloomreach.com/about/release-notes/16/16.0.0-release-notes.html). Can someone please confirm if this upgrade has been completed? Additionally, how can I check which version of the Bloomreach Cloud platform (Mission Control) is currently running?

2

Hi,

I suggest you make contact with support, but all stacks should be upgraded by this point. I can say little about your case without looking into your specific issues.

3

Thanks Jasper. I’ve created a support ticket.

4

The deployment issue has been resolved. It was caused by skipping a step in the upgrade process: Migrate From Sun Mail to Eclipse Angus Mail - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS.

We initially skipped this step because we didn’t have the old includes that needed to be replaced. However, after adding the new includes, we were able to successfully deploy the distribution on Bloomreach Cloud.

Thanks to the support team (Marijan Milicevic) for pointing this out.

5

Hi hcu,

Thanks for your update. Want to clarify a bit here so that we can improve the documentation.
You added:

<include>jakarta.activation:jakarta.activation-api</include>
<include>jakarta.mail:jakarta.mail-api</include>
<include>org.eclipse.angus:angus-activation</include>
<include>org.eclipse.angus:angus-mail</include>

and that resolved your issue. However, you didn’t initially add them because you did not have

<include>com.sun.activation:jakarta.activation</include>
<include>com.sun.mail:jakarta.mail</include>

in the project beforehand.

Could you please let me know if that’s correct? We can update some of the language is so.

6

Hi Nicholas,

Here is the original /src/main/assembly/common-lib-component.xml we had prior to the upgrade:

<component xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/component/1.1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/component/1.1.2 http://maven.apache.org/xsd/component-1.1.2.xsd">
  <dependencySets>
    <dependencySet>
      <useProjectArtifact>false</useProjectArtifact>
      <outputDirectory>common/lib</outputDirectory>
      <scope>provided</scope>
      <includes>
        <include>javax.jcr:jcr</include>
        <include>org.apache.geronimo.specs:geronimo-jta_1.1_spec</include>
        <include>javax.mail:mail</include>
      </includes>
    </dependencySet>
  </dependencySets>
</component>

We updated the javax.mail dependency to use the jakarta.mail namespace, specifically changing:

<include>javax.mail:mail</include>

to:

<include>jakarta.mail:mail</include>

However, this change led to deployment issues on Bloomreach Cloud. To resolve the issue, we replaced that line with the four new includes, like so:

<component xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/component/1.1.2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
           xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/component/1.1.2 http://maven.apache.org/xsd/component-1.1.2.xsd">
  <dependencySets>
    <dependencySet>
      <useProjectArtifact>false</useProjectArtifact>
      <outputDirectory>common/lib</outputDirectory>
      <scope>provided</scope>
      <includes>
        <include>javax.jcr:jcr</include>
        <include>org.apache.geronimo.specs:geronimo-jta_1.1_spec</include>
        <!-- <include>jakarta.mail:mail</include> -->
        <include>jakarta.activation:jakarta.activation-api</include>
        <include>jakarta.mail:jakarta.mail-api</include>
        <include>org.eclipse.angus:angus-activation</include>
        <include>org.eclipse.angus:angus-mail</include>
      </includes>
    </dependencySet>
  </dependencySets>
</component>
7

Thanks so much for your update! We’ll make the documentation clearer for others.

1 Like