Problem in opening J2EE server..
Dear all,
When i write the address of my J2EE server in the internet browser and try to open it. The system gives an error saying that..<b>The following error occurred:
[code=GATEWAY_TIMEOUT] A gateway timeout occurred. The server is unreachable. Retry the request.</b>
Can anybody suggest me the error cause and fix..
Thanks,
Anup
Hi Anup,
Are you specifying correct port?
Port should be 5<instance num>00.
Also check whether your server is running properly or not.
Regards,
Bhavik
Similar Messages
-
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 J2EE server, Syntax error in DOS
OS: Windows98
j2sdkee1.3
jsdk1.3
Hi, guys:
I try to run the example of J2ee Tutorial sample code but I find that that the setenv.bat in j2sdkee1.3\bin has sytax error in MS DOS in the following lines
set JAAS_OPTIONS=XXX=YYY
set SSL_OPTIONS=XXX=YYY
set LISTEN_OPTIONS=XXX=YYY
I don't understand why they have such a problem. Didn't they even try to run J2ee server on Windows ? Can't believe such irresponsible development is from SUN.
Can anyone help ? ThanksHi, Guys:
I found the answer base on my research and other's topic answers, especially thank Laughton Jackson.
#1) Change setenv.bat
***********OLD*****************
set JAAS_OPTIONS=-Djava.security.auth.policy=%J2EE_HOME%\lib\security\jaas.policy
set SSL_OPTIONS=-Djavax.net.ssl.trustStore=%J2EE_HOME%\lib\security\cacerts.jks
set LISTEN_OPTIONS=-Dcom.sun.CORBA.connection.ORBListenSocket=SSL:0,SSL_MUTUALAUTH:0,PERSISTENT_SSL:1060
set JAVACMD=%JAVA_HOME%\bin\java -Xmx128m %SSL_OPTIONS% %JAAS_OPTIONS%
change the above to
**************NEW*****************
set JAAS_OPTIONS=-Djava.security.auth.policy
set JAAS_OPTIONS1=%J2EE_HOME%\lib\security\jaas.policy
set SSL_OPTIONS=-Djavax.net.ssl.trustStore
set SSL_OPTIONS1=%J2EE_HOME%\lib\security\cacerts.jks
set LISTEN_OPTIONS=-Dcom.sun.CORBA.connection.ORBListenSocket
set LISTEN_OPTIONS1=SSL:0,SSL_MUTUALAUTH:0,PERSISTENT_SSL:1060
set CLASSPATH=%CLASSPATH%;%CPATH%
set JAVACMD=%JAVA_HOME%\bin\java -Xmx128m
Notice that we break those lines of the format
set XX=YY=ZZ and add set CLASSPATH=%CLASSPATH%;%CPATH%. Those env variables look very confusing at first. Actually they are nothing but tools that the original person who wrote this script uses to saving his typing !
#2 Change j2ee.bat
************OLD********************
%JAVACMD% %LISTEN_OPTIONS% -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter -Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl -Djms.home=%JMS_HOME% -Dcom.sun.jms.service.jdbc.dbpath=%JMS_DB_PATH% -Djms.properties=%J2EE_HOME%\config\jms_service.properties -Djava.security.policy==%J2EE_HOME%\lib\security\server.policy -Djava.security.auth.login.config=%J2EE_HOME%\lib\security\login.config -Dcom.sun.enterprise.home=%J2EE_HOME% -classpath %CPATH% com.sun.enterprise.server.J2EEServer %*
Change the above to
************NEW********************
%JAVACMD% %SSL_OPTIONS%=%SSL_OPTIONS1% %JAAS_OPTIONS%=%JAAS_OPTIONS1% %LISTEN_OPTIONS%=%LISTEN_OPTIONS1% -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter -Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl -Djms.home=%JMS_HOME% -Dcom.sun.jms.service.jdbc.dbpath=%JMS_DB_PATH% -Djms.properties=%J2EE_HOME%\config\jms_service.properties -Djava.security.policy==%J2EE_HOME%\lib\security\server.policy -Djava.security.auth.login.config=%J2EE_HOME%\lib\security\login.config -Dcom.sun.enterprise.home=%J2EE_HOME% com.sun.enterprise.server.J2EEServer %1 %2
Notice that we changed "com.sun.enterprise.server.J2EEServer %*" to
"com.sun.enterprise.server.J2EEServer %1 %2"
Good luck
Henry -
Problem in starting J2EE server
when i type j2ee at the command promt to start the j2ee server,i get an "Exception in thread Main" and the server does not start.When i checked the System.err file, it had:
java.lang.NoSuchMethodError
at com.sun.corba.ee.internal.corba.AnyImpl.createTypeCodeForClass(AnyImpl.java:1256)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.createTypeCode(ShutdownUtilDelegate.java:223)
at com.sun.corba.ee.internal.iiop.ShutdownUtilDelegate.writeAny(ShutdownUtilDelegate.java:178)
at javax.rmi.CORBA.Util.writeAny(Util.java:80)
Can anyone tell me where the problem is and how to solve it.I have already set the environment varaible J2EE_HOME to my j2sdkee path...Make sure you have J2SDK1.4 installed
-
Problem with starting J2EE server via MMC
I'm getting J2EE server not started (jcontrol stopped immediatelly when it starts) with the following issues in the log/trace:
[Thr 2372] Wed Apr 12 15:53:12 2006
[Thr 2372] *** ERROR => invalid return code of process [bootstrap_ID8265050] (exitcode=-2) [jstartxx.c 1433]
[Thr 2372] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID8265050] (rc=-2)
[Thr 2372] JControlCloseProgram: started (exitcode = -2)
[Thr 2372] JControlCloseProgram: good bye... (exitcode=-2)
and above
[Thr 2372] Wed Apr 12 15:53:11 2006
[Thr 2372] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID8265050]
[Thr 2372] INFO: Invalid property value [JLaunchParameters/]
[Thr 2372] [Node: server0 bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_11
Pleae help.
Thanks a lotHi
Thank you very much for your reply!
But,
I started SAPDB:J2E service, but I have the same outcome:
[Thr 3964] Tue Apr 18 13:45:53 2006
[Thr 3964] *** ERROR => invalid return code of process [bootstrap_ID8265050] (exitcode=-2) [jstartxx.c 1433]
[Thr 3964] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID8265050] (rc=-2)
[Thr 3964] JControlCloseProgram: started (exitcode = -2)
[Thr 3964] JControlCloseProgram: good bye... (exitcode=-2)
I tried to start: SAPDB: J2E (omststknl.exe)/SAPDB: J2E (quick)+slow + SAPDB: .M750018/SAPDB: .M750018 (omststknl.exe)/SAPDB: .M750018 (quick)+slow, but they coudn't be started - is this my problem?
==> log
[Thr 3964] Tue Apr 18 13:45:52 2006
[Thr 3964] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID8265050]
[Thr 3964] INFO: Invalid property value [JLaunchParameters/]
[Thr 3964] [Node: server0 bootstrap] java home is set by profile parameter
Java Home: C:\j2sdk1.4.2_11
JStartupIReadSection: read node properties [bootstrap_ID8265050]
-> node name : server0 bootstrap
-> node type : bootstrap
-> java path : C:\j2sdk1.4.2_11
-> java parameters : -Djco.jarm=1 -Djco.jarm=1
-> java vm version : 1.4.2_11-b06
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 1024M
-> root path : C:\usr\sap\J2E\JC00\j2ee\cluster
-> class path : .\bootstrap\launcher.jar
-> OS libs path : C:\usr\sap\J2E\JC00\j2ee\os_libs
-> main class : com.sap.engine.offline.OfflineToolStart
-> framework class : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path : C:\usr\sap\J2E\JC00\j2ee\os_libs\jstartup.jar
-> parameters : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID008265050
-> debuggable : yes
-> debug mode : no
-> debug port : 60000
-> shutdown timeout: 120000
JStartupStartJLaunch: program = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = C:\usr\sap\J2E\JC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_FY06P1J
-> arg[02] = -DSAPINFO=J2E_00_bootstrap
-> arg[03] = -file=C:\usr\sap\J2E\JC00\j2ee\cluster\instance.properties
-> arg[04] = -nodeName=bootstrap_ID8265050
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3892
-> arg[07] = -jvmOutFile=C:\usr\sap\J2E\JC00\work\jvm_bootstrap_ID8265050.out
-> arg[08] = -stdOutFile=C:\usr\sap\J2E\JC00\work\std_bootstrap_ID8265050.out
-> arg[09] = -locOutFile=C:\usr\sap\J2E\JC00\work\dev_bootstrap_ID8265050
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=C:\usr\sap\J2E\SYS\profile\J2E_JC00_FY06P1J
-> lib path = PATH=C:\j2sdk1.4.2_11\jre\bin\server;C:\j2sdk1.4.2_11\jre\bin;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;c:\program files\winzip;c:\data\notes;c:\program files\notes;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Adaptec Shared\System;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
-> exe path = PATH=C:\j2sdk1.4.2_11\bin;C:\usr\sap\J2E\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;c:\program files\winzip;c:\data\notes;c:\program files\notes;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Adaptec Shared\System;C:\usr\sap\J2E\SCS01\exe;C:\usr\sap\J2E\JC00\exe;C:\usr\sap\J2E\SYS\exe\run
[Thr 3964] Tue Apr 18 13:45:53 2006
[Thr 3964] *** ERROR => invalid return code of process [bootstrap_ID8265050] (exitcode=-2) [jstartxx.c 1433]
[Thr 3964] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID8265050] (rc=-2)
[Thr 3964] JControlCloseProgram: started (exitcode = -2)
[Thr 3964] JControlCloseProgram: good bye... (exitcode=-2)
Please help -
Problem while Starting J2EE Server
When I am starting the J2ee Server , I am getting this error
D:\>j2ee -verbose
J2EE server listen port: 1050
Exception in thread "main" java.lang.NoClassDefFoundError: com/sun/corba/se/internal/util/IdentityHashtable
at com.sun.corba.ee.internal.javax.rmi.CORBA.Util.<clinit>(Util.java:87)
at com.sun.corba.ee.internal.POA.POAImpl.activate(POAImpl.java:935)
at com.sun.corba.ee.internal.POA.POAImpl.activate_object(POAImpl.java:895)
at com.sun.corba.ee.internal.CosNaming.TransientNameService.initialize(TransientNameService.java:117)
at com.sun.corba.ee.internal.CosNaming.TransientNameService.<init>(TransientNameService.java:70)
at com.sun.enterprise.iiop.POAProtocolMgr.initializeNaming(POAProtocolMgr.java:103)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:226)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
D:\>
D:\>set path
Path=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;d:\clearcase\bin;D:\ANT\apache-ant-1.6.5\bin;D:\ANT\apache-ant-1.6.5\lib;D:\jdk1.5.0_06\bin;D:\gt4\bin;D:\Sun\jwsdp-2.0\apache-ant\bin;D:\j2sdkee1.3.1\bin;D:\Sun\jwsdp-2.0\jwsdp-shared\Bin
D:\>set java_home
JAVA_HOME=D:\jdk1.5.0_06
D:\>set j2ee_home
J2EE_HOME=D:\j2sdkee1.3.1
D:\>set ant_home
ANT_HOME=D:\ANT\apache-ant-1.6.5You might have to use older version of JDK supported for J2EE 1.3.
According to the page http://java.sun.com/j2ee/sdk_1.3/ JavaE 1.4 or later releases of 1.3 will work.
If you must use Java SE 5.0, try moving to a newer version of SDK, J2EE 1.4 or Java EE 5 available from http://java.sun.com/javaee -
Problem installing the J2EE server on a 6.40 WebAS System
On an AIX server I've installed Oracle 9.2, WebAS Central ABAP instance and
now I'm trying to install the J2EE server. When it gets to phase
"Deployment of JDDI" I get the following error. Does anyone have any
ideas on how to resolve this. Thanks!
Apr 4, 2005 2:17:21 PM Info: Starting deployment
Apr 4, 2005 2:17:21 PM Info: Loading selected archives...
Apr 4, 2005 2:17:21 PM Info: Loading archive '/dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA'
Apr 4, 2005 2:17:21 PM Info: Selected archives successfully loaded.
Apr 4, 2005 2:17:21 PM Info: Error handling strategy: OnErrorStop
Apr 4, 2005 2:17:21 PM Info: Update strategy: UpdateLowerVersions
Apr 4, 2005 2:17:21 PM Info: Starting to execute deployment action (deploy) for "synclog".
Apr 4, 2005 2:17:24 PM Info: Creating connections to database "DBW".
Apr 4, 2005 2:17:24 PM Info: Creating vendor connection to database.
Apr 4, 2005 2:17:24 PM Error: Creation of vendor connection failed.
Original error message is:
java.sql.SQLException: Io exception: Invalid number format for port number
Stack trace of original Exception or Error is:
java.sql.SQLException: Io exception: Invalid number format for port number
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:334)
at oracle.jdbc.ttc7.TTC7Protocol.handleIOException(TTC7Protocol.java:3649)
at oracle.jdbc.ttc7.TTC7Protocol.logon(TTC7Protocol.java:353)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:368)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:549)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:349)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Apr 4, 2005 2:17:24 PM Error: Execution of deployment action for "synclog" aborted: Db connect failed.
Apr 4, 2005 2:17:25 PM Error: Deployment NOT successful for synclog
Apr 4, 2005 2:17:25 PM Error: At least one of the Deployments failed
Apr 4, 2005 2:17:25 PM Info: Summarizing the deployment results:
Apr 4, 2005 2:17:25 PM Error: Aborted: /dvd/igs/J2EE1/J2EE-ENG/JDD/SYNCLOG.SDA
Apr 4, 2005 2:17:25 PM Error: Processing error. Return code: 4Also, I should mention I'm running the 64bit capable SDK for version 1.4.2 for AIX.
Thanks again! -
Problem in using J2EE server (deploy tool)
Hi All
I am in the starting phase of learning J2EE technology. I am facing some problem .
1. When I start the deployment tool by command "deploytool" , the console appears but it does not have menu "server".
2. I am not able to specify JNDI names as after selecting the application name, the Inspactor window does not have tabs "JNDI names"
Please help me out to solve these issues.
Thanks in advance
anuAfter you create ?.ear.xml as previously mentioned, you can include it in your enterprise archive as follows:
cd app\build
mkdir META-INF
copy ?.ear.xml META-INF\sun-j2ee-ri.xml
jar -uf ?.ear META-INF\sun-j2ee-ri.xml
Then you should be able to deploy your application and run your client successfully.
You also might want to check out:
http://groups.msn.com/J2EETools/createdescriptors14.msnw
for the specific steps on how to create the ?.ear.xml that includes JNDI names. -
Unable to open application server control page
Hi,
i have a problem to open application server control page in client machine.
below is the error gets while opening the page;
ERROR:
'An error was encountered while loading page. There was a communication problem contacting the agent. This may be a transient network problem. There was a communication problem fetching monitoring data. This may be a transient network problem'
Please help me to sort out this.
Thank you,
Naresh.See this thread: Uanble to open the App server console after installing the Oracle soa suite
Hi,
Are you sure you have configured a EM? Did you select "Configure this as an Administration OC4J instance" during the installation?
Regards,
Martin
Regards,
Martin -
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 -
J2EE Server Terminating (IN SAPMMC)
Hi friends,
I am facing this strange problem. My J2EE Server is always stopping when i am running my SAP console it is saying "synchronizing with binaries" and getting termiated.
Any helps please
cheers
RamHi
To be more specific about the error. i am providing the details of the error.
[Thr 3188] Thu Nov 09 10:51:46 2006
[Thr 3188] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx.c 1433]
[Thr 3188] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
[Thr 3188] JControlCloseProgram: started (exitcode = 66)
[Thr 3188] JControlCloseProgram: good bye... (exitcode=66)
Cheers
ram -
Please help me. Thanks a lot. The problem is as following:
C:\j2sdkee1.3.1\bin>j2ee -verbose
J2EE server listen port: 1050
Naming service started:1050
Binding DataSource, name = jdbc/EstoreDB, url = jdbc:cloudscape:rmi:Cloudsc
;create=true
Binding DataSource, name = jdbc/DB1, url = jdbc:cloudscape:rmi:CloudscapeDB
te=true
Binding DataSource, name = jdbc/DB2, url = jdbc:cloudscape:rmi:CloudscapeDB
te=true
Binding DataSource, name = jdbc/Cloudscape, url = jdbc:cloudscape:rmi:Cloud
DB;create=true
Binding DataSource, name = jdbc/InventoryDB, url = jdbc:cloudscape:rmi:Clou
eDB;create=true
Binding DataSource, name = jdbc/XACloudscape, url = jdbc/XACloudscape__xa
Binding DataSource, name = jdbc/XACloudscape__xa, dataSource = COM.cloudsca
re.RemoteXaDataSource@1202d69
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 : TopicConnectionFactory , Topic , No properties
Binding: < JMS Cnx Factory : jms/QueueConnectionFactory , Queue , No proper
>
Binding: < JMS Cnx Factory : jms/TopicConnectionFactory , Topic , No proper
>
Binding: < JMS Cnx Factory : QueueConnectionFactory , Queue , 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 already in
JVM_Bind
at org.apache.catalina.connector.http.HttpConnector.initialize(Http
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.
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 ...It looks like you already have a program listening on port 7000 or 8000. If that is the case, edit the container's configuration file to another port number (or do the same for the other program that is listening on that port).
- Saish
"My karma ran over your dogma." - Anon -
The problem is occurred with J2ee server node which is disabled it from MMC
Dear SAP Consultants,
The problem is occurred with J2ee server node which is disabled J2ee server node from MMS Console and the abap work process is working fine but the dispatcher is yellow status and I can login to the abap system but Iu2019m not able to start the j2ee from Tcode u201CSmicmu201D as well
The system parameters are:
BI 7.0 System as ABAP & JAVA add on, windows 2003 on Oracle database, 24 GB Ram
Paging files: Driveu201D Os system: minimum: 1525, maximum: 3048
Driveu201DEu201D application: minimum: 70855, maximum: 70855
I can see the log files as follow:
From dev_disp:
Sun Jun 21 13:10:28 2009
J2EE server info
start = TRUE
state = STARTED
pid = 2892
argv[0] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
argv[1] = E:\usr\sap\BWD\DVEBMGS00\exe\jcontrol.EXE
argv[2] = pf=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
argv[3] = -DSAPSTART=1
argv[4] = -DCONNECT_PORT=64990
argv[5] = -DSAPSYSTEM=00
argv[6] = -DSAPSYSTEMNAME=BWD
argv[7] = -DSAPMYNAME=cai-bwdev_BWD_00
argv[8] = -DSAPPROFILE=E:\usr\sap\BWD\SYS\profile\BWD_DVEBMGS00_cai-bwdev
argv[9] = -DFRFC_FALLBACK=ON
argv[10] = -DFRFC_FALLBACK_HOST=localhost
start_lazy = 0
start_control = SAP J2EE startup framework
DpJ2eeStart: j2ee state = STARTED
DpJ2eeLogin: j2ee state = CONNECTED
Sun Jun 21 13:10:29 2009
***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
ERROR => NiIRead: SiRecv failed for hdl 6 / sock 1032
(SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:1362) [nixxi.cpp 4424]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=2892)
ERROR => DpProcKill: kill failed [dpntdisp.c 371]
DpIJ2eeShutdown: j2ee state = SHUTDOWN
Sun Jun 21 13:10:48 2009
DpEnvCheckJ2ee: switch off j2ee start flag
From dev_jcontrol :
[Thr 2124] Sun Jun 21 13:10:29 2009
[Thr 2124] *** ERROR => invalid return code of process [bootstrap] (exitcode = 66) [jstartxx.c 1642]
[Thr 2124] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc = 66)
[Thr 2124] JControlCloseProgram: started (exitcode = 66)
[Thr 2124] JControlCloseProgram: good bye... (exitcode = 66)
From dev_bootstrap :
JHVM_BuildArgumentList: main method arguments of node [bootstrap]
-> arg[ 0]: com.sap.engine.bootstrap.Bootstrap
-> arg[ 1]: ./bootstrap
-> arg[ 2]: ID0072573
-> arg[ 3]: -XX:NewSize=57M
-> arg[ 4]: -XX:MaxNewSize=57M
-> arg[ 5]: -Xms256M
-> arg[ 6]: -Xmx256M
-> arg[ 7]: -XX:+DisableExplicitGC
-> arg[ 8]: -verbose:gc
-> arg[ 9]: -Djava.security.policy=.java.policy
-> arg[ 10]: -Djava.security.egd=file:/dev/urandom
-> arg[ 11]: -Djco.jarm=1
[Thr 5216] JLaunchIExitJava: exit hook is called (rc = 66)
[Thr 5216] **********************************************************************
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
[Thr 5216] JLaunchCloseProgram: good bye (exitcode = 66)
From server.0.log :
#1.5 #001E4F208703008A0001C7470000092000046A4414D60A1F#1242740546634#/System/Server##com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#J2EE_GUEST#0##n/a##27772ea0447811deb9bf001e4f208703#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#com.sap.caf.eu.gp.schedule.impl.ScheduleWorker#Plain###ERROR_ACQUIRE_CONNECTION
com.sap.caf.eu.gp.base.exception.EngineException: ERROR_ACQUIRE_CONNECTION
at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:92)
at com.sap.caf.eu.gp.schedule.impl.ScheduleDbImpl.getScheduleToProcess(ScheduleDbImpl.java:1936)
at com.sap.caf.eu.gp.schedule.impl.ScheduleService.getScheduleToProcess(ScheduleService.java:432)
at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.work(ScheduleWorker.java:77)
at com.sap.caf.eu.gp.schedule.impl.ScheduleWorker.run(ScheduleWorker.java:63)
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.engine.services.dbpool.exceptions.BaseSQLException: ResourceException in method ConnectionFactoryImpl.getConnection(): com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:59)
at com.sap.caf.eu.gp.base.db.ConnectionPoolJ2EE.getConnection(ConnectionPoolJ2EE.java:89)
... 8 more
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException thrown by the physical connection: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:193)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:267)
at com.sap.engine.services.dbpool.cci.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:51)
... 9 more
Caused by: com.sap.sql.log.OpenSQLException: Error while accessing secure store: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should..
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:145)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:226)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:197)
at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.createManagedConnection(ManagedConnectionFactoryImpl.java:117)
... 12 more
Caused by: com.sap.security.core.server.secstorefs.FileMissingException: File "
cai-bwdev
sapmnt
BWD
SYS
global
security
data
SecStore.properties" does not exist although it should.
at com.sap.security.core.server.secstorefs.StorageHandler.openExistingStore(StorageHandler.java:372)
at com.sap.security.core.server.secstorefs.SecStoreFS.openExistingStore(SecStoreFS.java:1946)
at com.sap.sql.connect.OpenSQLConnectInfo.getStore(OpenSQLConnectInfo.java:802)
at com.sap.sql.connect.OpenSQLConnectInfo.lookup(OpenSQLConnectInfo.java:783)
at com.sap.sql.connect.OpenSQLDataSourceImpl.setDataSourceName(OpenSQLDataSourceImpl.java:209)
... 14 more
Please advice with the right solution,
Regards,
Ahmedthanks
-
[b]problem in starting j2EE RI server[/b]
I am getting this error when i try to start j2EE server. it is a J2EE RI installed with sunONE studio 4 update 1 edition.
Can someone tell me what is the problem ?
C:\Program Files\s1studio\ee\j2sdkee1.3.1\bin>j2ee -verbose
No local string for j2ee.listenPort
J2EE server listen port: 1050
No local string for j2ee.naming
Naming service started: 1050
No local string for enterprise.log.logging.serverversion.started
No local string for enterprise.log.using.vm.name.version.from
No local string for enterprise.log.vm's.classpath
No local string for enterprise.log.j2ee.homedirectory
No local string for enterprise.log.logging.serverversion.started
No local string for enterprise.log.using.vm.name.version.from
No local string for enterprise.log.vm's.classpath
No local string for enterprise.log.j2ee.homedirectory
No local string for idle_resource_threshold_error
No local string for binding.datasource
No local string for binding.datasource
No local string for binding.datasource
No local string for binding.datasource
No local string for binding.datasource
No local string for binding.datasource
java.lang.ClassNotFoundException: com.pointbase.xa.xaDataSource
at java.net.URLClassLoader$1.run(URLClassLoader.java:198)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:186)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:140)
at com.sun.enterprise.repository.JdbcXAResource.createDataSource(JdbcXAResource.java:65)
at com.sun.enterprise.resource.ResourceInstaller.installJdbcXADataSources(ResourceInstaller.java:458)
at com.sun.enterprise.resource.ResourceInstaller.installJdbcDataSources(ResourceInstaller.java:349)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:264)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
No local string for poolmgr.datasourceerror
Error in creating data source object
No local string for jms.start
Starting JMS service...
No local string for enterprise.log.logging.serverversion.started
No local string for enterprise.log.using.vm.name.version.from
No local string for enterprise.log.vm's.classpath
No local string for enterprise.log.j2ee.homedirectory
No local string for enterprise.log.logging.serverversion.started
No local string for enterprise.log.using.vm.name.version.from
No local string for enterprise.log.vm's.classpath
No local string for enterprise.log.j2ee.homedirectory
No local string for enterprise.log.logging.serverversion.started
No local string for enterprise.log.using.vm.name.version.from
No local string for enterprise.log.vm's.classpath
No local string for enterprise.log.j2ee.homedirectory
No local string for jms.start.failed
Couldn't start JMS service...
javax.jms.JMSException: Can't start JMSService
at com.sun.jms.service.JMSManagerImpl.startJMSService(JMSManagerImpl.java:86)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:169)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:268)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
javax.jms.JMSException: Can't start JMSService
at com.sun.jms.service.JMSManagerImpl.startJMSService(JMSManagerImpl.java:86)
at com.sun.enterprise.jms.JmsUtil.startJmsService(JmsUtil.java:169)
at com.sun.enterprise.server.J2EEServer.run(J2EEServer.java:268)
at com.sun.enterprise.server.J2EEServer.main(J2EEServer.java:972)
java.lang.RuntimeException: Can't start JMSService
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: Can't start JMSService
Error executing J2EE server ...
java.lang.NoClassDefFoundError: com/pointbase/jdbc/jdbcDataSource
at com.sun.jms.service.JMSServiceImpl.stop(JMSServiceImpl.java:1329)
at com.sun.jms.service.JMSServiceImpl.stop(JMSServiceImpl.java:1308)
at com.sun.jms.service.JMSServiceImpl$1.run(JMSServiceImpl.java:102)Depending on your OS, there are two possibilities:
PointBase:
the .lck file was not being deleted due to a permission error, and that led to a string of events that would cause the check point error. (e.g. a rollback would be attempted on every access to the db)
Adding "FilePermission delete" to the servlet block of the lib/security/server.policy file fixed the problem.
or
After installing the Sun ONE Studio 4 update 1 software, I'm receiving errors trying to use the J2EE RI server, the PointBase database, and/or the internal UDDI Registry. How do I fix this?
Applicable to release S1S4u1 EEfJ. Also applicable to releases: S1S7 EEfS (Solaris environment only)
If you are in a Solaris(TM) environment and plan to use the PointBase Server 4.2 Restricted Edition database, the J2EE(TM) Reference Implementation 1.3.1 server, the internal Java(TM) Web Services Developer Pack's (JWSDP) Tomcat 4.1 server, or the internal UDDI registry server packaged with the Sun(TM) ONE Studio, Enterprise Edition for Java(TM) software (IDE), be aware that you must have write access to the IDE directories used by these components. To ensure a writeable IDE installation, install a personal copy of the Sun ONE Studio, Enterprise Edition for Java software in your home directory and run the product from this location.
Please note that the default Solaris installation procedure causes the <s1studio-install-dir> tree to be owned by the root user. Therefore, a non-root user running the IDE will be denied write access resulting in errors when attempting to run any of these packaged servers.
To install a personal copy of the Sun ONE Studio 4, Enterprise Edition for Java, please use the following instructions.
If you have the Sun ONE Studio 4 update 1 CD, do the following:
1.Be sure you are logged on as 'yourself', not a root user.
2.Insert the CD. NOTE: If the Auto run feature is enabled, an installer wizard appears and asks for the root password. Close this wizard. Do not install this product as root user.
3.From the directory where you want the IDE installed, type /cdrom/s1studio/image/ffj_installers_ee/ffj_ee_solsparc_en.bin
4.Follow the install panels, using the Sun ONE Studio 4, Enterprise Edition for Java Getting Started Guide (found at http://forte.sun.com/ffj/documentation/s1s41/getstartedee41.pdf )for any additional information.
If you have downloaded Sun ONE Studio 7, Enterprise Edition for Solaris from the web site, do the following:
1. Go to this web site http://www.sun.com/software/sundev/jde/buy/index.html and read the section called "Before you Download" for additional pre-install information.
2. Scroll to the area entitled Enterprise Edition for Java and click on the Try & Buy Download link. This takes you to the Download Center Login page.
3. Enter your username and password to login, (you may need to register). Accept the license agreement. You will be presented with the download page.
4. Be sure you are logged on as 'yourself', not a root user.
5. Find the correct file for the Solaris platform, ffj_ee_solsparc_en.bin, (151.54MB), and click the link to begin the product download, saving the file into a download directory of your choice.
6. Once the download is complete, set the DISPLAY environment variable to display to your local system, for example: % setenv DISPLAY your-local-system:0.0
7. Set the execute permission on the ffj_ee_solsparc_en.bin file by typing: % chmod a+x ffj_ee_solsparc_en.bin
8. Execute the installer as a non-root user by typing (from the download directory): % ffj_ee_solsparc_en.bin
9. See the Sun ONE Studio 4, Enterprise Edition for Java Getting Started Guide (found at http://forte.sun.com/ffj/documentation/s1s41/getstartedee41.pdf ) for additional installation and configuration information. -
There was a problem connecting to the server when opening Chrome or Evernote
At one time I had an external network drive that is now dead. I have remove it from the login items and the Finder list of recent servers, but whenever I open Chrome or Evernote I receive a series of "There was a problem connecting to the server" messages. Eventually the messages stop and both Chrome and Evernote work normally.
I've looked at the Chrome and Evernote settings and preferences and I cannot find any setting that tells them to connect to the old network drive.
I've also used the Console app and when the error message comes up I see...
11/18/14 2:44:38.023 PM NetAuthSysAgent[419]: DNSAddressResolver:Resolve CFNetServiceResolveWithTimeout failed
11/18/14 2:44:38.024 PM NetAuthSysAgent[419]: ERROR: AFP_GetServerInfo - connect failed 64
Any ideas on where to look and how to get rid of this?I understand you are getting unable to connect to server error message on your printer. I would first unplug router and printer for about 1 minute. I would plug router up first then printer. I would then try to enable web services. If not successful and you get same error message. I would follow these steps.
1. Obtain your printer's IP address
a. This can be done by pressing the wireless icon on printer.
2. Enter the printer's IP address in a browser.
3. Select the network tab at the top of the page.
4. On the left select networking.
5. Select Network Address (IP)
6. Select Manual DNS Server
a. Manual Preferred DNS should read 8.8.8.8
b. Alternate DNS Server should read. 8.8.4.4
7. Select apply you might get a warning just select okay.
Maybe you are looking for
-
How To-set DFF to null and Not required in OAF page ??
enabled service dff, added 2 segments. i want them displayed in service request oaf pages. details of dff- Application=Service , title = Additional Information for Agents in context field region : unchecked required and displayed In global data eleme
-
A weird 'person sitting at a laptop ' icon pops up suspending the use of my Mac. I see a countdown for 3 minutes and a line of letters to type in to allow me to continue working. I have 2 minutes to work. Help. What is this!
-
Bridge should display an overall progress bar when it is performing a batch image processor task. It would be nice to see at a glance how many of the images have been completed and how many remain. Bridge should have an option to play a sound (fanfar
-
Has anyone been involved in setting up Direct Debits in AR before? How does the information get passed to the banks and then back into Oracle. What information/input is required from the banks to set this up? Thanks
-
How to create BP organization from WebIC instead of BP Person.
Hi, I am using the component IUICMDC/SearchAll component/view for searching accounts and as well as creating new accounts of type BP Persons(Partner Category:Person1).Now I want to create New account BP Organization(Partner Category:Organization2)