DSCC logs-6.3

hi
i try to access the logs through browser,i get some error with some java codes written
The following error has occurred:
java.lang.NoClassDefFoundError: sun/text/resources/LocaleData
javax.servlet.ServletException: java.lang.NoClassDefFoundError: sun/text/resources/LocaleData
org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:855)
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:784)
org.apache.jsp.jsp.DSInstanceErrorLog_jsp._jspService(DSInstanceErrorLog_jsp.java:834)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:390)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain

If you are using JDK 1.6 try to downgrade to JDK 1.5.
BR,
jairsinho

Similar Messages

DSCC showing DS as 636 disabled, unexpected error,err=1 and 80

Dear All,
Am adding new DS on an existing DSEE 6.3 environment. Up to now, created a new DS instance remotely from the DSCC server, copied configuration settings from an existing DS server. After that stage, dscc was showing remote DS server as 636 (disabled} and unexpected error. This was expected due to SSL certs are not added in the DS. Today we have added the SSL cert and Root CA. And restarted the DS, and unregistered and registered back the DS on DSCC. But still the DS status on DSCC showing as 636 disabled, unexpected error
On more investigation, able to see like ldapsearch on secure port on local DS giving result, but when doing remotely from the DSCC server to DS server, result as below
bash-3.00$ sudo ./ldapsearch -D "cn=directory manager" -w xxx -h remote-host -p 636 -Z -P /opt/SUNWdsee/AAAinst/alias/slapd-cert8.db -b "" -s base objectclass=
ldap_simple_bind: Can't contact LDAP server
SSL error -8156 (Issuer certificate is invalid.)
Please advise me here,
Below are the logs am able to see from DS access and error log, please help.
[12/Sep/2011:19:31:24 +1000] conn=233 op=0 msgId=1 - EXT oid="1.3.6.1.4.1.1466.20037"
[12/Sep/2011:19:31:24 +1000] conn=233 op=0 msgId=1 - RESULT err=0 tag=120 nentries=0 etime=0, Start TLS request accepted.Server willing to negotiate SSL.
[12/Sep/2011:19:31:24 +1000] conn=233 op=-1 msgId=-1 - SSL 128-bit RC4
[12/Sep/2011:19:31:24 +1000] conn=233 op=1 msgId=2 - BIND dn="cn=admin,cn=Administrators,cn=dscc" method=128 version=3
[12/Sep/2011:19:31:25 +1000] conn=233 op=1 msgId=2 - RESULT err=1 tag=97 nentries=0 etime=1, Can't connect to the LDAP server
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - fd=26 slot=26 LDAP connection from 58.163.116.188:64087 to 172.17.67.235
[12/Sep/2011:19:31:25 +1000] conn=234 op=0 msgId=1 - BIND dn="cn=admin,cn=Administrators,cn=dscc" method=128 version=3
[12/Sep/2011:19:31:25 +1000] conn=234 op=0 msgId=1 - RESULT err=1 tag=97 nentries=0 etime=0, Can't connect to the LDAP server
[12/Sep/2011:19:31:25 +1000] conn=234 op=1 msgId=0 - RESULT err=80 tag=120 nentries=0 etime=0
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - closing from 58.163.116.188:64087 - A1 - Client aborted connection -
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - closed.
[12/Sep/2011:19:31:25 +1000] conn=235 op=-1 msgId=-1 - fd=26 slot=26 LDAPS connection from 58.163.116.188:64088 to 172.17.67.235
[12/Sep/2011:19:31:25 +1000] conn=235 op=-1 msgId=-1 - SSL 128-bit RC4
error
12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91).
[12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91). Retrying...
[12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91).
Thanks,
Edited by: user1175091 on Sep 12, 2011 4:34 AM

Dear All,
We were able to find the root cause for the above issue, the DSEE still using the default certificate instead of new SSL host certificate.
ssl-enabled : on
ssl-rsa-cert-name : defaultCert
Could you guide me the commands for changing this to new SSL certificate, through DSCC due to environmental problem we are not able to achieve this.

Audit log level

Hello there,
When i update an attribute to be multi-value in the schema section of DSCC, i want to see update in audit log. Now with default audit log level, i can see only the following but it does not show what attribute and what value is being modified. Is there audit log level i should set to ?
dn: cn=schema
changetype: modify
replace: modifiersname
modifiersname: cn=admin,cn=administrators,cn=dscc

Hi,
You hit defect 6997464 due to the fact in-memory schema entry is managed differently from the other entries.
Please contact your local Oracle support representative to get a relief if needed.
Regards
Sylvain

DSCC Registry Not Running

Glad to see u all back again
Im trying to open GUI cosnole of LDAP 6.3. It is asking me to DSCC registry but when i have done that its giving below error.(I have logged in as a root in the browser)
starting DSCC Registry. Logs:++
Warning: instance '/var/opt/SUNWdsee/dscc6/dcc/ads' is registered in SMF.
Only root can run this command Only root can run this command Starting DSCC Registry. Logs:
Warning: instance '/var/opt/SUNWdsee/dscc6/dcc/ads' is registered in SMF.
And below is the output of DSCC status (may be it will help u to find the cause)
bash-3.00# ./dsccsetup status
DSCC Application is registered in Sun Java (TM) Web Console
DSCC Agent is registered in Cacao
DSCC Registry has been created
Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads
Port of DSCC registry is 3998
DSCC registry is not running. You may start it using:
/opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads
Thanks for look into it :P

Thanks vamshi for yur reply
It is saying that its already started. Its is production env..I took some extreme step that i have run the dsccsetup demantle and initialize commands which i never run before. Oops. And now i there are no errors coming up but I have lost all the server configured info. So i registered existing each and every server. But for couple of servers its giving error in console while im trying register as
couldnt connect DSCC agent on abc.com server and when i checked cacaodm agent ..its running fine..pls give me where else i can dig more on this
Thanks again vamshi

Dscc in a sudo environment

Hi,
We have an issue in using dscc in an environment where configuration standards forbid "service users" to have a password.
The system baseline is such that the administrator must log with their own personal unix account to the servers (think compliance to security standards). If needed, they sudo a command to the "service user" owning the application files and processes.
We have installed directory servers and proxy (as well as a tomcat server and the cacao agents) as the sjes user. The sjes user as no password. Then DSCC asks for a unix user to run command when starting or stopping an instance. It can't be the sjes user as it has no password. Is there a solution to allow administrators to use their personal unix accounts there (group permissions or so).
OS is redhat linux.
Any solutions ?

Hi,
DSCC communicates with an Agent on the machine where the instance is.
This agent needs to be able to assume the identity of the Owner of the instance (or be root) in order to start the instance under that identity.
So far the agent only knows how to authenticate a user by id and password. It cannot use sudo or other su like mechanism.
I don't think there is a solution to your problem with the current state of DSCC and agents.
Regards,
Ludovic.

DPS DSCC doesn't show operational status

I have DPS 6.3.1 running against 4 6.3.1 directory server instances. On the data sources page of DSCC, the 'operational status' column shows 'Could Not Retrieve Status' for all 4 instances. I've tried upping the log level on the DPS server to see if I could figure out what is causing this. Does anyone know how DPS (or DSCC) goes about figuring out what should be in that column?
Thanks

We don't have a single dscc for all instances. This is because of a strict 3 tier network architecture we are required to have (to the point that tier 1 dps is not allowed to talk directly to tier 3 ds so we have a tier 2 dps pass-thru). So are you saying that dscc in our tier 2 dps environment has to be able to talk to cacaoadm in tier 3 to show operational status of the ds on the dps screens? I was definitely under the impression that the monitoring as configured in dscc, has the dps instances monitoring the ds instances and the dps instances would let dscc know the status. To me, I don't care if dscc in tier 2 knows that the tier 3 ds instances are up, I want to know that the dps servers can talk to ds.

Could not contact the DSCC agent

Hello,
I'm having a little problem with my DSCC.
As described here: http://docs.sun.com/app/docs/doc/820-2761/install-bits-zip?a=view
I tried to install the dscc on a sun web application server.
Everything went fine till i tried to install a directory server instance from the dscc web application.
I got the following error:
Could not contact the DSCC agent on <hostname>. Use the command cacaoadm to check that the DSCC agent is installed and running on port 11162.
The agent is running:
-bash-3.00$ ./cacaoadm status
default instance is DISABLED at system startup.
Current retries count : 0/4
Processes:
200
Uptime: 0 day(s), 18:25
and apparently the connections are established:
-bash-3.00$ netstat -a | grep 11162
***.47776 ***.11162 49152 0 49152 0 CLOSE_WAIT
***.11162 ***.47776 49152 0 49152 0 FIN_WAIT_2
***.47791 ***.11162 49152 0 49152 0 CLOSE_WAIT
***.11162 ***.47791 49152 0 49152 0 FIN_WAIT_2
*.11162 *.* 0 0 49152 0 LISTEN
***.47734 ***.11162 49152 0 49152 0 CLOSE_WAIT
I tried to re-deploy the war several times and to restart the agent as well, but no sigar !
Anyone got an idea what I'm doing wrong ?

Couple of bugs (6710514 and 6710506) talk about a very similar problem, but no solution. Is any exception thrown for you, on the DSCC popup or in App Server's logs? Does the problem go away when you try it again? Do let us know.

DSCC- DirectoryServers- Servers displaying replication agreements?

Hello Folks -
When working through DS 6.x I noticed that sometimes the creation of a replication agreement will result in that agreement being displayed under the Servers tab within the DSCC. It will not happen for all agreements. When logging into DSCC - there are numerous searches which take place against the all registered instances - I assume to get some data to display. The searches for the replication agreements take place on all hosts - so why only some are displayed is odd. Any help would be appriciated.
Thanks
Randy
Example:
All JES Installs
Host 1: DS 6.3
Host 2: DS 6.0
ADS exists on Host 1 - both instances registered.
SSL agreement from Host1 -> Host2 = not displayed
SSL agreement from Host2 -> Host1 = dispalyed in DSCC Servers tab
Example of display:
HOST1:HOST1_SSL_PORT -secure port- (server not registered) and no instance path is displayed

Ok - this has been resolved. The issue was - when HOST1 was registered locally to the ADS it was with the command 'dsccreg add-server $instance_path'. The name of the host was then taken from the local machine (from /etc/nodename?) and was not the FQDN. Then the replication agreement was created from HOST2 -> HOST1 and the FQDN was used. The DSCC was not able to match the host names and considered the replication agreement a new host which was not registered. The resolution was to either create the replication agreement with the same value which was stored during registration - or better yet - register the local host again with the FQDN.

DSCC can't contact registry

I have installed DSEE7's DSCC on a Solaris 10 10/09 server using the Webstack Apache 2.2 /Tomcat 5.5. When I browse to <server>:8080/dscc7 I am presented with the following error:
The DSCC Registry is not running
Directory Service Control Center requires the DSCC Registry to be up and running. Starts the DSCC registry using the dsadm command.
However, I believe this is not true...
$ dsccsetup status -v
## /usr/sbin/cacaoadm is present
## /opt/SUNWdsee7/lib/jar/nquickmodule.jar is present
## Running /usr/sbin/cacaoadm list-modules -r
DSCC Agent is registered in Cacao
## Running /usr/sbin/cacaoadm status
## Running /usr/sbin/cacaoadm list-modules
## Running /usr/sbin/cacaoadm get-param network-bind-address
## Running /usr/sbin/cacaoadm get-param jmxmp-connector-port
## /opt/SUNWdsee7/bin/dsadm is present
DSCC Registry has been created
Path of DSCC registry is /var/opt/SUNWdsee7/dcc/ads
Port of DSCC registry is 3998
$ ps -ef | grep ads
noaccess 4068 1 0 Apr 12 ? 2:46 /usr/java/bin/java -server -Xmx128m -XX:+UseParallelGC -XX:ParallelGCThreads=4
noaccess 26848 1 0 16:55:53 ? 0:48 /opt/SUNWdsee7/lib/64/ns-slapd -D /var/opt/SUNWdsee7/dcc/ads -i /var/opt/SUNWds
$ svcs -p sun-tomcat5
STATE STIME FMRI
online 17:01:21 svc:/network/http:sun-tomcat5
17:01:21 27095 java
$ ps -ef | grep 27095
root 27095 1 0 17:01:21 ? 1:05 /usr/java/bin/java -Djava.util.logging.config.file=/var/opt/webstack/tomcat/5.5
So, to me it appears that tomcat is running as root, which is needed to access the registry which runs as noaccess (good). And, the registry is confirmed as running per dsccsetup. Somehow though, the webapp is not able to contact the registry.
Any tips on where to troubleshoot from here?
Thank you,
Chris

Some things to check:
- run pfiles on the ADS pid (26848) to see what port it is listening on
- is the java version 1.5.0_21 in use? If so you should move to the next version (1.5.0_22 which is 118666-24 or 118667-24 depending on which solaris you're on)
- check the logs in the ADS instance (/var/opt/SUNWdsee7/dcc/ads/logs) to see if there're any obvious errors

Dscc hangs forever when do "New Entry"/Wizard

We have DSEE 6.3 installed on windows2003, with dscc.war under Tomcat, and are having a problem where, when we do a "New Entry" (i.e., to add a new user), the new (empty/blank) window appears for the Wizard, and then nothing else happens.
When we first start up Tomcat, it seems to work ok, but after navigating around (e.g., creating one or two users), we eventually get to the point when this problem happens.
Killing the browser, and/or logging out of DSCC doesn't help. Once it's in this situation, the only thing that seems to get it working again is to bounce Tomcat. Then it works for awhile until it hangs again.
I haven't seen it myself, but one of the other guys that I work with said that he's encountering a similar problem when trying to setup replication.
Things that we have tried:
- We've confirmed that the "enablePooling" is set to false in the Tomcat conf/web.xml
- We've tried several versions of Tomcat, including 5.5.7 and 5.5.26
- We originally saw this problem with DSEE 6.2.
Has anyone encountered this problem?
Thanks,

Thanks for helping to reolve the issue .I did dsccsetup war-file-create --overwrite and redeployed in Tomcat.Now it works fine,I confirming after some tests by doing back and fro to the wizard screens.
I dont know whats wrong to it on first time deployment.For previous deployment , Wizard screens of "New Entry Managment" the text field to select entry by browsing was always disabled and now it is enabled to modify the field also.For just to verify purposes here I am giving the tomcat logs for the previuos deployment .
12:55:40 | http-808-Processor24 | com.sun.web.ui.model.CCDefaultEntityResolver:getSystemId | entity resolver systemid: file:///C:/Tomcat%205.5/descriptor.dtd
12:55:42 | http-808-Processor24 | com.sun.web.admin.directory.dcc.solo.DCCSoloSessionManagerFilter:earlyTrace2 | Request: http-hostname-808: /dscc/wizard/WizardWindow12:55:42 | http-808-Processor24 | com.sun.web.admin.directory.dcc.solo.DCCSoloSessionManagerFilter:earlyTrace2 | Request Context Path: /dscc
12:55:42 | http-808-Processor24 | com.sun.web.admin.directory.dcc.solo.DCCSoloSessionManagerFilter:earlyTrace2 | Request Servlet Path: */wizard*
12:55:42 | http-808-Processor24 | com.sun.web.admin.directory.dcc.solo.DCCSoloSessionManagerFilter:earlyTrace2 | Request Path Info : /WizardWindow
12:55:42 | http-808-Processor24 | com.sun.web.ui.common.CCSystem:getResourceContextPath | RCPATH : /dscc/com_sun_web_ui
12:55:42 | http-808-Processor24 | com.sun.web.ui.model.CCDefaultEntityResolver:getSystemId | entity resolver systemid: file:///C:/Tomcat%205.5/com_sun_web_ui/dtd/propertysheet.dtd
12:55:42 | http-808-Processor24 | com.sun.web.ui.model.CCDefaultEntityResolver:getSystemId | entity resolver systemid: file:///C:/Tomcat%205.5/descriptor.dtd
12:55:42 | http-808-Processor24 | com.sun.web.ui.common.CCSystem:getResourceContextPath | RCPATH : /dscc/com_sun_web_ui
12:55:42 | http-808-Processor24 | com.sun.web.ui.model.CCDefaultEntityResolver:getSystemId | entity resolver systemid: file:///C:/Tomcat%205.5/com_sun_web_ui/dtd/pagetitle.dtd
12:55:42 | http-808-Processor24 | com.sun.web.ui.model.CCDefaultEntityResolver:getSystemId | entity resolver systemid: file:///C:/Tomcat%205.5/descriptor.dtd
12:55:42 | http-808-Processor24 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageTitleAlertAndText | Node has no attributes.
12:55:42 | http-808-Processor24 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageActions | Could not obtain pageactions element.**12:55:42 | http-808-Processor24 | com.sun.web.ui.taglib.pagetitle.CCPageTitleTag:appendPageViewsMenu | Could not obtain pageviews element.
12:55:42 | http-808-Processor24 | com.sun.web.admin.directory.dcc.WizardServlet:onUncaughtException | uncaught exception java.lang.IllegalStateException: Cannot forward after response has been committed at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:313)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301)
     at com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:340)
     at com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:261)
     at com.sun.web.ui.view.wizard.CCWizard.handleFinishButtonRequest(CCWizard.java:798)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at com.iplanet.jato.view.command.DefaultRequestHandlingCommand.execute(DefaultRequestHandlingCommand.java:183)
     at com.iplanet.jato.view.RequestHandlingViewBase.handleRequest(RequestHandlingViewBase.java:308)
     at com.iplanet.jato.view.ViewBeanBase.dispatchInvocation(ViewBeanBase.java:802)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:740)
     at com.iplanet.jato.view.ViewBeanBase.invokeRequestHandlerInternal(ViewBeanBase.java:760)
Edited by: siteminder on Nov 17, 2008 1:17 PM
Edited by: siteminder on Nov 17, 2008 1:19 PM

[Deploy WAR File with Tomcat] Blank page after login to DSCC

i installed Sun Java System Directory Server Enterprise Edition 6.3 ( Zip Distro) in SuSe Linux 10 sp2 (64bit )
and I've deployed DSCC web console in tomcat with following installation guide
http://docs.sun.com/app/docs/doc/820-2761/6nebf1543?a=view
open browser , go to http://hostname:8080/dscc, The Directory Service Manager Login page displays.
i entered username/password , after that, nothing come up in the page...
Anyone got idea ?
Edited by: ikcat on Jan 16, 2009 12:06 AM

Usually restarting Tomcat will help. Do the Tomcat logs have anything of interest?

DS6.0 - dscc won't start.

I saw some people talking about DS6. Exciting! I have been waiting for it for a while (Actually since the private Beta phase). Now I want to setup the GUI and show the "cool web interface" to someone. But stucked at the GUI. (Why Sun web console? not web server?)
My installation was good but the port 6789 won't be up since the webconsole couldn't be up. Here are some information:
Thanks in advance.
Richard
bash-3.00# ./dsccsetup status
DSCC Application is registered in Sun Java (TM) Web Console
DSCC Agent is registered in Cacao
DSCC Registry has been created
Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads
Port of DSCC registry is 3998
bash-3.00# smcwebserver status
Sun Java(TM) Web Console is stopped
bash-3.00# smcwebserver start
Console service cannot be started.
Run "svcadm clear system/webconsole:console" to repair.
bash-3.00# svcadm clear system/webconsole:console
bash-3.00# smcwebserver start
Starting Sun Java(TM) Web Console Version 3.0.2 ...
Cannot determine if console service is running.
Check log file: /var/svc/log/system-webconsole:console.log
Run "svcs system/webconsole:console" to determine its status.
bash-3.00# svcs system/webconsole:console
STATE STIME FMRI
maintenance 14:41:07 svc:/system/webconsole:console
bash-3.00# tail /var/svc/log/system-webconsole:console.log
[ Apr 10 13:53:09 Leaving maintenance because clear requested. ]
[ Apr 10 13:53:09 Enabled. ]
[ Apr 10 13:53:09 Executing start method ("/lib/svc/method/svc-webconsole start"
Javahelp version must be at least 2.0
[ Apr 10 13:53:20 Method "start" exited with status 95 ]
[ Apr 10 14:40:56 Leaving maintenance because clear requested. ]
[ Apr 10 14:40:56 Enabled. ]
[ Apr 10 14:40:56 Executing start method ("/lib/svc/method/svc-webconsole start"
Javahelp version must be at least 2.0
[ Apr 10 14:41:07 Method "start" exited with status 95 ]
---------------------------------------------------------------------------------

Hi
In order to figure out why the dscc stopped i was looking into the following log errors .
Could you please tell me what went wrong :
From /var/svc/log/system-webconsole:console.log :
[ Sep 5 15:54:01 Executing start method ("/lib/svc/method/svc-webconsole
start") ]
[ Sep 5 16:02:46 Executing start method ("/lib/svc/method/svc-webconsole
start") ]
[ Sep 5 16:07:47 Method or service exit timed out. Killing contract 14347
[ Sep 5 16:07:47 Method "start" failed due to signal KILL ]
[ Sep 6 08:14:16 Leaving maintenance because clear requested. ]
[ Sep 6 08:14:16 Enabled. ]
[ Sep 6 08:14:16 Executing start method ("/lib/svc/method/svc-webconsole
start") ]
[ Sep 6 08:19:17 Method or service exit timed out. Killing contract 14465
[ Sep 6 08:19:17 Method "start" failed due to signal KILL ]
From console_config_log :
6-Sep-2007 | 14:28:47 | INFO | The console is running.
6-Sep-2007 | 14:30:59 | INFO | The console instance "console" is stopping.
6-Sep-2007 | 14:32:08 | INFO | The console instance "console" is starting in
admin mode.
6-Sep-2007 | 14:32:08 | INFO | Resolving shared jar files
6-Sep-2007 | 14:32:08 | INFO | Resolving login modules
6-Sep-2007 | 14:32:08 | INFO | Resolving Java options
6-Sep-2007 | 14:32:08 | INFO | Resolving web modules
6-Sep-2007 | 14:32:09 | ERROR | Error generating product images for "dccapp"
web application: Product name string is empty or null
6-Sep-2007 | 14:32:09 | INFO | Deployed web application "dccapp".
6-Sep-2007 | 14:32:09 | INFO | The console instance "console" is starting in
user mode.
6-Sep-2007 | 14:32:35 | INFO | The console is running.
From debug_console_log :
==============================================================
Java Web Console Version 3.0.2 started on Thu Sep 6 12:37:26 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 stopping on Thu Sep 6 12:42:02 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 started on Thu Sep 6 12:42:23 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 started on Thu Sep 6 13:39:04 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 stopping on Thu Sep 6 14:27:37 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 started on Thu Sep 6 14:28:25 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 stopping on Thu Sep 6 14:30:57 CEST 2007
==============================================================
==============================================================
Java Web Console Version 3.0.2 started on Thu Sep 6 14:32:09 CEST 2007
==============================================================
StandardWrapperValve[wizardWindowServlet]: Servlet.service() for servlet wizardWindowServlet threw exception
java.lang.IllegalStateException: Cannot forward after response has been committed
java.lang.IllegalStateException: Cannot forward after response has been committed
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:324)
     at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:71)
     at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:86)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:304)
     at com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:340)
     at com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:261)
     at com.sun.web.admin.directory.dcc.WizardServlet.onUncaughtException(WizardServlet.java:50)
     at com.iplanet.jato.ApplicationServletBase.fireUncaughtException(ApplicationServletBase.java:1164)
     at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:639)
     at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:473)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
     at com.sun.management.services.session.CoreSessionManagerFilter.handleRequest(CoreSessionManagerFilter.java:638)
     at com.sun.management.services.session.CoreSessionManagerFilter.doFilter(CoreSessionManagerFilter.java:401)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:197)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Sep 6, 2007 2:40:21 PM com.sun.directory.dcc.core.TopologyCacheThread abort
INFO: Aborted thread is DSLoader[MyDS_Test_SERVER:389]
StandardWrapperValve[wizardWindowServlet]: Servlet.service() for servlet wizardWindowServlet threw exception
java.lang.IllegalStateException: Cannot forward after response has been committed
java.lang.IllegalStateException: Cannot forward after response has been committed
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:324)
     at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:71)
     at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:86)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:304)
     at com.iplanet.jato.view.ViewBeanBase.forward(ViewBeanBase.java:340)
     at com.iplanet.jato.view.ViewBeanBase.forwardTo(ViewBeanBase.java:261)
     at com.sun.web.admin.directory.dcc.WizardServlet.onUncaughtException(WizardServlet.java:50)
     at com.iplanet.jato.ApplicationServletBase.fireUncaughtException(ApplicationServletBase.java:1164)
     at com.iplanet.jato.ApplicationServletBase.processRequest(ApplicationServletBase.java:639)
     at com.iplanet.jato.ApplicationServletBase.doPost(ApplicationServletBase.java:473)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
     at sun.reflect.GeneratedMethodAccessor68.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:161)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:245)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
     at com.sun.management.services.session.CoreSessionManagerFilter.handleRequest(CoreSessionManagerFilter.java:638)
     at com.sun.management.services.session.CoreSessionManagerFilter.doFilter(CoreSessionManagerFilter.java:401)
     at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:243)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:272)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:217)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:197)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:50)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:156)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:152)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Thread.java:595)
Thanks in advance

Hostname change: Failed to contact DSCC registry

Dear all,
we have installed ODSEE 11.1.1.5 under Solaris x86 10 08/11 successfully
ie were able to log into DSCC as Directory Service Manager.
After changing the system's hostname from OLD to NEW we can't now use
the DSCC again because there is this message after putting in the directory service
password:
Failed to contact DSCC regisrty. Make sure that the DSCC registry is online and
listening on ldap://*OLD*:3998
How can we arrange it that the registry is listening now to ..//_NEW_:3998?
Should we use 'dsccsetup dismantle/initialize?
Many thanks in advance for any hint!
Rainer

1) "dsconf export -p 3998 -c cn=dscc /your_DSEE_INSTALL_PATH/var/dcc/ads/ldif/export.ldif" or something like that will do the job. You can also use "dsadm export" with a slightly different syntax. The main difference is that dsconf works offline I believe, so you need to stop the DSCC registry before.
2) Edit the LDIF export and remove the unwanted entries. Since you'll have to dismantle/reinitialize the DSCC registry, there's no need to keep the DSCC registry up. Moreover, you can safely stop it without any impact on your existing DS servers. The DSCC is just required for some dsadm/dpadm/dsconf/dpconf/dsccsetup commands and the GUI, but it's not a requirement at all to run your DS instances.

Directory Proxy Server java.io.IOException with DSCC

Using the DSCC to create a new proxy server instance, the proxy server can't be accessed. These messages are the result of clicking on the "Enable Access" button after proxy server creation to try and gain ldap access to the server. There seems to be a problem with the java SSL engine where connections are being terminated before data is sent. Basically premature SSL termination problems. The relevant logs are:
access:
[08/Oct/2008:16:49:21 -0700] - PROFILE - INFO - conn=11 assigned to connection handler cn=default connection handler, cn=connection handlers, cn=config
[08/Oct/2008:16:49:21 -0700] - OPERATION - INFO - conn=11 op=0 BIND dn="cn=admin,cn=administrators,cn=dscc" method="SIMPLE" version=3
[08/Oct/2008:16:49:21 -0700] - OPERATION - INFO - conn=11 op=0 BIND RESPONSE err=1 msg="Unable to retrieve a backend BIND connection" etime=0
[08/Oct/2008:16:49:21 -0700] - DISCONNECT - INFO - conn=11 reason="other" msg="Exception caught while polling client connection LDAPS.128.114.115.28.56465 -- java.io.IOException: Received CLOSED during initial handshaking"
error:
[08/Oct/2008:16:57:24 -0700] - BACKEND - WARN - Can't retrieve LDAP schema (LDAP error code: 32) No data view were found to process the search request.
[08/Oct/2008:16:57:24 -0700] - BACKEND - WARN - No data source available for ADD,BIND,COMPARE,DELETE,MODIFY,SEARCH, in data source pool cn=dscc admin data source pool,cn=datasource pools,cn=config .You may want to check whether the configuration of this pool contains at least one data source enabled and with non-zero weights.
[08/Oct/2008:16:57:24 -0700] - BACKEND - WARN - No data source available for ADD,BIND,COMPARE,DELETE,MODIFY,SEARCH, in data source pool cn=dscc admin data source pool,cn=datasource pools,cn=config .You may want to check whether the configuration of this pool contains at least one data source enabled and with non-zero weights.
[08/Oct/2008:16:57:24 -0700] - BACKEND - WARN - Can't retrieve LDAP schema (LDAP error code: 32) No data view were found to process the search request.

Hi,
does this show for any project you try to run, or just for a specific? If it does, does the same issue show after a fresh install of JDeveloper (you don't need to delete the existing instance for this) ?
Frank

Administrative Limit Exceeded - DSCC Entry Management Tab

DS 6.3.1
When performing searches in the DSCC under the Entry Management tab I am getting an error that says Administrative Limit Exceeded. I know this is being caused by the global searchlimit and/or lookthroughlimt settings. I can set those to unlimited to resolve the issue but I don't want to open those values up to all users. I also know that I can set these same limits on a per entry basis by adding the nssizelimit and nslookthroughlimit attributes with -1 values to the particular user's entry.
In the DSCC however, the user that is binding to my DS instance and performing the searches is: cn=admin,cn=Administrators,cn=dscc
This user exists in the DSCC registry, not my DS instance. I assume it can BIND to my DS instance via the Pass Through Authentication plugin. I have tried setting both the nssizelimt and nslookthroughlimit attributes to -1 in that user's entry in the DSCC registry but it doesn't work like it does when I set those to an entry that exists in my DS instance. I'm guessing the Pass Through Authentication plugin doesn't look for those attributes and/or doesn't return them to my DS instance.
Is there a way to set the sizelimit and lookthrough limits for "cn=admin,cn=Administrators,cn=dscc" so I don't get the error in the DSCC and where I don't have to open up those limits globally? Is there a best practice for this other than telling me that the Entry Management tab is not the best place to be doing such tasks? I'm aware of that but this is actually for a customer who desires to use the Entry Management section to search for and periodically manage his entries.
Thanks in advance.

The behaviour you're observing is documented in a bug. Unfortunately it's not implemented since the 5.2 days and not targeted for 7.0 either. You could create a local admin user and assign rights, or use a tool like "Apache Directory Studio" and log in as directory manager.
4534340 reslimit should provide interface for chaining and PTA plugin

DSCC logs-6.3

Similar Messages

Maybe you are looking for