cancel
Showing results for 
Search instead for 
Did you mean: 

Portal Runtime Error in ESS iview

Former Member
0 Kudos

Hi All,

I have implemented ESS 50.4 on EP 6.0 SP9. For SAP IAC iviws i am getting following error.

Portal Runtime Error

An exception occurred while processing a request for :

iView : pcd:portal_content/AFDB/Role/ESSRole/Office/SAPInbox/SAPInbox

Component Name : com.sap.portal.appintegrator.sap.IAC

Error in executing a process for compilation.

Exception id: 03:10_06/05/06_0031_4156850

See the details for the exception ID in the log file.

In the log file i am getting following error message.

com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "SAPEPPDB" is stopped or not started, 2) Connector service is stopped or has not been started.

Please help me to resolve the problem its very urgent.

Regards,

Vaishali

Accepted Solutions (0)

Answers (2)

Answers (2)

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Vaishali,

Nice to hear from you again.

Hope you are doing good.


I am not sure whether the error that you mentioned is the right one for this issue, but if this is the case, just to inform you that a new note has been released in this regard. Please check sap note: 1600085 as well and set the parameters accordingly.


Usually we need to see what kind of code is using the concerned connection.
Incase the issue persists, proceed as follows (it wil be better to do this when the value of the number of connections is really high, so that identifying the root cause can be easy.

1)
Set the severity of "com.sap.engine.services.connector.jca.ConnectionHashSet" to DEBUG.
You can change the severity of a location using the guide in the link below:

http://help.sap.com/saphelp_nwce72/helpdata/en/47/af551efa711503e10000000a42189c/frameset.htm

2)
- connect to the AS-JAVA via telnet
- then execute these commands:

> add connector
> switch_debug_mode SAPEPPDB (or the datasource name)
> jump (to go to the next servernode if you have multiple ones)
> add connector
> switch_debug_mode SAPEPPDB
... and so on on all the servernodes

- then wait for a few hours in order to see the connections not being
  released
- go back to the telnet console and call:

> list_conn SAPEPPDB -showTrace > server0.txt
> jump
> list_conn SAPEPPDB -showTrace > server1.txt
... and so on on all the servernodes

The serverX.txt files will be generated in the ../j2ee/cluster/server directories. Just check them to get more info.

Thank you!

____________

Kind Regards,

Hemanth

SAP AGS

0 Kudos

Hi Vaishali

Did you got the fix for this issue? If yes kindly share.

Thank you.

Regards

Raghavendra

Former Member
0 Kudos

Hi Rghavendra,

Check whether service activated or not in tcode sicf.

Regards,

PardhaSaradhi.