our application is deployed on jboos As 4.0x, we face some issues in jboss logging.. whenever the server is
restarted,
jboss stops logging , and there is no update in server.log. After that it is not updating the log file.
then we do touch cmd on log4j.xml, so that it creates the log files again.
Help me in fixing the issue we can't do touch everytine.
we face this issue in both the nodes.
I doubt if you have turned off any one of JBoss services. Please recheck if all JBoss services are ON.
Related
I just want to double-check what the exact steps are for updating the MQ Resource Adapter in JBoss.
I can find a lot of guides on how to deploy it and configure it, but none on updating it.
I have got JBoss 6.3 and MQ RA 7.5.0.5 (need to update to RA 7.5.0.9). Is it just a matter of stopping the application server, removing wmq.jmsra.rar from the deployment directory, copying the new wmq.jmsra.rar version in there and starting up JBoss?
Moving from 7.5.0.5 to 7.5.0.9 is a very small update so I wouldn't expect there would be any configuration updates required. The process you outlined (i.e. stop JBoss, update rar, start JBoss) should be perfectly fine.
we've an application, running in JBOSS EAP 6.4, generating a lot of logs. So we decided to give the application its own log, rotating each hour.
The application uses SFL4J, which is compatible with JBOSS Logging.
As we can't change parameters on JBOSS config we decided to use the logging per deployment feature and added, following the developers manual, a file logging.properties in the classpath, with the File Handler set up as below
handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler
handler.FILE.level=ALL
handler.FILE.formatter=PATTERN
handler.FILE.properties=append,autoFlush,enabled,suffix,fileName
handler.FILE.constructorProperties=fileName,append
handler.FILE.append=true
handler.FILE.autoFlush=true
handler.FILE.enabled=true
handler.FILE.suffix=.yyyy-MM-dd-HH
handler.FILE.fileName=${jboss.server.log.dir}\\pfl.log
While in DEV station everything works as expected (JBOSS Developer Studio 7.1.1 with JBOSS EAP 6.1), in production and test JBOSS generates correctly the pfl.log file and the hourly backups, BUT the pfl.log is never made empty. So it's growing indefinitely (and so the hourly files). Also we noted that the same behavior happens using dayly rotating logs
handler.FILE.suffix=.yyyy-MM-dd
This is getting us crazy.. How can we solve this ? Where can be the problem ? Did we make any config mistakes ?
JBoss startup and Server logs are not getting updated completely like started in XXXX ms. But all the services are being deployed successfully. Is there any way to debug why the logs are not printing?
Thanks,
Kusuma
Just check on your the logging subsystem configuration in your standalone.xml.
If that's not the issue, this is probably a problem with your application configuration and not JBoss, probably you just have to exclude some logging libraries in your jboss-deployment-structure.xml, to use the provided and not the jboss instance libs.
We are using Wildfly 8.2.0 Server and sometimes the hot deployment doesn't work, it says EAR/WAR module has been deployed but changes are not reflecting until we restart our Application Server. Please let me know if anyone has faced this issue and how to resolve this. Thanks.
A strange problem occurred yesterday on a production system which has been running fine for weeks on a JBoss 4.2.3 application server: the JAR file containing the web application was no longer in the deployment folder (so the clients could no longer access the application). The server is running on a Windows box.
There was no indication of undeployment in the server logs. Normally JBoss detects if somebody deletes (or moves) a deployed web application file and executes the standard undeployment procedure, so there would be a log entry in this case.
Other web applications on the same system continued to run fine, so it was only this JAR file which simply disappeared.
Has somebody seen a similar problem with web applications on JBoss?
I'd bet my shoes that's not possible to happen spontaneously.
Check your security settings - didn't you leave JMX console accessible? Etc.