[JBoss JIRA] (WFLY-11085) Upgrade Jboss Metadata to 12.0.0.Final
by ehsavoie Hugonnet (JIRA)
ehsavoie Hugonnet created WFLY-11085:
----------------------------------------
Summary: Upgrade Jboss Metadata to 12.0.0.Final
Key: WFLY-11085
URL: https://issues.jboss.org/browse/WFLY-11085
Project: WildFly
Issue Type: Component Upgrade
Components: EJB, Web (Undertow)
Affects Versions: 14.0.0.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
Upgrade Jboss Metadata to 12.0.0.Final (with the JavaEE 8 schemas and jboss descriptors using them)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFCORE-4135) Add a new property to disable backups of configuration XML files. Also avoid writing to standalone_xml_history when --read-only-server-config=<config> is set.
by Rafael Ruiz (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4135?page=com.atlassian.jira.plugi... ]
Rafael Ruiz commented on WFCORE-4135:
-------------------------------------
I have found twice problems using software based on wildfly-core (EAP, but also Infinispan/Datagrid) when running in a containerized environment. For example because of customized installations $WFCORE/standalone/configuration had to be read-only. Even running on non-containerized environment, but with very strict security rules that forced that directory to be only for read.
Also, in a less technical way, I heard some critics of users saying this is a 'legacy behaviour' senseless in containers. Maybe I have too much contact with cloud-native people. ;-)
"_Writing to history is required when --read-only-server-config=<config> is set if any management op that would require reload is invoked. The backup is what's read when 'reload' is invoked. If history backups were disabled the server would have to properly account for this use case; e.g. by failing any such op_"
I have tested to reload from CLI and its seems to work, but with no real changes pending of reload. Will do more tests
> Add a new property to disable backups of configuration XML files. Also avoid writing to standalone_xml_history when --read-only-server-config=<config> is set.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-4135
> URL: https://issues.jboss.org/browse/WFCORE-4135
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Management
> Reporter: Rafael Ruiz
>
> We need something like
> --disable-configuration-history
> to use when running in containers to avoid write to any directory ('standalone_xml_history').
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3046) Scenario simulation should index used fact types and fields
by Toni Rikkola (JIRA)
Toni Rikkola created DROOLS-3046:
------------------------------------
Summary: Scenario simulation should index used fact types and fields
Key: DROOLS-3046
URL: https://issues.jboss.org/browse/DROOLS-3046
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Toni Rikkola
Assignee: Toni Rikkola
Every asset that uses models is indexed for the used fact types and fields. This is for refactoring reasons, if a fact name or field changes the impacted scenario simulations can be detected.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFCORE-4136) Booting a slave HC fails if the content repository entry for a rollout plan is not present
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4136?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-4136:
-------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly-core/pull/3532
> Booting a slave HC fails if the content repository entry for a rollout plan is not present
> ------------------------------------------------------------------------------------------
>
> Key: WFCORE-4136
> URL: https://issues.jboss.org/browse/WFCORE-4136
> Project: WildFly Core
> Issue Type: Bug
> Components: Management
> Affects Versions: 6.0.2.Final
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
>
> Slave HC fails to boot if it connects to a DC that has a rollout-plan configured when the slave was shut down.
> See Steps to Reproduce.
> Failure is:
> {code}
> [Host Controller] 14:51:04,208 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 4) WFLYCTL0013: Operation ("add") failed - address: ([("management-client-content" => "rollout-plans")]): org.jboss.as.management.client.content.ContentStorageException: java.io.FileNotFoundException: /Users/bstansberry/tmp/support/02184219/slave/domain/data/content/2d/56893cc4da1c67a79f4845a57ae90c04a969b4/content (No such file or directory)
> [Host Controller] at org.jboss.as.management.client.content.ManagedDMRContentTypeResource.loadContent(ManagedDMRContentTypeResource.java:306)
> [Host Controller] at org.jboss.as.management.client.content.ManagedDMRContentTypeResource.<init>(ManagedDMRContentTypeResource.java:91)
> [Host Controller] at org.jboss.as.management.client.content.ManagedDMRContentTypeAddHandler.execute(ManagedDMRContentTypeAddHandler.java:58)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:982)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450)
> [Host Controller] at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
> [Host Controller] at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:490)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.access$1100(DomainModelControllerService.java:200)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.lambda$apply$0(DomainModelControllerService.java:1372)
> [Host Controller] at org.jboss.as.controller.access.InVmAccess.runInVm(InVmAccess.java:63)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.apply(DomainModelControllerService.java:1372)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor$1.apply(DomainModelControllerService.java:1369)
> [Host Controller] at org.jboss.as.host.controller.SecurityActions$Execution$1.execute(SecurityActions.java:77)
> [Host Controller] at org.jboss.as.host.controller.SecurityActions.privilegedExecution(SecurityActions.java:47)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1375)
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService.applyRemoteDomainModel(RemoteDomainConnectionService.java:603)
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService.access$1200(RemoteDomainConnectionService.java:138)
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnectionService$3.applyDomainModel(RemoteDomainConnectionService.java:546)
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection.applyDomainModel(RemoteDomainConnection.java:325)
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$RegisterSubsystemsRequest$1.execute(RemoteDomainConnection.java:468)
> [Host Controller] at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> [Host Controller] at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [Host Controller] at java.lang.Thread.run(Thread.java:748)
> [Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> [Host Controller] Caused by: java.io.FileNotFoundException: /Users/bstansberry/tmp/support/02184219/slave/domain/data/content/2d/56893cc4da1c67a79f4845a57ae90c04a969b4/content (No such file or directory)
> [Host Controller] at java.io.FileInputStream.open0(Native Method)
> [Host Controller] at java.io.FileInputStream.open(FileInputStream.java:195)
> [Host Controller] at java.io.FileInputStream.<init>(FileInputStream.java:138)
> [Host Controller] at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:51)
> [Host Controller] at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:318)
> [Host Controller] at org.jboss.as.management.client.content.ManagedDMRContentTypeResource.loadContent(ManagedDMRContentTypeResource.java:292)
> [Host Controller] ... 27 more
> [Host Controller]
> [Host Controller] 14:51:04,212 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 4) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-552" => "WFLYCTL0158: Operation handler failed: org.jboss.as.management.client.content.ContentStorageException: java.io.FileNotFoundException: /Users/bstansberry/tmp/support/02184219/slave/domain/data/content/2d/56893cc4da1c67a79f4845a57ae90c04a969b4/content (No such file or directory)"}}
> [Host Controller] 14:51:04,218 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://127.0.0.1:9999: 1-$-
> [Host Controller] at org.jboss.as.host.controller.RemoteDomainConnection$RegisterSubsystemsRequest$1.execute(RemoteDomainConnection.java:472)
> ...
> [Host Controller] 14:51:04,219 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
> [Host Controller] 14:51:04,220 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
> [Host Controller] 14:51:04,221 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0178: Aborting with exit code 99
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTA platform class use
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ]
Scott Marlow updated WFLY-11010:
--------------------------------
Description:
Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration.
Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache.
Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets "hibernate.transaction.jta.platform". This should help applications that have configured the transaction platform class.
was:
Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration.
Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache.
Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform". This should help applications that have configured to use JTA transaction factory or transaction platform classes.
> Document 2lc/JTA integration properties and add better detection of ehcache/JTA platform class use
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-11010
> URL: https://issues.jboss.org/browse/WFLY-11010
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 15.0.0.Alpha1
>
>
> Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration.
> Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache.
> Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets "hibernate.transaction.jta.platform". This should help applications that have configured the transaction platform class.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-11010) Document 2lc/JTA integration properties and add better detection of ehcache/JTA platform class use
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-11010?page=com.atlassian.jira.plugin... ]
Scott Marlow updated WFLY-11010:
--------------------------------
Summary: Document 2lc/JTA integration properties and add better detection of ehcache/JTA platform class use (was: Document 2lc/JTA integration properties and add better detection of ehcache/JTAFactoryClass use)
> Document 2lc/JTA integration properties and add better detection of ehcache/JTA platform class use
> --------------------------------------------------------------------------------------------------
>
> Key: WFLY-11010
> URL: https://issues.jboss.org/browse/WFLY-11010
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 14.0.0.Final
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Fix For: 15.0.0.Alpha1
>
>
> Document the "wildfly.jpa.regionfactory" and "wildfly.jpa.jtaplatform" properties for Hibernate ORM 5.3+ integration.
> Also automatically treat "wildfly.jpa.regionfactory" as false if [ehcache is being used|http://www.ehcache.org/documentation/2.7/integrations/hibernate.html] (e.g. check if the hibernate.cache.region.factory_class value starts with "net.sf.ehcache"). This should help applications that have configured to use Ehcache.
> Also automatically treat "wildfly.jpa.jtaplatform" as false if the application sets either "hibernate.transaction.factory_class" or "hibernate.transaction.jta.platform". This should help applications that have configured to use JTA transaction factory or transaction platform classes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (WFLY-11084) inter-app quickstart does not deploy (WildFly 14.0.1)
by Kevin Eagles (JIRA)
Kevin Eagles created WFLY-11084:
-----------------------------------
Summary: inter-app quickstart does not deploy (WildFly 14.0.1)
Key: WFLY-11084
URL: https://issues.jboss.org/browse/WFLY-11084
Project: WildFly
Issue Type: Bug
Reporter: Kevin Eagles
Assignee: Jason Greene
Priority: Minor
Using Wildfly 14.0.1.Final
When deploying inter-app-appA.war, Wildfly complains about the EJB lookup for:
@ejb(lookup = "java:global/inter-app-appB/BarImpl!org.jboss.as.quickstarts.interapp.shared.Bar")
Likewise, when deploying inter-app-appB.war, Wildfly complains about the EJB lookup for:
@ejb(lookup = "java:global/inter-app-appA/FooImpl!org.jboss.as.quickstarts.interapp.shared.Foo")
To reproduce, from the inter-app quickstart:
mvn install wildfly:deploy
Can also reproduce by just doing an mvn install, then manually deploying the jar, then appA, then appB using the HAL Management Console.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months
[JBoss JIRA] (DROOLS-3000) Enhance data type restrictions UX (decision tables & DT dialog)
by Cristiano Nicolai (JIRA)
[ https://issues.jboss.org/browse/DROOLS-3000?page=com.atlassian.jira.plugi... ]
Cristiano Nicolai commented on DROOLS-3000:
-------------------------------------------
[~uxdlc] if the use case is to restricted based on time range, +1 for using the same component as the manage section.
> Enhance data type restrictions UX (decision tables & DT dialog)
> ---------------------------------------------------------------
>
> Key: DROOLS-3000
> URL: https://issues.jboss.org/browse/DROOLS-3000
> Project: Drools
> Issue Type: Story
> Components: DMN Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Labels: UX, UXTeam, drools-tools
> Attachments: DataType selection ('Properties Panel' and 'in-grid').png, Screen Shot 2018-08-10 at 10.23.36 AM.png, Screen Shot 2018-08-24 at 8.38.37 AM.png, Screen Shot 2018-09-26 at 1.24.06 PM.png, Screen Shot 2018-09-26 at 4.48.04 PM.png, Screen Shot 2018-09-26 at 4.52.47 PM.png, pop-overc.png, pop-overcSpecs.png, select.png
>
>
> *Background*
> Persona: Business analyst or Rules practitioner
> Use Cases:
> * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table .
> * From the Data Types dialog - as a user I want the ability to define constraints for the following types: https://docs.google.com/spreadsheets/d/1HLYwi5JrCEU6IxWRge7RCKANLiHCL0d2E...
> Functional considerations/ pre conditions:
> * Consider interaction in light of Property panel and consistency.
> * Underscore the notion of one-off constraints.
> Verification conditions:
> * Scrum team and PO review.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 9 months