[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka commented on ARQ-710: ---------------------------------- Aslak: {quote} Not sure how to attack this.. in theory the stream that is wrapped in the managed container should be able to tell you which server it's from, so hench could be redirected somewhere, but not sure how to get 'client'. In AS4-6 CONSOLE was just another logger, i'm sure AS7 is similar. Wouldn't setting server1, server2 to log to specific file get you what you want? If no server logs to CONSOLE, then the assumption is the rest is 'client' ? {quote} I thought about that, but that would only separate by server. I believe it would be very convenient if separated by server _and_ test. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka edited comment on ARQ-710 at 12/23/11 2:49 AM: ------------------------------------------------------------ How about writing an Appender which would somehow be able to receive an event from arquillian, upon which it would shift the log file, like *RollingAppender's do. For example: Arquillian could set a system property with the name of the test being run. The appender would shift the files when this property changed. That could be changed through AS management: https://docs.jboss.org/author/display/AS71/CLI+Recipes {code:xml} /system-property=arq.runningTest:add(value=org.jboss.as.test.foo.BarTestCase) {code} was (Author: ozizka): How about writing an Appender which would somehow be able to receive an event from arquillian, upon which it would shift the log file, like *RollingAppender's do. For example: Arquillian could set a system property with the name of the test being run. The appender would shift the files when this property changed. I'm not sure if it's possible to set sys prop for a running JVM, so it could also be set through AS management. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka updated ARQ-710: ----------------------------- Description: What's the best way to separate server and client log messages? Currently, log messages can either go to the console, and Arquillian "forwards" them to Surefire, which causes mixed client and server messages. Or, messages can go to the server log file as usually. Which ends up in tens of megabytes long log files. So, either arq can log to an arbitrary file, or Surefire could have support for multiple logs. The later won't happen any soon I guess Arq just forwards anything to surefire. So, let's say I want to have separated log files in surefire-reports dir: * org.jboss.FooBarTestCase-client, * org.jboss.FooBarTestCase-server1, * org.jboss.FooBarTestCase-server2, ... This feature is quite important for large testsuites which produce tons of log messages, and even more for multi-node tests. was: What's the best way to separate server and client log messages? Currently, any output is redirected to Surefire. Which only creates one output. So, either arq can log to an arbitrary file, or surefire could have support for multiple logs. The later won't happen any soon I guess Arq just forwards anything to surefire. So, let's say I want to have separated log files in surefire-reports dir: * org.jboss.FooBarTestCase-client, * org.jboss.FooBarTestCase-server1, * org.jboss.FooBarTestCase-server2, ... This feature is quite important for large testsuites which produce tons of log messages, and even more for multi-node tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ARQ-710?page=com.atlassian.jira.plugin.sy... ] Ondrej Zizka updated ARQ-710: ----------------------------- Priority: Major (was: Critical) Discussed with QA dept -> lowering priority. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira