Service Operations Insight

View Only

SOI Tech Tip: CA SAM Application Server does not startup after RO92514 for SOI 4.0 CUM1

Recommend

Oct 14, 2016 09:16 AM

Britta Hoffner

After application of the Java Certificate patch RO92514 for SOI 4.0 CUM1 the CA SAM Application Service does not startup anymore.

You will see the following error messages in the soimgr-debug.log file in the SOI\tomcat\logs folder on the SOI Manager:

2016-10-13 13:13:15,440 INFO [localhost-startStop-1] context.ContextFactory.constructContextObject(441) - ContextException: com.aprisma.spectrum.app.util.context.ContextFactory.NO_CONTEXT_OBJECT_CLASS_REGISTERED_FOR_ID id "com.ca.sam.common.CallTimer" at scope "global"

2016-10-13 13:13:15,718 INFO [ServletInit] servlet.RegistrationServlet.initialize(427) - Started 4.0.1.103.20161010.Test
2016-10-13 13:13:17,163 INFO [ServletInit] servlet.ManagerInitServlet.initialize(116) - Manager initialization begins...
2016-10-13 13:13:22,014 INFO [ServletInit] security.EEMGlobalAccessPrivilegeManager.setupAllUsersAndGroups(647) - Setting max search size to 10000
2016-10-13 13:13:22,256 INFO [ServletInit] security.EEMGlobalAccessPrivilegeManager.setupAllUsersAndGroups(652) - Found 4 groups.
2016-10-13 13:13:22,572 INFO [ServletInit] security.EEMGlobalAccessPrivilegeManager.setupAllUsersAndGroups(664) - Found 3 users.
2016-10-13 13:13:24,848 INFO [ServletInit] servlet.ManagerInitServlet.startComponents(316) - Initial SessionFactory creation failed:
org.hibernate.InvalidMappingException: Could not parse mapping document from resource samdao/CIStagingTemp.hbm.xml
at org.hibernate.cfg.Configuration.addResource(Configuration.java:575)

This is because there is a duplicate entry for CIStagingTemp.hbm.xml after the installation of the fix in the SOI\tomcat\lib\hibernate.cfg.xml file which has to be manually removed.

this has to be changed into:

save the modifications and restart the SOI Services on the manager with

SOI\tools\soitoolbox --stopAllServices

SOI\tools\soitoolbox --startAllServices

Statistics

0 Favorited

2 Views

0 Files

0 Shares

0 Downloads

Tags and Keywords

Comments

Britta Hoffner

Oct 17, 2016 10:38 AM

Hello Daniel, I have applied to my SOI 3.3 CUM2 the patches T6CP013 and T6CP020 and still no duplicates in the file. I will have an eye on that when I upgrade this server to 4.0 + RO89152 and RO92514. As said in a native 4.0 + RO89152 and RO92514 the problem was not seen as well.

Kind regards,

Britta

Daniel Blanco

Oct 17, 2016 09:23 AM

Hi Britta,

Thanks I will remove those lines.

My upgrade was a SOI v3.3 CUM2 instance with the following Patch history file:

Sun 01/24/2016 14:58:20.62 Installed RO78774
Sun 01/24/2016 15:00:27.33 Installed RO81948
Sun 01/24/2016 15:01:56.07 Installed T6CP013
Tue 03/22/2016 12:00:17.78 Installed T6CP020

Now after upgrading to 4.0 my Patch history file is just:

Sat 10/15/2016 15:47:27.09 Installed RO89152
Sat 10/15/2016 16:14:10.68 Installed RO92514

Britta Hoffner

Oct 17, 2016 05:34 AM

Hello André and Daniel,

I have discussed your findings with sustaining engineering and the duplicate entry in the broker.properties files does not create any problems. This entry can be removed from the file.

Kind regards,

Britta

Britta Hoffner

Oct 17, 2016 03:29 AM

Hi Daniel and André, could you please share your SOIPatchLog.his file. I have looked into my LAB server with

SOI 3.3 CUM1 + RO78774, RO92521, T373724, T6BZ006, T6CP002, T6CP021, T6CP025, T6CP030, T6CP036

and broker.properties did not have the duplicate entry.

Are your both environments upgraded from SOI 3.1 or 3.2 to 3.3 ?

Kind regards,

Britta

Michael Boehm

Oct 17, 2016 03:22 AM

Hi Daniel,

you should remove the duplicate lines.

Normally it should not disturb the system to get information twice, but as we can see from the first example Britta has explained in this topic, it can cause problems.

MichaelBoehm

Andre Wawrzyniak

Oct 17, 2016 02:53 AM

Hi Daniel,

thats my SOI 3.3 CU1 + JAva TestFix broker.properties:

broker.1.protocols=ws
broker.1.ws.uri=http://localhost:8020/ucf/BrokerService

#broker.2.protocols=ws
#broker.2.ws.uri=http://@HOST.NAME@:8010/ucf/BrokerService //@HOST.NAME@:8010/ucf/BrokerService

broker.1.data.persist=true
broker.1.data.store.path=D:/CA/SOI/ucf/ucf_broker_store

I think you should remove the broker.1.data.store.path.

regards

André

Daniel Blanco

Oct 15, 2016 04:03 PM

Hello so can someone tell me if this is correct. I am running an upgrade from 3.3 to 4.0 and just finished applying CUM1 (RO89152.exe)

I had notepadd++ open on several key SOI-MGR configuration files and one that noticed had more duplicate entries was the SOI\ucfbroker\conf\broker.properties

It added two duplicate lines in that file:

--------------------

broker.1.protocols=ws

broker.1.data.persist=true

broker.1.ws.uri=http://localhost:8020/ucf/BrokerService

broker.1.data.store.path=D:/APPS/CA/SOI/ucf/ucf_broker_store

#broker.2.protocols=ws

#broker.2.ws.uri=http://@HOST.NAME@:8010/ucf/BrokerService //@HOST.NAME@:8010/ucf/BrokerService

broker.1.data.persist=true

broker.1.data.store.path=D:/APPS/CA/SOI/ucf/ucf_broker_store

----------------------

Should those two last duplicate lines be removed?

Service Operations Insight

SOI Tech Tip: CA SAM Application Server does not startup after RO92514 for SOI 4.0 CUM1

Tags and Keywords

Comments

Related Entries and Links