1 year ago
#377035
Roger Chu
System.out.println stop writing to WildFly server.log after run CrystalEnterprise.getSessionMgr()
The java code like this:
import com.crystaldecisions.sdk.framework.ISessionMgr;
...
System.out.println("1. before getSessionMgr");
ISessionMgr sm = CrystalEnterprise.getSessionMgr();
System.out.println("2. after getSessionMgr");
The code running well on JBoss7, JDK 1.6. That is server.log showed 1. before getSessionMgr
then 2. after getSessionMgr
.
Then it is compiled with JDK 1.8 and deploy to WildFly23, the server.log only showed 1. before getSessionMgr
but no 2. after getSessionMgr
. I know the code has been run to the end because the method output is got as expected. Only the log is missing from server.log. Afterward, System.out.println can no longer write to server.log. When the same method runs again, even the first log 1. before getSessionMgr
cannot be written.
From this post, I deleted all log4j.properties and log4j.xml in the deployment, as well as from jar inside lib, but does not help.
About the crystal report library, CrystalEnterprise is in cesession.jar Implementation-Title: Crystal Enterprise SDK session Implementation-Version: 14.2.5.2618
Any idea why this happened and how to solve this?
I have think of if crystal report library has run System.setOut and permenantly redirected the output steam to elsewhere. How can I prevent this?
java
crystal-reports
log4j
wildfly
0 Answers
Your Answer