java.lang.ExceptionInInitializerError - server not started after restart

Hi,

I was installing a IM multiplexor on another machine. but it complained that it was not able to connect to IM server at port 45222. Thus i went into the machine with IM server installed and restart it. The following is the error encountered. Any idea what is happening?

Thanks in advance...

Exception in thread "main" java.lang.ExceptionInInitializerError

at com.iplanet.am.sdk.AMStoreConnection.<clinit>(AMStoreConnection.java:141)

at com.iplanet.im.server.IdentityRealm.<init>(IdentityRealm.java:125)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessor Impl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructor AccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:494)

at java.lang.Class.newInstance0(Class.java:350)

at java.lang.Class.newInstance(Class.java:303)

at com.iplanet.im.server.RealmManager.get(RealmManager.java:455)

at com.iplanet.im.server.RealmManager.init(RealmManager.java:435)

at com.iplanet.im.server.NMS.loadConfig(NMS.java:680)

at com.iplanet.im.server.NMS.<init>(NMS.java:463)

at com.iplanet.im.server.NMS.create(NMS.java:305)

at com.iplanet.im.server.NMS.main(NMS.java:1367)

Caused by: java.lang.NullPointerException

at com.sun.identity.sm.ServiceManager.getVersions(ServiceManager.java:411)

at com.sun.identity.sm.ServiceManager.serviceDefaultVersion(ServiceManager.java:42 7)

at com.sun.identity.sm.ServiceConfigManager.<init>(ServiceConfigManager.java :94)

at com.iplanet.am.sdk.AMCommonUtils.populateManagedObjects(AMCommonUtils.java:497)

at com.iplanet.am.sdk.AMCommonUtils.<clinit>(AMCommonUtils.java:113)

... 14 more

[1907 byte] By [justCheeChong] at [2007-11-26 9:40:18]
# 1
The exception happened because your using SSO & Acess Manager Policies and your webcontainer ( Webserver or Appserver) is not up & running. Actually this exception states IM Server is not able to establish connection with AM Server.
AmitBakhru at 2007-7-7 0:37:13 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Instant Messaging...
# 2
Hi,Yes, your right! AM should be started first, if Identity SSO is choosen.Thanks!
justCheeChong at 2007-7-7 0:37:13 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Instant Messaging...