--
--
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: sa...@jpos.org
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 jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@googlegroups.com.
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.
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.
--
--
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: sa...@jpos.org
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 jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@googlegroups.com.
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.
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...@jpos.org> 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: sa...@jpos.org
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 jpos-...@googlegroups.com
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 unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/e111fd65-15ca-438f-b41d-87634acb7a4a%40googlegroups.com.
--
--
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: sa...@jpos.org
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 jpos-...@googlegroups.com
To unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/182f3654-aaec-3621-3375-3d481d98faaf%40talktalk.net.
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.
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.
To unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@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.
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 if1.the port numbers to verify it was on the same channel2.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 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
We have a single channel session…
Could this be related to using the default space for all the client channels that belong to different app modules?
To unsubscribe, send email to jpos-users+unsubscribe@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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/62ae4c8f-8fb2-4065-9fe3-99425df4fef7%40googlegroups.com.
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.
1. Yes , we have a commercial JPOS license.Great. With support?
2. No other connections are reporting unhandled response message.Then your matching process/config is broken/misconfigured.
3. We are using default space for all the client channel adaptors defined in the system.Do you have any name collisions, with different deployed components using a single in/out queue and causing a race condition or conflict?
Are you generating any space queues - are their names unique enough?
--
Mark
23 Feb 2017 11:21:07,778 DEBUG Logger:? - 1155,<null>,com.company.jpos,DEBUG,QMUX : request : Space : tspace:switch1 - <key count='1'>clientsimulator-switch1-adaptor.ready</key>
<key count='1'>clientsimulator-switch1-receive</key>
<key count='1'>clientsimulator-switch1-send.0200000000000810001334327.req</key>
<key count='0'>clientsimulator-switch1-send</key> <keycount>3</keycount> <gcinfo>0,0</gcinfo>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <log realm="channel/10.84.40.23:2172" at="Thu Feb 23 11:21:07 CST 2017.779" lifespan="1ms">
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <send>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <isomsg
23 Feb 2017 11:21:07,779 INFO STDOUT:? - >
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="0" value="0200"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="2" value="xxxxxxxxxxxx0001"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="3" value="310000"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="4" value="000000000000"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="7" value="0223172107"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="11" value="334327"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="12" value="172107"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="13" value="0223"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="14" value="1806"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="15" value="0223"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="17" value="0223"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="18" value="6999"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="19" value="840"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="22" value="012"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="32" value="1100000816 "/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="37" value="110000334327"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="41" value="810001 "/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="42" value=" "/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="43" value="ClientName FLUS"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="49" value="840"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="58" value="10101000211"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <field id="123" value="TDAV2167501 20 w 2nd AveCV0511510"/>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - </isomsg>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - [B@71ede81c
23 Feb 2017 11:21:07,779 INFO STDOUT:? - </send>
23 Feb 2017 11:21:07,779 INFO STDOUT:? - </log>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <log realm="channel/10.84.40.23:2172" at="Thu Feb 23 11:21:07 CST 2017.922" lifespan="372050ms">
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <receive>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <isomsg
23 Feb 2017 11:21:07,923 INFO STDOUT:? - >
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="0" value="0210"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="2" value="530406______0022"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="3" value="310000"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="4" value="000000000000"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="7" value="0223172107"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="11" value="334327"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="12" value="172107"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="13" value="0223"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="15" value="0223"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="18" value="6999"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="22" value="012"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="32" value="1100000816"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="37" value="110000334327"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="39" value="14"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="41" value="810001 "/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="49" value="840"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="58" value="10101000211"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="63" value="E0 DCI "/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="113" value="59236073872"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="123" value="TDAR01S"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - <field id="9999" value="1487870467922"/>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - </isomsg>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - </receive>
23 Feb 2017 11:21:07,923 INFO STDOUT:? - </log>
23 Feb 2017 11:21:07,924 DEBUG Logger:? - 0,<null>,com.company.jpos,DEBUG,QMUX : processUnhandled : Space : tspace:switch1 - <key count='1'>clientsimulator-switch1-adaptor.ready</key>
<key count='1'>clientsimulator-switch1-receive</key>
<key count='1'>clientsimulator-switch1-send.0200000000000810001334327.req</key> <keycount>2</keycount> <gcinfo>0,0</gcinfo>
/******************************* After application thread timesout - 20 seconds (current configuration)
23 Feb 2017 11:21:27,778 DEBUG Logger:? - 1155,<null>,com.company.jpos,DEBUG,QMUX : response : Space : tspace:switch1 - <key count='1'>clientsimulator-switch1-unhandled</key>
<key count='1'>clientsimulator-switch1-adaptor.ready</key>
<key count='1'>clientsimulator-switch1-receive</key> <keycount>2</keycount> <gcinfo>1,0</gcinfo>
/******************************* SUCCESS CASE *************************************************************/
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <log realm="channel/10.84.40.23:2172" at="Thu Feb 23 12:52:28 CST 2017.396">
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <send>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <isomsg
23 Feb 2017 12:52:28,396 INFO STDOUT:? - >
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="0" value="0200"/>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="2" value="530406______0012"/>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="3" value="310000"/>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="4" value="000000000000"/>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="7" value="0223185228"/>
23 Feb 2017 12:52:28,396 INFO STDOUT:? - <field id="11" value="603771"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="12" value="185228"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="13" value="0223"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="14" value="1806"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="15" value="0223"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="17" value="0223"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="18" value="6999"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="19" value="840"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="22" value="012"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="32" value="1100000816 "/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="37" value="110000603771"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="41" value="810001 "/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="42" value=" "/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="43" value="ClientName FLUS"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="49" value="840"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="58" value="10101000211"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - <field id="123" value="TDAV2167501 20 w 2nd AveCV0511222"/>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - </isomsg>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - [B@7db16f1c
23 Feb 2017 12:52:28,397 INFO STDOUT:? - </send>
23 Feb 2017 12:52:28,397 INFO STDOUT:? - </log>
23 Feb 2017 12:52:28,399 DEBUG Logger:? - 860,<null>,com.company.jpos,DEBUG,QMUX : request : Space : tspace:switch1 - <key count='1'>clientsimulator-switch1-adaptor.ready</key>
<key count='1'>clientsimulator-switch1-send.0200000000000810001603771.req</key> <keycount>1</keycount> <gcinfo>0,0</gcinfo>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <log realm="channel/10.84.40.23:2172" at="Thu Feb 23 12:52:41 CST 2017.619" lifespan="292234ms">
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <receive>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <isomsg
23 Feb 2017 12:52:41,619 INFO STDOUT:? - >
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="0" value="0210"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="2" value="530406______0012"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="3" value="312000"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="4" value="000000000000"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="7" value="0223185228"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="11" value="603771"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="12" value="185228"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="13" value="0223"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="15" value="0223"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="18" value="6999"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="22" value="012"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="32" value="1100000816"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="37" value="110000603771"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="38" value="500417"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="39" value="00"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="41" value="810001 "/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="49" value="840"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="58" value="10101000211"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="63" value="E0 DCI "/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="102" value="203012345"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="113" value="59236073872"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="123" value="TDAR01YCR01M"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - <field id="9999" value="1487875961618"/>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - </isomsg>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - </receive>
23 Feb 2017 12:52:41,619 INFO STDOUT:? - </log>
23 Feb 2017 12:52:41,620 DEBUG Logger:? - 860,<null>,com.company.jpos,DEBUG,QMUX : response : Space : tspace:switch1 - <key count='1'>clientsimulator-switch1-adaptor.ready</key> <keycount>0</keycount> <gcinfo>0,0</gcinfo>
For some reason I cannot figure out your response didn't match your request key.
Here is the evidence bolded and underlined.
There is little more I (and I guess the rest of us simple
mortals) can do with the data you provided. Your response is
processed as unhandled as soon as it arrives
Best regards
which fields are you using as key?
--
--
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: sa...@jpos.org
---
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 post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/c2f86aa3-e64a-4804-b6b5-25cc4bb90ba4%40googlegroups.com.
Hi Rama, the only explanation I can find is that the internal space could somehow end pointing to two different instances at input time than at output time.
Can you share your QMUX setup/config file? It seems that you are setting the reuse property to true, I don't know why or how yet but that could be being an issue.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/6389af1e-2efc-4b1e-b412-dd40f320f954%40googlegroups.com.
<channel-adaptor name='clientsimulator-switch1-adaptor'
class="com.company.jpos.ChannelAdaptor" logger="Q2">
<channel class="com.ondot.driver.MyPostChannel" name="client-switch1-channel"
packager="org.jpos.iso.packager.GenericPackager" logger="Q2">
<property name="packager-config" value="switch1.xml" />
</channel>
<in>clientsimulator-switch1-send</in>
<out>clientsimulator-switch1-receive</out>
<reconnect-delay>30000</reconnect-delay>
<ignore-iso-exceptions>yes</ignore-iso-exceptions>
<space>tspace:switch1</space>
</channel-adaptor>
<mux class="com.company.jpos.QMUX" logger="Q2" name="clientsimulator-switch1-mux">
<in>clientsimulator-switch1-receive</in>
<out>clientsimulator-switch1-send</out>
<unhandled>clientsimulator-switch1-unhandled</unhandled>
<space>tspace:switch1</space>
<request-listener class="com.company.jpos.UnhandledMsgDriver" logger="Q2">
<property name="Network" value="SWITCH1" />
<property name="registerId" value="UNHLD" />
</request-listener>
</mux>
> restart the App Server as a work around for now. Tried additional
> logging in QMUX of the space entries before the request is sent and
> after the response is received.
Your processing seems very wrong, a couple of questions...
1) Why is the PAN in the response different from that in the request?
2) Why is is :-
<log> realm="channel/10.84.40.23:2172"at="Thu Feb 23 11:21:07 CST>
2017.922"lifespan="*372050ms*">
> 23Feb201711:21:07,923 INFO STDOUT:?- <receive>
> 23Feb201712:52:41,619 INFO STDOUT:?-<log> realm="channel/10.84.40.23:2172"at="Thu Feb 23 12:52:41 CST> 2017.619"lifespan="*292234ms*">
> 23Feb201712:52:41,619 INFO STDOUT:?- <receive>
That lifespan feels odd.
3) The decline (unknown card I guess) fails and the approval works. you
have any problems parsing all the fields, are you leaving anything from
one response (or send) that is interfering with the next action on the
Channel?
>>All the fields are being parsed.
4) Thus does your Channel precisely match the target?
5) Does the Packager precisely match the target?
6) what does <null> here indicate ? :-
23 Feb 2017 11:21:07,778 DEBUG Logger:? -
1155,<null>,com.company.jpos,DEBUG,QMUX : request : Space :
tspace:switch1 - <key count='1'>clientsimulator-switch1-adaptor.ready</key>
>>"null" indicates Response not being matched to the right Request application thread.
23 Feb 2017 11:21:07,779 INFO STDOUT:? - <log realm="channel/10.84.40.23:2172" at="Thu Feb 23 11:21:07 CST 2017.779" lifespan="1ms">
ReceiveI think the lifespan in the receive log is high because the log event is created when the receive is invocated, which can be long before the message arrives.
Regards
--
--
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: sa...@jpos.org
---
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 post to this group, send email to jpos-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jpos-users/f02addb4-b7a5-4808-9ee2-f7f577d833a3%40googlegroups.com.