Skip to Content
avatar image
Former Member

Java Engine not connecting to DB

Dears,

From last some days on our ECC5 server which is having ABAP+JAVA stack on SQL server,we are facing one issue that my Java engine is not connecting to Database.

Due to which i am not able to work on my java stack.ABAP stack is working fine.On ABAP side there is no issue.Checked the database schema SAPSIDDB password is it correct.

This happened suddenly.Till evening system was working fine and next day in moring this issue occured means we have not made changes in any configuration or anywhere.

Configtool log says:

###Thread[AWT-EventQueue-0,6,main]##0#0#Warning##Java#SAP_LOGGING_FORMATTER_ERROR##Attempting to change a formatter on active log ! The reset() method must be called first!#1#.
system.log# #1.5#C000ACA8010400010000002801CF243B000455CDD9D74CA8#1220242518265#/System/Configuration/Logging##com.sap.tc.logging.APILogger.FileLog[setFormatter()]#######Thread[AWT-EventQueue-0,6,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the has been changed from to )!#5#formatter#FileLog#.
system.log#com.sap.tc.logging.ListFormatter#com.sap.tc.logging.ListFormatter# #1.5#C000ACA8010400010000002901CF243B000455CDD9D74CA8#1220242518265#/System/Server##com.sap.engine.core.configuration#######Thread[AWT-EventQueue-0,6,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###Properties for connect through secure store not set. Please check your connect properties. Trying to connect via plain user/password.##1.5#C000ACA8010400010000002A01CF243B000455CDD9D74CA8#1220242518265#/System/Configuration/Logging##com.sap.tc.logging.APILogger.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[AWT-EventQueue-0,6,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the has been changed from to )!#5#resource bundle name#LogController#/System/Database/sql/jdbc#<null>#com.sap.sql.log.OpenSQLResourceBundle# #1.5#C000ACA8010400010000002B01CF243B000455CDD9D74CA8#1220242518265#/System/Configuration/Logging##com.sap.tc.logging.APILogger.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[AWT-EventQueue-0,6,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the has been changed from to )!#5#resource bundle name#LogController#/System/Database/sql/jdbc#com.sap.sql.log.OpenSQLResourceBundle#com.sap.sql.log.OpenSQLResourceBundle# #1.5#C000ACA8010400010000002C01CF243B000455CDD9D74CA8#1220242518265#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnectionFactory#######Thread[AWT-EventQueue-0,6,main]##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0015#com.sap.sql.log.OpenSQLResourceBundle#Value "" is not allowed for parameter .#2#url## #1.5#C000ACA8010400010000002D01CF243B000455CDD9D74CA8#1220242518265#/System/Configuration/Logging##com.sap.tc.logging.APILogger.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[AWT-EventQueue-0,6,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The for the has been changed from to )!#5#resource bundle name#LogController#/System/Database/sql/jdbc#com.sap.sql.log.OpenSQLResourceBundle#com.sap.sql.log.OpenSQLResourceBundle#

ICM log says:

[Thr 3528] Mon Sep 01 09:46:32 2008

[Thr 3528] ICM running on: server2.prospecta.local

[Thr 3528] MtxInit: -2 0 0

[Thr 3528] IcmInit: listening to admin port: 65000

[Thr 3528] DpSysAdmExtCreate: ABAP is active

[Thr 3528] DpSysAdmExtCreate: JAVA is not active

[Thr 3528] DpShMCreate: sizeof(wp_adm) 38168 (1316)

[Thr 3528] DpShMCreate: sizeof(tm_adm) 2780232 (13832)

[Thr 3528] DpShMCreate: sizeof(wp_ca_adm) 24000 (80)

[Thr 3528] DpShMCreate: sizeof(appc_ca_adm) 8000 (80)

[Thr 3528] DpShMCreate: sizeof(comm_adm) 290000 (580)

[Thr 3528] DpShMCreate: sizeof(vmc_adm) 0 (372)

[Thr 3528] DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)

[Thr 3528] DpShMCreate: SHM_DP_ADM_KEY (addr: 02280040, size: 3220328)

[Thr 3528] DpShMCreate: allocated sys_adm at 02280040

[Thr 3528] DpShMCreate: allocated wp_adm at 02281B58

[Thr 3528] DpShMCreate: allocated tm_adm_list at 0228B070

[Thr 3528] DpShMCreate: allocated tm_adm at 0228B098

[Thr 3528] DpShMCreate: allocated wp_ca_adm at 02531CE0

[Thr 3528] DpShMCreate: allocated appc_ca_adm at 02537AA0

[Thr 3528] DpShMCreate: allocated comm_adm_list at 025399E0

[Thr 3528] DpShMCreate: allocated comm_adm at 025399F8

[Thr 3528] DpShMCreate: allocated vmc_adm_list at 025806C8

[Thr 3528] DpShMCreate: system runs without vmc_adm

[Thr 3528] DpShMCreate: allocated ca_info at 025806F0

[Thr 3528] Mon Sep 01 09:46:33 2008

[Thr 3528] IcmCreateWorkerThreads: created worker thread 0

[Thr 3528] IcmCreateWorkerThreads: created worker thread 1

[Thr 3528] IcmCreateWorkerThreads: created worker thread 2

[Thr 3528] IcmCreateWorkerThreads: created worker thread 3

[Thr 3528] IcmCreateWorkerThreads: created worker thread 4

[Thr 3528] IcmCreateWorkerThreads: created worker thread 5

[Thr 3528] IcmCreateWorkerThreads: created worker thread 6

[Thr 3528] IcmCreateWorkerThreads: created worker thread 7

[Thr 3528] IcmCreateWorkerThreads: created worker thread 8

[Thr 3528] IcmCreateWorkerThreads: created worker thread 9

[Thr 5804] IcmWatchDogThread: watchdog started

[Thr 3476] ISC: created 400 MB disk cache.

[Thr 3476] ISC: created 50 MB memory cache.

[Thr 3476] HttpSubHandlerAdd: Added handler HttpCacheHandler(slot=0, flags=12293) for /:0

[Thr 3476] HttpSubHandlerAdd: Added handler HttpSAPR3Handler(slot=1, flags=4101) for /:0

[Thr 3476] HttpSubHandlerAdd: Added handler HttpJ2EEHandler(slot=2, flags=1077253) for /:0

[Thr 3476] Started service 8000 for protocol HTTP on host "server2.prospecta.local"(on all adapters) (timeout=30)

[Thr 5600] MPI<3>0#3 Peak buffer usage: 1 (@ 64 KB)

[Thr 5084] MPI<5>2#3 Peak buffer usage: 2 (@ 64 KB)

[Thr 3476] Mon Sep 01 09:46:37 2008

[Thr 3476] *** WARNING => IcmNetCheck: NiAddrToHost(10.0.0.1) took 4 seconds [icxxtool.c 852]

*[Thr 3476] *** WARNING => IcmNetCheck: 1 possible network problems detected - please check the network/DNS settings [icxxtool.c 908]*

Please suggest.

Can it be that any of driver file of java get currupted or Is there any network issue.

Shivam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Sep 01, 2008 at 07:41 AM

    Hi,

    Please check with your network administrator,whther he has make some change in the host or in the DNS.

    and also try to login to the configtool,let me know what it is saying.

    Thanks,

    Satyabrat

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 01, 2008 at 09:55 AM

    Hi Shyam,

    If the j2ee is unable to connect to the db,the following could be the probable

    causes:

    1)the db is down

    2)the jdbc drivers have expired

    3)the jdbc user/pwd information specified in the securestore in configtool is incorrect.

    Please check the defaulttrace files present in j2ee/cluster/server0/log path.Be sure to check the

    latest default trace file(check the timestamp).Post the latest errors here,and will try to help you.

    Regards,

    Abhishek

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Abhishek,

      Logs in default trace are:

      #1.5#00145E41F759004E0000025A000015BC00044FEDA96A6E36#1213782074687#com.sap.engine.services.deploy##com.sap.engine.services.deploy####server2.prospecta_PRO_5851450#Guest#083f0f103d1911ddaba300145e41f759#SAPEngine_System_Thread[impl:5]_68##0#0#Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/com.sapportals.dqe.beans cannot be started. Reason: it has hard reference to resource DQE with type service, which is not active on the server. at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToService(ReferenceResolver.java:475) at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:396) at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328) at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:178) at com.sap.engine.services.deploy.server.application.StartTransaction.beginLocal(StartTransaction.java:152) at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:356) at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:117) at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:235) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4443) at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationsInitially(DeployServiceImpl.java:2568) at com.sap.engine.services.deploy.server.DeployServiceImpl.clusterElementReady(DeployServiceImpl.java:2425) at com.sap.engine.services.deploy.server.ClusterServicesAdapter.containerStarted(ClusterServicesAdapter.java:42) at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.processEvent(ContainerEventListenerWrapper.java:144) at com.sap.engine.core.service630.container.AdminContainerEventListenerWrapper.processEvent(AdminContainerEventListenerWrapper.java:19) at com.sap.engine.core.service630.container.ContainerEventListenerWrapper.run(ContainerEventListenerWrapper.java:102) 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:150) Caused by: com.sap.engine.frame.ServiceException: < Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: < Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl. at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:174) 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:150) ', Arguments: [] > : Can't find resource for bundle java.util.PropertyResourceBundle, key Service DQE error. Nested exception is: com.sap.engine.frame.ServiceException: < Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Could not start DQE service, reason: Could not initialize RuntimeStateAdminAPIImpl. at com.metamatrix.sap.service.MetaMatrixServiceFrame.start(MetaMatrixServiceFrame.java:174) 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:150) at com.sap.engine.core.service630.container.MemoryContainer.startServiceRuntime(MemoryContainer.java:389) at com.sap.engine.core.service630.container.ServiceWrapper.start(ServiceWrapper.java:107) at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToService(ReferenceResolver.java:468) ... 17 more # #1.5#00145E41F759006400000011000015BC00044FEDA9D59E32#1213782081718#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0####b5a905603d1a11dd9c8000145e41f759#SAPEngine_Application_Thread[impl:3]_5##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address HTTP request processing failed. HTTP error [401] will be returned. The error is [Cannot authenticate the user.No details available].# #1.5#00145E41F759005100000036000015BC00044FEDA9D5DB42#1213782081734#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0####b5ab76603d1a11dd941000145e41f759#SAPEngine_Application_Thread[impl:3]_25##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address HTTP request processing failed. HTTP error [401] will be returned. The error is [Cannot authenticate the user.No details available].# #1.5#00145E41F759005500000022000015BC00044FEDA9D62DE5#1213782081750#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0####b5ade7603d1a11ddbf9f00145e41f759#SAPEngine_Application_Thread[impl:3]_1##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address HTTP request processing failed. HTTP error [401] will be returned. The error is [Cannot authenticate the user.No details available].# #1.5#00145E41F759006C0000000A000015BC00044FEDA9D65B59#1213782081765#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0####b5b031503d1a11ddcdd000145e41f759#SAPEngine_Application_Thread[impl:3]_4##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address HTTP request processing failed. HTTP error [401] will be returned. The error is [Cannot authenticate the user.No details available].# #1.5#00145E41F759005400000011000015BC00044FEDA9D670CC#1213782081765#com.sap.aii.af.service.cpa.impl.servlet.CacheInvalidation#sap.com/com.sap.aii.af.cpa.app#com.sap.aii.af.service.cpa.impl.servlet.CacheInvalidation.init(ServletConfig)#J2EE_GUEST#0####b5a44a703d1a11ddb1ef00145e41f759#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Java###The AdatperFramework has not been registered to SLD after retries. Please restart the application com.sap.aii.service.cpa.monitor as soon as the SLD is available.#1#1#

      #1.5#00145E41F759006B000000EB000015BC00044FEDA9E66758#1213782082812#com.sap.jms#sap.com/irj#com.sap.jms.server.sessioncontainer.InboundBus instance=default#J2EE_GUEST#0####9d4208103d1911dda55b00145e41f759#Thread[Thread-56,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerSecurityException: Cannot create connection. User J2EE_ADMIN is locked.

      at com.sap.jms.server.service.impl.SecurityServiceImpl.checkAuthentication(SecurityServiceImpl.java:451)

      at com.sap.jms.server.sessioncontainer.handler.ConnectionHandler.onCreateRequest(ConnectionHandler.java:120)

      at com.sap.jms.server.sessioncontainer.handler.ConnectionHandler.process(ConnectionHandler.java:69)

      at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)

      at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)

      at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)

      at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)

      at com.sap.jms.server.JMSServerContainer.createConnection(JMSServerContainer.java:481)

      at com.sap.jms.server.ServerClientAdapter.sendAndWait(ServerClientAdapter.java:87)

      at com.sap.jms.client.connection.ConnectionFactory.sendConnectionCreateRequest(ConnectionFactory.java:412)

      at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:356)

      at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:257)

      at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)

      at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1128)

      at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1069)

      at java.lang.Thread.run(Thread.java:534)

      Shivam

  • avatar image
    Former Member
    Sep 01, 2008 at 10:53 AM

    Hi ,

    The following error is present in your post:

    instance=default#J2EE_GUEST#0####9d4208103d1911dda55b00145e41f759#Thread[Thread-56,5,SAPEngine_Application_Threadimpl:3]_Group##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerSecurityException:

    Cannot create connection. User J2EE_ADMIN is locked.

    Plz check the user j2ee_admin on the backend(i am still confused as nothing related to jdbc is thr in the error).Plz once again check the content of latest defaulttrace file.

    Regards,

    Abhishek

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 01, 2008 at 11:15 AM

    Hi,

    Plz check the errors in std_bootstratp.error file present in the work dir.

    Whatever error is faced by the j2ee while starting it will be logged in the

    respective dev_* files and std_server* files.

    The default trace is also a good place to look for errors.

    Regards,

    Abhishek

    Add comment
    10|10000 characters needed characters exceeded