Exception - Reference attribute CONFIG_REF is not defined du

Posted by dobrien on 11-Apr-2012 07:32

Hi All,

We have a customer - Vinci, who are deploy their development changes to Production using SDM. The build process worked until about 2 weeks ago, when some (unidentified) change to the Model appears to now cause the following Exception during the build.

Unfortunately, the error gives no clue as to what the problem may be, or where to start looking. Any pointers/advice would be greatly appreciated.

Thanks.

apply.config:

Applying configuration

Warning: Reference configure.class.path has not been set at runtime, but was found during

build file parsing, attempting to resolve. Future versions of Ant may support

referencing ids defined in non-executed targets.

INFO [main] [SdmModelProcessor] Execution Mode [write]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbJournal]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbSuffolk]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbFactoryMaster]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbVinciPickups]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbCCPro]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbMasternaut]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esb360]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbMaximo]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbVinci]

INFO [main] [StopComponents] Stopping [dmVinciUK-Test.ctESBVinci01:ID=esbCoins]

INFO [main] [ESBArchive] Importing D:\sonic_tmp\Model\xars\vinci.xar

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbVinci to Directory Services.

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbCoins to Directory Services.

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbMaximo to Directory Services.

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbCCPro to Directory Services.

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbmasternaut to Directory Services.

INFO [main] [AbstractESBConfig] Writing XQ_CONTAINER/esbFactoryMaster to Directory Services.

INFO [main] [ModelImporter] Writing ClusterComponent [/Clusters/clMessaging]

INFO [main] [ClusterComponent] Persisting [/Clusters/clMessaging] to Directory Services

INFO [main] [ModelImporter] Writing ContainerComponent [/Containers/ctESBVinci01]

INFO [main] [ContainerComponent] Persisting [/Containers/ctESBVinci01] to Directory Services

ERROR [main] [SdmModelProcessor] Reference attribute CONFIG_REF is not defined.

Reference attribute CONFIG_REF is not defined.

at com.sonicsw.pso.sdm.config.application.SdmModelProcessor.execute(SdmModelProcessor.java:266)

at com.sonicsw.pso.sdm.config.application.SdmModelProcessor.main(SdmModelProcessor.java:187)

Caused by: com.sonicsw.ma.mgmtapi.config.AttributeNotFoundException: Reference attribute CONFIG_REF is not defined.

at com.sonicsw.ma.mgmtapi.config.impl.MgmtSubBeanBase.getReferenceAttribute(MgmtSubBeanBase.java:347)

at com.sonicsw.mf.mgmtapi.config.gen.impl.AbstractContainerBean$AbstractStartupParams.getConfigRef(AbstractConta

inerBean.java:1299)

at com.sonicsw.mf.mgmtapi.config.impl.ContainerBean$ComponentsType.add(ContainerBean.java:373)

at com.sonicsw.mf.mgmtapi.config.impl.ContainerBean$ComponentsType.addEntry(ContainerBean.java:383)

at com.sonicsw.pso.sdm.config.ContainerMemberComponent.createStartupParams(ContainerMemberComponent.java:450)

at com.sonicsw.pso.sdm.config.ContainerMemberComponent.addTo(ContainerMemberComponent.java:222)

at com.sonicsw.pso.sdm.config.ContainerComponent.writeTo(ContainerComponent.java:384)

at com.sonicsw.pso.sdm.config.application.ModelImporter.writeBeanList(ModelImporter.java:652)

at com.sonicsw.pso.sdm.config.application.ModelImporter.writeComponents(ModelImporter.java:620)

at com.sonicsw.pso.sdm.config.application.ModelImporter.importMQConfigurations(ModelImporter.java:258)

at com.sonicsw.pso.sdm.config.application.ModelImporter.importConfigurations(ModelImporter.java:236)

at com.sonicsw.pso.sdm.config.application.ModelImporter.process(ModelImporter.java:128)

at com.sonicsw.pso.sdm.config.application.SdmModelProcessor.execute(SdmModelProcessor.java:259)

... 1 more

--- Nested Exception ---

Technology Partner - Forum

All Replies

Posted by davila on 11-Apr-2012 17:25

What SDM/MQ/ESB version are they using? At a high level, this error means that the lower level APIs tried to access an attribute in the container component schema that the API then determined does not exist (CONFIG_REF). This is unusual because the schema and the lower level APIs go hand in hand. If you provide us with the versions, we might be able to figure out if there is the possibility that some combinations of updates/patches, etc might have produced this incompatibility for the customer.

Posted by dobrien on 19-Apr-2012 04:36

Hi Maria,

Apologies for the delay in responing - I've been out for a while.

SonicESB version below - not sure if the SDM version is the same? Its certainly the version that was delpoyed with this version of ESB:

Sonic ESB Continuous Availability Edition [Serial Number: 4194338]

Release 8.0.1 Build Number 197

Nothing's changed from a version point of view though - the Customer's only been updating the XAR Tailoring file.

Dave.

Posted by davila on 19-Apr-2012 09:57

I was looking to see whether a product like ESB or SDM might have been patched while the other one had not, but looking at the history of the container schema, I can't see where an incompatibility would have been introduced. I think the best thing is to open a support case; we are going to need the customer's SDM model and their DS. I'm guessing that it an interaction between the schema stored in the DS, the version of MF and the version of SDM. The version of MF you'd get in the domain manager log; the version of SDM is output at the top of the SDM build output.

This thread is closed