Recently, a partner needs to migrate the original platform to apusic. It looks like a Java website content management platform. Of course, website presentation is a basic function.
However, we learned from the customer that when the platform was originally running under tomcat, we needed to add "-javaagent: C:/tomcat-6.0/lib/aspectjweaver" to the startup parameters. jar ", to run normally, and no matter why you need to add such a parameter (maybe some advanced features are used, this javaagent is said to be a new feature added after JDK, it is said that we can execute it before calling the main function. We can see that this parameter is added to apusic, and AAS cannot be started normally. After some hard work, I have learned that, the original use of the "javaagent" parameter in apusic, you need to make a simple modification to some other attributes, that is, in addition to the "-javaagent: C:/Apusic-6.0/lib/aspectjweaver. in addition to jar, add "-djava. util. logging. manager = "com. apusic. logging. manager. serverl Ogmanager "" to ensure that AAS can be started properly. It seems that the parameter of "javaagent" affects the default log management class and needs to be modified accordingly.