corrupted DM-TOOL.jar ?

[Andrej Matusek]

hello,

after updating CDA to v21.0.5. we upgraded also DM action pack with included action pack in version 1.4.9. most of the actions are working fine, but we have issues when executing DM action from remote server

action that is affected is PCK.AUTOMIC_DM.PUB.ACTION.SYNCED_EXECUTE_GENERAL_WORKFLOW. when trying to execute it from remote agent, we are getting following error:

F:\AUTOMIC\aeara\agents\bin>java -jar F:\AUTOMIC\aeara\agents\Resources\7000\dm-tool.jar rm ExecuteGeneralWorkflow -u "https://automic.ersteapps.com:4443/ara" -un "****" -p "****" -n "SVN Secure Upload for Dynamic Deployments" -d "" -m "NO" -e "" -q "" -dp "******************" 
DMTool: DMTool
DMTool: (c) Automic Software GmbH
DMTool: Version: 1.4.9
DMTool: Date: 2023-01-19 07:25
DMTool: 
DMTool: Executing ExecuteGeneralWorkflow started
DMTool: Started at 2023-10-10 15:14:39
DMTool: =================================================
DMTool: PARAM: manualstart = NO
DMTool: PARAM: queue = []
DMTool: PARAM: workflowname = SVN Secure Upload for Dynamic Deployments
DMTool: PARAM: executor = []
DMTool: PARAM: username = 7000/H500RUA/ARA
DMTool: PARAM: loglevel = 
DMTool: PARAM: url = https://automic.ersteapps.com:4443/ara
DMTool: PARAM: dynamicproperties = /svn/source_uri=https://svn.bi.eb-grp.net/svn_at/repo/AT/DYNAMIC/tags/20.1.2021
DMTool: PARAM: startdate = []
Oct 10, 2023 3:14:40 PM org.apache.axiom.util.stax.dialect.StAXDialectDetector detectDialect
WARNING: Unable to determine dialect of the StAX implementation at jar:file:/F:/AUTOMIC/aeara/agents/Resources/7000/dm-tool.jar!/
Oct 10, 2023 3:14:40 PM org.apache.axis2.deployment.AxisConfigBuilder processDeployers
WARNING: Unable to instantiate deployer org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details
Internal Error
org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
	at org.apache.axis2.AxisFault.makeFault(AxisFault.java:431) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:113) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:65) ~[dm-tool.jar:?]
	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:347) ~[dm-tool.jar:?]
	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:414) ~[dm-tool.jar:?]
	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225) ~[dm-tool.jar:?]
	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:150) ~[dm-tool.jar:?]
	at com.uc4.deploymentservice.DeploymentServiceStub.executeGeneralWorkflow(DeploymentServiceStub.java:2393) ~[dm-tool.jar:?]
	at com.uc4.ara.feature.rm.ExecuteGeneralWorkflow.run(ExecuteGeneralWorkflow.java:80) ~[dm-tool.jar:?]
	at com.uc4.ara.feature.AraFileCmd.main(AraFileCmd.java:126) [dm-tool.jar:?]
Caused by: org.apache.axiom.om.DeferredParsingException: javax.xml.stream.XMLStreamException: DOCTYPE is not allowed
	at org.apache.axiom.om.impl.stream.stax.pull.StAXPullReader.parserNext(StAXPullReader.java:342) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.stream.stax.pull.StAXPullReader.proceed(StAXPullReader.java:189) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.builder.BuilderImpl.next(BuilderImpl.java:59) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.mixin.CoreParentNodeSupport.ajc$interMethod$org_apache_axiom_core_impl_mixin_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$internalBuildNext(CoreParentNodeSupport.aj:139) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.llom.OMDocumentImpl.internalBuildNext(OMDocumentImpl.java:1) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.mixin.CoreParentNodeSupport.ajc$interMethodDispatch1$org_apache_axiom_core_impl_mixin_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$internalBuildNext(CoreParentNodeSupport.aj) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.mixin.CoreParentNodeSupport.ajc$interMethod$org_apache_axiom_core_impl_mixin_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$coreGetFirstChild(CoreParentNodeSupport.aj:156) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.llom.OMDocumentImpl.coreGetFirstChild(OMDocumentImpl.java:1) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.mixin.CoreParentNodeSupport.ajc$interMethodDispatch1$org_apache_axiom_core_impl_mixin_CoreParentNodeSupport$org_apache_axiom_core_CoreParentNode$coreGetFirstChild(CoreParentNodeSupport.aj) ~[dm-tool.jar:?]
	at org.apache.axiom.core.impl.mixin.CoreDocumentSupport.ajc$interMethod$org_apache_axiom_core_impl_mixin_CoreDocumentSupport$org_apache_axiom_core_CoreDocument$coreGetDocumentElement(CoreDocumentSupport.aj:53) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.llom.OMDocumentImpl.coreGetDocumentElement(OMDocumentImpl.java:1) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.mixin.AxiomDocumentSupport.ajc$interMethod$org_apache_axiom_om_impl_mixin_AxiomDocumentSupport$org_apache_axiom_om_impl_intf_AxiomDocument$getOMDocumentElement(AxiomDocumentSupport.aj:40) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:1) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.common.builder.OMXMLParserWrapperImpl.getDocumentElement(OMXMLParserWrapperImpl.java:73) ~[dm-tool.jar:?]
	at org.apache.axiom.om.impl.common.builder.OMXMLParserWrapperImpl.getDocumentElement(OMXMLParserWrapperImpl.java:66) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createDefaultDocumentElement(TransportUtils.java:221) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:198) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:135) ~[dm-tool.jar:?]
	at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:106) ~[dm-tool.jar:?]
	... 8 more

anybody who experienced this kind of behavior?

thanks for hints.

regards,

andrej

[Michael Dolinek]

Hi @Andrej Matusek

Does the used Java trust-store contain a valid certificate to access your CDA-server at https://automic.ersteapps.com:4443/ara ?

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Andrej Matusek]

hello,

yes in cacerts we have company CA root authority imported, automation engine server certificate and certificate from machine where we have ani and ara installed (automic.ersteapps.com is dns alias, sz11 is hostname.) certificates are valid

also other DM actions execute from same remote machine are working fine... for example dm set property action and others.

[Michael Dolinek]

Hi @Andrej Matusek

More questions:

• Is IIS and CDA-server properly configured using HTTPS?
• Is CDA's web.config adopted accordingly?

Michael

------------------------------
Michael K. Dolinek

Engineering Program Manager | Agile Operation Division
Broadcom Software
------------------------------

[Andrej Matusek]

hello, 
seems yes.
admin and deploymentservice.svc pages respond correctly on their https urls, certificates are valid too. web.config is enabled for both modes.