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.
Regards

Hi 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

Similar Messages

Com.sap.caf.mp.base.exception.EngineException: Problem in server response:

Hi,
I have created one CAF application,which is having one external webservice and one application service.Webservice takes two input parameters(string,boolean) and it returns an arraylist.
So when i test the CAF application on the CAF service browser it is giving me error like " com.sap.caf.mp.base.exception.EngineException: Problem in server response: [Bad Request]."
I am getting this error while creating object of web service.
Can anybody help me on this issue..
Thanks in Advance

It looks like you are not authorized to execute the webservice. Check the webservice authentication settings.
Peter

Starting the J2EE server

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>
Eugene

I 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!

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

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,
Mugundhan

What 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?

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 localhost

I'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.

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.

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/Venkat

Hi,
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.

Com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl

Hi SAP Expert,
I am trying to understand when I use the JCo library embedded by NetWeaver AS Java, a SessionReferenceProvider named com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl is registered to environment. What can this provider implementation do?
As I know, the session reference provider can be implemented by a runtime environment that has a session concept in order to provide JCo a simple reference to a session. JCo is using the ID associated with a JCoSessionReference internally for stateful function module invocations, i.e. the same physical connection is used for a sequence of function modules. In a generally stateless environment, e.g. JCo standalone, JCoContext.begin(JCoDestination destination) starts such a sequence for a destination. I would like to know what com.sap.engine.sessionmgmt.jco.applib.impl.SessionReferenceProviderImpl reference a JCo session to? and how to use it.
Thanks,
Jian

Hi Robert,
You can first try stopping a Java application named sessionmgmtjcoapplib from Star&Stop, then register yours sessionReferenceProvider again.
Jian

ERROR:com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException

Dear All,
We have taken a par file from another project and deployed in the J2EE engine using SDM.It was succesfully deployed with out any warnings.I have created an iview also.When we are trying to access that i view i am getting an error as follows:
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
    at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
    at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
    at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
    at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
    at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
    ... 51 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version     null
DOM version     null
Client Type     msie6
Client Type Profile     ie6
ActiveX     enabled
Cookies     enabled
Frames     enabled
Java Applets     enabled
JavaScript     enabled
Tables     enabled
VB Script     enabled
Server
Web Dynpro Runtime     Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Mon Mar 03 21:11:10 GMT+05:30 2008
J2EE Engine     7.00 patchlevel
Java VM     Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_13-b06, vendor: Sun Microsystems Inc.
Operating system     Windows 2003, version: 5.2, architecture: ia64
Session & Other
Session Locale     en
Time of Failure     Thu Apr 10 14:31:31 GMT+05:30 2008 (Java Time: 1207818091497)
Web Dynpro Code Generation Infos
local/WDHolidayCalendar
SapDictionaryGenerationCore     7.0009.20060802115015.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:24:21[UTC], changelist=413123, host=PWDFM101.wdf.sap.corp)
SapDictionaryGenerationTemplates     (unknown)
SapGenerationFrameworkCore     7.0009.20060719095755.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:12:57[UTC], changelist=411255, host=PWDFM101.wdf.sap.corp)
SapIdeWebDynproCheckLayer     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:00[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapMetamodelCommon     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:46[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelCore     7.0009.20060210160857.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:13:38[UTC], changelist=388995, host=PWDFM101.wdf.sap.corp)
SapMetamodelDictionary     7.0009.20060719095619.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:21:59[UTC], changelist=411251, host=PWDFM101.wdf.sap.corp)
SapMetamodelWebDynpro     7.0009.20060428190938.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:26:52[UTC], changelist=400815, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationCTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
SapWebDynproGenerationCore     7.0009.20060802115035.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:30:11[UTC], changelist=413124, host=PWDFM101.wdf.sap.corp)
SapWebDynproGenerationTemplates     7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:45:29[UTC], changelist=413534, host=pwdfm101)
sap.com/tcwddispwda
No information available     null
sap.com/tcwdcorecomp
No information available     null
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type extern:com.bel.holidaycal.model.types.WDModelHolical:com.bel.holidaycal.model.types.Zhrt029 could not be loaded: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:305)
     at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:234)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:448)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:386)
     at com.sap.tc.webdynpro.progmodel.controller.Component.getMappableContext(Component.java:415)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:79)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.initMapping(MappingInfo.java:121)
     at com.sap.tc.webdynpro.progmodel.context.MappingInfo.init(MappingInfo.java:117)
     at com.sap.tc.webdynpro.progmodel.context.MappedNodeInfo.doInit(MappedNodeInfo.java:212)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)
     at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)
     at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.doOpen(WebDynproWindow.java:295)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.show(ApplicationWindow.java:183)
     at com.sap.tc.webdynpro.clientserver.window.ApplicationWindow.open(ApplicationWindow.java:178)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:364)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.dictionary.runtime.DdException: Type com.bel.holidaycal.model.types.Zhrt029 does not exist
     at com.sap.dictionary.types.mdi.util.ProviderUtil.createAbapTypeXmlMap(ProviderUtil.java:400)
     at com.sap.dictionary.runtime.mdi.DataProvider.createSimpleTypeFromAbapType(DataProvider.java:586)
     at com.sap.dictionary.runtime.mdi.DataProvider.getDataType(DataProvider.java:286)
     at com.sap.dictionary.runtime.DdDictionary.getDataType(DdDictionary.java:95)
     at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:164)
     at com.sap.dictionary.runtime.DdBroker.getStructure(DdBroker.java:180)
     at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getStructure(DataTypeBroker.java:303)
     ... 49 more
I have created the JCO connections also ,i am able to test them also.I have imported the same into NWDS and deployed the application , its deploying but the out put is the same error.
I have cross checked the models and found that the Model is there in the model types.
Can any one help me regarding this.
Waiting for the response ASAP.
Thanks
Ravi.S

Hi,
I think you mean ear file and not par file. Check these threads. The exception is mentioned to be because of JCo problems only.
Type com.sap.xss.ser.xssmenu.model.types.P_Pernr does not exist
WDTypeNotFoundException: type model.types.Zbtr_Wbselement could not be load
WebDynpro using BAPI has an error
Regards,
Harini S

Error : com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

Hi
Just got the portal EP7.0 configured to my already existing HCM server ECC6. But on clicking any link i get this error :
Application error occurs during processing the request.
Details: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'sap.com/mss~pcr' since it is not a Web Dynpro object. The ID of this error is
Exception id: [001517258E860068000000B2000019D80004627960F883DF].
I searched the forum but could not get a solution though mnay have faced this problem. This is for all applications and not only PCR.
Thanks and regards
Pamela

Hi,
Check JCO destinations are active?
check the below link for further investigation
http://help.sap.com/saphelp_nw04/helpdata/en/1f/1b1041a0f6f16fe10000000a1550b0/frameset.htm
Koti Reddy

Com.sap.security.core.ume.service failed. J2EE Engine cannot be started

Hi,
I have configured SNC on NetWeaver 7.0 (ABAP+JAVA) System on Windows 2003 Server with MS-SQL 2005 Database.
After the SNC configuration restarted the Server but the JAVA Server process is going down with EXIT Code -11113. The SNC Configuration is working fine but JAVA is not running. SDM and dispatcher are in green but server process is going gray.
I have checked the log files under C:\usr\sap\SID\DVEBMGS00\j2ee\cluster\server0\log
The following is the part of log file.
#1.5#005056BA6C3F001D0000000F000008D8000489ACAFC86070#1277274683393#com.sap.engine.core.service630.container.ServiceRunner##com.sap.engine.core.service630.container.ServiceRunner#######SAPEngine_System_Thread[impl:5]_71##0#0#Error#1#/System/Server#Java###Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
[EXCEPTION]
#1#com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
     ... 6 more
#1.5#005056BA6C3F001D00000011000008D8000489ACAFC8628E#1277274683393#com.sap.engine.core.Framework##com.sap.engine.core.Framework#######SAPEngine_System_Thread[impl:5]_71##0#0#Fatal#1#/System/Server#Plain###Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.#
Please help me to solve the issue.
Thanks,
Ajay.

Hi Tim,
I have configured using Kerberos library for 32 bit on Net Weaver 7.0 with MS SQL 2005 Server on Windows 2003 Server. I didnt change any thing on JAVA side. I have configured as per the Kerberos configuration steps as per below URL
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/44/0ebf6c9b2b0d1ae10000000a114a6b/frameset.htm
The configuration was successful and I am able to login with out asking password, but After the configuration when I have restarted every thing on ABAP side works well but JAVA server process going down with EXIT code -11113. One of the log file contains follows error message.
com.sap.engine.frame.ServiceException: <Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME initialization failed.', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization failed.
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:372)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:105)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: SNC required for this connection
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:356)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:156)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:109)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:56)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:266)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:279)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jun 25, 2010 3:05:24 AM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_69] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
One of the line says "SNC required for this connection". What does this mean? What else need to be done for JAVA to communicate with ABAP?
Thanks,
Ajay.

FPN error: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException

Hi, all.
I am trying to initiate a webdynpro page from the producer to the consume portal via RDL. It works fine for a day. Then it starts giving me the error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page ...
This error cannot be cleared by clearning the FPN cache or synchronize with the producer. Of course, you can also delete the page from the consumer and copy it over from the producer again. It will work. But this is not a good workaround for a production system. We also don't know the cause either. Here is the stack trace:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.portal.fpn.exception.unchecked.FpnUnMarshallingException: Could not find a marshaller for 'com.sapportals.portal.page' from path 'pcd:consumer_content/DEP/portal_content/ca.ottawa.sap.supportcentre/ca.city.ottawa.OttawaRoles/ca.city.ottawa.ManagerInfo/ca.city.ottawa.ManagerInfo-FinanceOnly/ca.city.ottawa.ManagerInfo_MSS_Finance/ca.city.ottawa.Mileage_Parking_Managers'
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:323)
     at com.sap.portal.fpn.entrypoint.RuntimeFederatedPersistance.retrieveDLRemoteState(RuntimeFederatedPersistance.java:103)
     at com.sap.portal.fpn.FpnRuntimeService.bringRemoteState(FpnRuntimeService.java:134)
     at com.sap.portal.fpn.FpnRuntimeService.doFpnLookup(FpnRuntimeService.java:97)
     at com.sap.portal.fpnprovider.fpn.GenericContext.lookup(GenericContext.java:49)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:526)
     ... 31 more
Caused by: com.sap.portal.pcm.OperationFailedException: Creating DL outside the PCD
     at com.sap.portal.pcm.iviewserver.CiViewSLObjectsManager.instantiateDescriptor(CiViewSLObjectsManager.java:687)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:79)
     at com.sap.portal.pcm.page.PagesSrv.instantiateDescriptor(PagesSrv.java:71)
     at com.sap.portal.fpn.marshal.IViewMarshaller.instantiateRelatedItemDescriptor(IViewMarshaller.java:582)
     at com.sap.portal.fpn.marshal.IViewMarshaller.performSemanticActions(IViewMarshaller.java:506)
     at com.sap.portal.fpn.marshal.PageMarshaller.performSemanticActions(PageMarshaller.java:499)
     at com.sap.portal.fpn.marshal.IViewMarshaller.unmarshalResolvedDLChain(IViewMarshaller.java:715)
     at com.sap.portal.fpn.marshal.PageMarshaller.unmarshalResolvedDLChain(PageMarshaller.java:328)
     at com.sap.portal.fpn.marshal.ContentMarshallerService.unMarshallDLChain(ContentMarshallerService.java:320)
     ... 38 more
So far I found nothing on OSS or SDN on this FpnUnMarshallingException. Has anyone seen this error before?
Thanks.
Jonathan.
Edited by: Jonathan Ma on Apr 23, 2009 12:25 AM

Hi Jonathan,
you may deactivate the GPN cache as well as the old navigation cache. About the GPN there is note 1172433. Both caches are not used in FPN scenario and can lead to such strange problems. If this won't help please open a support message for this that we can analyse further.
Cheers,
Anja

Unable to start the managed server on OBIEE11.1.1.6.0, Oracle RTD exception

Hi
I am unable to start the Managed server on OBIEE 11.1.1.6.0 , as it is giving the following exception
"[bi_server1] [NOTIFICATION] [] [oracle.wsm.security.policy.scenario.executor.SecurityScenarioExecutor] [tid: RTD_Worker_9] [userId: <anonymous>] [ecid: 0000JxpZwaCDkZ__xPWByW1Hm1HW000001,1:23440] [APP: OracleRTD#11.1.1] [WSM_POLICY_NAME: oracle/wss_username_token_client_policy] Recipient Alias property not configured in the policy. Defaulting to encrypting with signers certificate.
Here I am providing the bi_server1.log, bi_server1.out log,bi_server1-diagnostic.log
Please suggest me workaround to resolve this issue,
thanks in advance
Pavan
bi_server1.log
==========
####<Jun 24, 2013 12:41:40 PM AST> <Info> <WebLogicServer> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900822> <BEA-000000> <WebLogic Server "bi_server1" version:
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Copyright (c) 1995, 2009, Oracle and/or its affiliates. All rights reserved.>
####<Jun 24, 2013 12:41:40 PM AST> <Notice> <Log Management> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900902> <BEA-170019> <The server log file /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/logs/bi_server1.log is opened. All server side log events will be written to this file.>
####<Jun 24, 2013 12:41:40 PM AST> <Info> <Log Management> <10.11.34.111> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1372066900906> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
####<Jun 24, 2013 12:41:40 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066900981> <BEA-320001> <The ServerDebug service initialized successfully.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901098> <BEA-002622> <The protocol "t3" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901098> <BEA-002622> <The protocol "t3s" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901099> <BEA-002622> <The protocol "http" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901099> <BEA-002622> <The protocol "https" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901100> <BEA-002622> <The protocol "iiop" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901101> <BEA-002622> <The protocol "iiops" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901102> <BEA-002622> <The protocol "ldap" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901102> <BEA-002622> <The protocol "ldaps" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901106> <BEA-002622> <The protocol "cluster" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901107> <BEA-002622> <The protocol "clusters" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002622> <The protocol "snmp" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002622> <The protocol "admin" is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901109> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <RJVM> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901133> <BEA-000570> <Network Configuration for Channel "bi_server1"
Listen Address   :9704
Public Address   N/A
Http Enabled   true
Tunneling Enabled false
Outbound Enabled false
Admin Traffic Enabled true>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901212> <BEA-002609> <Channel Service initialized.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901243> <BEA-000415> <System has file descriptor limits of - soft: 4,096, hard: 4,096>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901243> <BEA-000416> <Using effective file descriptor limit of: 4,096 open sockets/files.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901244> <BEA-000406> <PosixSocketMuxer was built on Jan 10 2008 23:07:45>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901301> <BEA-000436> <Allocating 4 reader threads.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <Socket> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901302> <BEA-000446> <Native IO Enabled.>
####<Jun 24, 2013 12:41:41 PM AST> <Info> <IIOP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066901427> <BEA-002014> <IIOP subsystem enabled.>
####<Jun 24, 2013 12:41:47 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066907382> <BEA-090894> <Successfully loaded the OPSS Policy Provider using oracle.security.jps.internal.policystore.JavaPolicyProvider.>
####<Jun 24, 2013 12:41:47 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066907849> <BEA-000000> <Starting OpenJPA 1.1.1-SNAPSHOT>
####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908041> <BEA-000000> <StoreServiceImpl.initJDO - StoreService is initialized with Id = ldap_LVk1d2v3EBrlDS/rSIpIRiGgLnM=>
####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908346> <BEA-090516> <The RoleMapper provider has preexisting LDAP data.>
####<Jun 24, 2013 12:41:48 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066908755> <BEA-090516> <The Authorizer provider has preexisting LDAP data.>
####<Jun 24, 2013 12:41:49 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909006> <BEA-090516> <The CredentialMapper provider has preexisting LDAP data.>
####<Jun 24, 2013 12:41:49 PM AST> <Info> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909180> <BEA-090093> <No pre-WLS 8.1 Keystore providers are configured for server bi_server1 for security realm myrealm.>
####<Jun 24, 2013 12:41:49 PM AST> <Notice> <Security> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909181> <BEA-090082> <Security initializing using security realm myrealm.>
####<Jun 24, 2013 12:41:49 PM AST> <Info> <Server> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909747> <BEA-002622> <The protocol "[iiop, ldap, http, https, ldaps, cluster-broadcast, admin, iiops, t3s, cluster-broadcast-secure, snmp, t3]" is now configured.>
####<Jun 24, 2013 12:41:49 PM AST> <Info> <XML> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909759> <BEA-130036> <Initializing XMLRegistry.>
####<Jun 24, 2013 12:41:49 PM AST> <Info> <messaging.interception> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066909771> <BEA-400000> <Initializing message interception service>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910180> <BEA-280008> <Opening the persistent file store "_WLS_bi_server1" for recovery: directory=/app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/store/default requestedWritePolicy="Direct-Write" fileLockingEnabled=true driver="wlfileio3".>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910314> <BEA-280009> <The persistent file store "_WLS_bi_server1" (fb352aa7-3e6f-4655-b314-8b2cf7d9caa3) has been opened: blockSize=4,096 actualWritePolicy="Direct-Write(read-buffered)" explicitIOEnforced=false records=109.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910462> <BEA-001135> <Initializing the JDBC service.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910473> <BEA-001137> <Initialization complete.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910474> <BEA-001138> <Resuming the JDBC service.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910474> <BEA-001140> <Resume complete.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <Connector> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910507> <BEA-190000> <Initializing J2EE Connector Service......>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <Connector> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910510> <BEA-190001> <J2EE Connector Service initialized successfully>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910593> <BEA-040305> <JMS service is initialized and in standby mode.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910637> <BEA-040090> <Deployed 8 default connection factories.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910638> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910638> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910639> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910640> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory1" with its JNDI name "weblogic.jms.XAConnectionFactory1" is started.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910641> <BEA-040306> <JMS service is active now.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910680> <BEA-101128> <Initializing HTTP services.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910697> <BEA-101135> <bi_server1 is the default Web server.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910697> <BEA-101052> <[HttpServer (defaultWebserver) name: bi_server1] Initialized>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <HTTP> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910700> <BEA-101129> <Initializing the Web application container.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910746> <BEA-180046> <INFO: Logging service enabled.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910749> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910750> <BEA-180046> <INFO: TC Task Manager instantiated!>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910753> <BEA-180046> <INFO: TC security service instantiated!>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910756> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WTC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910758> <BEA-180046> <INFO: TC Transaction service instantiated!>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910770> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910771> <BEA-220027> <Web Service reliable agents are started on the server.>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <JMX> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910888> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://10.11.34.111:9704/jndi/weblogic.management.mbeanservers.runtime .>
####<Jun 24, 2013 12:41:50 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066910904> <BEA-000256> <Invoking oracle.jrf.wls.JRFStartup.main(null)>
####<Jun 24, 2013 12:41:51 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066911658> <BEA-000256> <Invoking oracle.security.jps.wls.JpsWlsStartupClass.main(null)>
####<Jun 24, 2013 12:41:51 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066911696> <BEA-000256> <Invoking oracle.core.ojdl.weblogic.ODLConfiguration.main(null)>
####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912880> <BEA-000256> <Invoking oracle.jrf.AppContextStartup.main(null)>
####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912883> <BEA-000256> <Invoking oracle.as.jmx.framework.wls.spi.StartupListener.main(null)>
####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912942> <BEA-000256> <Invoking oracle.j2ee.ws.server.WebServiceServerStartup.main(null)>
####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912956> <BEA-000256> <Invoking oracle.ias.cache.Startup.main(null)>
####<Jun 24, 2013 12:41:52 PM AST> <Info> <WebLogicServer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000JxpZtZhDkZ__xPWByW1Hm1HW000000> <1372066912959> <BEA-000256> <Invoking oracle.dms.wls.DMSStartup.main(null)>
####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913225> <BEA-141278> <Java entropy configuration is: System property "java.security.egd= null"; JRE's java.security file property "securerandom.source= null"; Assumed Blocking Config= true; JDK version= 1.6.0; Operating System= AIX.>
####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913226> <BEA-141279> <Detected BLOCKING java entropy configuration. This is the most secure setting, but may cause performance issues on machines with few sources of entropy.>
####<Jun 24, 2013 12:41:53 PM AST> <Info> <Management> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913228> <BEA-141187> <Java system properties are defined as follows:
EPM_ORACLE_HOME = /app1/orabi/Oracle/Middleware/Oracle_BI1
EPM_ORACLE_INSTANCE = novalue
EPM_REG_PROPERTIES_PATH = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig
HYPERION_HOME = /app1/orabi/Oracle/Middleware/Oracle_BI1
XDO_FONT_DIR = /app1/orabi/Oracle/Middleware/Oracle_BI1/common/fonts
bi.oracle.home = /app1/orabi/Oracle/Middleware/Oracle_BI1
com.ibm.cpu.endian = big
com.ibm.oti.configuration = scar
com.ibm.oti.jcl.build = 20110622_1654
com.ibm.oti.shared.enabled = false
com.ibm.oti.vm.bootstrap.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
com.ibm.oti.vm.library.version = 24
com.ibm.vm.bitmode = 64
common.components.home = /app1/orabi/Oracle/Middleware/oracle_common
domain.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1
em.oracle.home = /app1/orabi/Oracle/Middleware/oracle_common
epm.useApplicationContextId = false
file.encoding = utf-8
file.separator = /
hyperion.home = /app1/orabi/Oracle/Middleware/Oracle_BI1
ibm.signalhandling.rs = false
ibm.signalhandling.sigchain = true
ibm.signalhandling.sigint = true
ibm.system.encoding = ISO8859-1
igf.arisidbeans.carmlloc = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/carml
igf.arisidstack.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/arisidprovider
java.assistive = ON
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jdbc_11.1.1/ojdbc6dms.jar:/app1/orabi/Oracle/Middleware/Oracle_BI1/bifoundation/jdbc/jdk16/bijdbc.jar::/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java6_64/lib/tools.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/app1/orabi/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app1/orabi/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.dms_11.1.1/dms.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jmx_11.1.1/jmxframework.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jmx_11.1.1/jmxspi.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.odl_11.1.1/ojdl.jar:/app1/orabi/Oracle/Middleware/oracle_common/soa/modules/commons-cli-1.1.jar:/app1/orabi/Oracle/Middleware/oracle_common/soa/modules/oracle.soa.mgmt_11.1.1/soa-infra-mgmt.jar:/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrf.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/xqrl.jar:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/java6_64/lib/tools.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/app1/orabi/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/app1/orabi/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/app1/orabi/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/app1/orabi/Oracle/Middleware
java.class.version = 50.0
java.compiler = j9jit24
java.endorsed.dirs = /usr/java6_64/jre/lib/endorsed
java.ext.dirs = /usr/java6_64/jre/lib/ext
java.fullversion = JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110624_85526 (JIT enabled, AOT enabled)
J9VM - 20110624_085526
JIT - r9_20101028_17488ifx17
GC   - 20101027_AA
java.home = /usr/java6_64/jre
java.io.tmpdir = /tmp/
java.jcl.version = 20110530_01
java.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/native:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/native:/usr/java6_64/jre/lib/ppc64/j9vm:/usr/java6_64/jre/lib/ppc64:/usr/java6_64/jre/../lib/ppc64:/app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/native:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/native:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64:/usr/lib:/app1/orabi/Oracle/Middleware/wlserver_10.3/server/native/aix/ppc64:/usr/lib:/usr/lib
java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
java.protocol.handler.pkgs = oracle.mds.net.protocol|weblogic.net
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = pap6460sr9fp2-20110627_03 (SR9 FP2)
java.security.policy = /app1/orabi/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy
java.specification.name = Java Platform API Specification
java.specification.vendor = Sun Microsystems Inc.
java.specification.version = 1.6
java.util.logging.config.class = oracle.core.ojdl.logging.LoggingConfiguration
java.util.prefs.PreferencesFactory = java.util.prefs.FileSystemPreferencesFactory
java.vendor = IBM Corporation
java.vendor.url = http://www.ibm.com/
java.version = 1.6.0
java.vm.info = JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr9-20110624_85526 (JIT enabled, AOT enabled)
J9VM - 20110624_085526
JIT - r9_20101028_17488ifx17
GC   - 20101027_AA
java.vm.name = IBM J9 VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Sun Microsystems Inc.
java.vm.specification.version = 1.0
java.vm.vendor = IBM Corporation
java.vm.version = 2.4
javax.management.builder.initial = weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
jrf.version = 11.1.1
jrockit.optfile = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt
jxe.current.romimage.version = 15
jxe.lowest.romimage.version = 15
oracle.biee.search.bisearchproperties = /app1/orabi/Oracle/Middleware/Oracle_BI1/bifoundation/jee/BISearchConfig.properties
oracle.core.ojdl.logging.applicationcontextprovider = oracle.core.ojdl.logging.WlsApplicationContextImpl
oracle.core.ojdl.logging.componentId = bi_server1
oracle.core.ojdl.logging.config.file = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.ovd_11.1.1/templates/ovd-logging.xml
oracle.core.ojdl.logging.usercontextprovider = oracle.core.ojdl.logging.WlsUserContextImpl
oracle.deployed.app.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/tmp/_WL_user
oracle.deployed.app.ext = /-
oracle.domain.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig
oracle.ecsf.configuration.class = oracle.biee.search.services.BISearchServiceConfiguration
oracle.ecsf.security.service = oracle.biee.search.security.BISearchSecurityService
oracle.notification.filewatching.interval = 2000
oracle.security.jps.config = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/jps-config.xml
oracle.server.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/fmwconfig/servers/bi_server1
org.apache.commons.logging.Log = org.apache.commons.logging.impl.Jdk14Logger
org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
org.xml.sax.driver = weblogic.xml.jaxp.RegistryXMLReader
org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
os.arch = ppc64
os.encoding = ISO8859-1
os.name = AIX
os.version = 6.1
path.separator = :
platform.home = /app1/orabi/Oracle/Middleware/wlserver_10.3
rtd.instanceName = RTD_bi_server1
server.group = obi
sun.arch.data.model = 64
sun.boot.class.path = /usr/java6_64/jre/lib/ppc64/default/jclSC160/vm.jar:/usr/java6_64/jre/lib/annotation.jar:/usr/java6_64/jre/lib/beans.jar:/usr/java6_64/jre/lib/java.util.jar:/usr/java6_64/jre/lib/jndi.jar:/usr/java6_64/jre/lib/logging.jar:/usr/java6_64/jre/lib/security.jar:/usr/java6_64/jre/lib/sql.jar:/usr/java6_64/jre/lib/ibmorb.jar:/usr/java6_64/jre/lib/ibmorbapi.jar:/usr/java6_64/jre/lib/ibmcfw.jar:/usr/java6_64/jre/lib/rt.jar:/usr/java6_64/jre/lib/charsets.jar:/usr/java6_64/jre/lib/resources.jar:/usr/java6_64/jre/lib/ibmpkcs.jar:/usr/java6_64/jre/lib/ibmcertpathfw.jar:/usr/java6_64/jre/lib/ibmjgssfw.jar:/usr/java6_64/jre/lib/ibmjssefw.jar:/usr/java6_64/jre/lib/ibmsaslfw.jar:/usr/java6_64/jre/lib/ibmjcefw.jar:/usr/java6_64/jre/lib/ibmjgssprovider.jar:/usr/java6_64/jre/lib/ibmjsseprovider2.jar:/usr/java6_64/jre/lib/ibmcertpathprovider.jar:/usr/java6_64/jre/lib/ibmxmlcrypto.jar:/usr/java6_64/jre/lib/management-agent.jar:/usr/java6_64/jre/lib/xml.jar:/usr/java6_64/jre/lib/jlm.jar:/usr/java6_64/jre/lib/javascript.jar
sun.boot.library.path = /usr/java6_64/jre/lib/ppc64/default:/usr/java6_64/jre/lib/ppc64
sun.io.unicode.encoding = UnicodeBig
sun.java.command = weblogic.Server
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = ISO8859-1
user.country = US
user.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1
user.home = /home/orabi
user.language = en
user.name = orabi
user.timezone = Asia/Riyadh
vde.home = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/ldap
weblogic.MaxMessageSize = 50000000
weblogic.Name = bi_server1
weblogic.ProductionModeEnabled = true
weblogic.ReverseDNSAllowed = false
weblogic.alternateTypesDirectory = /app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/app1/orabi/Oracle/Middleware/oracle_common/modules/oracle.oamprovider_11.1.1
weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
weblogic.ext.dirs = /app1/orabi/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/app1/orabi/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath
weblogic.home = /app1/orabi/Oracle/Middleware/wlserver_10.3/server
weblogic.jdbc.remoteEnabled = false
weblogic.management.clearTextCredentialAccessEnabled = ********
weblogic.management.discover = false
weblogic.management.server = http://10.11.34.111:7001
weblogic.nodemanager.ServiceEnabled = true
weblogic.security.SSL.enableJSSE = true
weblogic.security.SSL.ignoreHostnameVerification = true
weblogic.security.TrustKeyStore = DemoTrust
weblogic.system.BootIdentityFile = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/servers/bi_server1/data/nodemanager/boot.properties
wls.home = /app1/orabi/Oracle/Middleware/wlserver_10.3/server
wlw.iterativeDev = false
wlw.logErrorsToConsole = false
wlw.testConsole = false
xdo.server.config.dir = /app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/config/bipublisher
>
####<Jun 24, 2013 12:41:53 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066913766> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_internal">
####<Jun 24, 2013 12:41:54 PM AST> <Notice> <WebLogicServer> <10.11.34.111> <bi_server1> <main> <<WLS Kernel>> <> <> <1372066914573> <BEA-000365> <Server state changed to STANDBY>
####<Jun 24, 2013 12:41:54 PM AST> <Notice> <WebLogicServer> <10.11.34.111> <bi_server1> <main> <<WLS Kernel>> <> <> <1372066914579> <BEA-000365> <Server state changed to STARTING>
####<Jun 24, 2013 12:41:54 PM AST> <Info> <SAFService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914605> <BEA-281003> <SAF Service has been initialized.>
####<Jun 24, 2013 12:41:54 PM AST> <Info> <SAFService> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914612> <BEA-281002> <SAF Service has been started.>
####<Jun 24, 2013 12:41:54 PM AST> <Info> <WseeCore> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914622> <BEA-220502> <The Wsee Service is starting>
####<Jun 24, 2013 12:41:54 PM AST> <Info> <Deployer> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914743> <BEA-149209> <Resuming.>
####<Jun 24, 2013 12:41:54 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066914823> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls9_async_response">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916264> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_cluster_internal">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916333> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_deployment_internal">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916428> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "EPMSystemRegistry">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916440> <BEA-001177> <Creating Connection Pool named EPMSystemRegistry, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916455> <BEA-000626> <Free resources in pool "EPMSystemRegistry" will be tested every "300" seconds.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916577> <BEA-001124> <Created Connection Pool named EPMSystemRegistry.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916591> <BEA-001174> <Creating Data Source named EPMSystemRegistry, JNDI Name = jdbc/EPMSystemRegistry.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916642> <BEA-001512> <Data Source EPMSystemRegistry has been successfully created.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916644> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bip_datasource">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916652> <BEA-001177> <Creating Connection Pool named bip_datasource, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916654> <BEA-000626> <Free resources in pool "bip_datasource" will be tested every "300" seconds.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916655> <BEA-001124> <Created Connection Pool named bip_datasource.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916656> <BEA-001174> <Creating Data Source named bip_datasource, JNDI Name = jdbc/bip_datasource.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916676> <BEA-001512> <Data Source bip_datasource has been successfully created.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916678> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "mds-owsm">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916687> <BEA-001177> <Creating Connection Pool named mds-owsm, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = SendStreamAsBlob=true;user=DEV_MDS;oracle.net.CONNECT_TIMEOUT=10000;.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916688> <BEA-000626> <Free resources in pool "mds-owsm" will be tested every "300" seconds.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916690> <BEA-001124> <Created Connection Pool named mds-owsm.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916691> <BEA-001174> <Creating Data Source named mds-owsm, JNDI Name = jdbc/mds/owsm.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916726> <BEA-001512> <Data Source mds-owsm has been successfully created.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916728> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "rtd_datasource">
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916735> <BEA-001177> <Creating Connection Pool named rtd_datasource, URL = jdbc:oracle:thin:@ebspocapp:1521/EBPRD, Properties = user=DEV_BIPLATFORM;oracle.net.CONNECT_TIMEOUT=10000;.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <Common> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916736> <BEA-000626> <Free resources in pool "rtd_datasource" will be tested every "300" seconds.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916738> <BEA-001124> <Created Connection Pool named rtd_datasource.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916740> <BEA-001174> <Creating Data Source named rtd_datasource, JNDI Name = SDDS.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <JDBC> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916757> <BEA-001512> <Data Source rtd_datasource has been successfully created.>
####<Jun 24, 2013 12:41:56 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066916922> <BEA-280008> <Opening the persistent file store "BipJmsStore" for recovery: directory=/app1/orabi/Oracle/Middleware/user_projects/domains/bifoundation_domain1/BipJmsStore requestedWritePolicy="Direct-Write" fileLockingEnabled=true driver="wlfileio3".>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <Store> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917017> <BEA-280009> <The persistent file store "BipJmsStore" (68f997df-e4a0-4eb1-9497-8d994726f787) has been opened: blockSize=4,096 actualWritePolicy="Direct-Write(read-buffered)" explicitIOEnforced=false records=16.>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917027> <BEA-040321> <JMSServer "BipJmsServer" is resuming.>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917092> <BEA-282003> <The messaging kernel BipJmsServer will use up to 536,870,912 bytes of memory before paging begins>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917115> <BEA-282001> <The messaging kernel BipJmsServer is beginning recovery of its persistent state>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <Messaging> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917158> <BEA-282002> <The messaging kernel BipJmsServer has recovered 0 persistent messages>
####<Jun 24, 2013 12:41:57 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917200> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "BipJmsResource">
####<Jun 24, 2013 12:41:57 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066917408> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Burst.Job.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921006> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Burst.Report.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921044> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Email.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921063> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.File.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921078> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.FTP.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921091> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Print.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921107> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.WebDAV.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921125> <BEA-040406> <Distributed destination "BipJmsResource!BIP.Delivery.Fax.Q" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921143> <BEA-040406> <Distributed destination "BipJmsResource!BIP.System.T" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <JMS> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921170> <BEA-040108> <User connection factory "BipJmsResource!BIP.JMS.CF" is started.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <WorkManager> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921185> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "Module-FMWDFW">
####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921232> <BEA-320114> <Initializing the Diagnostics Harvester.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921241> <BEA-320117> <The Harvester is being disabled because there are no Harvestable types configured specified.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <Diagnostics> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921245> <BEA-320119> <The Harvester is now in a inactive state.>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921715> <BEA-160151> <Registered library Extension-Name: UIX, Specification-Version: 11, Implementation-Version: 11.1.1.1.0 (WAR).>
####<Jun 24, 2013 12:42:01 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066921841> <BEA-160151> <Registered library Extension-Name: adf.oracle.businesseditor, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922111> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (EAR).>
####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922334> <BEA-160151> <Registered library Extension-Name: adf.oracle.domain.webapp, Specification-Version: 1, Implementation-Version: 11.1.1.2.0 (WAR).>
####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372066922391> <BEA-160151> <Registered library Extension-Name: bithirdparty, Specification-Version: 11.1.1 (JAR).>
####<Jun 24, 2013 12:42:02 PM AST> <Info> <J2EE> <10.11.34.111> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <13

Hi,
I tried starting the server from the console as well as from command prompt. Here I am giving the command below.
nohup ./startManagedWebLogic.sh bi_server1 t3://machineIP:portNo > bis1_startup.log &
But each time I got the same exception.
Korandla

Com.sap.engine.services.dbpool.exceptions.BaseResourceException:

Hi
Jcontrol.exe is stopped. I checked in server0 log file.
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection:
Caused by: com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server
Caused by: java.net.ConnectException: Connection refused: connectCommunication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
com.sap.caf.eu.gp.mail.cf.core.exceptionhandling.MailCFExceptionHandler.throwMailCFRuntimeException(MailCFExceptionHandler.java:92)
#1.5 #0022198E9491001F000000130000390C00046999A2B0692D#1242008487314#com.sap.jms##com.sap.jms####n/a##6e72d7203dd211decd7d0022198e9491#SAPEngine_System_Thread[impl:5]_90##0#0#Error#1#/System/Server#Plain#JMSServerContainer.onServiceJoin##Configuration problem occurred while accessing JMS configuration resources.#
#1.5 #0022198E9491008E000000010000390C00046999A5B43D17#1242008537907#com.sap.sql.jdbc.direct.DirectPreparedStatement##com.sap.sql.jdbc.direct.DirectPreparedStatement#Guest#0##n/a##8c9ab8303dd211de99680022198e9491#SAPEngine_Application_Thread[impl:3]_2##0#0#Error#1#/System/Database/sql/jdbc/direct#Java#com.sap.sql_0003##SQL error occurred on connection apsgdc01hwebd:BPE:SAPBPEDB: code=-4,499, state="null", message="[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error";
SQL statement is "SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4".
[EXCEPTION]
#6#-4499#<null>#[ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error#apsgdc01hwebd:BPE:SAPBPEDB#SELECT "RESEND_INFO_UUID","SENT_MAIL_UUID","RI_START_TIME","RI_DELAY" FROM "CAF_GP_RESEND_INFO" ORDER BY 4#com.ibm.db2.jcc.b.DisconnectException: [ibm][db2][jcc][t4][2030][11211] A communication error has been detected. Communication protocol being used: TCP/IP.
Communication API being used: SOCKETS. Location where the error was detected: T4Agent.sendRequest().
Communication function detecting the error: OutputStream.flush(). Protocol specific error codes Software caused connection abort: socket write error, *, 0. Message: Software caused connection abort: socket write error
Regards
Rao

Hi, Please let me know if you managed to solve the problem.. We are facing the same issue
Regards
PN

Com.sap.mw.jco.JCO$Exception starting the J2EE server 620

Similar Messages

Maybe you are looking for