Details
-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
-
Deploy the attached reproduction code reproduce-EAPSUP-105.zip
with the below commandoc new-app --template eap73-basic-s2i -p APPLICATION_NAME=echo -p SOURCE_REPOSITORY_URL=https://<git-repo-for-reproduce-EAPSUP-105.zip> -p CONTEXT_DIR=echo -p SOURCE_REPOSITORY_REF=master
Description
EAP7.3 Container fails to start if the migration from jboss-eap-7/eap72-openshift to eap73-openjdk8-openshift-rhel7 is attempted without re-creating standalone-openshift.xml which is based on included in EAP7.3 container.
$ oc new-app --template eap73-basic-s2i ... $ oc logs -f <pod-name> ... WARN Configuration of an embedded messaging broker within the appserver is enabled but is not recommended. Support for such a configuration will be removed in a future release. WARN If you are not configuring messaging destinations, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true. INFO Configuring the server using embedded server Error applying /tmp/cli-configuration-script-1585617434.cli CLI script. Embedded server started successfully. The Operations were executed but there were unexpected values. See list of errors in /tmp/cli-script-error-1585617434.cli INFO Duration: 5604 milliseconds ERROR An embedded messaging broker is added by default, to disable configuring an embedded messaging broker set the DISABLE_EMBEDDED_JMS_BROKER environment variable to true. Fix your configuration to not contain a default server configured on messaging-activemq subsystem for this to happen.
The standalone-openshift.xml customization includes its in the source code `configuration` directory as below then replaces the standalone-openshift.xml by S2I build.
.
├── configuration
│ └── standalone-openshift.xml <<== customized standalone-openshift.xml
├── pom.xml
└── src
└── main
├── java
├── resources
└── webapp
└── WEB-INF
└── web.xml
The customized standalone-openshift.xml already contains the following embedded broker settings on messaging-activemq subsystem and the <!-- ##MESSAGING_SUBSYSTEM_CONFIG## --> configuration marker is not there.
<subsystem xmlns="urn:jboss:domain:messaging-activemq:4.0"> <server name="default"> <statistics enabled="${wildfly.messaging-activemq.statistics-enabled:${wildfly.statistics-enabled:false}}" /> <journal pool-files="10"/> <security-setting name="#"> <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/> </security-setting> <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10" redistribution-delay="1000"/> <http-connector name="http-connector" socket-binding="http-messaging" endpoint="http-acceptor"/> <http-connector name="http-connector-throughput" socket-binding="http-messaging" endpoint="http-acceptor-throughput"> <param name="batch-delay" value="50"/> </http-connector> <!-- ##AMQ_REMOTE_CONNECTOR## --> <in-vm-connector name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-connector> <http-acceptor name="http-acceptor" http-listener="default"/> <http-acceptor name="http-acceptor-throughput" http-listener="default"> <param name="batch-delay" value="50"/> <param name="direct-deliver" value="false"/> </http-acceptor> <in-vm-acceptor name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-acceptor> <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/> <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/> <connection-factory name="InVmConnectionFactory" connectors="in-vm" entries="java:/ConnectionFactory"/> <connection-factory name="RemoteConnectionFactory" connectors="http-connector" entries="java:jboss/exported/jms/RemoteConnectionFactory" reconnect-attempts="-1" /> <pooled-connection-factory name="activemq-ra" transaction="xa" connectors="in-vm" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory"/> <!-- ##AMQ_POOLED_CONNECTION_FACTORY## --> </server> </subsystem>
This error does not occur in jboss-eap-7/eap72-openshift container even if DISABLE_EMBEDDED_JMS_BROKER=true is not set.
If this issue is not considered as a breaking compatibility bug, in other words,
if we decide this JIRA won't fix, we should be document migration note from 7.2 or earlier to 7.3 to JBoss EAP 7.3 Getting Started with JBoss EAP for OpenShift Container Platform.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- links to
