Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
Java Agent prevents encoding parameters upon post-parameter processing
Description
During enabling JavaEE request trace at app#1 at WebSphere JVM#1.c1 & JVM#1.c2 (clustering). The app#2 at JVM#2 has incorrect database encoding -- means app#2 insert Thai characters into oracle database as question mark symbol '?'. I have proved 3 times, if not enable JavaEE request trace, the app#2 working fine -- Thai characters are correct. But if enable trace app#2 always insert Thai characters as '?'
Sign In Required
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Welcome to Quest Support
You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.
The Quest Software Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.