[jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

classic Classic list List threaded Threaded
39 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
My application connects to a server to send and receive responses using Channel Adaptor using QMUX. Below is the channel and mux definitions:

*********************** CHANNEL *********************************************

<?xml version="1.0" ?>

<channel-adaptor name='clientsimulator-adaptor'
    class="org.jpos.q2.iso.ChannelAdaptor" logger="Q2">
    <channel class="com.google.PostChannel" name="client-channel"
             packager="org.jpos.iso.packager.GenericPackager" logger="Q2">
        <property name="packager-config" value="iso8583.xml" />
    </channel>
    <in>clientsimulator-send</in>
    <out>clientsimulator-receive</out>
    <reconnect-delay>30000</reconnect-delay>
    <ignore-iso-exceptions>yes</ignore-iso-exceptions>
</channel-adaptor>

**********************************************************************************
************************* MUX **************************************************
<?xml version="1.0" ?>

<mux class="org.jpos.q2.iso.QMUX" logger="Q2" name="clientsimulator-mux">
    <in>clientsimulator-receive</in>
    <out>clientsimulator-send</out>
    <unhandled>clientsimulator-unhandled</unhandled>
    <request-listener class="com.google.UnhandledMsgDriver" logger="Q2">
        <property name="registerId" value="UNHLD" />
    </request-listener>
</mux>
**********************************************************************************

Env:
     JDK : 1.7
     jPOS : 1.9.0
     App Server: JBoss 5.1

The above configuration works just fine in locally and also used to for the past few months(in production) until few days ago after a recent RedHat patch, the requests are timing out. Looking at the logs I see that the response is received by the jPos and Un-packaged but not handed to request thread. The request thread times out after 20 secs(default config). I've even tried to add the "key"s to the mux config to see if it is an issue with the match key, it did not help.

Thx!

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Alejandro Revilla
Can you show us the log?



On Tue, Aug 23, 2016 at 9:20 PM, Rama Gullapalli <[hidden email]> wrote:
My application connects to a server to send and receive responses using Channel Adaptor using QMUX. Below is the channel and mux definitions:

*********************** CHANNEL *********************************************

<?xml version="1.0" ?>

<channel-adaptor name='clientsimulator-adaptor'
    class="org.jpos.q2.iso.ChannelAdaptor" logger="Q2">
    <channel class="com.google.PostChannel" name="client-channel"
             packager="org.jpos.iso.packager.GenericPackager" logger="Q2">
        <property name="packager-config" value="iso8583.xml" />
    </channel>
    <in>clientsimulator-send</in>
    <out>clientsimulator-receive</out>
    <reconnect-delay>30000</reconnect-delay>
    <ignore-iso-exceptions>yes</ignore-iso-exceptions>
</channel-adaptor>

**********************************************************************************
************************* MUX **************************************************
<?xml version="1.0" ?>

<mux class="org.jpos.q2.iso.QMUX" logger="Q2" name="clientsimulator-mux">
    <in>clientsimulator-receive</in>
    <out>clientsimulator-send</out>
    <unhandled>clientsimulator-unhandled</unhandled>
    <request-listener class="com.google.UnhandledMsgDriver" logger="Q2">
        <property name="registerId" value="UNHLD" />
    </request-listener>
</mux>
**********************************************************************************

Env:
     JDK : 1.7
     jPOS : 1.9.0
     App Server: JBoss 5.1

The above configuration works just fine in locally and also used to for the past few months(in production) until few days ago after a recent RedHat patch, the requests are timing out. Looking at the logs I see that the response is received by the jPos and Un-packaged but not handed to request thread. The request thread times out after 20 secs(default config). I've even tried to add the "key"s to the mux config to see if it is an issue with the match key, it did not help.

Thx!

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3D%3Dz4eA42R8VHqkSrTj9ai4yQX-j63zQf6AoOS7GFxbNxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
Below is the application log:

12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       

12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

On Tuesday, August 23, 2016 at 5:37:53 PM UTC-7, Alejandro Revilla wrote:
Can you show us the log?


--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr

On Tue, Aug 23, 2016 at 9:20 PM, Rama Gullapalli <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="RboBSfI3AwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ramaraidu....@gmail.com> wrote:
My application connects to a server to send and receive responses using Channel Adaptor using QMUX. Below is the channel and mux definitions:

*********************** CHANNEL *********************************************

<?xml version="1.0" ?>

<channel-adaptor name='clientsimulator-adaptor'
    class="org.jpos.q2.iso.ChannelAdaptor" logger="Q2">
    <channel class="com.google.PostChannel" name="client-channel"
             packager="org.jpos.iso.packager.GenericPackager" logger="Q2">
        <property name="packager-config" value="iso8583.xml" />
    </channel>
    <in>clientsimulator-send</in>
    <out>clientsimulator-receive</out>
    <reconnect-delay>30000</reconnect-delay>
    <ignore-iso-exceptions>yes</ignore-iso-exceptions>
</channel-adaptor>

**********************************************************************************
************************* MUX **************************************************
<?xml version="1.0" ?>

<mux class="org.jpos.q2.iso.QMUX" logger="Q2" name="clientsimulator-mux">
    <in>clientsimulator-receive</in>
    <out>clientsimulator-send</out>
    <unhandled>clientsimulator-unhandled</unhandled>
    <request-listener class="com.google.UnhandledMsgDriver" logger="Q2">
        <property name="registerId" value="UNHLD" />
    </request-listener>
</mux>
**********************************************************************************

Env:
     JDK : 1.7
     jPOS : 1.9.0
     App Server: JBoss 5.1

The above configuration works just fine in locally and also used to for the past few months(in production) until few days ago after a recent RedHat patch, the requests are timing out. Looking at the logs I see that the response is received by the jPos and Un-packaged but not handed to request thread. The request thread times out after 20 secs(default config). I've even tried to add the "key"s to the mux config to see if it is an issue with the match key, it did not help.

Thx!

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="RboBSfI3AwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sa...@...
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="RboBSfI3AwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...
To unsubscribe, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="RboBSfI3AwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="RboBSfI3AwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/7294d79e-3486-41fa-ae74-56cd7f969a35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
Quick update, restart of Application Server fixed the issue.

Thanks,
Rama

On Tuesday, August 23, 2016 at 11:30:29 PM UTC-7, Rama Gullapalli wrote:
Below is the application log:

12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       

12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

On Tuesday, August 23, 2016 at 5:37:53 PM UTC-7, Alejandro Revilla wrote:
Can you show us the log?


--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr

On Tue, Aug 23, 2016 at 9:20 PM, Rama Gullapalli <[hidden email]> wrote:
My application connects to a server to send and receive responses using Channel Adaptor using QMUX. Below is the channel and mux definitions:

*********************** CHANNEL *********************************************

<?xml version="1.0" ?>

<channel-adaptor name='clientsimulator-adaptor'
    class="org.jpos.q2.iso.ChannelAdaptor" logger="Q2">
    <channel class="com.google.PostChannel" name="client-channel"
             packager="org.jpos.iso.packager.GenericPackager" logger="Q2">
        <property name="packager-config" value="iso8583.xml" />
    </channel>
    <in>clientsimulator-send</in>
    <out>clientsimulator-receive</out>
    <reconnect-delay>30000</reconnect-delay>
    <ignore-iso-exceptions>yes</ignore-iso-exceptions>
</channel-adaptor>

**********************************************************************************
************************* MUX **************************************************
<?xml version="1.0" ?>

<mux class="org.jpos.q2.iso.QMUX" logger="Q2" name="clientsimulator-mux">
    <in>clientsimulator-receive</in>
    <out>clientsimulator-send</out>
    <unhandled>clientsimulator-unhandled</unhandled>
    <request-listener class="com.google.UnhandledMsgDriver" logger="Q2">
        <property name="registerId" value="UNHLD" />
    </request-listener>
</mux>
**********************************************************************************

Env:
     JDK : 1.7
     jPOS : 1.9.0
     App Server: JBoss 5.1

The above configuration works just fine in locally and also used to for the past few months(in production) until few days ago after a recent RedHat patch, the requests are timing out. Looking at the logs I see that the response is received by the jPos and Un-packaged but not handed to request thread. The request thread times out after 20 secs(default config). I've even tried to add the "key"s to the mux config to see if it is an issue with the match key, it did not help.

Thx!

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/7dbce84a-3219-40ef-99d0-4915fa329d71%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/06749a4d-7b4e-40ac-b3d0-7e37954ba1ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Alejandro Revilla
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.



--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

chhil
Did you check if it ended up with the unhandled driver?
Your fields 11,41 match, so it shouldn't have, but worth taking a look at.

-chhil

On Thu, Aug 25, 2016 at 12:34 AM, Alejandro Revilla <[hidden email]> wrote:
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.



--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAPazefC-NWzJLirtAVdvTk87vnTtuOziFtZTRkNitJ5khmDdgw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
Yes, it ended up with the unhandled driver. Verified the match keys, default and custom, in both cases it failed to match. We had a similar problem in another clients env but that was resolved after reverting to single session ChannelAdaptor from 16 sessions MultiSessionChannelAdaptor. Verified the thread stack as well, couldnt find any clues there.

Thanks,
Rama

On Wednesday, August 24, 2016 at 7:15:20 PM UTC-7, chhil wrote:
Did you check if it ended up with the unhandled driver?
Your fields 11,41 match, so it shouldn't have, but worth taking a look at.

-chhil

On Thu, Aug 25, 2016 at 12:34 AM, Alejandro Revilla <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="GeEPJtiLAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">a...@...> wrote:
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.

--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr


--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GeEPJtiLAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sa...@...
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GeEPJtiLAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...
To unsubscribe, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GeEPJtiLAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GeEPJtiLAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/560e2f65-a412-474f-8ba2-83b4bb32f069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
Is there any additional logging that we can enable on the QMUX? We currently have the Q2 loggers enabled as shown in the config.

Thanks,
Rama
On Thursday, August 25, 2016 at 9:56:57 AM UTC-7, Rama Gullapalli wrote:
Yes, it ended up with the unhandled driver. Verified the match keys, default and custom, in both cases it failed to match. We had a similar problem in another clients env but that was resolved after reverting to single session ChannelAdaptor from 16 sessions MultiSessionChannelAdaptor. Verified the thread stack as well, couldnt find any clues there.

Thanks,
Rama

On Wednesday, August 24, 2016 at 7:15:20 PM UTC-7, chhil wrote:
Did you check if it ended up with the unhandled driver?
Your fields 11,41 match, so it shouldn't have, but worth taking a look at.

-chhil

On Thu, Aug 25, 2016 at 12:34 AM, Alejandro Revilla <[hidden email]> wrote:
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.

--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr


--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Alejandro Revilla
No, but if you have channel level logging you might be able to figure out what could be wrong with your messages.




On Fri, Aug 26, 2016 at 4:30 PM, Rama Gullapalli <[hidden email]> wrote:
Is there any additional logging that we can enable on the QMUX? We currently have the Q2 loggers enabled as shown in the config.

Thanks,
Rama
On Thursday, August 25, 2016 at 9:56:57 AM UTC-7, Rama Gullapalli wrote:
Yes, it ended up with the unhandled driver. Verified the match keys, default and custom, in both cases it failed to match. We had a similar problem in another clients env but that was resolved after reverting to single session ChannelAdaptor from 16 sessions MultiSessionChannelAdaptor. Verified the thread stack as well, couldnt find any clues there.

Thanks,
Rama

On Wednesday, August 24, 2016 at 7:15:20 PM UTC-7, chhil wrote:
Did you check if it ended up with the unhandled driver?
Your fields 11,41 match, so it shouldn't have, but worth taking a look at.

-chhil

On Thu, Aug 25, 2016 at 12:34 AM, Alejandro Revilla <[hidden email]> wrote:
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.



--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]m
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]m.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DkdfFF%2BG3%3D%3Dv-FmvWQDfhV2-jKyJSobCzQymxdicE0yHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
We have verified the messages and the match key DE are not the problem. The request(0200) and response(0210) logs are as attached in the email below with data masked.

Thanks,
Rama
On Friday, August 26, 2016 at 12:32:51 PM UTC-7, Alejandro Revilla wrote:
No, but if you have channel level logging you might be able to figure out what could be wrong with your messages.



--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr

On Fri, Aug 26, 2016 at 4:30 PM, Rama Gullapalli <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="GM0OogoTBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ramaraidu....@gmail.com> wrote:
Is there any additional logging that we can enable on the QMUX? We currently have the Q2 loggers enabled as shown in the config.

Thanks,
Rama
On Thursday, August 25, 2016 at 9:56:57 AM UTC-7, Rama Gullapalli wrote:
Yes, it ended up with the unhandled driver. Verified the match keys, default and custom, in both cases it failed to match. We had a similar problem in another clients env but that was resolved after reverting to single session ChannelAdaptor from 16 sessions MultiSessionChannelAdaptor. Verified the thread stack as well, couldnt find any clues there.

Thanks,
Rama

On Wednesday, August 24, 2016 at 7:15:20 PM UTC-7, chhil wrote:
Did you check if it ended up with the unhandled driver?
Your fields 11,41 match, so it shouldn't have, but worth taking a look at.

-chhil

On Thu, Aug 25, 2016 at 12:34 AM, Alejandro Revilla <[hidden email]> wrote:
Then that's guaranteed to happen again. I hope you can isolate the logs of the problems so you can carefully try to understand why this happened.

--
<a style="font-family:garamond,serif" href="http://twitter.com/apr" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Ftwitter.com%2Fapr\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFRt8creb486OVHOJ12erdzV1NRIg&#39;;return true;">@apr


--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/CAAgSK%3DnT%3DEhvq6xYav_CR3tGKyZj%3Df7CU8X%2BSRjn8%3DV6eDLaQQ%40mail.gmail.com.

For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GM0OogoTBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sa...@...
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GM0OogoTBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...
To unsubscribe, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GM0OogoTBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="GM0OogoTBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/ff542c02-2ff0-43dc-88f6-596f45e8ca52%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

jPOS - Users mailing list
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

chhil
Are your IP/PORT intentionally removed in the logs? Mark raises a good point, if the request response are not on the same connection, it will go to the unhandled as it will see it as an unsolicited response.
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">

The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible.

-chhil

On Sat, Aug 27, 2016 at 3:10 AM, 'Mark Salter' via jPOS Users <[hidden email]> wrote:
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAPazefDH-EXJE9Y4KF78gH5VfDeGc7PpFjYSa5OhVm7%2BQSrL%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
@chill, yes the IP and port are intentionally masked as the logs were from prod. The same config which was working for more than 4  months broke recently, and a restart fixed the issue. Again, no config changes were made. Few notes on the existing config, we have multiple channels defined talking to various server sockets with similar config(i.e different application modules talking to different IP/Ports). Only this particular channel app module was timing out.

Please find the logs displayed below:
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       
12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.
connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

1. Take notice of the highlighted statements. The point at which the response thread was received and after which the app thread timed out after 20 seconds.
2. The default key config was used in the QMUX i.e 11 and 41. As you can see from the logs, the request and response keys match.

@chhil, could you please clarify the below statement in more detail :
"The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible."

From the app logs, the response was immediately received in a second.

Thanks,
Rama

- show quoted text -



On Saturday, August 27, 2016 at 1:44:41 AM UTC-7, chhil wrote:
Are your IP/PORT intentionally removed in the logs? Mark raises a good point, if the request response are not on the same connection, it will go to the unhandled as it will see it as an unsolicited response.
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">

The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible.

-chhil

On Sat, Aug 27, 2016 at 3:10 AM, 'Mark Salter' via jPOS Users <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="SH5TdEA-BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...> wrote:
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="SH5TdEA-BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sa...@...

Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="SH5TdEA-BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...
To unsubscribe, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="SH5TdEA-BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="SH5TdEA-BAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

chhil
I understand that the response was received immediately, my concern is, it was possibly received on a channel that did not send the request.
Configuration does not have to do anything with it. 
In this case the keys for the mux are fine but the mux that sent request has the match key and the mux that received the response doesn't hence it ended up in the unhandled.
So do check if 
1.the port numbers to verify it was on the same channel
2.the channel name in the log on which the request was sent and on which the response was received.

Lifespan Clarification :

The following is quoted from the blog.
So depending on the code using the logger, the meaning of the ‘lifespan’ attribute vary. 
In the ChannelAdaptor for example, we create a LogEvent, and then call channel.receive(), so the ‘lifespan’ attribute basically shows us 
how much time the channel was idle and we were waiting for a message to come.
 In order to understand the lifespan attribute, you need to take a look at the code that generates it.
So what the lifespan from your log hints at is, the receive part of the channel was idle for quite some time and likely not receiving anything for the duration from it events creation.
Which leads me to believe the receiver wasn't active in the system and all of a sudden it got a response.


-chhil

On Mon, Aug 29, 2016 at 5:00 AM, Rama <[hidden email]> wrote:
@chill, yes the IP and port are intentionally masked as the logs were from prod. The same config which was working for more than 4  months broke recently, and a restart fixed the issue. Again, no config changes were made. Few notes on the existing config, we have multiple channels defined talking to various server sockets with similar config(i.e different application modules talking to different IP/Ports). Only this particular channel app module was timing out.

Please find the logs displayed below:
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       
12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.
connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

1. Take notice of the highlighted statements. The point at which the response thread was received and after which the app thread timed out after 20 seconds.
2. The default key config was used in the QMUX i.e 11 and 41. As you can see from the logs, the request and response keys match.

@chhil, could you please clarify the below statement in more detail :
"The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible."

From the app logs, the response was immediately received in a second.

Thanks,
Rama

- show quoted text -



On Saturday, August 27, 2016 at 1:44:41 AM UTC-7, chhil wrote:
Are your IP/PORT intentionally removed in the logs? Mark raises a good point, if the request response are not on the same connection, it will go to the unhandled as it will see it as an unsolicited response.
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">

The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible.

-chhil

On Sat, Aug 27, 2016 at 3:10 AM, 'Mark Salter' via jPOS Users <[hidden email]> wrote:
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]m
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]m.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAPazefBeQK-5GP0Zguprf_9C30hszc-%2BgRUgfs%3D%3Dmu2_mnWSPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli
I've confirmed from the logs again, the IP and port in both request and response are same. You bring up a point on the lifespan, will look into it further. We have a single channel session that is used for all the app threads. Could this be related to using the default space for all the client channels that belong to different app modules?

Thanks,
Rama
On Sunday, August 28, 2016 at 8:41:39 PM UTC-7, chhil wrote:
I understand that the response was received immediately, my concern is, it was possibly received on a channel that did not send the request.
Configuration does not have to do anything with it. 
In this case the keys for the mux are fine but the mux that sent request has the match key and the mux that received the response doesn't hence it ended up in the unhandled.
So do check if 
1.the port numbers to verify it was on the same channel
2.the channel name in the log on which the request was sent and on which the response was received.

Lifespan Clarification :
Do read up on <a href="http://jpos.org/blog/2013/01/logger-lifespan-attribute/" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fblog%2F2013%2F01%2Flogger-lifespan-attribute%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF2aPongKaMY2w8cU54-YgXjVVh5Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fblog%2F2013%2F01%2Flogger-lifespan-attribute%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF2aPongKaMY2w8cU54-YgXjVVh5Q&#39;;return true;">http://jpos.org/blog/2013/01/logger-lifespan-attribute/

The following is quoted from the blog.
So depending on the code using the logger, the meaning of the ‘lifespan’ attribute vary. 
In the ChannelAdaptor for example, we create a LogEvent, and then call channel.receive(), so the ‘lifespan’ attribute basically shows us 
how much time the channel was idle and we were waiting for a message to come.
 In order to understand the lifespan attribute, you need to take a look at the code that generates it.
So what the lifespan from your log hints at is, the receive part of the channel was idle for quite some time and likely not receiving anything for the duration from it events creation.
Which leads me to believe the receiver wasn't active in the system and all of a sudden it got a response.


-chhil

On Mon, Aug 29, 2016 at 5:00 AM, Rama <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="c69wQuDKBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">ramaraidu....@gmail.com> wrote:
@chill, yes the IP and port are intentionally masked as the logs were from prod. The same config which was working for more than 4  months broke recently, and a restart fixed the issue. Again, no config changes were made. Few notes on the existing config, we have multiple channels defined talking to various server sockets with similar config(i.e different application modules talking to different IP/Ports). Only this particular channel app module was timing out.

Please find the logs displayed below:
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       
12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.
connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

1. Take notice of the highlighted statements. The point at which the response thread was received and after which the app thread timed out after 20 seconds.
2. The default key config was used in the QMUX i.e 11 and 41. As you can see from the logs, the request and response keys match.

@chhil, could you please clarify the below statement in more detail :
"The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible."

From the app logs, the response was immediately received in a second.

Thanks,
Rama

- show quoted text -



On Saturday, August 27, 2016 at 1:44:41 AM UTC-7, chhil wrote:
Are your IP/PORT intentionally removed in the logs? Mark raises a good point, if the request response are not on the same connection, it will go to the unhandled as it will see it as an unsolicited response.
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">

The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible.

-chhil

On Sat, Aug 27, 2016 at 3:10 AM, 'Mark Salter' via jPOS Users <[hidden email]> wrote:
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c69wQuDKBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">sa...@...
 
Join us in IRC at <a href="http://webchat.freenode.net/?channels=jpos" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwebchat.freenode.net%2F%3Fchannels%3Djpos\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFCrTYvEQkbnSq84YoEMPHY73h7rA&#39;;return true;">http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see <a href="http://jpos.org/wiki/JPOS_Mailing_List_Readme_first" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjpos.org%2Fwiki%2FJPOS_Mailing_List_Readme_first\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH6q2fBfGcVvwbjbbUxCvM0VXXD3Q&#39;;return true;">http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c69wQuDKBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-...@...
To unsubscribe, send email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c69wQuDKBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com
For more options, visit this group at <a href="http://groups.google.com/group/jpos-users" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;" onclick="this.href=&#39;http://groups.google.com/group/jpos-users&#39;;return true;">http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="c69wQuDKBAAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jpos-users+...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com.

For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/62ae4c8f-8fb2-4065-9fe3-99425df4fef7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

chhil

We have a single channel session…

If you have a single channel then its its not possible to get a response on anything but that channel.

Could this be related to using the default space for all the client channels that belong to different app modules?

I don't have sufficient knowledge to answer this, hopefully someone in this group with a better understanding of the internals can assist you here.

-chhil


On Mon, Aug 29, 2016 at 1:43 PM, Rama <[hidden email]> wrote:
I've confirmed from the logs again, the IP and port in both request and response are same. You bring up a point on the lifespan, will look into it further. We have a single channel session that is used for all the app threads. Could this be related to using the default space for all the client channels that belong to different app modules?

Thanks,
Rama
On Sunday, August 28, 2016 at 8:41:39 PM UTC-7, chhil wrote:
I understand that the response was received immediately, my concern is, it was possibly received on a channel that did not send the request.
Configuration does not have to do anything with it. 
In this case the keys for the mux are fine but the mux that sent request has the match key and the mux that received the response doesn't hence it ended up in the unhandled.
So do check if 
1.the port numbers to verify it was on the same channel
2.the channel name in the log on which the request was sent and on which the response was received.

Lifespan Clarification :

The following is quoted from the blog.
So depending on the code using the logger, the meaning of the ‘lifespan’ attribute vary. 
In the ChannelAdaptor for example, we create a LogEvent, and then call channel.receive(), so the ‘lifespan’ attribute basically shows us 
how much time the channel was idle and we were waiting for a message to come.
 In order to understand the lifespan attribute, you need to take a look at the code that generates it.
So what the lifespan from your log hints at is, the receive part of the channel was idle for quite some time and likely not receiving anything for the duration from it events creation.
Which leads me to believe the receiver wasn't active in the system and all of a sudden it got a response.


-chhil

On Mon, Aug 29, 2016 at 5:00 AM, Rama <[hidden email]> wrote:
@chill, yes the IP and port are intentionally masked as the logs were from prod. The same config which was working for more than 4  months broke recently, and a restart fixed the issue. Again, no config changes were made. Few notes on the existing config, we have multiple channels defined talking to various server sockets with similar config(i.e different application modules talking to different IP/Ports). Only this particular channel app module was timing out.

Please find the logs displayed below:
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:35,701  INFO STDOUT:? -   <send>
12:51:35,701  INFO STDOUT:? -     <isomsg
12:51:35,701  INFO STDOUT:? - >
12:51:35,701  INFO STDOUT:? -       <field id="0" value="0200"/>
12:51:35,701  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="3" value="330000"/>
12:51:35,701  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:35,701  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:35,701  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="14" value="1908"/>
12:51:35,701  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="17" value="0822"/>
12:51:35,701  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:35,701  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="22" value="062"/>
12:51:35,701  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:35,701  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:35,701  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:35,701  INFO STDOUT:? -       <field id="42" value="               "/>
12:51:35,701  INFO STDOUT:? -       <field id="43" value="
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:35,701  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:35,701  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -       <field id="123" value="XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"/>
12:51:35,701  INFO STDOUT:? -     </isomsg>
12:51:35,701  INFO STDOUT:? -     [B@7af56382
12:51:35,701  INFO STDOUT:? -   </send>
12:51:35,701  INFO STDOUT:? - </log>
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">
12:51:36,437  INFO STDOUT:? -   <receive>
12:51:36,437  INFO STDOUT:? -     <isomsg
12:51:36,437  INFO STDOUT:? - >
12:51:36,437  INFO STDOUT:? -       <field id="0" value="0210"/>
12:51:36,437  INFO STDOUT:? -       <field id="2" value="XXXXXXXXXXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="3" value="332000"/>
12:51:36,437  INFO STDOUT:? -       <field id="4" value="000000000000"/>
12:51:36,437  INFO STDOUT:? -       <field id="7" value="0822175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="11" value="223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="12" value="175135"/>
12:51:36,437  INFO STDOUT:? -       <field id="13" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="15" value="0822"/>
12:51:36,437  INFO STDOUT:? -       <field id="18" value="6999"/>
12:51:36,437  INFO STDOUT:? -       <field id="19" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="32" value="1100000939 "/>
12:51:36,437  INFO STDOUT:? -       <field id="37" value="110000223297"/>
12:51:36,437  INFO STDOUT:? -       <field id="39" value="00"/>
12:51:36,437  INFO STDOUT:? -       <field id="41" value="TERMINALID"/>
12:51:36,437  INFO STDOUT:? -       <field id="49" value="840"/>
12:51:36,437  INFO STDOUT:? -       <field id="54" value="2002840C0000000070202001840C000000007020"/>
12:51:36,437  INFO STDOUT:? -       <field id="58" value="10101000211"/>
12:51:36,437  INFO STDOUT:? -       <field id="63" value="XXXXXXXX"/>
12:51:36,437  INFO STDOUT:? -       <field id="102" value="000008____3229"/>
12:51:36,437  INFO STDOUT:? -       <field id="123" value="TDAR01YCR01M"/>
12:51:36,437  INFO STDOUT:? -       <field id="126" value="0250828701000"/>
12:51:36,437  INFO STDOUT:? -       <field id="9999" value="1471888296437"/>
12:51:36,437  INFO STDOUT:? -     </isomsg>
12:51:36,437  INFO STDOUT:? -   </receive>
12:51:36,437  INFO STDOUT:? - </log>
12:51:36,437  INFO Logger:? - 0,<null>,com.company.driver,INFO,ISORequestHandler: received message
12:51:36,437 DEBUG Logger:? - 0,<null>,com.company.routing.core,DEBUG,get message processor for 0210                       
12:51:55,702 DEBUG Logger:? - 225,<null>,com.company.
connector.registration.services,DEBUG, validatePAN-> result null
12:51:55,702 ERROR Logger:? - 225,<null>,com.company.connector.registration.services,ERROR,PAN validation failed

1. Take notice of the highlighted statements. The point at which the response thread was received and after which the app thread timed out after 20 seconds.
2. The default key config was used in the QMUX i.e 11 and 41. As you can see from the logs, the request and response keys match.

@chhil, could you please clarify the below statement in more detail :
"The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible."

From the app logs, the response was immediately received in a second.

Thanks,
Rama

- show quoted text -



On Saturday, August 27, 2016 at 1:44:41 AM UTC-7, chhil wrote:
Are your IP/PORT intentionally removed in the logs? Mark raises a good point, if the request response are not on the same connection, it will go to the unhandled as it will see it as an unsolicited response.
12:51:35,701  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:35 CDT 2016.701">
12:51:36,437  INFO STDOUT:? - <log realm="channel/IP:PORT" at="Mon Aug 22 12:51:36 CDT 2016.437" lifespan="88185ms">

The lifespan appears to be pretty large, usually the case when the channels logevent was created but hasn't received data and thus indicating idle time.
If the response came back on the same channel, I think such a large lifespan would not be visible.

-chhil

On Sat, Aug 27, 2016 at 3:10 AM, 'Mark Salter' via jPOS Users <[hidden email]> wrote:
On 26/08/16 22:30, Rama Gullapalli wrote:
> We have verified the messages and the match key DE are not the problem.
If the response ended up in the unhandled queue, then they are the issue
- either by config, failure of the response to reach the mux through
which the request was sent or the message content. Or the MTI
request/response values do not align.

What fields have you configured your mux to match on?

> The request(0200) and response(0210) logs are as attached in the email
> below with data masked.
Sorry they did not make it to the mailing list.

Please present the 'keys' from the MUX config, the request and response
messages (in parsed form from the log and perhaps in raw if you can).

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]m
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]m.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to jpos-users+...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jpos-users+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/4cb2f2ff-a2d4-441c-95cb-5fdea4fe6599%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/62ae4c8f-8fb2-4065-9fe3-99425df4fef7%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/CAPazefAm8u3sA-%2BS3Fu3k_0L3cYnJ4nzoHx%3DbibOnmKnVi3P4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

jPOS - Users mailing list
In reply to this post by Rama Gullapalli
On 29/08/16 00:30, Rama wrote:
> yes the IP and port are intentionally masked as the logs were
> from prod.
Do you hold a commercial license for using jpos?

> The same config which was working for more than 4  months
> broke recently,
What changed recently?
> and a restart fixed the issue.
Not fixed, but stopped happening I guess you mean.

> Again, no config changes were made.
What other changes occurred, if nothing jPOS related changed, then you
need to look elsewhere.

>  Few notes on the existing config, we have multiple channels
> defined talking to various server sockets with similar config(i.e
> different application modules talking to different IP/Ports). Only this
> particular channel app module was timing out.
So you need to work out what is different about this connection or other
system.

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/68d6c55e-7f5d-8e0b-26e6-4b0ffe9a1f15%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

jPOS - Users mailing list
In reply to this post by Rama Gullapalli
On 29/08/16 09:13, Rama wrote:
> Could this be related to using the default space for all the client
> channels that belong to different app modules?
Without knowing how you are using this (perhaps) single space across
your client's how would we know?

Are you sharing space keys between components?

Are any other connections reporting an unhandled response message?

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/060114cd-0d7f-4414-6450-473d3f4c3559%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

jPOS - Users mailing list
In reply to this post by Rama Gullapalli
On 24/08/16 01:20, Rama Gullapalli wrote:
> until few days ago after a recent RedHat patch
What was patched?

Unpatch it?

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage.  Please support jPOS, contact: [hidden email]

Join us in IRC at http://webchat.freenode.net/?channels=jpos

You received this message because you are subscribed to the  "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/1e8c37b2-881a-44a7-69f3-5dc9f2975e26%40talktalk.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [jpos-users] QMUX Request Timeouts after 20 Seconds Even though Response is received!

Rama Gullapalli

1. Yes , we have a commercial JPOS license.
2. No other connections are reporting unhandled response message.
3. We are using default space for all the client channel adaptors defined in the system.

Thanks!

On Monday, August 29, 2016 at 3:08:50 AM UTC-7, Mark Salter wrote:
On 24/08/16 01:20, Rama Gullapalli wrote:
> until few days ago after a recent RedHat patch
What was patched?

Unpatch it?

--
Mark

--
--
jPOS is licensed under AGPL - free for community usage for your open-source project. Licenses are also available for commercial usage. Please support jPOS, contact: [hidden email]
 
Join us in IRC at http://webchat.freenode.net/?channels=jpos
 
You received this message because you are subscribed to the "jPOS Users" group.
Please see http://jpos.org/wiki/JPOS_Mailing_List_Readme_first
To post to this group, send email to [hidden email]
To unsubscribe, send email to [hidden email]
For more options, visit this group at http://groups.google.com/group/jpos-users
---
You received this message because you are subscribed to the Google Groups "jPOS Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/df23ecc2-b4ea-4e5d-b9f4-c37f454b6f97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
12
Loading...