2:37 p.m.
Console log output in Arquillian and JBoss Container Managed 6
--------------------------------------------------------------
Key: ARQ-454
URL: https://issues.jboss.org/browse/ARQ-454
Project: Arquillian
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: JBoss Containers
Affects Versions: 1.0.0.Alpha5
Reporter: Ove Ranheim
It should be possible to configure console log output in in arquillian.xml, so the logger
would redirected server.log to console output. This would require a change in
ServiceController:
http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4...
For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive
about that, so to get proper integration tests running, this is a requirement.
This issue should probably be raised with Ryan Campbell.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [JBoss JIRA] Commented: (ARQ-454) Console log output in Arquillian and JBoss Container Managed 6
[
https://issues.jboss.org/browse/ARQ-454?page=com.atlassian.jira.plugin.sy...
]
Aslak Knutsen commented on ARQ-454:
-----------------------------------
ServerController only forks the JVM where JBoss is running. Having server.log rerouted to
another process's console out would require some kind of log4j network logger plugin..
A simpler solution is probably to configure your jboss servers logging to log what you
need from server.log to the console logger, which will end up in the ServerControllers
inputstream.. /conf/login-config.xml
Not sure if this can be done from the command line, but if it can, you can use the
javaVmArguments in the ContianerConfiguration to pass over the appropriate parameters to
the JBoss jvm.
Console log output in Arquillian and JBoss Container Managed 6
--------------------------------------------------------------
Key: ARQ-454
URL: https://issues.jboss.org/browse/ARQ-454
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JBoss Containers
Affects Versions: 1.0.0.Alpha5
Reporter: Ove Ranheim
It should be possible to configure console log output in in arquillian.xml, so the logger
would redirected server.log to console output. This would require a change in
ServiceController:
http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4...
For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive
about that, so to get proper integration tests running, this is a requirement.
This issue should probably be raised with Ryan Campbell.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:16 p.m.
New subject: [JBoss JIRA] (ARQ-454) Console log output in Arquillian and JBoss Container Managed 6
[
https://issues.jboss.org/browse/ARQ-454?page=com.atlassian.jira.plugin.sy...
]
Dan Allen commented on ARQ-454:
-------------------------------
Actually, the issue is that ServerController "pumps" the stdout and sterr to
corresponding files in server/default/log. This is hard coded behavior and there is no way
outside of ServerController to change this behavior.
If ServerController didn't route the two input streams to files, then the output would
show up in the console just as it does with other managed and embedded containers.
Here's the code in question:
{code:java}
final BufferedReader errStream = new BufferedReader(new
InputStreamReader(process.getErrorStream()));
final BufferedReader inStream = new BufferedReader(new
InputStreamReader(process.getInputStream()));
final File outFile = server.getOutputLog(); // <- output.log
initalizeLog(outFile);
final PrintWriter outlog = new PrintWriter(new FileWriter(outFile));
server.setOutWriter(outlog);
Thread outPump = new OutputPumper(inStream, outlog);
outPump.start();
final File errorFile = server.getErrorLog(); // <- error.log
initalizeLog(errorFile);
final PrintWriter errorlog = new PrintWriter(new FileWriter(errorFile));
server.setErrorWriter(errorlog);
Thread errorPump = new OutputPumper(errStream, errorlog);
errorPump.start();
{code}
Console log output in Arquillian and JBoss Container Managed 6
--------------------------------------------------------------
Key: ARQ-454
URL: https://issues.jboss.org/browse/ARQ-454
Project: Arquillian
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: JBoss AS Containers
Affects Versions: 1.0.0.Alpha5
Reporter: Ove Ranheim
It should be possible to configure console log output in in arquillian.xml, so the logger
would redirected server.log to console output. This would require a change in
ServiceController:
http://anonsvn.jboss.org/repos/jbossas/projects/server-manager/tags/1.0.4...
For Bamboo users; Bamboo Jobs are sniffing on the console log output and is sensitive
about that, so to get proper integration tests running, this is a requirement.
This issue should probably be raised with Ryan Campbell.
--
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
4563
days inactive
4914
days old
arquillian-issues@lists.jboss.org
2 comments
3 participants
participants (3)
-
Aslak Knutsen (JIRA) -
Dan Allen (JIRA)
-
Ove Ranheim (JIRA)