Can't start Oc4j Server with EJBs

My application consists of a few jsf sides and one ejb for database connection. When
I started the application for the first time everything worked wonderful. But when
I started it for the second time i got this error-message:
Error instantiating application 'current-workspace-app' at file: /C:/documents/myFiles/project/RDV-Project-oc4j-app.xml : Error initializing ejb-module; Exception null
Could anybody help me?

I found the solution. In Jdeveloper you have to make a right click on the EJB and then select Verify Enterprise Bean.
bye

Similar Messages

Can't start WebLogic Server with SP6 and jdk1.2.2 using WebLogic Console

Hi All,
I am trying to install WebLogic 5.1 with SP6 under Windows NT 4.0 with SP6. My goal is to run JSP/Servlets. After going through all the steps described in SP6 Readme I am getting th following exception:
ava.lang.reflect.InvocationTargetException: java.lang.NoSuchMethodError: weblogic.boot.ServerClassLoader: method getClassLoadNotify()Lweblogic/boot/ClassLoadNotify; not found
     at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:140)
     at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:112)
     at weblogic.utils.classloaders.GenericClassLoader.<init>(GenericClassLoader.java:104)
     at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader.<init>(RecursiveReloadOnModifyClassLoader.java:53)
     at weblogic.utils.classloaders.RecursiveReloadOnModifyClassLoader$SingleSlave.<init>(RecursiveReloadOnModifyClassLoader.java:149)
     at weblogic.servlet.internal.ServletContextImpl.setClassLoader(ServletContextImpl.java:1408)
     at weblogic.servlet.internal.ServletContextImpl.<init>(ServletContextImpl.java:518)
     at weblogic.t3.srvr.HttpServer.initServletContexts(HttpServer.java, Compiled Code)
     at weblogic.t3.srvr.HttpServer.start(HttpServer.java:388)
     at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java, Compiled Code)
     at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:827)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.Server.startServerDynamically(Server.java:99)
     at weblogic.Server.main(Server.java:65)
     at weblogic.Server.main(Server.java:55)
The installation document is pretty bad intermixing different types of installations. Where can I find steps or what do I need to do to get WebLogic to run with JDK1.2.2 if I want to start it up from WebLogic console only?
Thanks,
Mark.

Try rather using the 1.4 version available here: http://java.sun.com/j2ee/1.4/
and use this dedicated forum: http://forum.java.sun.com/forum.jsp?forum=136
-Alexis

Can't start report server on windows 2000

I can't start report server with error code 186, my tnsname.ora is
REP60_DUQ = Rep60_DUQ
is it error?
who can tell me how to resolve it!!!

but I have add tnsnames.ora following
Rep60_REPORT_SERVER =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = REPORT_SERVER)(PORT = 1951))
then I start report server with:
/PATH_TO_REPORTSERVER/report60_server start
it still says:
REP-0186: Daemon failed to listen to port
what is problem?
any thing must be done to activate changes in
tnsnames.ora?
null

How to use the same OC4j server with different port number

How to use the same OC4j server with different port numbers..?
I have to OC4J installed on my machine on different hard disk drives....
I want to be able to run both the server simultaneously..?
is it possible ..it yes then how..?
for that i have changed the port number of one server...
but when i am trying to start the other server with different port number..it says that JVM -Bind already...
Is there any clues...?
Nilesh G

In the config directory:
default-web-site.xml: Change the port the HTTP listener listens on
jms.xml: Change the port the JMS service listens on
rmi.xml: Change the port the ORMI listener listens on.
Or, you can add another web-site.xml file, and deploy your applications to 1 server, and bind the web applications to the different web sites. This way you only have to deploy your applications to 1 place.
Rob
Oracle

Can't start http server ASControl service

Hi, I installed http server from companion cd for oracle 10.2.0.3 but when configuration assistants was setting http server give the message failed.
Now i can´t start http server service.
INFO: El asistente de configuración "OC4J Configuration Assistant" se ha ejecutado correctamente
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Created a new file C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.1
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.2
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.3
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.4
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.5
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.6
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: --------------------------------------
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolAllCommands" contiene todos los comandos que van a ejecutar los asistentes de configuración. Este archivo se puede utilizar para ejecutar los asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.7
GRAVE: OUI-25029: Uno o más asistentes de configuración "recomendados" no han terminado correctamente. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
INFO: Usuario seleccionado: Sí/Aceptar
INFO:
*** Fin de Instalación Página***
La instalación de Oracle Database 10g Companion Products ha sido correcta, pero han fallado, se han cancelado o se han saltado algunos asistentes de configuración opcionales.
ADVERTENCIA: ¿Seguro que desea salir?
INFO: Usuario seleccionado: Sí/Aceptar

user13078324 wrote:
How ?in cmd run this
netstat -an
and search for a line like
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
The important is TCP, 80 and keyword LISTENING
Other may differ

Urgent: Can not start admin server

I installed Sun One directory server 5.1 on Solaris 8 01/01 version patched with Solaris 8 patch cluster.
In installation, there is error message
Can't start Admin server [home/iplanet/servers/start-admin > /var/tmp/aaax0aOBb 2>&1] (error: No such file or directory)
idskture only shows one ERROR message:
ERROR : Patch 111085-02 (SunOS 5.8: /usr/bin/login patch) is required but not installed.
But it seems fine since I reinstalled Solaris 8 01/01 release and install 5.1sp2 and with the same error message running idsktune, the installation of 5.1 but works fine.
Do you have any idea why the installation fail before I reinstlall Solaris 8?
Thanks,
Iris

Have you checked the EAS logs, <MIDDLEWARE_HOME>user_projects\epmsystem1\diagnostics\logs\services
Cheers
John
http://john-goodwin.blogspot.com/

Is there any way to start weblogic server with java 7?

Hi. Is there any way to start weblogic server with jdk 1.7?

Hi,
You can start your Weblogic Server with java 7(JDK 1.7)
Go to Domain_home/bin and click on StartWeblogic.cmd it will start your Admin Server
It depends on which JDK you have used while creating domain if you have selected Jdk 1.7 it will use the same to start the server
See the Ex:
================
starting weblogic with Java version:
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Starting WLS with line:
C:\PROGRA~1\Java\JDK17~1.0_5\bin\java -client -Xms256m -Xmx512m -XX:CompileThr
eshold=8000 -XX:PermSize=48m -XX:MaxPermSize=128m -Dweblogic.Name=AdminServer -
Djava.security.policy=H:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy
-Xverify:none -Xverify:none -da -Dplatform.home=H:\Oracle\MIDDLE~1\WLSERV~1.3 -
Dwls.home=H:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=H:\Oracle\MIDDLE~
1\WLSERV~1.3\server -Dweblogic.management.discover=true -Dwlw.iterativeDev= -
Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=H:\Oracle\MIDDLE
~1\patch_wls1036\profiles\default\sysext_manifest_classpath weblogic.Server
<Mar 3, 2015 1:08:32 PM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ J
CE Provider self-integrity check for better startup performance. To enable this
check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Mar 3, 2015 1:08:33 PM PST> <Info> <Security> <BEA-090906> <Changing the defaul
t Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable
this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Mar 3, 2015 1:08:33 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebL
ogic Server with Java HotSpot(TM) 64-Bit Server VM Version 24.51-b03 from Oracle
Corporation>
=======================================
If you are using a Lower version of JDK and want to upgrade to JKD 1.7 you can do so by changing setDomainEnv.sh in Weblogic
Have a look at the below link to do so
The Weblogic Wasp: change java version / JDK of a weblogic domain
http://www.baigzeeshan.com/2012/05/how-to-change-jdk-used-by-weblogic.html
Hope it helps

Integrating java application running on OC4J server with EP Iview

Hi,
I Want to Integrate Java Application running on OC4J server with my Enterprise portal
Can any one please help me out in this??
Regards
Padma N

Hi Padma
Its possible to integrate a java application running in the other server with enterprise portal.In portal i think there is a IView template call Java application template.Using this generally we can do this.But in you case what type of a java application is it?Just a class or webapplication or a server side application.This you can also acheive using a webdynpro applications as these are very flexible with integration into EP.In webdynpro you can use suspend and resume plugs to navigate from one application to other application.I have given my ideas how to implement.But integration mainly depends upon your landscape and version compatibilities and type of the application you need to integrate.
Hope this answer helps you in implementation.
Regards
Kalyan

How to start Integration server with the user XISUPER

Hi,
How to start Integration server with the user XISUPER?
Regards,

Mahesh,
In the post installation document, under Creating User XISUPER,
I see the following,
1.You must now log on to the Integration server host with the user XISUPER, to switch the initial password to a valid password.
2.You must restart the J2EE engine to transfer the user creation to the J2EE immediately.
I am unable to proceed here.Can you please help me to resume the post installation steps ?
Thanks,

Can not start Messaging server in Sun Java System Messaging Server 6 2005Q1

Hi all,
I installed Sun Java System Messaging Server 6 2005Q1 from Solaris 10 DVD on Solaris 10.
After the installation, I got directory server, admin server running but messaging server not running. I can not start Messaging server (start smtp, http, pop, imap). I found in directory which I installed messaging server but I could not see script "start-msg" and "stop-msg".
# pwd
/opt/SUNWmsgsr/sbin
# ls
MoveUser ha_ip_config imquotacheck imsdirmig mkbackupdir
UpgradeMsg5toMsg6.pl hashdir imsbackup imsexport readership
configure imexpire imsconnutil imsimport reconstruct
control-params.txt iminitquota imscripter imsrestore relinker
deliver immonitor-access imsdaaci mboxutil useconfig
Any idea what might have gone wrong?
Thanks.

Thanks.
I have a problem when I configure the Messaging Server (by running the /opt/SUNWmsgsr/sbin/configure script):
Hostname mailtest for this machine is not a fully qualified domain name. Please
correct this before attempting to configure Messaging Server. Please make sure
that your DNS is working properly.
<Press ENTER to continue> {"<" goes back, "!" exits}
Can you help me fix this problem?
Thanks.

Error starting managed server with JRockit VM

I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace

I found the solution . The reason for this is that JRockit's High Performance Thread
System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
The two asynchronous I/O systems clash and the result is the error you see.
There are two ways around this problem. Either disable JRockit's High Performance
Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
disable Weblogic's Native I/O.
For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
and change this to NativeIOEnabled="false".
For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
to
weblogic.system.nativeIO.enable=false
"Manoj jayadevan" <[email protected]> wrote:
>
I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
option on. The OS is NT. Any clues , please ?
exception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
D:\i252\services>runtxnserver
JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
Garbage Collector, started.
[JRockit] Starting Management Server on port 7090
Starting WebLogic Server ....
Connecting to http://ocncat2:7991...
<May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
fd:
4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
35c4a
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
tected attempting to connect to admin server at http://ocncat2:7991 during
i
alization of managed server ( null:7551 ). The reported error was: < java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) > This condition generally results when the managed
and
n servers are using the same listen address and port.>
<May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
th
rver: 'Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: java.io
xception: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException:
.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
parameter is incorrect.
(error 87, fd 824)
at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
2410
at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
C
@23e31b90
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
Cod
3e30810
at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
0660
at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
led Code)@23d7ec10
at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
ouldn't initialize IOPort: The parameter is incorrect.
(error 87, fd 824) - with nested exception:
[java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
e parameter is incorrect.
(error 87, fd 824)]
at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
Code
d7db70
at weblogic.management.Admin.start(Compiled Code)@23d7c060
at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
at weblogic.Server.main(Compiled Code)@23590050
--- End of stack trace

Starting managed server with nodemanager

Hi there,
Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
(1) set up the main server and able to run the server successfully.
(2) set up one managed server, set up one machine on same server as main server.
(3) assign machine to created managed server.
(4) after that i've tried to run that managed server and error giving as below:
Error from main server terminal
===================
<NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
Error from Node Manager Termal
====================
<Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
<Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
Thanks in advance,
Tim

Sorry , i forgot to mention that the OS i am using is Solaris.
Thx

Can't start OC4J instance

hi all
i can't start OC4J for forms , this happend after installed jdeveloper 10.1.3
on IDS 10.1.2.0.2
if any advice to help me in this issue
thanks

Don't install JDeveloper on top of any Oracle Home - install it in a separate directory.
The install guide clearly states so - http://www.oracle.com/technology/products/jdev/htdocs/10.1.3.1/install.html#install_start_windows

New install of SJS Ent 8 on Solaris, can't start Application Server 8.1

Hello,
Appreciate in advance your help.
Just downloaded and installed SJS 8.1 on a new Sun Solaris 10 box. I'm able to run the IDE and have started the Tomcat server, but when attempting to start the SJS 8.1 application server, I get:
The Sun Java System Application Server 8.1 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used)
- Incorrect server configuration
- Corrupted Deployed Applications
The problems are:
- There is no server.log file in the expected directory at /opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs
- I ran netstat -a, but could glean no useful information
- I have not modified the server configuration since the new install
- I have not deployed my application (since I can't start the server).
Forgive my ignorance since I'm not a Solaris expert. I would greatly appreciate your assistance.

No difference in server.log after setting level="FINEST".
Don't know if it would help, but the contents of my server.log file follow:
[#|2006-09-25T15:39:46.485-0400|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
/opt/sun/jstudio_ent8/jdk1.5.0_04/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs/server.log
-Djava.endorsed.dirs=/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/endorsed
-Djava.security.policy=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/server.policy
-Djava.security.auth.login.config=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/cacerts.jks
-Djava.ext.dirs=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/ext:/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=myDomain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=myDomain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/config
-Djava.library.path=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386/client:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/../lib/i386:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib:/usr/lib/lwp::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/opt/sun/jstudio_ent8/jdk1.5.0_04/lib/tools.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/activation.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/mail.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/admin-cli.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-admin.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-jstl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-logging.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee-svc.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jax-qname.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/dom.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/relaxngDatatype.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xsdlib.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote_optional.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/rmissl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xalan.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xercesImpl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-upgrade.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-ext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/install/applications/jmsra/imqjmsra.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/jaxm-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/fscontext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/ant/lib/ant.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbclient.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start|#]
I do notice that the class path references jdk1.5.0_04. When installing SJS I selected the separately installed jdk1.5.0_07. Could that be causing the problem?
You have great patience.

My hard drive died. How can I start my computer with my Time Machine external drive?

My hard drive died. How can I start my computer with my Time Machine external drive?

Pondini wrote:
If you're on 10.7.2, yes, you can boot from the TM drive.
Beep, beep, beep....
Hold ON! Getting a call on the red phone.
"Yes...yes.... ok!"
It's confirmed, H.e.l.l. has finally frozen over! TM drives are now bootable!
Still it's not a real bootable clone, can't run the computer off the external drive for long in only Recovery mode, still requires the boot drive to be replaced if it not functional, and with TM backing up every hour, isn't going to offer much software protection as the TM drive is just as likely to be as messed up as the internal boot drive.
For a iMac it still requires the computer to be taken in to Apple for a drive replacement, as ONLY Apple can do it due to proprietary connections and firmware on the iMac hard drives.
But it is bootable!
The backup time factor can be controlled using TimeMachine Editor, from every hour to just when the user thinks it's necessary.
Apple lurches slightly forward! Hurray!
Question is, can one restore from earlier stable TM's or just the last one? In this bootable fashion?

Can't start Oc4j Server with EJBs

Similar Messages

Maybe you are looking for