iwui/servletd error on solaris 10/teamsite 6.7.1

I just completed a fresh install of TeamSite 6.7.1 on Solaris 10. servletd is thowing errors and refusing to come up.

# uname -a
SunOS star-auth-proto 5.10 Generic_118833-24 sun4v sparc SUNW,Sun-Fire-T200

Logs attached.

Also, I noticed that iw-webd would not come up unless the following was set in nsswitch.conf:

#hosts:      files nis
# jedm - TeamSite only works w/ the following "hosts" config
#        searching for a fix.
hosts:      files dns nis [NOTFOUND=return] files

Any thoughts about the servletd issue? I fear a support call will be in my future.

~jed

Find more posts tagged with

Comments

Phanie

iw-home/private/bin/iwuiboot had to be changed at the sudo command for the iwui user to start tomcat.

It needed the '-' to signify to login as iwui rather than just run the specified
command.

I guess you can try this.

Thanks,
Phanie

jed

iw-home/private/bin/iwuiboot had to be changed at the sudo command for the iwui user to start tomcat.

It needed the '-' to signify to login as iwui rather than just run the specified
command.

Thanks for the suggestion, but no dice--Same error.

~jed

jed

The servletd issue is resolved. t2000's come with a crypto chip which is confliting with a JVM setting used by servletd. Support sent over the following fix:

The error you are seeing with servltd may be related to the cryptographic accelerator on your server. To determine if you have one on your server, please run the cryptoadm list, http://partneradvantage.sun.com/protected/solaris10/adoptionkit/general/cryptoadm1.txt, on the system. A card is present if the output contains the following:

Kernel hardware providers:
ncp/0

If a cryptographic accelerator is present, perform the following steps:
· Open the java.security file in iw-home/tools/java/jre/lib/security.
· Replace the priority number of security providers. Make sure that the SunJCE provider has priority 1 as specified below:

security.provider.1=com.sun.crypto.provider.SunJCE

Also, make sure that the PKCS11 provider is running at a lower priority:

security.provider.6=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/sunpkcs11-solaris.cfg

Alternatively, you can comment out the PKCS provider altogether.
· Save the java.security file.
· Restart the TeamSite server.

Phanie

Interesting point & solution.