Problem starting the j2ee server
I am trying to run
j2ee -verbose
and I am getting the following error.
I am running it on Windows 2000
and my environment variables are set like this
set JAVA_HOME=C:\jdk1.3.1_04
set J2EE_HOME=C:\j2sdkee1.3.1
set CLASSPATH=%J2EE_HOME%\lib\j2ee.jar;%J2EE_HOME%\lib\locale;.;
set PATH=%J2EE_HOME%\bin;C:\jdk1.3.1_04\bin;
Did anyone encountered the same problem. Any ideas on how to solve it.
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB;cre
te=true
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:CloudscapeD
;create=true
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB;cre
te=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Cloudsca
eDB;create=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscap
DB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.c
re.RemoteXaDataSource@7ecd78
Starting JMS service...
Initialization complete - waiting for client requests
Binding: < JMS Destination : jms/Topic , javax.jms.Topic >
Binding: < JMS Destination : jms/Queue , javax.jms.Queue >
Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No properties
>
Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , No properties >
Binding: < JMS Cnx Factory : TopicConnectionFactory , Topic , No properties >
Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No properties
>
Starting web service at port: 8000
Starting secure web service at port: 7000
J2EE SDK/1.3.1
LifecycleException: null.open: java.net.BindException: Address in use: JVM_Bin
d
at org.apache.catalina.connector.http.HttpConnector.initialize(HttpConne
ctor.java:1116)
at org.apache.catalina.startup.Embedded.start(Embedded.java:962)
at com.sun.web.server.WebService.start(WebService.java:217)
at com.sun.web.server.WebServer.start(WebServer.java:189)
at com.sun.enterprise.server.J2EEServer.startWebService(J2EEServer.java:
796)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:297)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: null.open
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: null.open
Error executing J2EE server ...
Same problem here. Looked at the following file and made change: http.port=8001.
C:\j2sdkee1.3.1\config\web.properties
J2EE Server now starts. Thanks to sangineni.
Similar Messages
-
Having trouble starting the J2EE Server... for hours and hours...
Hi:
I am having problem starting the J2EE Server.
I have looked through this page where lots of people had similar problem:
http://forum.java.sun.com/thread.jsp?forum=136&thread=468079
but the solutions provided there could not solve my problem...
My problem, specifically, is that when I try to start the sever, I get:
com.sun.enterprise.admin.servermgmt.DomainException: ...
CLI156 Could not start the domain domain1.
I am using Windows XP Professional on IBM ThinkPad X30.
Does anyone have some idea how to solve the problem?
Thanx!bsankararao,
Thanks for the quick response. I am currently using the latest IE6.0 XPXP2 version and yes I doe have a successful start of the domain1 process. Here is the startup log for verification:
[#|2004-02-02T15:03:04.765-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-02T15:03:12.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-02T15:03:12.436-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-02T15:03:14.649-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-02T15:03:15.470-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-02T15:03:15.491-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-02T15:03:15.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-02T15:03:32.084-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-02T15:03:34.338-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-02T15:03:34.938-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-02T15:03:36.391-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-02T15:03:36.421-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|autoDeployment status dir missing, creating a new one|#]
[#|2004-02-02T15:03:36.451-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\MEjbApp.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.471-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Selecting file [D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear] for autodeployment|#]
[#|2004-02-02T15:03:36.481-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\MEjbApp.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:38.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:38.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5108: EJBC - Generated code for remote home and EJBObject implementations for [MEjbApp]|#]
[#|2004-02-02T15:03:48.818-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
[#|2004-02-02T15:03:49.549-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 12728 msec, Total EJB Compiler Module Time: 10775 msec, Portion spent EJB Compiling: 84%
Breakdown of EJBC Module Time: Total Time for EJBC: 10775 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 10605 msec (98%), JAX-RPC Generation: 20 msec (0%),
|#]
[#|2004-02-02T15:03:49.750-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
[#|2004-02-02T15:03:50.571-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\MEjbApp.ear.|#]
[#|2004-02-02T15:03:50.591-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear ] for autodeployment.|#]
[#|2004-02-02T15:03:51.292-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.029-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.309-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 5688 msec, Total EJB Compiler Module Time: 4737 msec, Portion spent EJB Compiling: 83%
Breakdown of EJBC Module Time: Total Time for EJBC: 4737 msec, CMP Generation: 2674 msec (56%), Java Compilation: 1933 msec (40%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
|#]
[#|2004-02-02T15:03:56.339-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-02T15:03:56.740-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\lib\install\applications\__ejb_container_timer_app.ear.|#]
[#|2004-02-02T15:03:56.810-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-02T15:03:57.210-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-02T15:03:57.461-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-02T15:03:57.521-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-02T15:03:57.571-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-02T15:03:57.721-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-02T15:03:59.924-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-02T15:04:00.315-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.355-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-02T15:04:00.936-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.946-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-02T15:04:00.966-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:00.986-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-02T15:04:01.266-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075755841276|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-02T15:04:01.276-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-02T15:18:13.512-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T15:18:13.522-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T15:18:39.119-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T15:18:39.119-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:27:40.443-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:41.174-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:27:49.076-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [].|#]
[#|2004-02-02T19:27:49.076-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for .|#]
[#|2004-02-02T19:31:57.022-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=11;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:31:57.022-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T19:32:08.869-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T19:32:08.869-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-02T20:00:22.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=12;|SEC5046: Audit: Authentication refused for [admin].|#]
[#|2004-02-02T20:00:22.424-0600|WARNING|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=12;|Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.|#]
[#|2004-02-03T08:30:22.556-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T08:30:23.808-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T08:30:23.998-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T08:30:26.422-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T08:30:27.143-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T08:30:27.203-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T08:30:27.253-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T08:30:31.509-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T08:30:33.462-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T08:30:33.963-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T08:30:34.914-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T08:30:36.036-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T08:30:36.877-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T08:30:37.027-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T08:30:37.428-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T08:30:37.618-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T08:30:37.638-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T08:30:37.668-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T08:30:37.798-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T08:30:39.901-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T08:30:40.202-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.242-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T08:30:40.402-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.412-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T08:30:40.442-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.452-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T08:30:40.732-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075818640752|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T08:30:40.752-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T08:48:32.383-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Selecting file [ D:\Sun\AppServer\domains\domain1\autodeploy\hello.war ] for autodeployment.|#]
[#|2004-02-03T08:48:33.785-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [hello]|#]
[#|2004-02-03T08:48:33.835-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [hello]|#]
[#|2004-02-03T08:48:34.606-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 1862 msec, Total EJB Compiler Module Time: 50 msec, Portion spent EJB Compiling: 2%
Breakdown of EJBC Module Time: Total Time for EJBC: 50 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 10 msec (20%),
|#]
[#|2004-02-03T08:48:34.807-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/hello]|#]
[#|2004-02-03T08:48:35.007-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T08:48:36.719-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-02-03T08:48:36.729-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=11;|[AutoDeploy] Successfully autodeployed : D:\Sun\AppServer\domains\domain1\autodeploy\hello.war.|#]
[#|2004-02-03T14:53:47.246-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T14:53:48.718-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T14:53:48.929-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T14:53:51.222-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T14:53:52.003-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T14:53:52.033-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T14:53:52.043-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T14:53:56.449-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T14:53:58.492-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T14:53:58.983-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T14:53:59.985-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T14:54:01.206-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T14:54:02.048-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T14:54:02.188-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T14:54:02.678-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T14:54:02.899-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T14:54:02.919-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T14:54:02.939-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T14:54:02.989-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T14:54:03.119-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T14:54:05.563-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T14:54:05.883-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:05.943-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T14:54:06.083-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.093-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T14:54:06.123-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.133-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T14:54:06.424-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075841646434|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T14:54:06.434-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-03T23:32:20.272-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02] from [Sun Microsystems Inc.]|#]
[#|2004-02-03T23:32:22.004-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-02-03T23:32:22.234-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-02-03T23:32:24.608-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating Engine server|#]
[#|2004-02-03T23:32:25.629-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-02-03T23:32:25.659-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-02-03T23:32:25.689-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-02-03T23:32:31.237-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-02-03T23:32:33.781-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-02-03T23:32:34.332-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-02-03T23:32:35.453-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-02-03T23:32:37.156-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-02-03T23:32:38.137-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-02-03T23:32:38.317-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-02-03T23:32:38.948-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-02-03T23:32:39.179-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-02-03T23:32:39.199-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-02-03T23:32:39.229-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello] in virtual server [server] at [hello]|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-02-03T23:32:39.269-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-02-03T23:32:39.439-0600|INFO|j2ee-appserver1.4|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: J2EETM 1.4 Application Server|#]
[#|2004-02-03T23:32:42.343-0600|INFO|j2ee-appserver1.4|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-02-03T23:32:42.724-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.764-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-02-03T23:32:42.944-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.954-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-02-03T23:32:42.994-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.014-0600|INFO|j2ee-appserver1.4|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-02-03T23:32:43.315-0600|INFO|j2ee-appserver1.4|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = domain1_server, Home = [D:\Sun\AppServer\imq\bin].|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1075872763335|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-02-03T23:32:43.335-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-02-04T08:31:44.681-0600|INFO|j2ee-appserver1.4|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_02 -
Hi:
I am new to J2EE and I followed the instruction on the J2EE Tutorial setting up the J2EE SDK. When I tried to start the J2EE server by typing in "C:\j2ee -verbose", the server can't seem to start... After it gets to "Starting JMS service..." , it jumps back to the command prompt "C:\>"
If I then try to do a "j2ee -stop", I get an error "javax.naming.CommunicationException: Can't find SerialContextProvider" (which, I think, indicates the server never got started)
I am using Windows 2000 and I am pretty sure I have the environment variables set properly. Does anyone know why this is happening? Thanx!
The following is the trace of me doing "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/Cloudscape, url = jdbc:cloudscape:rmi:Cloudscape
DB;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/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudscape.co
re.RemoteXaDataSource@b301f2
Starting JMS service...
C:\j2sdkee1.3.1\bin>
EugeneI have read some posts and get the answer
change the pc language to English
and reinstall j2ee
all should be ok!
I get message "J2EE server startup complete" now.
luck! -
Com.sap.mw.jco.JCO$Exception starting the J2EE server 620
We are using J2EE 620 pl26, with the latest JCO, but often trying to acces the J2EE services like Mobile Engine Webconsole 21 or the WebEnabled Sapconsole 640 we recive the message:
'Dispatche runningbut no server connected'.
The J2EE dispatcher and server are started at Sap startup. Just after that time the J2EE is working fine, but after some time the J2EE server get down.
We found this message into the J2EE console_logs:
"RFCEngine: Server startup error, stopping "SAPProfile:F:\usr\sap\CAM\SYS\profile\CAM_DVEBMGS00_itmif089" :
com.sap.mw.jco.JCO$Exception: (129) JCO_ERROR_SERVER_STARTUP: Server startup failed at Fri Oct 15 09:58:20 CEST 2004.
This is caused by either a) erroneous server settings, b) the backend system has been shutdown, c) network problems. Will try next startup in 2 seconds.
Could not establish the lcom accepted connection: lcomListenCreate failed with rc 9"
We do not find any Oss notes for that.
Any advise is wellcome.
RegardsHi Mauro,
normally when you apply a new SAP Kernel a frfclib.sar file is delivered. This frfclib file need to be copied to the J2EE directory /os_libs and need to be extracted there. This frfclib version must always match to the SAP Kernel version.
Ciao
tc -
Problems starting the http server
I have problems starting 9ias http server. I issue:
/u09/ora9ias/infra/opmn/bin> opmnctl startall
opmnctl: starting opmn and all managed processes...
Request partial success -- 1 of 4 processes started.
and the HTTP server does not start.
If I go to the enterprise manager, the only service started is Single Sign On.
If I try to enter to the HTTP server it gives me the following error:
An error was encountered while loading page. Failed to initialize configuration management user session.. Repository access failed Root Cause: Password could not be retrieved. Password could not be retrieved
The iasdb is already started and working.
Any clues what can be going wrong??
help is greatly appreciated.Jorge, I suspect you've already fixed this problem. But if not, I have a standard operating procedure for this. Here's the gist of it, let me know if you need more detail.
1. shutdown the opmn layer (opmnctl stopall)
2. determine if the httpd.pid file exists (it's in the Apache/logs directory on linux)
3. delete the .pid file if it's there
4. if not, or if there's still a problem, tail the error_log for info
5. try to start the httpd (dcmctl start -ct ohs)
6. still a problem? ps -auxw | grep httpd
7. kill off the process(es)
8. try again to start up with dcmctl command in step 5
I can usually get it going at this point. If not, I have to do a reboot, which has always worked. Don't forget to shutdown the emctl and webcachectl if you're rebooting.
Hopefully this helps. It took a lot of learn-as-you-go for us to get this procedure. I'm sure the pros will role their eyes! :-) -
Problem installing the J2EE server on a 6.40 WebAS System
On an AIX server I've installed Oracle 9.2, WebAS Central ABAP instance and
now I'm trying to install the J2EE server. When it gets to phase
"Deployment of JDDI" I get the following error. Does anyone have any
ideas on how to resolve this. Thanks!
Apr 4, 2005 2:17:21 PM Info: Starting deployment
Apr 4, 2005 2:17:21 PM Info: Loading selected archives...
Apr 4, 2005 2:17:21 PM Info: Loading archive '/dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA'
Apr 4, 2005 2:17:21 PM Info: Selected archives successfully loaded.
Apr 4, 2005 2:17:21 PM Info: Error handling strategy: OnErrorStop
Apr 4, 2005 2:17:21 PM Info: Update strategy: UpdateLowerVersions
Apr 4, 2005 2:17:21 PM Info: Starting to execute deployment action (deploy) for "synclog".
Apr 4, 2005 2:17:24 PM Info: Creating connections to database "DBW".
Apr 4, 2005 2:17:24 PM Info: Creating vendor connection to database.
Apr 4, 2005 2:17:24 PM Error: Creation of vendor connection failed.
Original error message is:
java.sql.SQLException: Io exception: Invalid number format for port number
Stack trace of original Exception or Error is:
java.sql.SQLException: Io exception: Invalid number format for port number
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3649)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:353)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:368)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:549)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:349)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Apr 4, 2005 2:17:24 PM Error: Execution of deployment action for "synclog" aborted: Db connect failed.
Apr 4, 2005 2:17:25 PM Error: Deployment NOT successful for synclog
Apr 4, 2005 2:17:25 PM Error: At least one of the Deployments failed
Apr 4, 2005 2:17:25 PM Info: Summarizing the deployment results:
Apr 4, 2005 2:17:25 PM Error: Aborted: /dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA
Apr 4, 2005 2:17:25 PM Error: Processing error. Return code: 4Also, I should mention I'm running the 64bit capable SDK for version 1.4.2 for AIX.
Thanks again! -
Problem in Starting the J2EE Server
Hi All,
I am getting the following error message when I start the Server.
[Thr 3820] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]
[Thr 3820] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
[Thr 3820] JControlCloseProgram: started (exitcode = 66)
[Thr 3820] JControlCloseProgram: good bye... (exitcode = 66)
Expecting any clue to resolve this issue.
Reg/VenkatHi,
This error might be due to the memory heap size. To resolve this:
Stop ur server.
1)Go to My Computer>properties>Advanced.
2)In the performance tab>settings>performance options-->Advanced -->change
3)Change the heap size of the memory to the local drives.
Initial size (1524) and Max size(3048).
<u><b>Alternate Solution</b></u>
Go to services.msc and start all the oracle instances. (Manual Start)
Restart the cluster. The server will start to run.
Hope it helps,
Regards,
Nagarajan. -
Error in starting the j2ee server
Hi...... I installed the j2sdkee-1_3_1-win........... I was able to deploy and run some sample web apps but after compiling a java file (tag lib) and setting my classpath (to point to a servlet jar file) I started getting this errors (see below).... Can someone tell me how to go about this? the keystore.jks is definitely existing in my C:\j2sdkee1.3.1\lib\security\ folder.
Thanks in advance!
C:\Documents and Settings\cruzm1>j2ee
Cannot write the seed file for fast startup. The next startup will be slow.
J2EE server listen port: 1050
java.io.FileNotFoundException: C:\j2sdkee1.3.1\lib\security\keystore.jks (The sy
stem cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at com.sun.enterprise.security.SSLUtils.loadKS(SSLUtils.java:147)
at com.sun.enterprise.security.SSLUtils.initKeyStore(SSLUtils.java:78)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.init(IIOPSSLSocketFactor
y.java:74)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(II
OPSSLSocketFactory.java:153)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPS
SLSocketFactory.java:139)
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
243)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Documents and Settings\cruzm1>j2ee
Cannot write the seed file for fast startup. The next startup will be slow.
J2EE server listen port: 1050
java.io.FileNotFoundException: C:\j2sdkee1.3.1\lib\security\keystore.jks (The sy
stem cannot find the path specified)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at com.sun.enterprise.security.SSLUtils.loadKS(SSLUtils.java:147)
at com.sun.enterprise.security.SSLUtils.initKeyStore(SSLUtils.java:78)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.init(IIOPSSLSocketFactor
y.java:74)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createSSLServerSocket(II
OPSSLSocketFactory.java:153)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.createServerSocket(IIOPS
SLSocketFactory.java:139)
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
243)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
org.omg.CORBA.INTERNAL: vmcid: SUN minor code: 209 completed: No
at com.sun.corba.ee.internal.iiop.GIOPImpl.createListener(GIOPImpl.java:
256)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:205
at com.sun.corba.ee.internal.iiop.GIOPImpl.initEndpoints(GIOPImpl.java:1
40)
at com.sun.corba.ee.internal.POA.POAORB.getServerEndpoint(POAORB.java:49
2)
at com.sun.corba.ee.internal.POA.POAImpl.pre_initialize(POAImpl.java:156
at com.sun.corba.ee.internal.POA.POAImpl.<init>(POAImpl.java:114)
at com.sun.corba.ee.internal.POA.POAORB.makeRootPOA(POAORB.java:114)
at com.sun.corba.ee.internal.POA.POAORB$1.evaluate(POAORB.java:132)
at com.sun.corba.ee.internal.core.Future.evaluate(Future.java:21)
at com.sun.corba.ee.internal.corba.ORB.resolveInitialReference(ORB.java:
2488)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.ja
va:2423)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:196)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:206)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Unable to create ORB. Possible causes include TCP/IP
ports in use by another process
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:346)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
J2EE server reported the following error: Unable to create ORB. Possible causes
include TCP/IP ports in use by another process
Error executing J2EE server ...
C:\Documents and Settings\cruzm1>deploytool
Starting Deployment tool, version 1.3.1
(Type 'deploytool -help' for command line options.)
Could not connect to localhostI'm not sure the IOException is the real issue. It looks like there may be some other process using one of the ports the SDK is attempting to bind to. Did you try rebooting your machine and restarting the SDK? If there is another process using a port the SDK requires you may need to change the ports used by the SDK. You can find most of the port settings in the config directory in one of the properties files, depending which port you would like to change. Looks like the orb port is you issue so reboot or modify orb.properties.
-
Error : While Starting the J2EE Server
Hi All,
When i am trying to open the SAP Console Management i am getting this following error.
"sapstartsrv.exe has encountered a problem and needs to close. We are sorry for the inconvenience."
The server which was installed was also not visible int\ SAP Console Management.
Thanks,
MugundhanWhat is the "Event Log" entries says? Just check the filesystems which stores profiles and executable are available in read/write mode.
Make the SAP services to "Manual" mode and then restart the Windows server. Once the server comes up, check whether the following services are up
1. Server
2. Computer Browser
3. Remote Procedure Call
4. Workstation
Check all the required filesystems are available. If yes, then try to start the service.
Did you apply any windows patches recently? What is the windows service pack level used? -
ABAP Trial version u2013 starting the application server
Hi,
I have a problem starting the application server via the management console. After choosing action ->start I have to enter user and password. Do I have to create a new user password combination, use the OS password or try bcuser and minisap? None of these three options worked out. I always get the message 'Start failed: 2 Invalid Credentials'. Or went there something wrong during the installation?
Thanks for your help.
BirgitHey Birgit,
In my case I installed ABAP Trial version (also known as MiniSap) on my local machine (Windows).
When I turn on the machine, my Windows(OS) requires a User/Password (It was configured this way but it is possible you configure to not require a User/Password, it uses a default).
When I instaled the ABAP Trial version, I logged on with a User/Password with administrator rights (it is necessary for installation).
When, in the "Management Console", I start the ABAP (the "NSP" node), it asks me the user and password and I use the OS User/Password that I used to install ABAP Trial (above).
If you are doing the same I don't know why the message "Start failed: 2 Invalid Credentials".
Merry Christmas,
Edited by: Walmir Catunda on Dec 15, 2008 11:34 AM -
Problem with deploying : SDM could not start the J2EE cluster on the host .
Hello, All
I have following problem with deploying the aplication I get this messenger:
16/09/2008 07:59:44 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : 192.168.0.14
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Result
=> deployment aborted : file:/C:/DOCUME1/PENITU1/LOCALS~1/Temp/temp47114ZChangeRequestDatabase.ear
Aborted: development component 'ZChangeRequestDatabase'/'local'/'LOKAL'/'0.2008.05.03.04.24.17'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated. There is no cluster control instance running on host Jupiter which is described in SecureStorage . The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :|Name:JM_T1221612526745_0_penitus15 |Host:PENITUS15 |State:5|HostAddress:192.168.0.205||Name:JM_T1221612357814_0_Jupiter |Host:pfs |State:5|HostAddress:192.168.0.14||Name:JC_Jupiter_JTP_00 |Host:pfs |State:5|HostAddress:192.168.0.14|Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Deployment exception : The deployment of at least one item aborted
I dont'n know How do I solver this error?
- I reviewed the virtual memory and I increase the virtual memory
- I restarted the server and the system
- I reviwed the parameter in the config tool --> cluster --> security storage it is OK
Any suggestion for solver this problem
Thanks
Regards
DSI found this messenger in Additional log information., Please si
17/09/2008 03:04:51 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[004]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\JTP\JC00\SDM\program\log\sdmcl20080917200328.log]/>
<!PATTERN[sdmcl20080917200328.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Sep 17, 2008 1:04:40 PM Info: -
Starting deployment -
Sep 17, 2008 1:04:40 PM Info: Error handling strategy: OnErrorStop
Sep 17, 2008 1:04:40 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Sep 17, 2008 1:04:40 PM Info: Update strategy: UpdateAllVersions
Sep 17, 2008 1:04:40 PM Info: Starting deployment prerequisites:
Sep 17, 2008 1:04:40 PM Info: Loading selected archives...
Sep 17, 2008 1:04:40 PM Info: Loading archive 'C:\usr\sap\JTP\JC00\SDM\program\temp\temp62604ZIssueDatabase.ear'
Sep 17, 2008 1:04:41 PM Info: Selected archives successfully loaded.
Sep 17, 2008 1:04:41 PM Info: Actions per selected component:
Sep 17, 2008 1:04:41 PM Info: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:41 PM Info: Ending deployment prerequisites. All items are correct.
Sep 17, 2008 1:04:43 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Saved current Engine state.
Sep 17, 2008 1:04:45 PM Info: Starting: Initial deployment: Selected development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0' will be deployed.
Sep 17, 2008 1:04:45 PM Info: SDA to be deployed: C:\usr\sap\JTP\JC00\SDM\root\origin\local\ZIssueDatabase\LOKAL\0\0.2008.04.17.10.53.03\temp62604ZIssueDatabase.ear
Sep 17, 2008 1:04:45 PM Info: Software type of SDA: J2EE
Sep 17, 2008 1:04:45 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Info: Starting cluster instance processes.
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[PENITUS15] Throwable: java.net.UnknownHostException Throwable message: PENITUS15
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: Unable to compare host[Jupiter] and host[pfs] Throwable: java.net.UnknownHostException Throwable message: pfs
Sep 17, 2008 1:04:45 PM Error: An error occured while starting a cluster instance.
Sep 17, 2008 1:04:45 PM Error: There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
Sep 17, 2008 1:04:45 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Sep 17, 2008 1:04:45 PM Error: Aborted: development component 'ZIssueDatabase'/'local'/'LOKAL'/'0.2008.04.17.10.53.03'/'0':
SDM could not start the J2EE cluster on the host Jupiter! The online deployment is terminated.
There is no clutser control instance running on host Jupiter which is described in SecureStorage .
The instances, returned by MessageServer [MS host: Jupiter; MS port: 3901], are :
Name:JM_T1221672404781_2_penitus15
Host:PENITUS15
State:5
HostAddress:192.168.0.215
Name:JM_T1221679486171_0_Jupiter
Host:pfs
State:5
HostAddress:192.168.0.14
Name:JC_Jupiter_JTP_00
Host:pfs
State:5
HostAddress:192.168.0.14
Please check if there is an appropriate running cluster instances.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).STARTUP_CLUSTER)
Sep 17, 2008 1:04:45 PM Info: Starting to save the repository
Sep 17, 2008 1:04:46 PM Info: Finished saving the repository
Sep 17, 2008 1:04:47 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Sep 17, 2008 1:04:47 PM Error: -
At least one of the Deployments failed -
Any help will be well received about this problema
Thk
Regards
DS -
Problem in starting the weblogic server
HI friends,
I have a problem running the weblogic server, i am getting error as follows:
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http:\\hostname:port\console *
starting weblogic with Java version:
java version "1.4.2_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
Starting WLS with line:
C:\bea\JDK142~1\bin\java -client -Xms256m -Xmx512m -XX:CompileThreshold=8000 -
XX:PermSize=32m -XX:MaxPermSize=128m -Djrockit.codegen.optpriority=1 -Xverify:
none -Xverify:none -da -Dplatform.home=D:\bea\WEBLOG~1 -Dwls.home=D:\bea\WEBLOG
~1\server -Dwli.home=D:\bea\WEBLOG~1\integration -Dweblogic.management.discover
=true -Dweblogic.ProductionModeEnabled= -Dwlw.iterativeDev= -Dwlw.testConsole=
-Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\bea\patch_weblogic901\profiles\
default\sysext_manifest_classpath -Dweblogic.Name=AdminServer -Djava.security.po
licy=D:\bea\WEBLOG~1\server\lib\weblogic.policy weblogic.Server
The WebLogic Server encountered a critical failure
Exception in thread "main" java.lang.NoClassDefFoundError
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:174)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:372)
at weblogic.Server.main(Server.java:66)
So plz suggest me.
Regrads
Abhi007Hi,
NoClassDefFoundError signifies that there is a classpath problem.
May be you are missing some critical jars in your classpath
for ex. weblogic.jar, jdk's rt.jar or something else.
You need to find this out.
HTH
VJ -
Hello,
The J2EE Server not starting. (Not able to communicate with message server)
The following is the description I got from SAP.
" Most likely you did configurations on the instance properties, instead
of the global properties, which is the one where the the configurations
should be done. That is why now you did set local properties
which are now false, for example : ume.ldap.access.server_port=[]
This is the cause why the LDAP connection data cannot be retrieved.
This is why the UME service cannot be started.
This is why the J2ee engine is not comming up. "
Pls help.Hi Karan
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool.
2.No go to instance -
>server----->services--->com.sap.security.core.ume.services node.
3.Look for ume.ldap.access.server_port=[]
4.See if you have changed the value for the above parameter.If yes change the value to default and restart the engine.It will work
If at all you want to change any configurations you should do it following the below steps:
1.Go to \usr\sap\SID\JCXX\j2ee\configtool and start the config tool
2.Go to Global Server Configurations-->Services--
>
Please award points: -
Problem of start up J2EE server
Recently, I installed the J2SE1.5.0. Unfortunately, I cannot start my J2EE server, and get an error message as following:
Starting Domain domain1, please wait.
Log redirected to C:\Sun\AppServer\domains\domain1\logs\server.log.
Provider org.apache.crimson.jaxp.DocumentBuilderFactoryImpl not found
Press any key to continue . . .
Is there anyone can help me? Than you.This is a known issue with J2EE 1.4 Application Server and J2SE 1.5 - this is corresponding bug report:
http://developer.java.sun.com/developer/bugParade/bugs/4967167.html
Fix will become available in upcoming Application Server 8 PE release. In the meantime, you should reinstall J2EE 1.4 on this system in such a way that it uses J2SE 1.4.2 as its J2SE installation. -
Problem in starting the web-server after configuring .so on AIX
I am trying to configure a .so file in iplanet fasttrack web server 4.1 on AIX 4.3. I have build the .so file on IBM AIX 4.3. But while starting the web-server it failed to start.It fails when I include the following in obj.conf "Init fn="test-init" config="ConfigFile". While starting web-server I got the following :
server terminated (signal 11): watchdog is restarting it
failure: server initialization failed
Any pointers on this would be helpful.I got similar errors in the past when the web server process was running in the background. Sometimes shutting down WAS does not work.
Before you start WAS ensure that no java process is running or better try rebooting.
Maybe you are looking for
-
CRM : creation of service in transaction COMMPR01
Hi Experts Can anyone tell me how to create a service in transaction COMMPR01 and also the BAPI or function modules used to create service in CRM . Thanks & Regards.
-
Problem in ECC 5.0 Installation
Hi Gurus, please anyone can suggest wheather m gone right procedure for SAP ECC & SOL installation, 1st i have install SOL & generate Key from it, In SOL config, CI = SOL Inst # = 00 DB = KKK SOL GET installed successfully & i have generated KEY als
-
Variable screen in Planning Function for Integrated Planning
Hi all. I have created a planning application with the WAD, based on an Input_ready Query. Manual planning works fine and even planning functions go well, using the command wizard. However, if I try to use a variable in a planning function and I set
-
I'm trying to figure out why in album view some Compilations by Various Artists get sorted by Artist under "V" and then some compilations also by Various Artists or Unknown Artist get sorted after the "Z"'s or numerical titled albums. here's example
-
Core i7 15" MacBook Pro not rebooting or shutting down
Hi All, My MacBook Pro will not shut down or reboot properly - it sits at the gray screen with the spinning circle. I have tried resetting the SMC but to no avail and I have to turn off by holding down the power switch. This has just become more of a