[JBoss JIRA] (WFLY-11860) Persistent deployments are lost on restart with '--read-only-server-config'
by Maxim Sermin (Jira)
[ https://issues.jboss.org/browse/WFLY-11860?page=com.atlassian.jira.plugin... ]
Maxim Sermin commented on WFLY-11860:
-------------------------------------
Thanks a lot for your elaborate explanation.
So it looks like:
- we didn't fully understand the original intention behind `--read-only-server-config`
- we're still looking for a way to solve our problem, which we believe should be rather common nowadays in config management driven environments
The basic outline of what we're trying to achieve is:
- control a basic/general set of configuration options of WFLY through an external configuration management application
- control which artefacts should be deployed through an external configuration management application
- make the deployments persistent, so a restart of the WFLY service outside of the configuration management scope is possible
Initially, we faced the issue of flip-flopping the state of `standalone.xml` as its content was one the one hand controlled through config management tools, on the other hand, it was modified at runtime by WFLY.
So we figured, `--read-only-server-config` was meant to provide a read-only configuration for exactly this scenario, while WFLY continues to write its runtime modifications as before to the read-write `standalone.xml`.
This ended up resulting in the reported issue of deployments not surviving a restart of the WFLY service.
In general, this situation violates the separation of the "configuration" and "runtime" domains, as the runtime leaks into the configuration domain which is a undesirable situation from a systems design PoV.
Right now, it looks like we might be able to temporarily work around this issue by only controlling specific XML attributes through Augeas, while letting WFLY handle its `standalone.xml` as it used to.
In the end, we believe a RFE to introduce the behavior of having a separated "read-only" and "runtime-modified" configuration to allow for the separation of those domains should be considered.
> Persistent deployments are lost on restart with '--read-only-server-config'
> ---------------------------------------------------------------------------
>
> Key: WFLY-11860
> URL: https://issues.jboss.org/browse/WFLY-11860
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Reporter: Maxim Sermin
> Assignee: Brian Stansberry
> Priority: Major
>
> I wanted to use the `read-only-server-config` feature in order to be able to have `standalone.xml` managed by configuration management. Additionally, I need the ability to restart Wildfly and have the same state afterwards. Unfortunately, in this case the artefacts that were deployed are not deployed anymore after the restart.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (DROOLS-3774) Add auditing functionality to record/log which rules fired during a specific run
by Duncan Doyle (Jira)
Duncan Doyle created DROOLS-3774:
------------------------------------
Summary: Add auditing functionality to record/log which rules fired during a specific run
Key: DROOLS-3774
URL: https://issues.jboss.org/browse/DROOLS-3774
Project: Drools
Issue Type: Feature Request
Components: core engine
Affects Versions: 7.19.0.Final
Reporter: Duncan Doyle
Assignee: Mario Fusco
We've had multiple requests to add an ootb auditing/logging feature to Drools. The basic requirements is to allow users to audit which rules fired against which data and for what reason.
For example, when you want to determine a fraud transaction, and you insert transactions into an engine, you want to know why a transaction was marked as fraudulent. So you want to know which rules fired against which transaction.
Another requirement I've seen is the following:
[quote]
Furthermore, they want the dashboard to show all the rules that execute by task stage in summary and then have the ability to drill into that list to see the individual delinquent account and the rules fired against it.
[/quote]
I know that we can add listeners to the engine to record things like MatchFired, but it would be great if we would have an ootb feature for this. Maybe even an API that instead of returning the number of rules fired, would be able to return the entire execution context.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by SHREYAS HOLLA P (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
SHREYAS HOLLA P commented on WFLY-11865:
----------------------------------------
I am aware that Setting add-logging-api-dependencies to false will switch off implicit logging.
But this should not stop logging the boot information which tell if the WAR is deployed and the server has started, something like,
WFLYUT0021: Registered web context: /cas
WFLYSRV0010: Deployed "cas.war" (runtime-name : "cas.war")
WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 27978ms - Started 483 of 772 services (383 services are lazy, passive or on-demand)
But the above is not getting logged
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Reporter: SHREYAS HOLLA P
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang updated WFLY-11865:
-----------------------------
Component/s: Logging
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang commented on WFLY-11865:
----------------------------------
If you set {{add-logging-api-dependencies}} to false in logging subsystem, implicit logging API dependencies are not added to your deployments.
As the deployment war is about 120M without source. The code could affect logging during deployment. But I'm not able to investigate what happened behind the scene.
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Reporter: SHREYAS HOLLA P
> Assignee: Chao Wang
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11865) Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
by Chao Wang (Jira)
[ https://issues.jboss.org/browse/WFLY-11865?page=com.atlassian.jira.plugin... ]
Chao Wang reassigned WFLY-11865:
--------------------------------
Assignee: (was: Chao Wang)
> Wildfly console logging stops with statement, "2 Spring WebApplicationInitializers detected on classpath"
> ----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11865
> URL: https://issues.jboss.org/browse/WFLY-11865
> Project: WildFly
> Issue Type: Bug
> Components: Logging
> Reporter: SHREYAS HOLLA P
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> We are deploying CAS-5.3.8.WAR on on WildFly 10.0.0.Final, the WAR gets deployed successfully and the application works fine but wildfly server console log stops,
> This happens when we add "<add-logging-api-dependencies value="false"/>".
> WFLYSRV0027: Starting deployment of "cas.war" (runtime-name: "cas.war")
> WFLYSRV0027: Starting deployment of "BankFusion.ear" (runtime-name: "BankFusion.ear")
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
> JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xercesImpl.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry xml-apis.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYSRV0059: Class Path entry serializer.jar in /E:/FusionBanking/FBP531.5/WildFly/wildfly-10.0.0.Final/bin/content/cas.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
> WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause)
> WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause)
> WFLYWELD0013: Deployment deployment "cas.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations)
> 2 Spring WebApplicationInitializers detected on classpath
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months
[JBoss JIRA] (WFLY-11867) Cannot get exception as pass-by-reference
by Wolf-Dieter Fink (Jira)
Wolf-Dieter Fink created WFLY-11867:
---------------------------------------
Summary: Cannot get exception as pass-by-reference
Key: WFLY-11867
URL: https://issues.jboss.org/browse/WFLY-11867
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 16.0.0.Final, 17.0.0.Beta1
Reporter: Wolf-Dieter Fink
Despite of <in-vm-remote-interface-invocation pass-by-value="false"/>, an exception is not thrown by reference, which results in java.io.NotSerializableException if the exception doesn't implement Serializable. This is a blocker of a large migration project from WebLogic because it throws by reference even if that doesn't implement Serializable.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 3 months