Exported File has different value in jms:enable-message-persistence, jms:jndi-timeout, and jms:expiration with email alert action. (Doc ID 2722593.1)

Last updated on OCTOBER 24, 2020

Applies to:

Symptoms

When the application contains Email Alert, by export and import the project, some element value has changed.

before

<tran:provider-specific xsi:type="jms:JmsEndPointConfiguration" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Bytes</jms:message-type>
<jms:enable-message-persistence>false</jms:enable-message-persistence>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
<jms:jndi-timeout>0</jms:jndi-timeout>
</tran:provider-specific>

after

<tran:provider-specific xsi:type="jms:JmsEndPointConfiguration" xmlns:jms="http://www.bea.com/wli/sb/transports/jms">
<jms:is-queue>true</jms:is-queue>
<jms:is-secure>false</jms:is-secure>
<jms:outbound-properties>
<jms:message-type>Bytes</jms:message-type>
<jms:expiration>0</jms:expiration>
<jms:pass-caller-subject>false</jms:pass-caller-subject>
</jms:outbound-properties>
<jms:request-encoding>UTF-8</jms:request-encoding>
</tran:provider-specific>

1. <jms:enable-message-persistence>false</jms:enable-message-persistence> was gone after export/import.
2. <jms:jndi-timeout>0</jms:jndi-timeout> is gone after export/import
3. <jms:expiration>0</jms:expiration> is added after export/import

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.