[JBoss JIRA] (DROOLS-5652) String relational comparison fails with executable-model
by Toshiya Kobayashi (Jira)
Toshiya Kobayashi created DROOLS-5652:
-----------------------------------------
Summary: String relational comparison fails with executable-model
Key: DROOLS-5652
URL: https://issues.redhat.com/browse/DROOLS-5652
Project: Drools
Issue Type: Bug
Components: executable model
Affects Versions: 7.43.1.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
String relational comparison fails with executable-modelString relational comparison fails with executable-model
{noformat}Person( name >= "Bob" )\{noformat}
generates Predicate like this:
{code:java}@org.drools.compiler.kie.builder.MaterializedLambda()public enum LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B implements org.drools.model.functions.Predicate1<org.drools.modelcompiler.domain.Person> \{ ... @Override() public boolean test(org.drools.modelcompiler.domain.Person _this) throws java.lang.Exception { return org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(_this.getName(), "Bob"); }}\{code}
then, fails with this error:
{noformat}[ERROR] testStringComparison[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 2.563 s <<< ERROR!java.lang.RuntimeException: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark. at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95) at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:133) at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:136) ...Caused by: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark. at java.base/java.math.BigDecimal.<init>(BigDecimal.java:518) at java.base/java.math.BigDecimal.<init>(BigDecimal.java:401) at java.base/java.math.BigDecimal.<init>(BigDecimal.java:834) at org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(EvaluationUtil.java:113) at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:17) at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:8) at org.drools.model.functions.Predicate1$Impl.test(Predicate1.java:39) at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:92) ... 48 more\{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (DROOLS-5652) String relational comparison fails with executable-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5652?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5652:
--------------------------------------
Description:
String relational comparison fails with executable-model
{noformat}
Person( name >= "Bob" )
{noformat}
generates Predicate like this:
{code:java}
@org.drools.compiler.kie.builder.MaterializedLambda()
public enum LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B implements org.drools.model.functions.Predicate1<org.drools.modelcompiler.domain.Person> {
...
@Override()
public boolean test(org.drools.modelcompiler.domain.Person _this) throws java.lang.Exception {
return org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(_this.getName(), "Bob");
}
}
{code}
then, fails with this error:
{noformat}
[ERROR] testStringComparison[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 2.563 s <<< ERROR!
java.lang.RuntimeException: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:133)
at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:136)
...
Caused by: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
at java.base/java.math.BigDecimal.<init>(BigDecimal.java:518)
at java.base/java.math.BigDecimal.<init>(BigDecimal.java:401)
at java.base/java.math.BigDecimal.<init>(BigDecimal.java:834)
at org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(EvaluationUtil.java:113)
at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:17)
at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:8)
at org.drools.model.functions.Predicate1$Impl.test(Predicate1.java:39)
at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:92)
... 48 more
{noformat}
was:
String relational comparison fails with executable-modelString relational comparison fails with executable-model
{noformat}Person( name >= "Bob" )\{noformat}
generates Predicate like this:
{code:java}@org.drools.compiler.kie.builder.MaterializedLambda()public enum LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B implements org.drools.model.functions.Predicate1<org.drools.modelcompiler.domain.Person> \{ ... @Override() public boolean test(org.drools.modelcompiler.domain.Person _this) throws java.lang.Exception { return org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(_this.getName(), "Bob"); }}\{code}
then, fails with this error:
{noformat}[ERROR] testStringComparison[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 2.563 s <<< ERROR!java.lang.RuntimeException: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark. at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95) at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:133) at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:136) ...Caused by: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark. at java.base/java.math.BigDecimal.<init>(BigDecimal.java:518) at java.base/java.math.BigDecimal.<init>(BigDecimal.java:401) at java.base/java.math.BigDecimal.<init>(BigDecimal.java:834) at org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(EvaluationUtil.java:113) at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:17) at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:8) at org.drools.model.functions.Predicate1$Impl.test(Predicate1.java:39) at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:92) ... 48 more\{noformat}
> String relational comparison fails with executable-model
> --------------------------------------------------------
>
> Key: DROOLS-5652
> URL: https://issues.redhat.com/browse/DROOLS-5652
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.43.1.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> String relational comparison fails with executable-model
> {noformat}
> Person( name >= "Bob" )
> {noformat}
> generates Predicate like this:
> {code:java}
> @org.drools.compiler.kie.builder.MaterializedLambda()
> public enum LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B implements org.drools.model.functions.Predicate1<org.drools.modelcompiler.domain.Person> {
> ...
> @Override()
> public boolean test(org.drools.modelcompiler.domain.Person _this) throws java.lang.Exception {
> return org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(_this.getName(), "Bob");
> }
> }
> {code}
> then, fails with this error:
> {noformat}
> [ERROR] testStringComparison[PATTERN_DSL](org.drools.modelcompiler.CompilerTest) Time elapsed: 2.563 s <<< ERROR!
> java.lang.RuntimeException: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
> at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:95)
> at org.drools.modelcompiler.constraints.LambdaConstraint.isAllowed(LambdaConstraint.java:133)
> at org.drools.core.reteoo.AlphaNode.assertObject(AlphaNode.java:136)
> ...
> Caused by: java.lang.NumberFormatException: Character J is neither a decimal digit number, decimal point, nor "e" notation exponential mark.
> at java.base/java.math.BigDecimal.<init>(BigDecimal.java:518)
> at java.base/java.math.BigDecimal.<init>(BigDecimal.java:401)
> at java.base/java.math.BigDecimal.<init>(BigDecimal.java:834)
> at org.drools.modelcompiler.util.EvaluationUtil.greaterThanStringsAsNumbers(EvaluationUtil.java:113)
> at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:17)
> at defaultpkg.P3B.LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.test(LambdaPredicate3B9CCAE898D00108D2F033D685F4C75B.java:8)
> at org.drools.model.functions.Predicate1$Impl.test(Predicate1.java:39)
> at org.drools.modelcompiler.constraints.ConstraintEvaluator.evaluate(ConstraintEvaluator.java:92)
> ... 48 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13871) Re-implement correct suspend/resume behaviour for EJB client
by Joerg Baesner (Jira)
[ https://issues.redhat.com/browse/WFLY-13871?page=com.atlassian.jira.plugi... ]
Joerg Baesner commented on WFLY-13871:
--------------------------------------
[~rachmato] unfortunately this updated PR will lead to a client that is in a a hanging state, not processing any further requests...
> Re-implement correct suspend/resume behaviour for EJB client
> ------------------------------------------------------------
>
> Key: WFLY-13871
> URL: https://issues.redhat.com/browse/WFLY-13871
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 21.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> When a server is suspended, in order to avoid receipt of invocations which will never be correctly processed, all connected clients should be notified that all modules on that server are now unavailable; when the server is resumed, all connected clients should be notified that all modules on that server are now again available so that the server may again take part in processing invocations.
> This behaviour was present in versions of EAP before EAP 7.1 but was not ported over to the new EJB client server-side classes which were substantially refactored.
> This issue will re-instante that behaviour. The two cases of standalone and clustered deployments should be considered.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13882) StartException with "AMQ229204: Address already exists" on existing multicast queue creation
by Chao Wang (Jira)
Chao Wang created WFLY-13882:
--------------------------------
Summary: StartException with "AMQ229204: Address already exists" on existing multicast queue creation
Key: WFLY-13882
URL: https://issues.redhat.com/browse/WFLY-13882
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 21.0.0.Beta1
Reporter: Chao Wang
Assignee: Emmanuel Hugonnet
# configure a MDB with jms topic to read message from a remote artemis server.
# trigger a server reload to recreate multicast queue on the remote artemis server.
{code:java}
11:13:49,627 ERROR [org.wildfly.extension.messaging-activemq] (Thread-0 (ActiveMQ-client-global-threads)) Creating topic jms.topic.testTopic on node UP {"name":"b5f8a47b-f95c-11ea-8a99-b4d5bdef5ecf","factoryClassName":"org.apache.activemq.artemis.core.remoting.impl.netty.NettyConnectorFactory","params":{"port":"61616","localAddress":"127.0.0.1","host":"localhost"},"extraProps":{}} failed: org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0099: Creating the remote destination jms.topic.testTopic failed with error ["AMQ229204: Address already exists: jms.topic.testTopic"]
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.DestinationConfiguration.createTopic(DestinationConfiguration.java:147)
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.ExternalJMSTopicService$1.nodeUP(ExternalJMSTopicService.java:92)
at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.client.impl.Topology$3.run(Topology.java:371)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
11:13:49,628 WARN [org.apache.activemq.artemis.utils.actors.OrderedExecutor] (Thread-0 (ActiveMQ-client-global-threads)) org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0099: Creating the remote destination jms.topic.testTopic failed with error ["AMQ229204: Address already exists: jms.topic.testTopic"]: java.lang.RuntimeException: org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0099: Creating the remote destination jms.topic.testTopic failed with error ["AMQ229204: Address already exists: jms.topic.testTopic"]
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.ExternalJMSTopicService$1.nodeUP(ExternalJMSTopicService.java:95)
at org.apache.activemq.artemis@2.10.1//org.apache.activemq.artemis.core.client.impl.Topology$3.run(Topology.java:371)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:42)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.OrderedExecutor.doTask(OrderedExecutor.java:31)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.actors.ProcessorBase.executePendingTasks(ProcessorBase.java:66)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at org.apache.activemq.artemis.journal//org.apache.activemq.artemis.utils.ActiveMQThreadFactory$1.run(ActiveMQThreadFactory.java:118)
Caused by: org.jboss.msc.service.StartException in anonymous service: WFLYMSGAMQ0099: Creating the remote destination jms.topic.testTopic failed with error ["AMQ229204: Address already exists: jms.topic.testTopic"]
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.DestinationConfiguration.createTopic(DestinationConfiguration.java:147)
at org.wildfly.extension.messaging-activemq//org.wildfly.extension.messaging.activemq.jms.ExternalJMSTopicService$1.nodeUP(ExternalJMSTopicService.java:92)
... 7 more
{code}
This happens because WFLY-13581 changed the invocation name from {{createQueue}} to {{createAddress}}, the reply body includes
{code:xml}
["AMQ229204: Address already exists: jms.topic.testTopic"]{code}
which is not being checked in the {{destinationAlreadyExist}} method
{code:java}
private boolean destinationAlreadyExist(String body) {
return body.contains("AMQ119019") || body.contains("AMQ119018") || body.contains("AMQ229019") || body.contains("AMQ229018");
}
{code}
Based on https://github.com/apache/activemq-artemis/blob/master/artemis-server/src..., including the extra {{AMQ229204}} would fix this.
Also, I am not sure about Artemis 1.x series as there is no such {{createAddress}} invocation in Artemis 1.x.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFCORE-5055) Complete the support for capabilities for the remaining Remoting resources
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFCORE-5055?page=com.atlassian.jira.plug... ]
Brian Stansberry commented on WFCORE-5055:
------------------------------------------
Note that WFCORE-5107 dealt with org.wildfly.remoting.connector. WFLY-13813 is about taking advantage of that in EJB.
> Complete the support for capabilities for the remaining Remoting resources
> --------------------------------------------------------------------------
>
> Key: WFCORE-5055
> URL: https://issues.redhat.com/browse/WFCORE-5055
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Remoting
> Affects Versions: 13.0.0.Beta1
> Reporter: Richard Achmatowicz
> Assignee: Flavia Rainone
> Priority: Major
>
> There are some Remoting resources which still use legacy service name generation for installing services (e.g. Connector) which means that any subsystems which depend on these resources cannot establish capability references to the capabilities they depend on.
> For example:
> {noformat}
> /** The name of the remoting service */
> public static final ServiceName REMOTING_BASE = ServiceName.JBOSS.append("remoting");
> /** The name of the endpoint service installed by the remoting subsystem. */
> public static final ServiceName SUBSYSTEM_ENDPOINT = REMOTING_ENDPOINT_CAPABILITY.getCapabilityServiceName(Endpoint.class);//REMOTING_BASE.append("endpoint", "subsystem");
> /** The base name of the connector services */
> private static final ServiceName CONNECTOR_BASE = REMOTING_BASE.append("connector");
> /** The base name of the stream server services */
> private static final ServiceName SERVER_BASE = REMOTING_BASE.append("server");
> public static final ServiceName HTTP_LISTENER_REGISTRY = HTTP_LISTENER_REGISTRY_CAPABILITY.getCapabilityServiceName(ListenerRegistry.class);{noformat}
> It would be nice to provide capability-based installation for connector and stream services as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFLY-13881) Clean up diffs between the dist-legacy and ee-dist output
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-13881:
---------------------------------------
Summary: Clean up diffs between the dist-legacy and ee-dist output
Key: WFLY-13881
URL: https://issues.redhat.com/browse/WFLY-13881
Project: WildFly
Issue Type: Task
Components: Build System, Clustering, Mail
Reporter: Brian Stansberry
Assignee: Paul Ferraro
The placement of the 'pending-puts' cache differs between the Galleon and legacy dists.
The legacy version of the mail-smtp outbound socket binding config is also missing updates made to the Galleon config.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (WFWIP-357) No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template
by Jan Blizňák (Jira)
[ https://issues.redhat.com/browse/WFWIP-357?page=com.atlassian.jira.plugin... ]
Jan Blizňák updated WFWIP-357:
------------------------------
Steps to Reproduce:
Analysis provides this information:
{code:java}
Test EAP S2I image changes
- Import a more recent version of EAP S2I images (test should be done for both the builder and runtime images referenced by the imagestreams)
{code}
However, in current template configuration there is no trigger upon EAP_RUNTIME_IMAGE imagestream change.
This is obvious why it doesn't happen when we look into template:
bc ${APPLICATION_IMAGE}-build-artifacts - [https://github.com/jmesnil/jboss-eap-openshift-templates/blob/eap-s2i-bui...]
{code:java}
triggers:
- github:
secret: ${GITHUB_WEBHOOK_SECRET}
type: GitHub
- generic:
secret: ${GENERIC_WEBHOOK_SECRET}
type: Generic
- imageChange: {}
type: ImageChange
- type: ConfigChange
{code}
bc ${APPLICATION_IMAGE} - [https://github.com/jmesnil/jboss-eap-openshift-templates/blob/eap-s2i-bui...]
{code:java}
triggers:
- imageChange:
from:
kind: ImageStreamTag
name: ${APPLICATION_IMAGE}-build-artifacts:latest
type: ImageChange
- type: ConfigChange
{code}
-> no trigger for EAP_RUNTIME_IMAGE imagestream changes
So now the expectation (rebuild app image on both builder or runtime image change) is broken.
was:
Analysis provides this information:
{code:java}
Test EAP S2I image changes
- Import a more recent version of EAP S2I images (test should be done for both the builder and runtime images referenced by the imagestreams)
{code}
However, in current template configuration there is no trigger upon EAP_RUNTIME_IMAGE imagestream change.
This is obvious why it doesn't happen when we look into template:
bc ${APPLICATION_IMAGE}-build-artifacts - [https://github.com/jmesnil/jboss-eap-openshift-templates/blob/eap-s2i-bui...]
{code:java}
triggers:
- github:
secret: ${GITHUB_WEBHOOK_SECRET}
type: GitHub
- generic:
secret: ${GENERIC_WEBHOOK_SECRET}
type: Generic
- imageChange: {}
type: ImageChange
- type: ConfigChange
{code}
bc ${APPLICATION_IMAGE} - [https://github.com/jmesnil/jboss-eap-openshift-templates/blob/eap-s2i-bui...]
{code:java}
triggers:
- imageChange:
from:
kind: ImageStreamTag
name: ${APPLICATION_IMAGE}-build-artifacts:latest
type: ImageChange
- type: ConfigChange
{code}
-> no trigger for EAP_RUNTIME_IMAGE imagestream changes
So now the expectation (rebuild app image on both builder or runtime image change) is broken.
This can be probably fixed just by adding additional trigger to either of BuildConfigs, eg. equivalent of this:
{code:java}
oc set triggers bc autoupgrading-app --from-image=eap7-runtime-imagestream:latest
{code}
But design decision needs to be made:
# leave as is (probably not? - contrary to analysis)
## no rebuild when _only_ runtime image gets updated - we can argue how big issue it is as theoretically what needs to go to runtime image most likely is needed for builder image too, so it gets updated
# add trigger to the second-in-chan BuildConfig
## quicker as only one build is triggered and intermediate resources reused
## requires intermediate imagestream to exist
## doesn't suffer from duplicated rebuild
# add trigger to the first-in-chain BuildConfig
## safer as everything is build from scratch
## slower as two builds need to be done
## could suffer from double rebuild - when both builder and runtime image is updated
> No autoupdate for EAP_RUNTIME_IMAGE in eap-s2i-build template
> -------------------------------------------------------------
>
> Key: WFWIP-357
> URL: https://issues.redhat.com/browse/WFWIP-357
> Project: WildFly WIP
> Issue Type: Bug
> Components: OpenShift
> Reporter: Jan Blizňák
> Assignee: Jeff Mesnil
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months