File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes was admin server couldn't start Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login
JavaRanch » Java Forums » Products » Websphere
Reply Bookmark "was admin server couldn Watch "was admin server couldn New topic
Author

was admin server couldn't start

yongdong zhou
Greenhorn

Joined: Jul 25, 2001
Posts: 3

Hi,
I have a WAS V3.5 running on Windows 2000, this week I couldn't
start WS admin server, I got this error message:
could not start the ibm ws adminserver service on local computer, error 1067: the process terminated
unexpectedly
The HTTP server and DB2 are running well. Since last week our
university's network is down, my machine's ip address has been
changed, I think the problem might be related to it.
The following is part of tracefile:
[01.07.24 16:17:03:093 EDT] d4cbce5a IExtendedSecu A 2001.07.24 16:17:03.093 SecurityConfiguration reportVerificationAnalysis IBM WebSphere Security Configuration component: standardClaimQOPModels = integrity
[01.07.24 16:17:03:140 EDT] d4cbce5a IExtendedSecu A 2001.07.24 16:17:03.140 SecurityConfiguration reportVerificationAnalysis IBM WebSphere Security Configuration component: delegateCredentials = methoddefined
[01.07.24 16:17:03:187 EDT] d4cbce5a IExtendedSecu A 2001.07.24 16:17:03.187 SecurityConfiguration reportVerificationAnalysis IBM WebSphere Security BasicAuth credentials will not expire.
[01.07.24 16:17:03:203 EDT] d4cbce5a IExtendedSecu A 2001.07.24 16:17:03.203 SecurityConfiguration verifyConfigurationCompleteness IBM WebSphere Security The configuration appears to be complete.
[01.07.24 16:17:03:234 EDT] d4cbce5a IExtendedSecu A 2001.07.24 16:17:03.234 SecurityConfiguration verifyConfigurationConsistency IBM WebSphere Security The configuration appears to be consistent.
[01.07.24 16:17:04:609 EDT] d4cbce5a ORBRas A 2001.07.24 16:17:04.609 IIOPSSLConnection createSSLSocket IBM WebSphere ORB JORB0025: ""SSLSocket.SSLSocket(host, port, sslContext, SSLSocket.CLIENT)"" throws [com.ibm.WAS35sslight.SSLException category=PEERCERTIFICATE error=AFTERCERTIFICATEVALIDITYPERIOD int1=0
byte1[]=
00 |.|
]. IIOPSSLConnection cannot create a new SSLSocket.
[01.07.24 16:17:04:656 EDT] d4cbce5a AdminServer F Encountered an exception in the main method java.rmi.RemoteException: ; nested exception is:
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
----- Begin backtrace for detail
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
----- Begin backtrace for detail
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
FATAL Encountered an exception in the main method {0} java.rmi.RemoteException: ; nested exception is:
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
----- Begin backtrace for detail
com.ibm.ejs.EJSException: Could not register with Location Service Daemon; nested exception is:
java.lang.ClassCastException
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
----- Begin backtrace for detail
java.lang.ClassCastException
at java.lang.Throwable.<init>(Throwable.java:84)
at java.lang.Exception.<init>(Exception.java:35)
at java.lang.RuntimeException.<init>(RuntimeException.java:39)
at java.lang.ClassCastException.<init>(ClassCastException.java:38)
at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:324)
at com.ibm.CORBA.services.lsd.LocationServiceClient.<init>(LocationServiceClient.java:140)
at com.ibm.CORBA.services.lsd.LocationServiceClient.initialize(LocationServiceClient.java:161)
at com.ibm.ejs.oa.LocationService.registerExplicit(LocationService.java:191)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:135)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:324)
at com.ibm.ejs.sm.server.ManagedServer.initializeOrb(ManagedServer.java:780)
at com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:516)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)

Can anybody help me!
Thanks!
Yongdong
Rahul Mahindrakar
Ranch Hand

Joined: Jul 28, 2000
Posts: 1825

looks like there occured some problem as stated in the code above that was fatal.
I am not able to tell you what is the problem.
The only suggestion that i have is reinstall. If you do not want to do it could you please specify what kind of installation have you undertaken ie Quick, full or custom

check up your admin.conf file if there are any inconsistencies in it with the changed ip address.

[This message has been edited by Rahul Mahindrakar (edited July 26, 2001).]
yongdong zhou
Greenhorn

Joined: Jul 25, 2001
Posts: 3

Hi, Rahul:
Thanks for the response. We had a full installation for Websphere. I also checked admin.conf file, it looks nothing related to network setting.
schrikanth
Greenhorn

Joined: Oct 16, 2001
Posts: 1
solution status: in progress
ip change
-----------
* the config files maintain the host hence change in ip never affects
-----------
i get the same error when i have enabled the security in was advance settings. (with rest of the properties default)
i seek: if i could change the setting back to DISABLE security in was...(if yes) which config file is to be edited


srikanth
Lorenzo Dee
Greenhorn

Joined: Nov 06, 2001
Posts: 3
WAS Admin Server can't start with security enabled because the DummyKeyring has already expired. It expires on July 19, 2001. For a quick fix (and to save your time from re-installing), adjust the system date of your machine (to a date before July 19, 2001), start the WAS Admin service, disable your Global Security Settings, and return the system date to normal.
You can download patches to update the DummyKeyRing file.
Please refer to http://www.ibm.com/software/webservers/security.html for more information.
The issue is described as:
- - - - -
The IBM WebSphere Application Server team has identified an issue where the certificates in the DummyKeyring on WebSphere releases 3.5.2 and 3.0.2.3 and all older releases will expire on July 19, 2001. Use of the DummyKeyring is only intended for test and development environments. Please do not use the DummyKeyring in production environments. WebSphere releases 3.5.3 and 3.0.2.4 already have the DummyKeyring with new certificates and therefore do not need this patch. All older versions should apply this patch if they are using the DummyKeyring in their test or development environments.
- - - - -
Hope this helps.
kolja hecht
Greenhorn

Joined: Nov 23, 2001
Posts: 1
hi there
thanks for the above advice ... helped a lot so far.
but once you created a new kering using that tool described in the ibm documentation (http://www-4.ibm.com/software/webservers/appserv/doc/v35/ae/infocenter/was/050506.html) where do I put it and how do I tell Websphere that there is a new keyring?
cheers
kolja.
 
 
subject: was admin server couldn't start
 
Threads others viewed
error starting WAS (startupServer.sh)
WAS 4.0 Startup Exception
Urgent Please ! Can't start adminserver with error code 10
W.A.S. 4.0 - Cannot start admin server after fix pack (GIOPVersionException)
Problen in starting WAS4 Application Server
developer file tools