Problem Note 64709: Using the SOAP procedure for scheduling causes an exception error to appear in the SAS® log
 |  |  |  |  |
A PROC SOAP call to a scheduling server does not complete correctly. An exception error message that is similar to the following then appears in the SAS log:
2019-05-06 11:00:11,603 [tomcat-http--2] ERROR [unknown]
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASWIPSoapServices].
[scheduling-ws] - Allocate exception for servlet [scheduling-ws]
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptionsTwo classes have the same XML type name
"{http://www.sas.com/xml/schema/sas-svcs/schedulingservice-9.3}ReleaseFlowParameters".
Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at
com.sas.svcs.scheduling.client.types.ReleaseFlowParameters
at
public javax.xml.bind.JAXBElementcom.sas.svcs.scheduling.client.types.ObjectFactory.createReleaseFlow (com.sas.
svcs.scheduling.client.types.ReleaseFlowParameters)
at
com.sas.svcs.scheduling.client.types.ObjectFactory
this problem is related to the following location:
at
com.sas.svcs.scheduling.client.types.TriggerFlowParameters
at
public javax.xml.bind.JAXBElementcom.sas.svcs.scheduling.client.types.ObjectFactory.createTriggerFlow(com.sas.
svcs.scheduling.client.types.TriggerFlowParameters)
at
com.sas.svcs.scheduling.client.types.ObjectFactory
org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/SASWIPSoapServices].
[scheduling-ws] - Allocate exception for servlet [scheduling-ws]
com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptionsTwo classes have the same XML type name
"{http://www.sas.com/xml/schema/sas-svcs/schedulingservice-9.3}ReleaseFlowParameters".
Use @XmlType.name and @XmlType.namespace to assign different names to them.
this problem is related to the following location:
at
com.sas.svcs.scheduling.client.types.ReleaseFlowParameters
at
public javax.xml.bind.JAXBElementcom.sas.svcs.scheduling.client.types.ObjectFactory.createReleaseFlow (com.sas.
svcs.scheduling.client.types.ReleaseFlowParameters)
at
com.sas.svcs.scheduling.client.types.ObjectFactory
this problem is related to the following location:
at
com.sas.svcs.scheduling.client.types.TriggerFlowParameters
at
public javax.xml.bind.JAXBElementcom.sas.svcs.scheduling.client.types.ObjectFactory.createTriggerFlow(com.sas.
svcs.scheduling.client.types.TriggerFlowParameters)
at
com.sas.svcs.scheduling.client.types.ObjectFactory
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Web Infrastructure Platform | Microsoft® Windows® for x64 | 9.4_M6 | 9.4 TS1M6 | ||
| 64-bit Enabled AIX | 9.4_M6 | 9.4 TS1M6 | ||||
| 64-bit Enabled Solaris | 9.4_M6 | 9.4 TS1M6 | ||||
| HP-UX IPF | 9.4_M6 | 9.4 TS1M6 | ||||
| Linux for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
| Solaris for x64 | 9.4_M6 | 9.4 TS1M6 | ||||
A fix for this issue for SAS Management Console 9.4_M6 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/D8N.html#64709| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2019-09-09 10:36:07 |
| Date Created: | 2019-08-29 08:12:49 |