Aller au contenu principal

Recherche

Recherche

Only 1 Label Printed When Sending 2 By Http

Commentaires

5 commentaires

  • Avatar
    Ian Cummings
    Modérateur
    Out of interest, if you configure the BarTender command handler to run more than one BarTender process do you still get this issue?
    0
  • Avatar
    Legacy Poster
    [quote name='Ian C - Seagull Support' timestamp='1327327362' post='1557']
    Out of interest, if you configure the BarTender command handler to run more than one BarTender process do you still get this issue?
    [/quote]
    We have configured 5 BarTender processes. Sometimes I don't even get any btxml response back (means written as file to disk) for one of the two requests. I have 2 requests which I write to disk, then transformation happens and content is written after transformation to file. Until now everything looks good for both requests. I always get one correct response and printed label, for the second request I sometimes get an answer like in the first post and sometimes I don't see any response file.
    0
  • Avatar
    Ian Cummings
    Modérateur
    What trigger detection parameters have you specified for constituting a trigger event?

    Do you send both triggers in a single network connection, one after the other, or do you create a new connection for each trigger? Please give details.
    0
  • Avatar
    Legacy Poster
    [quote name='Ian C - Seagull Support' timestamp='1327337557' post='1561']
    What trigger detection parameters have you specified for constituting a trigger event?

    Do you send both triggers in a single network connection, one after the other, or do you create a new connection for each trigger? Please give details.
    [/quote]

    I have attached a screenshot of trigger and command settings. I get two input files like this, I assume it's two seperate connections:

    POST / HTTP/1.0
    content-type: text/xml; charset=utf-8
    content-length: 778
    user-agent: SAP Web Application Server (1.0;701)
    host: 172.xx.xx.xx:8001
    accept-encoding: gzip
    sap-language: D

    <?xml version="1.0" encoding="UTF-8"?><ZEQUIPRT01><IDOC BEGIN="1"><EDI_DC40 SEGMENT="1"><TABNAM>EDI_DC40</TABNAM>.......</IDOC></ZEQUIPRT01>

    I first remove the HTTP header with Search and Replace command, so only XML content remains. This is transformed to btXML.
    0
  • Avatar
    Legacy Poster
    Seems like I found the reason for the problem. Because I couldn't reproduce the error on a local installation on my pc, I checked the differences and only noticed in Commander that there have been open connections for the TCP/IP port which did not seem to close automatically. After restarting the Commander Service it seems to work now. What I do not understand is why some connections are not aborted by Commander because I set a timeout for the port of 60000 milliseconds. And why open connections disturbe the processing of btxml in bartender process because input files and transformation output always worked for both requests correctly?
    0

Vous devez vous connecter pour laisser un commentaire.