nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ERROR - Error loading JNDI context JndiContext-11

Bill Klish

OpenDeploy 6.0.2 SP1
RedHat EL 3.0

Why does this keep getting dumped every 5 minutes into my AdminServer/odadmin/log/<my server name>_adminEventReporting.log file?

2005-11-09 17:31:31,478 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:31:31,478 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:31:31,478 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:36:31,488 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:36:31,488 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:36:31,488 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:41:31,708 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:41:31,708 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:41:31,708 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:46:31,718 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:46:31,718 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:46:31,718 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:51:31,518 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:51:31,518 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:51:31,518 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:56:31,528 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:56:31,528 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:56:31,528 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 18:01:31,748 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 18:01:31,748 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 18:01:31,748 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.

Find more posts tagged with

Comments

kailash1

Hi Bill,

I think there could be some problem with your hypersonic db. Rebuild them.

Regards
Kailash

Bill Klish

This is on a brand new install. There is nothing currently being scheduled to run. How do I rebuild?

Nick_Ayles

I have exactly the same thing. I have a problem with DAS not publishing. I was wondering if the two were connected but this may just be the case that for us the eventReporting service is disabled.

Any ideas?

Migrateduser

i have the same issue and my DAS submit event isnt working...please help!

2005-11-16 11:19:12,192 [Thread-4] ERROR - Error loading JNDI context JndiContext-11.
2005-11-16 11:19:12,192 [Thread-4] INFO - Reason: Failed to connect to JNDI provider
2005-11-16 11:19:12,192 [Thread-4] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.

WoW Profile
TS 6.5 SP1
OD 6.0.2

DavidMusser

Ever Solve this?

David R Musser
Eye Street Software
540-542-5257
dmusser@eyestreet.com
Win2k, TS 6.5 SP1, OD 6.01

Migrateduser

well das is triggering, im not exactly sure the cause/specific fix though which is rather worrysome. here is what support had me do:

I would like to confirm that you have both attributes set in the [event_subsystem] section of the iw.cfg file: es_enable=true ew_enable=true If you don't have both lines, please add them and then run iwreset -a on TeamSite server and see if that helps.

1) Stop TeamSite ESS;
2) Rebuild Teamsite ESS tables, from Oracle database using SQL*Plus:
- Backup the existing tables;
- Run iw-home/eventsubsystem/conf/ddl/create_oracle.sql.
3) Stop OD;
4) clean odbase.log;
5) Start TeamSite ESS;
6) Run iwreset -ui;
7) Wait for 2 minutes;
8) Start OD.

and even though they said it wasnt necessary, i made the below change to our eventsubsystem.properties file

# (e.g. jdbc_classpath=D:\\jdbc_vendor\\jdbc_vendor.jar)
# jdbc_classpath=d:\\Interwoven\\TeamSite\\eventsubsystem\\lib\\classes12.zip
jdbc_classpath=d:\\Interwoven\\TeamSite\\eventsubsystem\\lib\\classes12.jar

WoW Profile
TS 6.5 SP1
OD 6.0.2

Migrateduser

Hi:
I got the same problem in CAP.
2007-04-16 15:15:18,590 [Thread-3] ERROR - Error loading JNDI context JndiContext-2.
2007-04-16 15:15:18,590 [Thread-3] INFO - Reason: Failed to connect to JNDI provider
2007-04-16 15:15:18,590 [Thread-3] WARN - Skipping JNDI context JndiContext-2 and all its subordinate objects.
I tried to follow arthas76's instructions, but it not work here.

CRB

i get that error because my eventreporting is not enable... and this error is not affecting the deployments in any way...

Migrateduser

OpenDeploy 6.0.2 SP1
RedHat EL 3.0

Why does this keep getting dumped every 5 minutes into my AdminServer/odadmin/log/<my server name>_adminEventReporting.log file?

2005-11-09 17:31:31,478 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:31:31,478 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:31:31,478 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:36:31,488 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:36:31,488 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:36:31,488 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:41:31,708 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:41:31,708 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:41:31,708 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:46:31,718 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:46:31,718 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:46:31,718 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:51:31,518 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:51:31,518 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:51:31,518 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 17:56:31,528 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 17:56:31,528 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 17:56:31,528 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.
2005-11-09 18:01:31,748 [Thread-2] ERROR - Error loading JNDI context JndiContext-11.
2005-11-09 18:01:31,748 [Thread-2] INFO - Reason: Failed to connect to JNDI provider
2005-11-09 18:01:31,748 [Thread-2] WARN - Skipping JNDI context JndiContext-11 and all its subordinate objects.

These messages are related to OD Reporting. The AdminServer is configured (in the adminEventReportingConfig.xml) by default to expect an ODServer with EventReporting enabled on the local machine on either port 9172 or 9173 (depending on the version of the Admin Server). If it cannot connect, it retries every five minutes. These Errors should not effect DAS or anything other than Reporting.

If you do not have Reporting enabled, or if it is on a non-default port, you can edit the adminEventReportingConfig.xml and find the element near the bottom of the document that looks like this:

[HTML][/HTML]

and remove it or change it to the correct port number.

Thanks,
Mike