craig_welton
Legendary Poster
This is not on your TR, but the idea is the same...
Try turning on the LOG2 settings in jdelog.properties (should be set to LEVEL=DEBUG, COMPONENT=ALL). Set the FILE to somewhere easy (I create a c:\jdelogs\ folder so mine is c:\jdelogs\jasdebug.log)
Restart the local JAS and make sure that file is logging stuff (it will grow quickly).
Try to retrieve the PDF.
In the log, you should see a call to ube.myService(): Servlet UBE service called server...
Start digging below that. I see an entry with "Resolved database object F986110 to data source " and the server map data source
There may be a clue as to why the OCM cache lookup doesn't seem to be working.
Comparing the working log to the failing log could help.
BTW, what is APPLIB9? The default TBLE data source?
Craig
Try turning on the LOG2 settings in jdelog.properties (should be set to LEVEL=DEBUG, COMPONENT=ALL). Set the FILE to somewhere easy (I create a c:\jdelogs\ folder so mine is c:\jdelogs\jasdebug.log)
Restart the local JAS and make sure that file is logging stuff (it will grow quickly).
Try to retrieve the PDF.
In the log, you should see a call to ube.myService(): Servlet UBE service called server...
Start digging below that. I see an entry with "Resolved database object F986110 to data source " and the server map data source
There may be a clue as to why the OCM cache lookup doesn't seem to be working.
Comparing the working log to the failing log could help.
BTW, what is APPLIB9? The default TBLE data source?
Craig