Skip to Main Content

Analytics Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

[nQSError: 43081] Illegal operation attempted on a closed session.

707038Nov 17 2009 — edited Nov 17 2009
Hello everybody,

I have a HTML file which calls several dashboards, some including prompts, some without prompts. When I run the separate reports everything works fine. My call to display the dashboard is something like:

http://aserver.com:9704/analytics/saw.dll?Dashboard&NQUser=user&NQpassword=password&Options=r&PortalPath=/shared/Support/_portal/MT&Page=KPI%201&Action=Navigate&col1=Product.Product&val1=%22OHI%20Back%20Office%22&col2=Status.%22Indication%20IBC%22&val2=%22No%22

And I have several more of these in the html file. The HTML is used to rotate through some key dashboards.

My problem is the following. When I start the HTML on one or more clients, after a while the error:

Odbc driver returned an error (SQLSetStmtAttrW).
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred.
*[nQSError: 43081] Illegal operation attempted on a closed session. (HY000)*
---------------------------------------
Type: Error
Severity: 40
Time: Tue Nov 17 07:53:13 2009
File: project/webodbcaccess/odbcstatementimpl.cpp Line: 196
Properties: ThreadID-2375716
Location:
saw.querycache.executeQuery
saw.threadPool
saw.threads

shows up. This message is taken from the sawlog0.log, there's nothing in the NQQuery.log, nor in the NQServer.log.

When looking in the session management view and cursorcache I also see error:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. *[nQSError: 12002] Socket communication error at call=send: (Number=32) Broken pipe (HY000)*

The error appears randomly and seperate from every client that is starting the HTML. So on one client the error will show after a few minutes and on the other after an hour. I have been modifying all settings in the connection pool whithout result. One thing that strikes me and I can't explain is that although I'm using the Oracle Call Interface to connect to the source databases, the error has something to do with ODBC.

This is the instanceconfig.xml we are using:
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<DSN>AnalyticsWeb</DSN>
<CatalogPath>/ozg/app/oracle/product/OracleBIData/web/catalog/samplesales</CatalogPath>
<Alerts>
<ScheduleServer>aserver.com</ScheduleServer>
</Alerts>
<AdvancedReporting>
<ReportingEngine>XmlP</ReportingEngine>
<Volume>XmlP</Volume>
<ServerURL>http://aserver.com:9704/xmlpserver/services/XMLPService</ServerURL>
<WebURL>http://aserver.com:9704/xmlpserver</WebURL>
<AdminURL>http://aserver.com:9704/xmlpserver/servlet/admin</AdminURL>
<AdminCredentialAlias>bipublisheradmin</AdminCredentialAlias>
</AdvancedReporting>
<JavaHome>/usr/java/jdk1.6.0_06</JavaHome>
<BIforOfficeURL>client/OracleBIOffice.exe</BIforOfficeURL>
<CacheMaxExpireMinutes>-1</CacheMaxExpireMinutes>
<CacheMinExpireMinutes>-1</CacheMinExpireMinutes>
<CacheMinUserExpireMinutes>-1</CacheMinUserExpireMinutes>
</ServerInstance>
</WebConfig>

The connection pool at the moment has the following properties set:
Call inerface: OCI 10g/11g
Maximum Connections: 200
Shared Logon is selected with username password set (have tried deselecting this, without good result)
Enable connection pooling is selected (have tried deselecting this, without good result)
Parameters supported is selected
Isolation level Default.

We have the BI server, OC4J and presentation services running on Oracle Enterprise Linux 4 and the html on a Windows XP (SP3) client. Connecting to the repository is no problem as well as modifying it.

I can not find anything useful about this error on the Web or Oracle Support. Before logging a service request, is there somebody that may have a solution to this problem?

Logging out and then back in again solves the problem for a short while, but that's not what we want in the rotating dashboards.

Regards,
Rob
Comments
Locked Post
New comments cannot be posted to this locked post.