Blog

Running a professional Java EE application with JBoss EAP/Wildfly or any other application server involves a good housekeeping strategy for log files. Pay attention that most developers make the mistake to log information twice, hence in most scenarios the default texturation is kept. So the log information will be written into the console.log and server.log. Furthermore if you don’t use a files size rotator, the server.log will be rotated daily. The potential threat is, if you write the logs to separate SAN partition with limited disk space, you might crash the application, if he has no disk space left. To prevent this, one possibility is to use logrotate on Linux for the job.

If you the situation, that a lot of zero byte files exists in your current directory a simple find command, helps you to get rid of it.

vim has the behaviour, if you paste a beginning line with comment, the following lines get also commented and indented. To disable this behaviour switch to the paste mode.

If you are working with Oracle you may experience unexpected behaviors considering your Oracle’s National Language Support (NLS). Some SQL statements to setup properly for your working session.

Create (admin) user for new pdb. Set password expiration to none.

Why use PDBs? In a multitenant environment, each customer has their own PDB which is isolated from other customers’ PDBs. A clean (domain) separation. This post covers how to get rid of one. A quick example how to drop PDBs (pluggable databases) in the multi-database architecture of Oracle DB (since v12c).

A new option for Oracle Database 12c, Oracle Multitenant delivers a new architecture that allows a multitenant container database (CDB) to hold many pluggable databases (PDB). An existing database can simply be adopted with no application changes required. Sadly some old sql scripts won’t work anymore. This post describes the basic changes.

RiskShield is a fraud detection and prevention software, which is highly configurable on the server components. I got the desire to provide a stateless service, that any monitoring solution can poll and check if the RiskShield server is still available. Following configuration was done on Version 4.34a. The configuration options are provided by the manufacturer the Inform Software and described in their manual. It is an easy and straightforward example to demonstrate the configuration capability e.g. RiskShield Decision Server.

The RiskShield Servers provide the capability to filter log messages, since log4j is under the hood. Especially in early stages, the INFO or DEBUG messages may produce too much “noise” to see the misconfiguration or problems the RiskShield Server is telling you. To filter only the log entries with incorrect content (WARN, ERROR, FATAL) you can use the show option to limit to these messages.