Can't start J2EE server
I have installed Java 2 SDK, Enterprise Edition version 1.3 on Win NT server. Installation was successfull.
While starting J2EE server, I am getting following error:
Exception in thread "main" java.lang.NoClassDefFoundError: COMPUTER\db\
A few basic steps taken from http://java.sun.com/j2ee/sdk_1.3/install.html#win_soft
Installing the Windows Bundle
1. If you have installed a previous version of the J2EE SDK product, you must delete or un-install the previous version from your computer before proceeding with the new version.
2. Set the environment variables.
Before running the J2EE SDK, you must set these environment variables:
J2EE_HOME - the directory where you installed this release.
JAVA_HOME - the directory where the Java 2 SDK Standard Edition is installed.
PATH - include the bin directory beneath the directory where you've installed this release.
Similar Messages
-
Can't start J2ee server using j2sdkee1.3.1
When i try to start j2ee server , it shows the following
Error message.
Exception in thread "main" java.lang.NoClassDefFoundError: javax/naming/Context
at com.sun.enterprise.server.J2EEServer.<clinit>(J2EEServer.java:53)
I have set all environment variables as follows
set path=.;c:\jdk1.2.2\bin;c:\j2sdkee1.3.1\bin;
set classpath=.c:\jdk1.2.2\lib;c:\j2sdkee1.3.1\lib\j2ee.jar
set JAVA_HOME=c:\jdk1.2.2
set J2EE_HOME=c:\j2sdkee1.3.
pls kindly give a solution.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 J2EE server :o(
Hi,
I'm getting started with J2EE but I can't start the J2EE server. I have to point out that I read the instructions in J2EE Tutorial 1.3 but I use J2EE SDK 1.4 Beta.. But it should work, shouldn't it??? I don't expect the problem to be very serious but I'm a greener and can't solve it myself :oI
Thanks a lot for every hint and sorry for my not very good English :o)
Dojcland
Here are the "printStackTraces" I get:
(The last line you can see is the last one that appears. Never "C:\" again. If I close the window "Stopping J2EE server" message appears before the window is closed.)
C:\>j2ee -stop
Shutting down the J2EE server.
Unable to shutdown the J2EE server.
C:\>cleanup
This will delete all deployed applications and clean all log files
Do you want to proceed (y/n)
y
Cleaning directory C:\j2sdkee1.4\logs ...
Cleaning directory C:\j2sdkee1.4\repository ...
Cleaning directory C:\j2sdkee1.4\connector\adapters ...
Cleaning directory C:\j2sdkee1.4\public_html ...
Cleaning directory C:\WINNT\TEMP\j2ee-ri-Dojcland ...
Cleaning directory C:\j2sdkee1.4\web\repository ...
Cleanup completed. Please restart j2ee server.
C:\>j2ee -verbose
J2EE server listen port: 1050
Naming service started: 1050
Binding DataSource, name = jdbc/DB1, url =
jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/EstoreDB, url =
jdbc:cloudscape:rmi:CloudscapeDB
;create=true
Binding DataSource, name = jdbc/InventoryDB, url =
jdbc:cloudscape:rmi:Cloudscap
eDB;create=true
Binding DataSource, name = jdbc/DB2, url =
jdbc:cloudscape:rmi:CloudscapeDB;crea
te=true
Binding DataSource, name = jdbc/Cloudscape, url =
jdbc:cloudscape:rmi:Cloudscape
DB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource =
COM.cloudscape.co
re.RemoteXaDataSource@119e583
Binding DataSource, name = jdbc/_ejb_container, url = jdbc/_ejb_container__xa
Binding DataSource, name = jdbc/_ejb_container__xa, dataSource =
COM.cloudscape.
core.XaDataSource@b05236
Starting JMS service...
Initialization complete - waiting for client requests
Starting JMS via Resource Adapter
Deploying jmsra.rar in C:\j2sdkee1.4\lib\system_apps\jmsra.rar
org.w3c.dom.DOMException: DOM003 Namespace error
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:129)
at
org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocument
Impl.java:1422)
at
org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:596
at
com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttrib
ute(DeploymentDescriptorNode.java:501)
at
com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(Lo
calizedNode.java:65)
at
com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisp
layableComponentInfo(DisplayableComponentNode.java:56)
at
com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleN
ode.java:104)
at
com.sun.enterprise.deployment.node.connector.ConnectorNode.writeDescr
iptor(ConnectorNode.java:210)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2
EEDocumentBuilder.java:77)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:120)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Exception stringifying deployment descriptor
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:236)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:239)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
ResourceAdapter jmsra.rar started...
Initializing Coyote HTTP/1.1 on port 8000
Initializing Coyote HTTP/1.1 on port 7000
Loaded registry information 3275 ms
Starting service J2EE(TM) Web Server
Apache Tomcat/5.0
Missing application web.xml, using defaults only
StandardEngine[Standard-Engine]
.StandardHost[localhost].StandardContext[]
Added certificates -> request attribute Valve
Starting Coyote HTTP/1.1 on port 8000
Starting Coyote HTTP/1.1 on port 7000
JACC:Policy Repository set to C:\j2sdkee1.4\repository\policy
Added certificates -> request attribute Valve
Configured an authenticator for method FORM
J2EE Web Admin Tool started
JAXR:Installing JAXR RA
Deploying jaxr-ra.rar in C:\j2sdkee1.4\lib\system_apps\jaxr-ra.rar
org.w3c.dom.DOMException: DOM003 Namespace error
at org.apache.xerces.dom.AttrNSImpl.<init>(AttrNSImpl.java:129)
at
org.apache.xerces.dom.CoreDocumentImpl.createAttributeNS(CoreDocument
Impl.java:1422)
at
org.apache.xerces.dom.ElementImpl.setAttributeNS(ElementImpl.java:596
at
com.sun.enterprise.deployment.node.DeploymentDescriptorNode.setAttrib
ute(DeploymentDescriptorNode.java:501)
at
com.sun.enterprise.deployment.node.LocalizedNode.writeLocalizedMap(Lo
calizedNode.java:65)
at
com.sun.enterprise.deployment.node.DisplayableComponentNode.writeDisp
layableComponentInfo(DisplayableComponentNode.java:57)
at
com.sun.enterprise.deployment.node.BundleNode.writeDescriptor(BundleN
ode.java:104)
at
com.sun.enterprise.deployment.node.connector.ConnectorNode.writeDescr
iptor(ConnectorNode.java:210)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.getDocument(J2
EEDocumentBuilder.java:77)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:120)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Exception stringifying deployment descriptor
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
java.lang.IllegalArgumentException: The input node can not be null for a
DOMSour
ce for newTemplates!
at
org.apache.xalan.transformer.TransformerIdentityImpl.transform(Transf
ormerIdentityImpl.java:346)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.write(J2EEDocu
mentBuilder.java:125)
at
com.sun.enterprise.deployment.node.J2EEDocumentBuilder.descriptorToSt
ring(J2EEDocumentBuilder.java:153)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModuleAndItsComponents(J2EEManagementObjectManager.java:408)
at
com.sun.enterprise.management.util.J2EEManagementObjectManager.regist
erResourceAdapterModule(J2EEManagementObjectManager.java:203)
at
com.sun.enterprise.resource.ResourceInstaller.installSystemResourceAd
apter(ResourceInstaller.java:706)
at com.sun.enterprise.jaxr.JaxrUtil.installJaxrRA(JaxrUtil.java:40)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:278)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:720)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.apache.commons.launcher.ChildMain.run(ChildMain.java:280)
Binding Connection Factory, name = QueueConnectionFactory
Binding Connection Factory, name = jms/TopicConnectionFactory
Binding Connection Factory, name = jms/QueueConnectionFactory
Binding Connection Factory, name = TopicConnectionFactory
Binding Connection Factory, name = eis/JAXR
Binding Administered Object, name = jms/Topic
Binding Administered Object, name = jms/Queue
Starting EJB Timer Service...
J2EE server startup complete.Check another similar question in the same forums.. I have posted an answer there. Hopefully that should work for you.
-
Starting j2ee server from a java Application
Hi.
I'm trying to start j2ee server by clicking a button in an application I'm developing. I don't know how to do it. I haven't found In the documentation some topic related. I look at the j2ee.bat but it just call a class named J2EEServer, and the API of this class is not in the API of the j2ee.
Can you help me please??
Thanks
Mauchothanks!
That was my first approach , and it works, but the problem is that I can't kill the process then, cause the method destroy() don't kill j2ee. Maybe it kills the j2ee.bat, but not the server itself. Maybe you know how to do it, I'll really appreciate it.
Regards -
Error message while starting J2EE Server!
Hi!
I get this error message when i try to start J2EE server:
c:\j2ee -verbose
Exception in thread "main" java.lang.NoSuchMethodError
at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImp
l.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(Sh
utdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(Shutdown
UtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.re
bind(Unknown Source)
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:188
at com.sun.enterprise.naming.SerialContext.rebind(SerialContext.java:202
at javax.naming.InitialContext.rebind(InitialContext.java:370)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManag
erImpl.java:192)
at com.sun.enterprise.naming.NamingManagerImpl.publishObject(NamingManag
erImpl.java:149)
at com.sun.enterprise.server.J2EEServer.bindObject(J2EEServer.java:718)
at com.sun.enterprise.server.J2EEServer.createServerObject(J2EEServer.ja
va:473)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:244)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
Can someone tell me why?
ThanksYou need jsdk 1.3.1_03 or above to run j2ee 1.3.1 Any other version will give you this error.
-
When starting J2EE server .....
I have installed j2sdk 1.4 & j2sdkee1.3 on Windows XP. I have set Environment variables.
When I start j2ee server
COMMAN PROMPT SAYS
C:\>j2ee
Warning: This J2EE SDK release has only been tested on J2SE v1.3
J2EE server listen port: 1050
Redirecting the output and error streams to the following files:
c:\j2sdkee1.3\logs\home\j2ee\j2ee\system.out
c:\j2sdkee1.3\logs\home\j2ee\j2ee\system.err
Exception in thread "main"
C:\>
SYSTEM.ERR shows
Logging for J2EE Server Version: 1.3-b16 started at: Wed Apr 07 16:03:55 GMT+05:30 2004..
Using the Java HotSpot(TM) Client VM and the version number 1.4.0 from Sun Microsystems Inc..
VM is using the classpath: c:\j2sdkee1.3\lib\system\cloudscape.jar;c:\j2sdkee1.3\lib\system\tools.jar;c:\j2sdkee1.3\lib\cloudscape\RmiJdbc.jar;c:\j2sdkee1.3\lib\cloudscape\client.jar;c:\j2sdkee1.3\lib\classes;c:\j2sdkee1.3\classes;c:\j2sdkee1.3\lib\j2ee.jar;c:\j2sdkee1.3\lib\locale;c:\j2sdk1.4.0\jre\lib\rt.jar;c:\j2sdk1.4.0\lib\tools.jar;.;;c:\j2sdkee1.3\lib\jhall.jar .
J2EE Home Directory has been set to: c:\j2sdkee1.3.
java.lang.NoSuchMethodError: loadClass0
at com.sun.corba.ee.internal.util.JDKClassLoader.specialLoadClass(Native Method)
at com.sun.corba.ee.internal.util.JDKClassLoader.loadClass(JDKClassLoader.java:58)
at com.sun.corba.ee.internal.util.JDKBridge.loadClassM(JDKBridge.java:181)
at com.sun.corba.ee.internal.util.JDKBridge.loadClass(JDKBridge.java:84)
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.loadClass(Util.java:392)
at javax.rmi.CORBA.Util.loadClass(Util.java:233)
at javax.rmi.PortableRemoteObject.createDelegateIfSpecified(PortableRemoteObject.java:179)
at javax.rmi.PortableRemoteObject.<clinit>(PortableRemoteObject.java:58)
at com.sun.enterprise.server.J2EEServer.createActivationObjects(../../src/share/com/sun/enterprise/server/J2EEServer.java:397)
at com.sun.enterprise.server.J2EEServer.run(../../src/share/com/sun/enterprise/server/J2EEServer.java:227)
at com.sun.enterprise.server.J2EEServer.main(../../src/share/com/sun/enterprise/server/J2EEServer.java:901)
SYSTEM.OUT shows
Logging for J2EE Server Version: 1.3-b16 started at: Wed Apr 07 16:03:55 GMT+05:30 2004..
Using the Java HotSpot(TM) Client VM and the version number 1.4.0 from Sun Microsystems Inc..
VM is using the classpath: c:\j2sdkee1.3\lib\system\cloudscape.jar;c:\j2sdkee1.3\lib\system\tools.jar;c:\j2sdkee1.3\lib\cloudscape\RmiJdbc.jar;c:\j2sdkee1.3\lib\cloudscape\client.jar;c:\j2sdkee1.3\lib\classes;c:\j2sdkee1.3\classes;c:\j2sdkee1.3\lib\j2ee.jar;c:\j2sdkee1.3\lib\locale;c:\j2sdk1.4.0\jre\lib\rt.jar;c:\j2sdk1.4.0\lib\tools.jar;.;;c:\j2sdkee1.3\lib\jhall.jar .
J2EE Home Directory has been set to: c:\j2sdkee1.3.
Naming service started:1050
I tried changing the port number from 1050 to 10590 (as shown in Sun site) but didn't help. Same problem.
One more thing, can this problem be b'coz of "Warning: This J2EE SDK release has only been tested on J2SE v1.3" this starting line on start of server.
Can anyone tell me, y am I facing this problem and how to solve it. Other applications like deploytool, cloudscape r running fine. I didn't try others.
Looking for help as soon as possible
Thanks
TruptiYou may want to try and use J2SE 1.3 instead of J2SE 1.4. This may alleviate your issue.
-
When starting J2EE server PE8 on Linux
When starting J2EE server PE8 on Linux Fedora Core 1, the following message is displayed:-
"Unable to read system environment. No system environment will be used."
1. Is there any side effect to the J2EE server PE8 performance or functionalities about this warning message?
2. Is there any way to avoid this issuea in case it does have side effect?
Regards,
WilliamI find libcliutil.so in $J2EE_HOME/lib and did the followings and got:-
#> ldd libcliutil.so
ldd: warning: you do not have execution permission for `./libcliutil.so'
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x008ad000)
libdl.so.2 => /lib/libdl.so.2 (0x00782000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x00433000)
libresolv.so.2 => /lib/libresolv.so.2 (0x00913000)
libstdc++-libc6.2-2.so.3 => not found
libm.so.6 => /lib/tls/libm.so.6 (0x0075e000)
libc.so.6 => /lib/tls/libc.so.6 (0x00623000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x0060b000)
Can we infer that the warning message is displayed due to "libstdc++-libc6.2-2.so.3 => not found"?
Regards,
William -
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. -
Cannot start J2EE server on Windows 2000 server
Hi..
I installed J2EE 1.3(beta) along with J2SE1.3 that comes with the Java Jump start CDs.
The installation process went fine...I configured the environment variables but when I try to start the J2EE server from command prompt I get the following error.
E:\>j2ee -verbose
Exception in thread "main" java.lang.NoClassDefFoundError: javax/naming/Context at com.sun.enterprise.server.J2EEServer.<clinit>(J2EEServer.java:59)
The same error is encountered with other switches(stop, version etc.) of j2ee.
There is no conflict of port numbers. Can anyone please guide me properly what I have done wrong in the installation process?
ThanksWell...I removed the CLASSPATH variable all together and reinstalled J2SE 1.3 again(refreshed all the environment variables) and then started j2ee server....and it worked this time...
Thanks alot... -
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. -
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 -
Error at starting j2ee server (newbie)
Dear all,
I am not able to start j2ee server successfully. I keep getting the following error when I try to start the server by typing j2ee:
C:\Documents and Settings\ali>j2ee
J2EE server listen port: 1050
Redirecting the output and error streams to the following files:
C:\j2sdkee1.3.1\logs\nofear\j2ee\j2ee\system.out
C:\j2sdkee1.3.1\logs\nofear\j2ee\j2ee\system.err
Exception in thread "main"
I have j2sdkee1.3.1 and jdk1.3.0_05 installed in my laptop with the following settings:
User variable:
PATH=C:\jdk1.3.0_05\bin;C:\j2sdkee1.3.1\bin;C:\Program Files\Java\jre1.6.0_02\bin;C:\Program Files\Java\jdk1.6.0_02\bin; C:\j2sdkee1.3.1\bin;
CLASSPATH=.;C:\Program Files\Java\jre1.6.0_02\bin;C:\jdk1.3.0_05\bin;C:\j2sdkee1.3.1\bin;
System variable:
PATH=D:\MikTex\miktex\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jdk1.6.0_02\bin;C:\PROGRA~1\CINDER~1\CINDER~2\Program;C:\Program Files\Java\jre1.6.0_02\bin;C:\PROGRA~1\ATT\Graphviz\bin\tools;C:\WINDOWS\system32\wbem;C:\Program Files\ImageConverter Plus;C:\Program Files\Samsung\Samsung PC Studio 3\;C:\Program Files\QuickTime\QTSystem\;C:\jdk1.3.0_05\bin;C:\j2sdkee1.3.1\bin;
CLASSPATH= .;C:\jdk1.3.0_05\bin;C:\Program Files\Java\jdk1.6.0_02\bin; C:\Program Files\Java\jre1.6.2_02\bin;C:\Program Files\Java\jdk1.6.0_02\bin;C:\Program Files\Java\jre1.6.0_05\lib\ext\QTJava.zip;C:\j2sdkee1.3.1\bin;C:\j2sdkee1.3.1;
Java_home= C:\jdk1.3.0_05
J2ee_home= C:\j2sdkee1.3.1
Could you please tell me why as I am not able to pass this stage without help?
Kind regards,
AlModify your JAVA_HOME to C:\Program%20%Files\j2sdk1.4.2_08
as spaces are not allowed. Most probably it will work.
I have installed J2EE SDK 1.3 on my machine. I have
set
J2EE_HOME=C:\j2sdkee1.3.1
JAVA_HOME=C:\Program Files\j2sdk1.4.2_08
and
PATH=C:\j2sdkee1.3.1\bin
CLASSPATH
=%J2EE_HOME%\lib\j2ee.jar;%J2EE_HOME%\lib\locale
environmental variables. All the four path seem to
OK. But when I'm trying to start application server
using j2ee -verbose command on my dos prompt I'm
getting following error
'C:\Program' is not recognized as an internal or
external command, operable program or batch file.
I tried j2ee -verbose command from C: prompt as well
as from C:\j2sdkee1.3.1\bin prompt in which j2ee
batch file is present.
Please help/guide on above issue -
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í/Aceptaruser13078324 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 -
I installed J2EE on Windows NT. I am getting the following exceptions when I started J2EE Server....
1. java.lang.NullPointerException at com.sun.enterprise.server.J2EEServer.....
2. RuntimeException: Unable to create ORB. Possible causes include TCP/IP ports in use by another process....
I tried to change the port no. from the default 1050 to 10500, but it didn't help.
Any suggestions please?Since u r getting the TCP/IP port already in use error, u probably have some other service/server running on that port.Try the following steps:
1) Start menu >> Control Panel >> Services
2) See which services are running presently. In case u have any web server,Appln. server running. , stop them and then start J2EE again.
But, I still think u r missing something in the classpath. -
I can not accessed J2EE Server because i dont know username and password
I set username and password as tutorials but not successful.
and after that i can't access J2EE server with localhost:4848.
please tell me the way access J2EE server.Or Default username and password of it.
Thanks your help!Hi,
Can you please send more infomation on exactly what is failing? Are you trying to execute asadmin commands?
Also, which platform are you running the appserver on? Does the appserver show up in the list of currently running processes?
I believe that the default username is "admin" and the password is "adminadmin".
Thanks,
Kyle
Maybe you are looking for
-
My new iPod Touch 5g gets hung up when updating apps.
The blue installation line freezes when complete and a duplicate app then appears. Solution?
-
What is the process in the browser when executing the applet over the internet? When it's downloaded from the internet, is it saved to the local machine like in temp directory? When I use the same applet, I realized that it downloads the applet only
-
Can't delete certain emails from Mail. Instead, I get the message "An error occurred while moving messages to the mailbox, etc." The problem appears randomly.
-
I'm using Airport Express to go on the net which works fine, but when I try to use AirTunes I get a dialogue saying The remote speaker "Base Station **** " is not compatible with this version of iTunes. It's 7.0.2 (the latest). I've turned IPv6 off.
-
Car Rental Web Service WebDynpro Example
I implemented this. When I run the application the fields are read only. I checked the context mapping everything looks ok. Any help is highly appreciated. Regards Mike