#70 Windows - Servent 0.3.11 - XDB missing method exception

[jmk_ie]

Got following console output when attempting to start 0.3.11 servent on Windows.

Updated \ to \\ in log4j.props and servent.props and also corrected xdbserverinstalldir setting in servent.props but did not solve the problem.

Servent log output attached - DEBUG mode.

Rgds,
- John.

------------

C:\DBE\servents\servent_0_3_11\bin>REM

C:\DBE\servents\servent_0_3_11\bin>java -Djava.library.path=../dht/win32
-mx192M
-verify -ea:bamboo... -classpath
./../common/servent-common-0.3.11.jar;./../com
mon/servent-provider-0.3.11.jar;./../common/servent-server-0.3.11.jar
org.dbe.se
rvent.ServentStarter ./../servent.props
servent.properties file:
C:\DBE\servents\servent_0_3_11\bin\.\..\servent.props
--
./lib/:
./common/:
/C:/DBE/servents/servent_0_3_11/common/axis-1.2.1.jar
/C:/DBE/servents/servent_0_3_11/common/axis-jaxrpc-1.2.jar
/C:/DBE/servents/servent_0_3_11/common/axis-saaj-1.2.1.jar
/C:/DBE/servents/servent_0_3_11/common/axis-wsdl4j-1.2-RC2.jar
/C:/DBE/servents/servent_0_3_11/common/bamboo-cvs-2006-03-03.jar
/C:/DBE/servents/servent_0_3_11/common/bamboo-extensions-0.2.jar
/C:/DBE/servents/servent_0_3_11/common/bcprov-jdk15-134.jar
/C:/DBE/servents/servent_0_3_11/common/commons-cli-1.0.jar
/C:/DBE/servents/servent_0_3_11/common/commons-discovery-0.2.jar
/C:/DBE/servents/servent_0_3_11/common/commons-logging-1.0.3.jar
/C:/DBE/servents/servent_0_3_11/common/db-4.2.52.jar

/C:/DBE/servents/servent_0_3_11/common/dbe-toolkit-protocoladapter-0.5.5
.jar

/C:/DBE/servents/servent_0_3_11/common/dbe-toolkit-proxyframework-0.6.10
.jar
/C:/DBE/servents/servent_0_3_11/common/diva-26Sep02.jar
/C:/DBE/servents/servent_0_3_11/common/fada-client-5.3.8.jar
/C:/DBE/servents/servent_0_3_11/common/fada-common-5.3.8.jar
/C:/DBE/servents/servent_0_3_11/common/identity-mgmt-0.5.jar
/C:/DBE/servents/servent_0_3_11/common/identity-p2p-0.8.jar
/C:/DBE/servents/servent_0_3_11/common/identity-tools-0.7.jar
/C:/DBE/servents/servent_0_3_11/common/javax.servlet.jar
/C:/DBE/servents/servent_0_3_11/common/jrpcgen-1.0.5.jar
/C:/DBE/servents/servent_0_3_11/common/log4j-1.2.8.jar
/C:/DBE/servents/servent_0_3_11/common/oncrpc-1.0.5.jar
/C:/DBE/servents/servent_0_3_11/common/org.mortbay.jetty-4.2.24.jar
/C:/DBE/servents/servent_0_3_11/common/ostore-seda-emu-20050304.jar
/C:/DBE/servents/servent_0_3_11/common/p2p-service-0.4.jar
/C:/DBE/servents/servent_0_3_11/common/quartz-1.5.1.jar
/C:/DBE/servents/servent_0_3_11/common/saaj-api-1.1.jar
/C:/DBE/servents/servent_0_3_11/common/servent-common-0.3.11.jar
/C:/DBE/servents/servent_0_3_11/common/servent-dynamic-0.3.10.jar
/C:/DBE/servents/servent_0_3_11/common/servent-dynamic-0.3.11.jar
/C:/DBE/servents/servent_0_3_11/common/servent-provider-0.3.10.jar
/C:/DBE/servents/servent_0_3_11/common/servent-provider-0.3.11.jar
/C:/DBE/servents/servent_0_3_11/common/servent-server-0.3.11.jar
/C:/DBE/servents/servent_0_3_11/common/timer-service-0.4.jar
/C:/DBE/servents/servent_0_3_11/common/xmlrpc-1.2-b1.jar
log4j:WARN No appenders could be found for logger
(org.dbe.servent.ServentConfig
urationImpl).
log4j:WARN Please initialize the log4j system properly.
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown
Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown
Sou
rce)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.dbe.servent.ServentStarter.start(ServentStarter.java:117)
at org.dbe.servent.ServentStarter.main(ServentStarter.java:233)
Caused by: java.lang.NoSuchMethodError:
org.dbe.servent.ServentConfiguration.get
OSType()Ljava/lang/String;
at org.sun.dbe.xdb.XDBStarter.init(XDBStarter.java:163)
at
org.dbe.servent.core.ComponentManagerImpl.init(ComponentManagerImpl.j
ava:110)
at
org.dbe.servent.core.ComponentManagerImpl.init(ComponentManagerImpl.j
ava:476)
at org.sun.dbe.server.ServentImpl.<init>(ServentImpl.java:104)
... 6 more
context: org.dbe.servent.ServentContextImpl@f38798
Exception in thread "Thread-1" java.lang.NullPointerException
at
org.sun.dbe.server.ServentImpl$ShutdownHook.run(ServentImpl.java:216)

[jmk_ie]

Servent Log file - DEBUG setting

[Juanjo Aparicio Jara]

Logged In: YES
user_id=228477
Originator: NO

The log4j.props and servent.props issues with / and \\ on windows should have been mentioned in the README file. Only the servent.props is mentioned. This problem is likely to persist for some time. The location of the xdb-server is a problem caused by the lack of communication between the xdb-server installer and the ExE installer. This should be mentioned in the README as well.

Regarding the getOSType method, I see from the attachment that a servent-common-0.3.10.jar and a servent-dynamic-0.3.10.jar exist in the common directory, while I can not find those jar files in my own test installations. Please make sure that these are copied by the installer and not a remnant of old installations.

In spite of this, try just removing the 0.3.10 versions and run again, it should start. If it doesn't, please add more details in this report.

[jmk_ie]

Logged In: YES
user_id=1306099
Originator: YES

Thanks. Those two old 0.3.10 jars came with the installer. I found them in the identitymgmt.tar file (they may be elsewhere too). Removing them fixed the problem.

FYI, I noticed that run.bat now starts FADA by default - so probably need to update the readme about that too.

Also, regarding the installer, it would be great if it could update the file bin/run_dht.bat too.

Rgds, - John.

[Juanjo Aparicio Jara]

Logged In: YES
user_id=228477
Originator: NO

The run_dht.bat and run_dht.sh should be eliminated from the installer, as the default run.sh and run.bat should start the dht by default.

Please test that the run.bat/run.sh start the dht so I can remove run_dht.sh/run_dht.bat from the installer.

[jmk_ie]

Logged In: YES
user_id=1306099
Originator: YES

Yes, run_dht.bat and run_dht.sh can be removed from the installer - TCD have confirmed this.

I have confirmed that run.bat can start the dht after configuring bamboo.props and servent.props.

Note that we could not get KB/SR/RC services to run with the XDB starter core component (the services did not renew their FADA lease). We had to remove XDB core component references in servent.props and start XDB manually for these 3 services to work. There are some kb.mdrman null pointer exceptions in console output - not sure if they are significant or not.