rknox,
We have exactly the same issue since 2006. We use log4j from JCN and all the files are created with -rw-rw---- permissions. We tried all kind of tests, could not figure out a solution. Here is what we found.
- It has nothing to do with log4j. We created a file from within JCN (without using log4j), and that test file ended up with -rw-rw----
- Created a file using a simple java application and run as the same user which starts the broker. That file ended up with our umask setting which was set to 022 and the file permissions are -rw-r--r--
- Created a file using vi from the same terminal, which also ended up with 022 permission.
So except when you create a file from broker process, things are perfect. It is something about the broker that changes the permission.
Let us know if you find something interesting.
Note: For our test applications we used the JVM that is part of broker installation.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum