[JBoss JIRA] (WFLY-785) @PreDestroy not called on view scoped managed bean
by Stan Silvert (JIRA)
[ https://issues.jboss.org/browse/WFLY-785?page=com.atlassian.jira.plugin.s... ]
Stan Silvert closed WFLY-785.
-----------------------------
Resolution: Out of Date
> @PreDestroy not called on view scoped managed bean
> --------------------------------------------------
>
> Key: WFLY-785
> URL: https://issues.jboss.org/browse/WFLY-785
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Environment: Initializing Mojarra 2.1.7-jbossorg-2 (20120412-0335) and all native Jboss JSF impl
> Reporter: Mauricio Fenoglio
> Assignee: Stan Silvert
> Labels: jsf2, jsf21, memoryleak
> Attachments: InjectionTest.jar, InjectionTest.war, InjectionTest.war, InjectionTestV2.jar, TestingJSFMemoryLeak-1.0-SNAPSHOT.war
>
>
> All JSF ManagedBean are not destroyed and generate a great memory problem.
> This happen for View Scopes
> Nor are running @PreDestroy
> It is not possible to have production environments with jsf, so it is a blocker issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-848) Problem using MyFaces + CODI
by Stan Silvert (JIRA)
[ https://issues.jboss.org/browse/WFLY-848?page=com.atlassian.jira.plugin.s... ]
Stan Silvert closed WFLY-848.
-----------------------------
Resolution: Out of Date
> Problem using MyFaces + CODI
> ----------------------------
>
> Key: WFLY-848
> URL: https://issues.jboss.org/browse/WFLY-848
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Reporter: Rich DiCroce
> Assignee: Stan Silvert
> Labels: cdi, myfaces
>
> I have been experimenting with the dormant support for MyFaces added by AS7-5649. After setting up a recent JBoss snapshot build (#1292) as described in that issue (adding commons-digester, myfaces-api, and myfaces-impl to modules), I attempted to use my application. It deploys successfully (which is a big step, before it failed due to AS7-5849 / AS7-1628), but as soon as I try to log in, it blows up with this stack trace:
> {code}
> 12:31:56,371 ERROR [com.lapis.cerberus.portal.exception.ExceptionHandlingFilter.Full] (http-localhost/127.0.0.1:8080-20) Exception ID 6183872498: java.lang.IllegalStateException: Error restoring component: j_id1
> at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.restoreStateFromMap(DefaultFaceletsStateManagementStrategy.java:665) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.restoreStateFromMap(DefaultFaceletsStateManagementStrategy.java:680) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.restoreStateFromMap(DefaultFaceletsStateManagementStrategy.java:696) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.restoreView(DefaultFaceletsStateManagementStrategy.java:330) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.application.StateManagerImpl.restoreView(StateManagerImpl.java:130) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.shared.view.ViewDeclarationLanguageBase.restoreView(ViewDeclarationLanguageBase.java:106) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.restoreView(FaceletViewDeclarationLanguage.java:2118) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.application.ViewHandlerImpl.restoreView(ViewHandlerImpl.java:300) [myfaces-impl-2.1.9.jar:2.1.9]
> at com.ocpsoft.pretty.faces.application.PrettyViewHandler.restoreView(PrettyViewHandler.java:109) [prettyfaces-jsf2-3.3.3.jar:]
> at org.apache.myfaces.extensions.cdi.jsf.impl.scope.conversation.WindowContextAwareViewHandler.restoreView(WindowContextAwareViewHandler.java:122) [myfaces-extcdi-jsf20-module-impl-1.0.5.jar:1.0.5]
> at org.apache.myfaces.extensions.cdi.jsf.impl.CodiViewHandler.restoreView(CodiViewHandler.java:99) [myfaces-extcdi-jsf20-module-impl-1.0.5.jar:1.0.5]
> at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:83) [myfaces-api-2.1.9.jar:2.1.9]
> at javax.faces.application.ViewHandlerWrapper.restoreView(ViewHandlerWrapper.java:83) [myfaces-api-2.1.9.jar:2.1.9]
> at org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.java:127) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:170) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) [myfaces-impl-2.1.9.jar:2.1.9]
> at org.apache.myfaces.extensions.cdi.jsf2.impl.listener.phase.CodiLifecycleWrapper.execute(CodiLifecycleWrapper.java:95) [myfaces-extcdi-jsf20-module-impl-1.0.5.jar:1.0.5]
> at javax.faces.webapp.FacesServlet.service(FacesServlet.java:197) [myfaces-api-2.1.9.jar:2.1.9]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:62) [weld-core-1.1.10.Final.jar:2012-10-12 10:00]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:145) [prettyfaces-jsf2-3.3.3.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.jboss.solder.servlet.exception.CatchExceptionFilter.doFilter(CatchExceptionFilter.java:65) [solder-impl-3.1.0.Final.jar:3.1.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.jboss.solder.servlet.event.ServletEventBridgeFilter.doFilter(ServletEventBridgeFilter.java:74) [solder-impl-3.1.0.Final.jar:3.1.0.Final]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.primefaces.webapp.filter.FileUploadFilter.doFilter(FileUploadFilter.java:79) [primefaces-3.4.1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at com.lapis.cerberus.portal.exception.ExceptionHandlingFilter.doFilter(ExceptionHandlingFilter.java:71) [classes:]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:246) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.event(JBossWebContext.java:67)
> at org.jboss.modcluster.container.jbossweb.JBossWebContext$RequestListenerValve.invoke(JBossWebContext.java:48)
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:350) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(Http11NioProtocol.java:900) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at org.apache.tomcat.util.net.NioEndpoint$ChannelProcessor.run(NioEndpoint.java:1025) [jbossweb-7.2.0.Alpha2.jar:7.2.0.Alpha2]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_09]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_09]
> at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_09]
> Caused by: java.lang.ClassCastException: javax.faces.component.UIViewRoot$ViewScope cannot be cast to javax.faces.convert.Converter
> at javax.faces.component.UIOutput.restoreState(UIOutput.java:248) [myfaces-api-2.1.9.jar:2.1.9]
> at org.apache.myfaces.view.facelets.DefaultFaceletsStateManagementStrategy.restoreStateFromMap(DefaultFaceletsStateManagementStrategy.java:661) [myfaces-impl-2.1.9.jar:2.1.9]
> ... 54 more
> {code}
> After some experimentation, I determined that this is due to the use of the MyFaces CODI extensions in the project. If I remove the CODI libraries from the project (which is doable because it is only used in a few places, but not ideal), I do not get this exception. CODI has been tested against MyFaces, and I cannot find anyone else experiencing this problem, so I believe JBoss (or perhaps Weld) is doing something that CODI does not expect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ELY-341) PEM file format support
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ]
Pedro Igor reassigned ELY-341:
------------------------------
Assignee: Pedro Igor
> PEM file format support
> -----------------------
>
> Key: ELY-341
> URL: https://issues.jboss.org/browse/ELY-341
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: KeyStores
> Reporter: David Lloyd
> Assignee: Pedro Igor
> Fix For: 1.1.0.Beta7
>
>
> We should add support for PEM formats for formats including (but not limited to):
> * X.509 Certificate
> * CSRs
> * CRLs
> * RSA and DSA Public and Private Keys
> * PKCS8 format Private Keys
> * DH parameters
> * ECDSA Public Key
> * EC Private Key
> * EC Parameters
> This API could be consumed by various utilities or by custom credential storage implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ELY-341) PEM file format support
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-341?page=com.atlassian.jira.plugin.sy... ]
Pedro Igor commented on ELY-341:
--------------------------------
Is {{org.wildfly.security.pem.Pem}} layout OK or are you also looking for a more 'fancy' API ? For instance, maybe use a builder / fluent API, more user-friendly, handle inputstreams directly, etc ?
> PEM file format support
> -----------------------
>
> Key: ELY-341
> URL: https://issues.jboss.org/browse/ELY-341
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: KeyStores
> Reporter: David Lloyd
> Fix For: 1.1.0.Beta7
>
>
> We should add support for PEM formats for formats including (but not limited to):
> * X.509 Certificate
> * CSRs
> * CRLs
> * RSA and DSA Public and Private Keys
> * PKCS8 format Private Keys
> * DH parameters
> * ECDSA Public Key
> * EC Private Key
> * EC Parameters
> This API could be consumed by various utilities or by custom credential storage implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ELY-19) OAuth Broker Security Realm
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys... ]
Pedro Igor edited comment on ELY-19 at 7/1/16 9:59 AM:
-------------------------------------------------------
Keycloak subsystem does not provide the necessary means to get access to its repository. For that, we would need to implement a SecurityRealm based on Keycloak Admin Client which basically provides an API to access the Keycloak Administration RESTful API (based on RESTeasy Client API).
The Admin RESTful API does not return user credentials when querying an user (for obvious reasons). There are other ways to authenticate users though, but that would require some additional configurations to a realm in Keycloak, such as enable resource owner password grant type to a client.
The resource owner password grant type is suitable when the client is highly trusted. The reason for that is that user's credentials are shared with the client. However, for this particular case, specially CLI access, I think we can say that we have a highly trusted client. So that could be an option to implement the security realm.
Considering all that, do you want me to start implementing it ? May I change the title of this issue to 'Introduce a Keycloak Security Realm' ?
was (Author: pcraveiro):
Keycloak subsystem does not provide the necessary means to get access to its repository. For that, we would need to implement a SecurityRealm based on Keycloak Admin Client which basically provides an API to access the Keycloak Administration RESTful API (based on RESTeasy Client API).
Even if we use Keycloak Admin Client, we won't be able to support authentication because credentials are not returned by the Admin RESTful API (for obvious reasons).
There are other ways to authenticate users though, but that would require some additional configurations to a realm in Keycloak, such as enable resource owner password grant type to a client.
The resource owner password grant type is suitable when the client is highly trusted. The reason for that is that user's credentials are shared with the client. However, for this particular case, specially CLI access, I think we can say that we have a highly trusted client. So that could be an option to implement the security realm.
Considering all that, do you want me to start implementing it ? May I change the title of this issue to 'Introduce a Keycloak Security Realm' ?
> OAuth Broker Security Realm
> ---------------------------
>
> Key: ELY-19
> URL: https://issues.jboss.org/browse/ELY-19
> Project: WildFly Elytron
> Issue Type: Sub-task
> Reporter: Darran Lofthouse
> Assignee: Pedro Igor
> Fix For: 1.1.0.Beta7
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (ELY-19) OAuth Broker Security Realm
by Pedro Igor (JIRA)
[ https://issues.jboss.org/browse/ELY-19?page=com.atlassian.jira.plugin.sys... ]
Pedro Igor commented on ELY-19:
-------------------------------
Keycloak subsystem does not provide the necessary means to get access to its repository. For that, we would need to implement a SecurityRealm based on Keycloak Admin Client which basically provides an API to access the Keycloak Administration RESTful API (based on RESTeasy Client API).
Even if we use Keycloak Admin Client, we won't be able to support authentication because credentials are not returned by the Admin RESTful API (for obvious reasons).
There are other ways to authenticate users though, but that would require some additional configurations to a realm in Keycloak, such as enable resource owner password grant type to a client.
The resource owner password grant type is suitable when the client is highly trusted. The reason for that is that user's credentials are shared with the client. However, for this particular case, specially CLI access, I think we can say that we have a highly trusted client. So that could be an option to implement the security realm.
Considering all that, do you want me to start implementing it ? May I change the title of this issue to 'Introduce a Keycloak Security Realm' ?
> OAuth Broker Security Realm
> ---------------------------
>
> Key: ELY-19
> URL: https://issues.jboss.org/browse/ELY-19
> Project: WildFly Elytron
> Issue Type: Sub-task
> Reporter: Darran Lofthouse
> Assignee: Pedro Igor
> Fix For: 1.1.0.Beta7
>
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (JBMX-20) QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
by Vlastimil Eliáš (JIRA)
[ https://issues.jboss.org/browse/JBMX-20?page=com.atlassian.jira.plugin.sy... ]
Vlastimil Eliáš deleted JBMX-20:
--------------------------------
> QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBMX-20
> URL: https://issues.jboss.org/browse/JBMX-20
> Project: JBossMX
> Issue Type: Bug
> Environment: QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
> QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
> QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
> QBᴔᴔᴔŒŒŒHelpline1*8 4 4 - 4 1 4-4 8 6 8 Quickbooks Tech Support phone number,Quickbooks Support phone number
> Reporter: john dboss
>
> Intuit Quickbooks +++»--A- 1-844-414-4868 Quickbooks Support Phone Number 1-844-414-4868 Quickbooks technical phone number,
> 1-844-414-4868 Quickbooks technical number, 1-844-414-4868 Quickbooks technical support contact number,1-844-414-4868
> Quickbooks contact number, 1-844-414-4868Quickbooks contact phone number, 1-844-414-4868 Quickbooks contact telephone
> number, Quickbooks 24 hour contact number, Quickbooks customer support contact number, Quickbooks customer service contact
> number, 1-844-414-4868Quickbooks official number, Quickbooks official contact number, Quickbooks 877 contact number,
> Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number Quickbooks support
> phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support number.Quickbooks
> support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number, Quickbooks
> customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone number,
> Quickbooks support phone number. Help@Call 1-844-414-4868/.Quickbooks 24/7 support phone number,Quickbooks telephone number
> for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks contact telephone
> numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks official
> number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone numberQuickbooks
> support number,Quickbooks telephone number for support QB SUPPORT ON ((1-844-414-4868) Quickbooks PHONE NUMBER AND
> Quickbooks SUPPORT PHONE NUMBER Online Support For Quickbooks support help intuit customer service number tech support for Quickbooks technical support for Quickbooks technical support for intuit Quickbooks help website Quickbooks support website Quickbooks .com/helpme Quickbooks customer support website intuit Quickbooks head office intuit Quickbooks call center intuit support number (any thing with intuit ) buy Quickbooks enhance buy intuit enhance customer support for Quickbooks customer support for intuit customer support for intuit Quickbooks www.Quickbooks .com/support (((1-844-414-4868)!!! Quickbooks ((Technical)) Support phone number Quickbooks HELP DESK phone number Online Support For
> (((1-844-414-4868)!!! Quickbooks ((Technical)) Support phone number Quickbooks HELP DESK phone number Helpline TECH ))1-844-414-4868((Quickbooks technical support phone number Quickbooks phone number QB SUPPORT ON ((1-844-414-4868)) Quickbooks
> PHONE NUMBER AND Quickbooks SUPPORT PHONE NUMBER Quickbooks Toll Free, Intuit@(1-844-414-4868)@ Quickbooks HELP DESK Phone
> Number vides online solution for all USA/CANADA clients. For any help of query call 1-844-414-4868to get all Quickbooks
> account solution. @@Call, 1-844-414-4868 for all type help by Quickbooks HELP DESK phone number, Intuit Quickbooks HELP
> DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
> number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number, Quickbooks
> technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number, Quickbooks Customer
> Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline Number, Quickbooks
> Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks Helpline Number;
> Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
> Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
> number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks HELP DESK
> Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone number,
> Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular toll free
> number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service
> Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline
> Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone number,
> Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
> technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
> number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
> Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
> Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
> Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
> Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
> number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
> Quickbooks customer support phone number 1-844-414-4868 Quickbooks technical help telephone number, Quickbooks technical
> help contact number, Quickbooks technical support contact number, Quickbooks contact number, Quickbooks contact phone
> number, Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
> Quickbooks customer service contact number, Quickbooks official number, Quickbooks official contact number, Quickbooks 877
> contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number
> Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support
> number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number,
> Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone
> number, Quickbooks support phone number. Help@Call 1-877-778-8714/.Quickbooks 24/7 support phone number,Quickbooks
> telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks
> contact telephone numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks
> official number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone
> numberQuickbooks support number,Quickbooks telephone number for support Quickbooks Toll Free, Intuit@(1-877-778-8714)@
> Quickbooks HELP DESK Phone Number vides online solution for all USA/CANADA clients. For any help of query call 1 877 778
> 8714 to get all Quickbooks account solution. @@Call, 1-877-778-8714 for all type help by Quickbooks HELP DESK phone number,
> Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
> technical support phone number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
> number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
> Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline
> Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks
> Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks
> Support Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support
> contact number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks
> HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
> number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular
> toll free number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer
> Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service
> Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone
> number, Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number,
> Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support
> phone number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
> Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
> Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
> Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
> Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
> number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
> Quickbooks customer support phone number 1-844-414-4868 Quickbooks technical help telephone number, Quickbooks technical
> help contact number, Quickbooks technical support contact number, Quickbooks contact number, Quickbooks contact phone
> number, Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
> Quickbooks customer service contact number, Quickbooks official number, Quickbooks official contact number, Quickbooks 877
> contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support phone number
> Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks technical support
> number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks customer support number,
> Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks customer service phone
> number, Quickbooks support phone number. Help@Call 1-877-778-8714/.Quickbooks 24/7 support phone number,Quickbooks
> telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone number, Quickbooks
> contact telephone numbertelephone number for Quickbooks online support,Quickbooks official support number,Quickbooks
> official number,Quickbooks official phone number,phone number for Quickbooks supportQuickbooks 24/7 support phone
> numberQuickbooks support number,Quickbooks telephone number for support Talk:TollFree,California ((1877 778 8714 USA))
> Quickbooks technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone Number Call,Av..1
> (877) 778.8714..(((( Quickbooks support phone number, Quickbooks customer service phone number 1-877-778-8714 FREE FREE
> FREE FREE FREE for all type help by QuickBook?.s HELP DESK phone number, Intuit QuickBook?.s HELP DESK Phone Number,
> QuickBook?.s Help Desk Phone Number, QuickBook?.s HELP DESK number, QuickBook?.s technical support phone number,@@@
> QuickBook?.s phone number, QuickBook?.s technical support number, QuickBook?.s support phone number, QuickBook?.s technical
> support, QuickBook?.s Customer Service Phone Number, QuickBook?.s Customer Service Number, QuickBook?.s Customer Support
> Phone Number, QuickBook?.s Customer Support Number,@@@@ QuickBook?.s Customer Service Helpline Number, QuickBook?.s
> Customer Care Number, QuickBook?.s support team phone number Talk:TollFree,California ((1877 778 8714 USA)) Quickbooks
> technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone Number TollFree?,California
> ((1877 778 8714 USA)) Quickbooks technical support phone number,1..877..778..8714 Intuit Quickbooks customer service Phone
> Number QuickBook?.s help number-QuickBook?.s Helpline Number; QuickBook?.s help phone number-QuickBook?.s Helpline Number,
> QuickBook?.s HELP DESK Toll free Number, QuickBook?.s Support Telephone Number, QuickBook?.s HELP DESK Telephone number,
> QuickBook?.s HELP DESK contact number, QuickBook?.s support contact number, QuickBook?.s technical support contact number.
> Call, QuickCallSend? SMSCall from mobileAdd to Skype You'll need Skype CreditFree? via Skype Helpline Number)).. 1 (877)
> 778.8714..(((( Quickbooks HELP DESK phone number, Quickbooks customer service phone number Call,QB customer..1 (877)
> 778.8714..(((( Quickbooks support phone number, Quickbooks customer service phone number Call,..1 (877) 778.8714((((
> Quickbooks technical support phone number.Quickbooks phone number Quickbooks Toll Free, Intuit@(1-877-778-8714)@-:
> Quickbooks HELP DESK Phone Number vides online solution for all USA/CANADA clients. For any help of query call 1 877 778
> 8714 to get all Quickbooks account solution. @@Call, 1-877-778-8714 for all type help by Quickbooks HELP DESK phone number,
> Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks
> technical support phone number,@@@ Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone
> number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
> Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number,@@@@ Quickbooks Customer Service Helpline
> Number, Quickbooks Customer Care Number, Quickbooks support team phone number, @@@@@ Quickbooks help number-Quickbooks
> Helpline Number; Quickbooks help phone number-Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks
> Support Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support
> contact number, Quickbooks technical support contact number. Call, Quickbooks HELP DESK phone number, Intuit Quickbooks
> HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number, Quickbooks technical support phone
> number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support phone number. It is very popular
> toll free number which vide by Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer
> Service Number, Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service
> Helpline Number, Quickbooks Customer Care Number, Quickbooks support team phone number. Call, Quickbooks HELP DESK phone
> number, Intuit Quickbooks HELP DESK Phone Number, Quickbooks Help Desk Phone Number, Quickbooks HELP DESK number,
> Quickbooks technical support phone number, Quickbooks phone number, Quickbooks technical support number, Quickbooks support
> phone number, Quickbooks technical support, Quickbooks Customer Service Phone Number, Quickbooks Customer Service Number,
> Quickbooks Customer Support Phone Number, Quickbooks Customer Support Number, Quickbooks Customer Service Helpline Number,
> Quickbooks Customer Care Number, Quickbooks support team phone number, Quickbooks help number-Quickbooks Helpline Number;
> Quickbooks help phone number, Quickbooks Helpline Number, Quickbooks HELP DESK Toll free Number, Quickbooks Support
> Telephone Number, Quickbooks HELP DESK Telephone number, Quickbooks HELP DESK contact number, Quickbooks support contact
> number, Quickbooks technical support contact number, Quickbooks support phone number, Quickbooks support phone number.
> Quickbooks customer support phone number
> Support helpline+++»--A- 1-844-414-4868 Quickbooks Support Phone Number US 1-844-414-4868 Quickbooks technical help
> telephone number, 1-844-414-4868 Quickbooks technical help contact number, 1-844-414-4868 Quickbooks technical support
> contact number,1-844-414-4868 Quickbooks contact number, 1-844-414-4868Quickbooks contact phone number, 1 877 778
> 8714Quickbooks contact telephone number, Quickbooks 24 hour contact number, Quickbooks customer support contact number,
> Quickbooks customer service contact number, 1-844-414-4868Quickbooks official number, Quickbooks official contact number,
> Quickbooks 877 contact number, Quickbooks toll free number, 877 number for Quickbooks support, Quickbooks 24/7 support
> phone number Quickbooks support phone number,Quickbooks support phone number,Quickbooks help phone number, Quickbooks
> technical support number.Quickbooks support number, Quickbooks phone number, Quickbooks HELP DESK number, Quickbooks
> customer support number, Quickbooks customer support phone number, Quickbooks customer service phone number, Quickbooks
> customer service phone number, Quickbooks support phone number. Help@Call 1-844-414-4868/.Quickbooks 24/7 support phone
> number,Quickbooks telephone number for support? call 1-844-414-4868@./Quickbooks contact number, Quickbooks contact phone
> number
> Support helpline+++»--A- 1-844-414-4868 Quickbooks Support Phone Number 1-844-414-4868 Quickbooks telephone number US 1-844-414-4868 Quickbooks technical help telephone number,1-844-414-4868 Quickbooks technical help contact number,1-844-414-4868
> Quickbooks technical support contact number,1-844-414-4868 Quickbooks contact number,1-844-414-4868 Quickbooks contact phone
> number,1-844-414-4868 Quickbooks contact telephone number,1-844-414-4868 Quickbooks 24 hour contact number,1-844-414-4868
> Quickbooks customer support contact number,1-844-414-4868 Quickbooks customer service contact number,1-844-414-4868
> Quickbooks official number, Quickbooks official contact number, Quickbooks 877 contact number, Quickbooks toll free number,
> 877 number for Quickbooks support, Quickbooks 24/7 support phone number
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (WFLY-6797) Is there a way to have more than one logging subystem belonging to one profile
by Preeta Kuruvilla (JIRA)
[ https://issues.jboss.org/browse/WFLY-6797?page=com.atlassian.jira.plugin.... ]
Preeta Kuruvilla updated WFLY-6797:
-----------------------------------
Description:
I have "ha" profile in my domain.xml which has many subsystems.
Below is the structure I have:-
{color:#205081}<server-groups>
<server-group name="main-server-group" profile="ha">
<socket-binding-group ref="ha-sockets"/>
<deployments>
<deployment name="RC.war" runtime-name="RC.war"/>
</deployments>
</server-group>
<server-group name="other-server-group" profile="ha">
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="SL.war" runtime-name="SL.war"/>
</deployments>
</server-group>
</server-groups>{color}
There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
Example:-
RC.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>
{color}
while SL.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="ISEE">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="isee.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="FILE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="DB_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="MQ_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="JMS_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="HTTP_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VMWARE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VSOC_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="CLOUD_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>{color}
Thanks,
Preeta
was:
I have "ha" profile in my domain.xml which has many subsystems.
Below is the structure I have:-
{color:#205081}<server-groups>
<server-group name="main-server-group" profile="ha">
<socket-binding-group ref="ha-sockets"/>
<deployments>
<deployment name="RC.war" runtime-name="RC.war"/>
</deployments>
</server-group>
<server-group name="other-server-group" profile="ha">
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="SL.war" runtime-name="SL.war"/>
</deployments>
</server-group>
</server-groups>{color}
There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
Example:-
RC.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>
{color}
while SL.war needs to use the below:-
{color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
<console-handler name="CONSOLE">
<level name="INFO"/>
<formatter>
<named-formatter name="COLOR-PATTERN"/>
</formatter>
</console-handler>
<periodic-rotating-file-handler name="ISEE">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="isee.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="FILE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="DB_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="MQ_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="JMS_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="HTTP_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VMWARE_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="VSOC_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<periodic-rotating-file-handler name="CLOUD_ADAPTER">
<formatter>
<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
<suffix value=".yyyy-MM-dd"/>
<append value="false"/>
</periodic-rotating-file-handler>
<logger category="com.arjuna">
<level name="WARN"/>
</logger>
<logger category="org.apache.tomcat.util.modeler">
<level name="WARN"/>
</logger>
<logger category="org.jboss.as.config">
<level name="DEBUG"/>
</logger>
<logger category="sun.rmi">
<level name="WARN"/>
</logger>
<logger category="jacorb">
<level name="WARN"/>
</logger>
<logger category="jacorb.config">
<level name="ERROR"/>
</logger>
<root-logger>
<level name="INFO"/>
<handlers>
<handler name="CONSOLE"/>
<handler name="FILE"/>
</handlers>
</root-logger>
<formatter name="PATTERN">
<pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
<formatter name="COLOR-PATTERN">
<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
</formatter>
</subsystem>{color}
Thanks,
Preeta
> Is there a way to have more than one logging subystem belonging to one profile
> ------------------------------------------------------------------------------
>
> Key: WFLY-6797
> URL: https://issues.jboss.org/browse/WFLY-6797
> Project: WildFly
> Issue Type: Task
> Components: Domain Management
> Affects Versions: 8.2.0.Final
> Reporter: Preeta Kuruvilla
> Assignee: Brian Stansberry
>
> I have "ha" profile in my domain.xml which has many subsystems.
> Below is the structure I have:-
> {color:#205081}<server-groups>
> <server-group name="main-server-group" profile="ha">
> <socket-binding-group ref="ha-sockets"/>
> <deployments>
> <deployment name="RC.war" runtime-name="RC.war"/>
> </deployments>
> </server-group>
> <server-group name="other-server-group" profile="ha">
> <socket-binding-group ref="standard-sockets"/>
> <deployments>
> <deployment name="SL.war" runtime-name="SL.war"/>
> </deployments>
> </server-group>
> </server-groups>{color}
> There is a logging subsystem which needs to be different for RC.war and SL.war. Both RC.war and SL.war belong to same profile.
>
> Is there a way to have 2 logging related subsystems defined in "ha" profile, such that RC can point to one and SL to the other although they belong to same profile?
> Example:-
> RC.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>
> {color}
> while SL.war needs to use the below:-
> {color:#205081}<subsystem xmlns="urn:jboss:domain:logging:2.0">
> <console-handler name="CONSOLE">
> <level name="INFO"/>
> <formatter>
> <named-formatter name="COLOR-PATTERN"/>
> </formatter>
> </console-handler>
> <periodic-rotating-file-handler name="ISEE">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="isee.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="FILE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="fileadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="DB_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="dbadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="MQ_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="mqadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="JMS_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="jmsadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="HTTP_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="httpadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VMWARE_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vmwareadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="WSLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="wslisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="SERVICEITEMLISTENER_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="serviceitemlisteneradapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="VSOC_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="vsocadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <periodic-rotating-file-handler name="CLOUD_ADAPTER">
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <file relative-to="jboss.server.log.dir" path="cloudadapter.log"/>
> <suffix value=".yyyy-MM-dd"/>
> <append value="false"/>
> </periodic-rotating-file-handler>
> <logger category="com.arjuna">
> <level name="WARN"/>
> </logger>
> <logger category="org.apache.tomcat.util.modeler">
> <level name="WARN"/>
> </logger>
> <logger category="org.jboss.as.config">
> <level name="DEBUG"/>
> </logger>
> <logger category="sun.rmi">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb">
> <level name="WARN"/>
> </logger>
> <logger category="jacorb.config">
> <level name="ERROR"/>
> </logger>
> <root-logger>
> <level name="INFO"/>
> <handlers>
> <handler name="CONSOLE"/>
> <handler name="FILE"/>
> </handlers>
> </root-logger>
> <formatter name="PATTERN">
> <pattern-formatter pattern="%d{yyyy-MM-dd HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> <formatter name="COLOR-PATTERN">
> <pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </subsystem>{color}
> Thanks,
> Preeta
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months