The issue is that you should never invoke blappserv directly. Always use the init.d scripts to stop, start, and restart. Otherwise you mess up ownership
1 of 1 people found this helpful
also, the 'bladmin' account that owns the files is the OS local user account, it has nothing to do w/ the 'BLAdmins:BLAdmin" role:user in the application.
Ok that makes sense now. Thanks
I run Suse BLApp servers and I have experienced exactly the same problem several times now.
And I have only ever used the init.d scripts to stop and start these.
After I did a bit of reviewing around when I experienced this issue it appears to be after I've applied a hotfix.
I'm going to check this the next time I apply one.