on 05-25-2011 1:53 PM
Hi Everyone,
I've a piece of code, where I open a crystal report using RAS, edit a particular formula, and save it back. Till yesterday it was running fine (from the same env.), but now the code just hangs on the openDocument method. I waited for more than 20 mins, and it was still the same, and it doesn't throw any exceptions. (Nothing has changed in the environment). The following is the piece of code that I use.
IReportAppFactory reportAppFactory = (IReportAppFactory) boeSession.getService("RASReportFactory");
ReportClientDocument rcd = reportAppFactory.openDocument(myInfoObj, 0, java.util.Locale.US);
The infoObject seems to be valid, and am able to print the attributes of it.
I restarted the server and the machine from which I execute this program. But no luck (All the BO servers are running fine)
Version details: BO XI R 3.1 SP3
Any info on this would help much.
Thanks.
First thing I'd do is trace the RAS server.
Sincerely,
Ted Ueda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just to clarify my recommendation - when the SDK sends a request to the RAS server, the SDK opens a listener port on its machine, to wait for the RAS server to communicate back with results.
The default timeout is 10 minutes for this listener port.
Since it waited longer than that, my assumption here is that the RAS server did respond, but the complete results took unexpectedly longer. So it'll be interesting to see what RAS server was doing.
Sincerely,
Ted Ueda
Thanks Ted for your inputs.
I did a trace on the RAS and the following is the error message logged.
ErrorLog 2011 5 30 5:46:15.772 4664 7528 (*:0) (.\dts\corbaclientrequestcommadapter.cpp:419): CORBA communication failure: reason[error number WSAETIMEDOUT] minor[1330577418] reqType[154] agentId=[""]
ErrorLog 2011 5 30 5:46:16.850 4664 7528 (*:0) (.\dts\corbaclientrequestcommadapter.cpp:320): Resending result to client. reqType=154 agentId="" nRetryInterval=1000
The above two messages got repeated, until I had stopped the server.
And interestingly, even after I had stopped the SIA, the client code remained the same, and I had to force quit it.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.