Fred,

thank you so much for your reply!

I'm on 7.5 Patch 7 and Mid-tier 7.6.3.

I've changed the logging to debug so. I now can see the actual XML
being passed between the systems.

Unfortunately I can't see any error in the arjavaplugin.log. I shows
me the XML being passed forth and back.

In the API log I can see a FAIL while doing the Set in the filter
without further explanation of what failed. And I can see a failed set
fields in the filter log. But that's it.

No errors in the arerror log, no errors in any other log. I really
want to avoid rising a ticket with BMC as this will consume a lot of
time and yield no results, but mapping these fields over and over
again is also a pain.

This is so frustrating!


Mark


On 28 Feb., 18:00, "Grooms, Frederick W" <[email protected]>
wrote:
> It sounds like the problem is in the data being returned back to ARS (the 
> Output mapping) from the external system so it may not occur on every 
> transaction.
>
> Depending on which ARS version you are using turn on the Plugin log and set 
> the Plugin log version to Info or Debug. With the logging turned on you can 
> see the actual XML being passed between systems.  Look at the data being 
> returned to see if there is any types not allowed (data types not allowed by 
> ARS are listed in the documentation).
>
> For ARS 7.1.x and earlier the web service plugin uses the arplugin log.  You 
> would set the logging level in the ar.conf (ar.cfg for Windows).  
> Plugin-Log-Level:400
>
> ARS 7.5.x and later uses a Java web service plugin so the log data would be 
> in the arjavaplugin.log.  You would set the logging level in the 
> log4j_pluginsvr.xml (in the pluginsvr directory).  
>         <logger name="com.bmc.arsys.ws">  
>                 <level  value="debug" />   <!-- or  value="info"  -->
>         </logger>  
>
> Fred
>
>
>
> -----Original Message-----
> From: Action Request System discussion list(ARSList) 
> [mailto:[email protected]] On Behalf Of Mark Milke
> Sent: Monday, February 28, 2011 10:35 AM
> To: [email protected]
> Subject: ARERR [8959] The XML data type is not supported. <>
>
> Hi Listers,
>
> I've build a SOAP Message Queue and I'm testing a web service with our
> partner.
>
> I'm testing in manual mode, i.e. I'm setting every message's status to
> Completed in order to initiate the comsumption of our partner's Web
> Service.
>
> While consuming a web service I'm getting the error mentioned in the
> title and I have no idea what is causing it.
>
> What's even more odd is, that is SOAP message arrives at the Web
> Service provider, just can't set my message to Completed because of
> the error. When I let an escalation run over it, it will fail I guess.
>
> The top of oddity is that when I redo the mapping in the filter, the
> error disappears for a few hours to return a few hours later.
>
> Do you guys have an idea how to track down the problem?
>
> Mark
>
> ___________________________________________________________________________­____
> UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org
> attend wwrug11www.wwrug.comARSList: "Where the Answers Are"- Zitierten Text 
> ausblenden -
>
> - Zitierten Text anzeigen -

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"

Reply via email to