cancel
Showing results for 
Search instead for 
Did you mean: 

We encountered a problem during use the Configtool access JAVA engine.

Former Member
0 Kudos

We encountered a problem during use the Configtool access JAVA engine.

Our environment of system as below:

HardWard: IBM i570

OS: IBM as/400 V5E3

DB: DB2/400

Application system:SAP XI 3.0

The problem we encountered as below:

Our company used XI 3.0 SR1 for exchange data between SAP R/3 and no-sap system.For now,we wanna create a backup system(for

offline recovery),so we backup the XI product system throught entiry system save in AS/400(we stopped the XI system before

save process start).And following,we restored from the tape that we save from XI product system to the new backup system(they

are whole different paratition),but the problem is coming.Describe as following item:

1. The application seem to can be started but the java node always restart circularly(We have 4 java node now),I think

because of different of hardware configure(between XI product and Backup system) and lack of hardware resource.(XI prduction

have 5 CPUs and 22G Mem,Backup system have 2 CPUs and 16G MEM ).Therefore we wanna decrease the number of java nodes for

start application in backup system(throught configtool).

2. We wanna use configtool to decrease the java nodes for start backup system.But we encountered a problem during running the

configtool ,the information of prompt dialog as following:

Error occurred while working with Configuration (Scanning).

Msg:Error while connecting to DB.

We also see the system.log that below the directory of usr\sap\PXI\DVEBMGS00\j2ee\configtool,and found some error as

following text:

#1.5#C0000A0008A8000000000000017A906E000423BFFC7246E0#1165207387826#/System/Configuration/Logging##com.sap.tc.logging.APILogg

er.LogController[addLog()]#######Thread[main,5,main]##0#0#Info##Java#TC_LOGGING_CONFIGURATION_NEW_ITEMS

[C0000A305666000000000002018FB1F70003D67C779ECE88]##The () has been added to the !#3#Log#.
system.log#/System# #1.5#C0000A0008A8000000000001017A906E000423BFFC73A670#1165207388006#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store Z:
sapmnt
PXI
global
security
lib
tools
iaik_jce_export.jar# #1.5#C0000A0008A8000000000002017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store Z:
sapmnt
PXI
global
security
lib
tools
iaik_jsse.jar# #1.5#C0000A0008A8000000000003017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store Z:
sapmnt
PXI
global
security
lib
tools
iaik_smime.jar# #1.5#C0000A0008A8000000000004017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store Z:
sapmnt
PXI
global
security
lib
tools
iaik_ssl.jar# #1.5#C0000A0008A8000000000005017A906E000423BFFC73CD80#1165207388016#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###ConfigurationManager: found jar for secure store Z:
sapmnt
PXI
global
security
lib
tools
w3c_http.jar# #1.5#C0000A0008A8000000000006017A906E000423BFFC9C25A0#1165207390660#/System/Configuration/Logging##com.sap.tc.logging.APILogg er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,main] ##0#0#Info##Java#TC_LOGGING_CONFIGURATION_IS_CHANGED[C0000A305666000000000000018FB1F70003D67C779CD2B8]##The
for the has been changed from to )!#5#resource bundle name#LogController#com.sap.security.core.server.secstorefs.SecStoreFS#<null>#com.sap.security.core.server.secstorefs.SecStore FSResources# #1.5#C0000A0008A8000000000007017A906E000423BFFC9C4CB0#1165207390670#/System/Configuration/Logging##com.sap.tc.logging.APILogg er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,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/Security/SecStoreFS#<null>#com.sap.security.core.server.secstorefs.SecStoreFSResources# #1.5#C0000A0008A8000000000008017A906E000423BFFCAC7D38#1165207391731#/System/Server##com.sap.engine.core.configuration#######T hread[main,5,main]##0#0#Info#1#com.sap.engine.core.configuration#Plain###OpenSQLDataSource successfully created with secure store.# #1.5#C0000A0008A8000000000009017A906E000423BFFCDA3070#1165207394726#/System/Configuration/Logging##com.sap.tc.logging.APILogg er.LogController[setResourceBundleName(String resourceBundleName)]#######Thread[main,5,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#C0000A0008A800000000000A017A906E000423BFFCDB41E0#1165207394796#/System/Database/sql/jdbc##com.sap.sql.jdbc.NativeConnect ionFactory#######Thread[main,5,main] ##0#0#Error#1#com.sap.sql.jdbc.NativeConnectionFactory#Java#com.sap.sql_0002#com.sap.sql.log.OpenSQLResourceBundle#SQL error occurred on connection : code={0,number,integer}, state="", message="".#5#-99999#08001#The application requester

cannot establish the connection. (XIPRD)#jdbc:as400://XIPRD/SAPPXIDB;transaction isolation=read uncommitted;data

truncation=true;date format=jis;time format=jis;sort=hex;hold input locators=true;hold statements=true;cursor

hold=false#<null>#

The "SQL error occurred on connection" happened during start run configtool.

We don't know how to solve this problem.

Thanks

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

The problem has been solved,thanks

Former Member
0 Kudos

sorry,Version of JDK in XIPRD system is 1.4.2-08

Former Member
0 Kudos

Version of JDK in XIPRD system is 1.3.1

I don't know how to check the security policy you mention.

Former Member
0 Kudos

Hi

Which JDK you are using?Check the security files have all the rights.Check for two security files ie US Policy and local policy jars.See if it is overwrritten.If yes take a new US Policy and local policy from some other location and replace it.