Migration Solutions for ColdFusion Applications to ASP.NET
      
New Atlanta Product Forums Profile | Search | Login | RSS
New Topic Reply   Previous Page  Page: 1 2   Next Page

Thread: Starting Iplanet >>Failed to find main java class
Created on: 05/11/10 08:01 AM Replies: 20
yashgoley


Joined: 05/11/10
Posts: 15
Starting Iplanet >>Failed to find main java class
05/11/10 8:01 AM

Hi ALL,

I have installed ServletExec5.0 after SunOne Java Web server 6.1 SP5 on our Solaris 10 Sparc server.

After installing servlet when i restarted webserver i got this error.

[11/May/2010:03:14:26] info (28195): ServletExec: Collect web server signal settings
[11/May/2010:03:14:26] info (28195): ServletExec: LD_LIBRARY_PATH is:
[11/May/2010:03:14:26] info (28195): ServletExec: /usr/lib/lwp:/app/iplanet/web/bin/https/lib:/app/iplanet/web/bin/https/jdk/
jre/lib/sparc/server:/app/iplanet/web/bin/https/jdk/jre/lib/sparc:/app/iplanet/web/bin/https/jdk/jre/lib/sparc/native_threads
::/usr/lib/mps/secv1:/usr/lib/mps:/usr/lib/mps/sasl2:/usr/lib:/usr/java/jre/lib/sparc:/usr/java/lib/sparc:/usr/java/jre/lib/s
parc:/usr/java/jre/lib/sparc/native_threads:/usr/java/jre/lib/sparc/classic:/usr/java/lib/sparc:/usr/java/lib/sparc/native_th
reads:/usr/java/lib/sparc/classic
[11/May/2010:03:14:26] info (28195): ServletExec: CLASSPATH is:
[11/May/2010:03:14:26] info (28195): ServletExec: :/app/NewAtlanta/ServletExecNSAPI/lib/activation.jar:/app/NewAtlanta/Servle
tExecNSAPI/lib/mail.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jaxp-api.jar:/app/NewAtlanta/ServletExecNSAPI/lib/dom.jar:/app/N
ewAtlanta/ServletExecNSAPI/lib/sax.jar:/app/NewAtlanta/ServletExecNSAPI/lib/xercesImpl.jar:/app/NewAtlanta/ServletExecNSAPI/l
ib/xalan.jar:/app/NewAtlanta/ServletExecNSAPI/lib/xsltc.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jstl.jar:/app/NewAtlanta/Ser
vletExecNSAPI/lib/standard.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jdbc2_0-stdext.jar:/app/NewAtlanta/ServletExecNSAPI/lib/c
ommons-el.jar:/app/NewAtlanta/ServletExecNSAPI/lib/servlet.jar:/app/NewAtlanta/ServletExecNSAPI/lib/ServletExec50.jar:/app/Ne
wAtlanta/ServletExecNSAPI/lib/ServletExecAdmin.jar:/app/iplanet/web/bin/https/jdk/lib/tools.jar:/app/NewAtlanta/ServletExecNS
API/https-usdasapp2001.us.ingrammicro.com/classes
[11/May/2010:03:14:26] info (28195): ServletExec: About to read /app/NewAtlanta/ServletExecNSAPI/https-usdasapp2001.us.ingram
micro.com/ServletExecData/VMSettings.pref...
[11/May/2010:03:14:26] info (28195): ServletExec: ServletExecNSAPI::readFile() failed to open /app/NewAtlanta/ServletExecNSAP
I/https-usdasapp2001.us.ingrammicro.com/ServletExecData/VMSettings.pref.
[11/May/2010:03:14:26] info (28195): ServletExec: Using default JavaVM settings.
[11/May/2010:03:14:26] info (28195): ServletExec: -Xms4194304
[11/May/2010:03:14:26] info (28195): ServletExec: -Xmx67108864
[11/May/2010:03:14:26] info (28195): ServletExec: Enabled JITC with default compiler
[11/May/2010:03:14:26] info (28195): ServletExec: Additional VM options:
[11/May/2010:03:14:26] info (28195): ServletExec: -Djava.naming.factory.initial=com.newatlanta.servletexec.InitialContextFact
ory
[11/May/2010:03:14:26] info (28195): ServletExec: JavaVM running.
[11/May/2010:03:14:26] info (28195): CORE3282: stdout: ServletExec: caught exception - java.lang.Exception: ServletExec: Need
write access to /app/NewAtlanta/ServletExecNSAPI/https-usdasapp2001.us.ingrammicro.com/ServletExecData/
[11/May/2010:03:14:26] warning (28195): CORE3283: stderr: java.lang.Exception: ServletExec: Need write access to /app/NewAtla
...skipping...
parc:/usr/java/jre/lib/sparc/native_threads:/usr/java/jre/lib/sparc/classic:/usr/java/lib/sparc:/usr/java/lib/sparc/native_th
reads:/usr/java/lib/sparc/classic
[11/May/2010:04:35:10] info (28655): ServletExec: CLASSPATH is:
[11/May/2010:04:35:10] info (28655): ServletExec: :/app/NewAtlanta/ServletExecNSAPI/lib/activation.jar:/app/NewAtlanta/Servle
tExecNSAPI/lib/mail.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jaxp-api.jar:/app/NewAtlanta/ServletExecNSAPI/lib/dom.jar:/app/N
ewAtlanta/ServletExecNSAPI/lib/sax.jar:/app/NewAtlanta/ServletExecNSAPI/lib/xercesImpl.jar:/app/NewAtlanta/ServletExecNSAPI/l
ib/xalan.jar:/app/NewAtlanta/ServletExecNSAPI/lib/xsltc.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jstl.jar:/app/NewAtlanta/Ser
vletExecNSAPI/lib/standard.jar:/app/NewAtlanta/ServletExecNSAPI/lib/jdbc2_0-stdext.jar:/app/NewAtlanta/ServletExecNSAPI/lib/c
ommons-el.jar:/app/NewAtlanta/ServletExecNSAPI/lib/servlet.jar:/app/NewAtlanta/ServletExecNSAPI/lib/ServletExec50.jar:/app/Ne
wAtlanta/ServletExecNSAPI/lib/ServletExecAdmin.jar:/app/iplanet/web/bin/https/jdk/lib/tools.jar:/app/NewAtlanta/ServletExecNS
API/https-usdasapp2001.us.ingrammicro.com/classes
[11/May/2010:04:35:10] info (28655): ServletExec: About to read /app/NewAtlanta/ServletExecNSAPI/https-usdasapp2001.us.ingram
micro.com/ServletExecData/VMSettings.pref...
[11/May/2010:04:35:10] info (28655): ServletExec: ServletExecNSAPI::readFile() failed to open /app/NewAtlanta/ServletExecNSAP
I/https-usdasapp2001.us.ingrammicro.com/ServletExecData/VMSettings.pref.
[11/May/2010:04:35:10] info (28655): ServletExec: Using default JavaVM settings.
[11/May/2010:04:35:10] info (28655): ServletExec: -Xms4194304
[11/May/2010:04:35:10] info (28655): ServletExec: -Xmx67108864
[11/May/2010:04:35:10] info (28655): ServletExec: Enabled JITC with default compiler
[11/May/2010:04:35:10] info (28655): ServletExec: Additional VM options:
[11/May/2010:04:35:10] info (28655): ServletExec: -Djava.naming.factory.initial=com.newatlanta.servletexec.InitialContextFact
ory
[11/May/2010:04:35:10] info (28655): ServletExec: JavaVM running.
[11/May/2010:04:35:10] info (28655): CORE3282: stdout: ServletExec: caught exception - java.lang.Exception: ServletExec: Need
write access to /app/NewAtlanta/ServletExecNSAPI/https-usdasapp2001.us.ingrammicro.com/ServletExecData/
[11/May/2010:04:35:10] warning (28655): CORE3283: stderr: java.lang.Exception: ServletExec: Need write access to /app/NewAtla
nta/ServletExecNSAPI/https-usdasapp2001.us.ingrammicro.com/ServletExecData/
[11/May/2010:04:35:10] warning (28655): CORE3283: stderr: at com.newatlanta.servletexec.ServletExec.Init(ServletExec.ja
va:604)
[11/May/2010:04:35:10] warning (28655): CORE3283: stderr: at com.newatlanta.servletexec.ServletExec.Init(ServletExec.ja
va:545)
[11/May/2010:04:35:10] info (28655): ServletExec: Init failed, code = 3
[11/May/2010:04:35:10] info (28655): ServletExec: InitMsg OK
[11/May/2010:04:35:10] info (28655): ServletExec: java.lang.Exception: ServletExec: Need write access to /app/NewAtlanta/Serv
letExecNSAPI/https-usdasapp2001.us.ingrammicro.com/ServletExecData/
[11/May/2010:04:35:10] info (28655): ServletExec: ready and waiting.
[11/May/2010:04:35:10] info (28655): CORE4006: JVM instance has already been created within the process, numVMs=1
[11/May/2010:04:35:10] failure (28655): CORE4011: Internal error: Unable to locate class: com/iplanet/ias/server/J2EERunner
[11/May/2010:04:35:10] failure (28655): CORE3187: Late initialization failed: Error running init function load-modules: initi
alization of /app/iplanet/web/bin/https/lib/libj2eeplugin.so failed
[11/May/2010:04:35:10] info (28655): ServletExec: Netscape server is exiting!
[11/May/2010:04:35:10] info (28655): ServletExec: Shutting down!
[11/May/2010:04:35:10] info (28655): ServletExec: Failed to find main java class.


Can anyone help me out With the proper solution.

Thanks
yash
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/11/10 2:52 PM

I see 2 problems.
The first appears to be a permissions issue.

The evidence is:

ServletExec: ServletExecNSAPI::readFile() failed to open /app/NewAtlanta/ServletExecNSAP
I/https-usdasapp2001.us.ingrammicro.com/ServletExecData/VMSettings.pref.

-and-

Need write access to /app/NewAtlanta/Serv
letExecNSAPI/https-usdasapp2001.us.ingrammicro.com/ServletExecData/


Perhaps you are not starting your SunONE 6.1 server under an account that has enough permissions?


The 2nd issue I see is:

CORE4006: JVM instance has already been created within the process, numVMs=1
[11/May/2010:04:35:10] failure (28655): CORE4011: Internal error: Unable to locate class: com/iplanet/ias/server/J2EERunner
[11/May/2010:04:35:10] failure (28655): CORE3187: Late initialization failed: Error running init function load-modules: initi
alization of /app/iplanet/web/bin/https/lib/libj2eeplugin.so failed



which suggests to me that you did not disable SunONE's Built-in Servlet/JSP engine *before* you installed SE 5.0 NSAPI.

I will make the following recommendations to you:

1. Uninstall SE 5.0 NSAPI.
2. Restore obj.conf and magnus.conf to their pre-ServletExec state (backups of those files were made by the SE 5.0 NSAPI installer which you may use to restore them).

3. Make sure your SunONE is working with no SE in the picture. Make sure you can start and stop it and that it can serve you a simple hello.html file

4. Disable SunONE's built-in Servlet/JSP Engine.
The best information for this is in section 3.3.3 of the SE 5.0 Installation Guide.
Here is a copy/paste for your convenience:

=============
3.3.3 Disable the Built-In Servlet Engine (Sun ONE Web Server 6.1)
For Sun ONE Web Server 6.1, the built-in servlet engine is enabled by default. You must disable the built-in servlet engine before installing ServletExec/NSAPI.

To disable the Servlet Engine

1. From the Sun ONE Administration Server home page, click the appropriate server.
ServletExec 5.0 Installation Guide 22
3. SERVLETEXEC/NSAPI: NES/IWS/SUN ONE PLUGIN (WINDOWS)
2. On the Server Manager page, click the Java tab.
3. On the Enable/Disable Servlets/JSP page, disable Java globally and for all virtual servers, and click OK.
4. On the resulting page, click Save and Apply
=============


5.
Repeat my recommendation step #3 to ensure that your SunONE 6.1 webserver is still operational.

6. Consider installing SE 6.0 AS or SE 5.0 AS instead of SE 5.0 NSAPI.

With SE AS the JVM runs in a process that is separate from the SunONE process which may not only help to avoid these kinds of issues but will also give you more freedom in terms of the JVM version that is used.
For example go here:
http://www.newatlanta.com/c/support/servletexec/self_help/faq/detail?faqId=221

and search that FAQ for "1.4.1" (no quotes) and read what it says.
With SE NSAPI you are somewhat tied to the JVM that SunONE uses. With SE AS you can download JVM 1.4 or 1.5 from java.sun.com and have SE AS use that.

In my personal opinion, SE AS is architecturally superior to SE NSAPI.

To better understand why I say that, please see:
http://www.newatlanta.com/products/servletexec/product_info/configurations.jsp

I hope all that helps you.
Let me know how it goes.

Matt
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 8:04 AM

Thanks Mattm,
i am trying your recommendations , But didn't find how to stop JVM of Iplanet webserver from Command Line.Bcoz i am working from remote.
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/12/10 9:59 AM

You should still be able to point a browser to the SunONE Admin server and use it's browser-based admin to disable the built-in Servlet/JSP engine as described in the SE Installation Guide.

If you can't do that and only have the command line then let's be clear...
You don't want to stop the JVM of your SunONE 6.1 web server. You want to:

1. turn the webserver off
2. restore obj.conf and/or magnus.conf to their pre-servletexec state.
3. turn the webserver back on and make sure it works
4. turn the webserver off
5. make changes to it's obj.conf and/or magnus.conf files to disable the built-in Servlet/JSP Engine
6. turn the webserver back on and make sure it works
7. turn the webserver off
8. install SE 6.0 AS or SE 5.0 AS

Even with the built-in Servlet/JSP engine disabled, your SunONE 6.1 webserver will still make use of it's own JVM for the purpose of serving the SunONE Admin pages.

Matt
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 12:28 PM

Thanks,

Can you please more elaborate what to edit in "obj.conf" and "magnus.conf" to stop iplanet's built in JSP engine.As i am getting confused
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 12:54 PM

Obj.conf

<Object name="default">
AuthTrans fn="match-browser" browser="*MSIE*" ssl-unclean-shutdown="true"
NameTrans fn=pfx2dir from=/sitemindercgi dir="/app/siteminder/admin" name="cgi"
NameTrans fn=pfx2dir from=/siteminder dir="/app/siteminder/admin"
NameTrans fn="ntrans-j2ee" name="j2ee"
NameTrans fn=pfx2dir from=/mc-icons dir="/app/iplanet/web/ns-icons" name="es-internal"
NameTrans fn=document-root root="$docroot"
PathCheck fn=unix-uri-clean
PathCheck fn="check-acl" acl="default"
PathCheck fn=find-pathinfo
PathCheck fn=find-index index-names="index.html,home.html,index.jsp"
ObjectType fn=type-by-extension
ObjectType fn=force-type type=text/plain
Service method=(GET|HEAD) type=magnus-internal/imagemap fn=imagemap
Service method=(GET|HEAD) type=magnus-internal/directory fn=index-common
Service method=(GET|HEAD|POST) type=*~magnus-internal/* fn=send-file
Service method=TRACE fn=service-trace
Error fn="error-j2ee"
AddLog fn=flex-log name="access"
</Object>

<Object name="j2ee">
Service fn="service-j2ee" method="*"
</Object>

<Object name="cgi">
ObjectType fn=force-type type=magnus-internal/cgi
Service fn=send-cgi user="$user" group="$group" chroot="$chroot" dir="$dir" nice="$nice"
</Object>

<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>

<Object name="send-compressed">
PathCheck fn="find-compressed"
</Object>

<Object name="compress-on-demand">
Output fn="insert-filter" filter="http-compression"
</Object>
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 12:55 PM

magnus.conf


<Object name="cgi">
ObjectType fn=force-type type=magnus-internal/cgi
Service fn=send-cgi user="$user" group="$group" chroot="$chroot" dir="$dir" nice="$nice"
</Object>

<Object name="es-internal">
PathCheck fn="check-acl" acl="es-internal"
</Object>

<Object name="send-compressed">
PathCheck fn="find-compressed"
</Object>

<Object name="compress-on-demand">
Output fn="insert-filter" filter="http-compression"
</Object>

$ ls
default-web.xml magnus.conf.servletinstall obj.conf.clfilter
keyfile mime.types obj.conf.servletinstall
login.conf nsfc.conf server.policy
magnus.conf obj.conf server.xml
magnus.conf.clfilter obj.conf.2010-05-11-12-04-28.bak server.xml.clfilter
$ more magnus.conf
#
# The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED.
# They will not be supported in future releases of the Web Server.
NetsiteRoot /app/iplanet/web
ServerName sm
ServerID https-sm
#
RqThrottle 128
DNS off
Security off
PidLog /app/iplanet/web/https-sm/logs/pid
User http
StackSize 131072
TempDir /tmp/https-sm-f3267595

Init fn=flex-init access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-r
equest%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
Init fn="load-modules" shlib="/app/iplanet/web/bin/https/lib/libj2eeplugin.so" shlib_flags="(global|now)"
Init fn="init-cgi" SM_ADM_UDP_PORT="44444" SM_ADM_TCP_PORT="44444"
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 1:01 PM

Sorry correct magnus.conf is


# The NetsiteRoot, ServerName, and ServerID directives are DEPRECATED.
# They will not be supported in future releases of the Web Server.
NetsiteRoot /app/iplanet/web
ServerName sm
ServerID https-sm
#
RqThrottle 128
DNS off
Security off
PidLog /app/iplanet/web/https-sm/logs/pid
User http
StackSize 131072
TempDir /tmp/https-sm-f3267595

Init fn=flex-init access="$accesslog" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-r
equest%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"
Init fn="load-modules" shlib="/app/iplanet/web/bin/https/lib/libj2eeplugin.so" shlib_flags="(global|now)"
Init fn="init-cgi" SM_ADM_UDP_PORT="44444" SM_ADM_TCP_PORT="44444"
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 1:08 PM

I have One more query !!
While installing SE.AS6.0 what i need to install

As a instance or Web adapter

!!
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/12/10 1:19 PM

I've always used the SunONE browser-based admin to turn off it's built-in Servlet/JSP Engine so I can't say for certain what manual changes you'd need to make to the obj.conf and magnus.conf files.

However looking at your file I will make the following guesses (be sure to turn off SunONE and to make backup copies of those files before making any manual edits to them)...

Try commenting out or removing the following lines:

obj.conf
---------
NameTrans fn="ntrans-j2ee" name="j2ee"
Error fn="error-j2ee"
<Object name="j2ee">
Service fn="service-j2ee" method="*"
</Object>


magnus.conf
-----------
Init fn="load-modules" shlib="/app/iplanet/web/bin/https/lib/libj2eeplugin.so" shlib_flags="(global|now)"



When installing SE AS, choose to install an instance (the first and default choice).
When installing an instance you get both an instance and an adapter which is what you want.

When installing only an adapter you get only an adapter which is rarely what anyone wants.

Matt
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 1:23 PM

I am just trying to do...will update you
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/12/10 2:31 PM

Matt, I think it worked!!
After backing up every changes ( magnus.conf and obj.conf) while starting iplanet webserver it gives following warnings.

Sun ONE Web Server 6.1SP5 B08/17/2005 22:09
info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 is initializing...

info: ServletExecNSAPIAdapter reports: About to read /app/NewAtlanta/ServletExecAS/config/webadapter.properties...

info: ServletExecNSAPIAdapter reports: Done reading /app/NewAtlanta/ServletExecAS/config/webadapter.properties.

info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 has initialized.

info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_03] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [https-sm] at [/search]
info: ServletExecNSAPIAdapter reports: Failed to send additional request info to ServletExec.

info: ServletExecNSAPIAdapter reports: Failed to send additional request info to ServletExec.

info: ServletExecNSAPIAdapter reports: Failed to send additional request info to ServletExec.

info: HTTP3072: [LS ls1] http://sm:80 ready to accept requests
startup: server started successfully


Can you please tell is thr any issue
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/12/10 2:47 PM

Did you turn on the java side of SE AS?
That's the SE AS instance.

Try:

/usr/local/NewAtlanta/ServletExecAS/se-<instanceName>/StartServletExec.sh &
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/12/10 2:49 PM

Correction...

For you, your path would be:

/app/NewAtlanta/ServletExecAS/se-<instanceName>/StartServletExec.sh &
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/13/10 7:10 AM

Hi I am getting this response !!

bash-3.00$ sudo ./StartServletExec
Password:
/usr/java/bin/java -Xrs -Djava.naming.factory.initial=com.newatlanta.servletexec.InitialContextFactory -classpath /app/NewAtlanta/ServletExecAS/lib/servlet-api.jar:/app/NewAtlanta/ServletExecAS/lib/jsp-api.jar:/app/NewAtlanta/ServletExecAS/lib/ServletExec60.jar:/app/NewAtlanta/ServletExecAS/lib/ServletExecAdmin.jar:/app/NewAtlanta/ServletExecAS/lib/el-api.jar:/app/NewAtlanta/ServletExecAS/lib/jasper-el.jar:/usr/java/lib/tools.jar:/app/NewAtlanta/ServletExecAS/lib/jstl.jar:/app/NewAtlanta/ServletExecAS/lib/appserv-jstl.jar:/app/NewAtlanta/ServletExecAS/lib/activation.jar:/app/NewAtlanta/ServletExecAS/lib/mail.jar:/app/NewAtlanta/ServletExecAS/se-usdasapp2001/classes ServletExec -name usdasapp2001 -home /app/NewAtlanta/ServletExecAS/se-usdasapp2001 -mimetypes /app/iplanet/web/https-sm/config/mime.types -root /app/iplanet/web/docs -port 8888

Initializing ServletExec 6.0 with the following settings:

port = 8888
backlog = 50
name = usdasapp2001
home = /app/NewAtlanta/ServletExecAS/se-usdasapp2001/
log = /app/NewAtlanta/ServletExecAS/se-usdasapp2001/
mimetypes = /app/iplanet/web/https-sm/config/mime.types
root = /app/iplanet/web/docs/
allow = 127.0.0.1, [0000:0000:0000:0000:0000:0000:0000:0001]
adapter = native


If a failure occurs, check ServletExec.log for error messages.

ServletExec 6.0 initialized in 02.04 seconds.
ServletExec 6.0 shutdown complete in 00.01 seconds.
An instance of ServletExec was unable to bind to its port (port #8888) and so it was shutdown. Something else (perhaps another ServletExec instance) may already be running on that port.


May be this is because i have configured web server on 8888 port.

Thanks
yash
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/13/10 7:16 AM

Output of log file

bash-3.00$ more ServletExec.log
[Thu May 13 04:05:05 PDT 2010] ServletExec: Initializing Session Tracking for vi
rtual server - default, application - default-app
[Thu May 13 04:05:05 PDT 2010] ServletExec: Initialized Session Tracking for vir
tual server - default, application - default-app
[Thu May 13 04:05:05 PDT 2010] ServletExec: Initializing Session Tracking for vi
rtual server - default, application - servletexec
[Thu May 13 04:05:05 PDT 2010] ServletExec: Initialized Session Tracking for vir
tual server - default, application - servletexec
[Thu May 13 04:05:05 PDT 2010] ServletExec 6.0 initialized in 02.04 seconds.
[Thu May 13 04:05:05 PDT 2010] ServletExec 6.0 was initialized with the followin
g settings:
[Thu May 13 04:05:05 PDT 2010] port = 8888
[Thu May 13 04:05:05 PDT 2010] backlog = 50
[Thu May 13 04:05:05 PDT 2010] name = usdasapp2001
[Thu May 13 04:05:05 PDT 2010] home = /app/NewAtlanta/ServletExecAS/se-
usdasapp2001/
[Thu May 13 04:05:05 PDT 2010] log = /app/NewAtlanta/ServletExecAS/se-
usdasapp2001/
[Thu May 13 04:05:05 PDT 2010] mimetypes = /app/iplanet/web/https-sm/config/
mime.types
[Thu May 13 04:05:05 PDT 2010] root = /app/iplanet/web/docs/
[Thu May 13 04:05:05 PDT 2010] allow = 127.0.0.1, [0000:0000:0000:0000:0
000:0000:0000:0001]
[Thu May 13 04:05:05 PDT 2010] adapter = native
[Thu May 13 04:05:05 PDT 2010]
[Thu May 13 04:05:05 PDT 2010] ServletExec: caught exception - java.net.BindExce
ption: Address already in use
[Thu May 13 04:05:05 PDT 2010] java.net.BindException: Address already in use
[Thu May 13 04:05:05 PDT 2010] at java.net.PlainSocketImpl.socketBind(Native Me
thod)
[Thu May 13 04:05:05 PDT 2010] at java.net.PlainSocketImpl.bind(PlainSocketImpl
.java:359)
[Thu May 13 04:05:05 PDT 2010] at java.net.ServerSocket.bind(ServerSocket.java:
319)
at java.net.ServerSocket.bind(ServerSocket.java:
319)
[Thu May 13 04:05:05 PDT 2010] at java.net.ServerSocket.<init>(ServerSocket.java:185)
[Thu May 13 04:05:05 PDT 2010] at java.net.ServerSocket.<init>(ServerSocket.java:141)
[Thu May 13 04:05:05 PDT 2010] at ServletExec.startRunning(ServletExec.java:75)
[Thu May 13 04:05:05 PDT 2010] at ServletExec.main(ServletExec.java:210)
[Thu May 13 04:05:05 PDT 2010] ServletExec: caught exception - java.lang.NullPointerException
[Thu May 13 04:05:05 PDT 2010] java.lang.NullPointerException
[Thu May 13 04:05:05 PDT 2010] at ServletExec.stopRunning(ServletExec.java:113)
[Thu May 13 04:05:05 PDT 2010] at ServletExec.Shutdown(ServletExec.java:153)
[Thu May 13 04:05:05 PDT 2010] at ServletExec.startRunning(ServletExec.java:82)
[Thu May 13 04:05:05 PDT 2010] at ServletExec.main(ServletExec.java:210)
[Thu May 13 04:05:05 PDT 2010] ServletExec 6.0 is shutting down...
[Thu May 13 04:05:05 PDT 2010] ServletExec: Shutting down Session Tracking for virtual server - default, application - servletexec
[Thu May 13 04:05:05 PDT 2010] ServletExec: Shut down Session Tracking for virtual server - default, application - servletexec
[Thu May 13 04:05:05 PDT 2010] ServletExec: Shutting down Session Tracking for virtual server - default, application - default-app
[Thu May 13 04:05:05 PDT 2010] ServletExec: Shut down Session Tracking for virtual server - default, application - default-app
[Thu May 13 04:05:05 PDT 2010] ServletExec 6.0 shutdown complete in 00.01 seconds.
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/13/10 7:18 AM

output of iplanet start script

bash-3.00$ sudo ./start
Sun ONE Web Server 6.1SP5 B08/17/2005 22:09
info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 is initializing...

info: ServletExecNSAPIAdapter reports: About to read /app/NewAtlanta/ServletExecAS/config/webadapter.properties...

info: ServletExecNSAPIAdapter reports: Done reading /app/NewAtlanta/ServletExecAS/config/webadapter.properties.

info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 has initialized.

info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_03] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [https-sm] at [/search]
info: HTTP3072: [LS ls1] http://sm:80 ready to accept requests
startup: server started successfully
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/13/10 7:21 AM

In current environment we are installing CA Siteminder Policy server 6.0 SP5 on solaris 10 soarc and to run its, openview monitor we need to install this servlet over iplanet webserver.

Is there any know impact of SE AS 6.0 , or any other usefull info you can share..
Link | Top | Bottom
yashgoley


Joined: 05/11/10
Posts: 15
RE: Starting Iplanet >>Failed to find main java class
05/13/10 8:18 AM

Hi Matt,
I think i got the issue "same clashing port"

now everything working fine !!

sudo ./StartServletExec &
[1] 1700
bash-3.00$ /usr/java/bin/java -Xrs -Djava.naming.factory.initial=com.newatlanta.servletexec.InitialContextFactory -classpath

/app/NewAtlanta/ServletExecAS/lib/servlet-api.jar:/app/NewAtlanta/ServletExecAS/lib/jsp-api.jar:/app/NewAtlanta/ServletExecAS/lib/ServletExec60.jar:/app/NewA

tlanta/ServletExecAS/lib/ServletExecAdmin.jar:/app/NewAtlanta/ServletExecAS/lib/el-api.jar:/app/NewAtlanta/ServletExecAS/lib/jasper-el.jar:/usr/java/lib/tool

s.jar:/app/NewAtlanta/ServletExecAS/lib/jstl.jar:/app/NewAtlanta/ServletExecAS/lib/appserv-jstl.jar:/app/NewAtlanta/ServletExecAS/lib/activation.jar:/app/New

Atlanta/ServletExecAS/lib/mail.jar:/app/NewAtlanta/ServletExecAS/se-usdasapp2001/classes ServletExec -name usdasapp2001 -home

/app/NewAtlanta/ServletExecAS/se-usdasapp2001 -mimetypes /app/iplanet/web/https-sm/config/mime.types -root /app/iplanet/web/docs -port 9999

Initializing ServletExec 6.0 with the following settings:

port = 9999
backlog = 50
name = usdasapp2001
home = /app/NewAtlanta/ServletExecAS/se-usdasapp2001/
log = /app/NewAtlanta/ServletExecAS/se-usdasapp2001/
mimetypes = /app/iplanet/web/https-sm/config/mime.types
root = /app/iplanet/web/docs/
allow = 127.0.0.1, [0000:0000:0000:0000:0000:0000:0000:0001]
adapter = native


If a failure occurs, check ServletExec.log for error messages.

ServletExec 6.0 initialized in 01.94 seconds.


bash-3.00$ ps -ef | grep ServletExec
usghad00 1711 1330 0 05:14:19 pts/2 0:00 grep ServletExec
root 1700 1330 0 05:13:40 pts/2 0:00 /bin/sh ./StartServletExec


bash-3.00$ sudo ./start
Sun ONE Web Server 6.1SP5 B08/17/2005 22:09
info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 is initializing...

info: ServletExecNSAPIAdapter reports: About to read /app/NewAtlanta/ServletExecAS/config/webadapter.properties...

info: ServletExecNSAPIAdapter reports: Done reading /app/NewAtlanta/ServletExecAS/config/webadapter.properties.

info: ServletExecNSAPIAdapter reports: The ServletExec-NSAPI Adapter for ServletExec 6.0 has initialized.

info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.5.0_03] from [Sun Microsystems Inc.]
info: WEB0100: Loading web module in virtual server [https-sm] at [/search]
info: HTTP3072: [LS ls1] http://sm:80 ready to accept requests
startup: server started successfully


Now waiting for your comments !!

Thanks
Link | Top | Bottom
mattm


Joined: 10/10/07
Posts: 266
RE: Starting Iplanet >>Failed to find main java class
05/13/10 9:15 AM

I see that you have configured your SE AS instance [ASI] to listen on port 9999.

Whenever you change the port on which the ASI listens, you must also tell the native side of SE (the SE AS native adapter) about that.

So turn off your SunONE Webserver instance so that the SE AS native adapter will turn off.
Then edit the
/app/NewAtlanta/ServletExecAS/config/webadapter.properties.

to change 8888 to 9999.
Save the change and then start the SunONE webserver.

Then try to request /servletexec/admin or /servlet/TestServlet

Matt
Matt McGinty, New Atlanta Technical Support
Link | Top | Bottom

New Post
Please login to post a response.


company media information terms of use privacy policy contact us
This page was dynamically built on the BlueDragon CFML Engine