on 09-04-2007 8:06 AM
Hi All.
I installed a Dialog instance.
After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
Here it is the std_server0.out log:
-
stdout/stderr redirect
-
node name : server0
pid : 1298548
system name : PRP
system nr. : 10
started at : Mon Sep 3 19:07:54 2007
[Thr 1] Mon Sep 3 19:07:55 2007
[Thr 1] MtxInit: -2 0 0
JVMST080: verbosegc is enabled
JVMST082: -verbose:gc output will be written to stderr
^MSAP J2EE Engine Version 7.00 PatchLevel is starting...
^M
Loading: LogManager ... 1887 ms.
Loading: PoolManager ... 3 ms.
Loading: ApplicationThreadManager ... 452 ms.
Loading: ThreadManager ... 428 ms.
Loading: IpVerificationManager ... 16 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 392 ms.
Loading: LockingManager ... 140 ms.
Loading: ConfigurationManager ... 4656 ms.
Loading: LicensingManager ... 28 ms.
Loading: CacheManager ... 311 ms.
Loading: ServiceManager ...
<AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
<AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
<GC(1): GC cycle started Mon Sep 3 19:08:13 2007
<GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
<GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
<GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
<AF[1]: completed in 159 ms>
Loading services.:
Service cross started. (72 ms).
Service file started. (156 ms).
Service memory started. (160 ms).
Service userstore started. (24 ms).
Service timeout started. (51 ms).
Service runtimeinfo started. (8 ms).
Service trex.service started. (90 ms).
Service jmx_notification started. (77 ms).
Service p4 started. (182 ms).
Service classpath_resolver started. (99 ms).
Service deploy started. (9491 ms).
Service MigrationService started. (28 ms).
Service bimmrdeployer started. (6 ms).
Service log_configurator started. (21621 ms).
Service locking started. (3 ms).
Service http started. (772 ms).
Service naming started. (1518 ms).
Service failover started. (23 ms).
Service appclient started. (29 ms).
Service javamail started. (87 ms).
Service ts started. (70 ms).
Service jmsconnector started. (80 ms).
Service licensing started. (10 ms).
Service iiop started. (141 ms).
Service connector started. (119 ms).
Service configuration started. (31 ms).
Service webservices started. (463 ms).
Service dbpool started. (8765 ms).
Sep 3, 2007 6:08:47 PM com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
persistence adapter "PRIVATE_DATASOURCE" failed.
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=FALSE
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
ume.db.connection_pool_type=SAP/BC_UME
ume.db.connection_pool.j2ee.xatransactions_used=false
ume.db.connection_pool.j2ee.is_unicode=FALSE
ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 3, 2007 6:08:47 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Anyone can help?
Thanks,
Marco
Hi,
I had the same problem and it is because the DI could not communicate and get authenticated by our ERP system, which is our CUA. by edidting the /etc/service file and add the line (sapmsRP1 3610/tcp) the problem solved. of course, you should add the entry in the /etc/services file based on your system as in the following format:
sapms<SID> 36<SNo>
bye,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem was solved, but I do not remember what the cause was.
I'm really Sorry.
Marco
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Add the 'sapgw10 3310/tcp' to the services file of the target and calling (dialog isnatnce) machine!
Also be sure to have the entry 'sapmsPRP 3610' on the machine of the dialog instance (to be able to call massage server of target system).
Regards,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
the 'sapgw10 3310/tcp" entry exists in both 'services' file (Central and dialog instances).
I also have an entry 'sapmsPRP 3605' in the dialog 'services' file.
This is due to the central instace (ABAP+Java) has instance number '05' (SCS instace has '01' and Dialog Instance has '10').
Is it correct to replace my entry with the one you suggested?
Regards,
Marco
Hi,
In the config tool, check if the UME datasource property is set.
If your server is standalone then the datasource should be set as database only.xml else it should be ABAP.xml.
Regards,
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
after some corrections, now the problem is changed.
Here you can find the std_server0.out:
<b>com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
ailed.
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'SAPPRP-DB:sapgw10' not reached
TIME Fri Sep 7 15:01:11 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 79
ERRNO TEXT A remote host refused an attempted connect operation.
COUNTER 1
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Sep 7, 2007 2:01:11 PM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
Thanks all,
Marco
User | Count |
---|---|
84 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.