| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem in TCP/IP Node |
View previous topic :: View next topic |
| Author |
Message
|
| mona |
 Posted: Thu Mar 15, 2012 12:09 am Post subject: Problem in TCP/IP Node |
 |
|
Novice
Joined: 14 Mar 2012
Posts: 19
|
Hi.
I'm using WMB v7.0.3
I want Sent Data From POS to WMB.
POS===>TCPIP Server Input ====>MQ Output
after send Message (data = NOT NULL) from POS, one Message Genereate in MQ Output ,But
Data length = 0
message data = null
why?? |
|
| Back to top |
|
 |
| MrSmith |
| Posted: Thu Mar 15, 2012 12:56 am Post subject: |
|
|
Master
Joined: 20 Mar 2008
Posts: 215
|
There is not enough information there and you would find that you will get more help if you post a trace, having of course worked through the trace to see if you can not resolve this yourself
Run usertrace first and if you can not see the problem then post the relevant contents of the trace on here.
Thx
_________________
-------- *
“Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read.” |
|
| Back to top |
|
|
| mona |
| Posted: Fri Mar 16, 2012 8:57 pm Post subject: |
|
|
Novice
Joined: 14 Mar 2012
Posts: 19
|
I'm sorry,I'm very tried, but doesn't work.
-----------------------------------------------
data of send to WMB
00 87 60 00 03 01 03 08 00 20 20 01 00 00 80 00
02 99 00 00 29 30 77 01 03 39 39 39 39 30 30 30
33 01 00 13 42 53 84 F8 AD FD D8 57 8C 54 7A 4E
18 47 2F AA 3B BE 70 1D 84 80 A1 A4 17 9E 0B 84
59 6E DF DC AE D4 60 8C 04 D1 BB 1E 1B B4 82 4B
23 5F 1C 18 52 9C 18 C0 9E 6B 45 C2 B1 DF E1 0E
F2 54 FE 1D 75 9D A0 43 E7 A3 A5 6A 03 51 02 D0
FD 56 81 B8 81 F3 32 BD 56 1E 3E 43 8F 9E DA 25
F0 AC 2C C6 B6 65 D6
----------------------------------------------
config TCPIP Server Input : connection details -->localhost:1413 (other config =default)
----------------------------------------------
Error:
1-( MB7BROKER.ny ) Timeout occurred on connection (Hostname ''localhost'', Port ''1413'', Id ''ae47c6:1361fe6290c:-7fd2'') while waiting for all the data required to form a record. The timeout period was ''60'' and the last data received was ''BD 56 1E 3E 43 8F 9E DA 25 F0 AC 2C C6 B6 65 D6 ''.
A TCP/IP node attempted to read a record from an input stream, but the time limit was reached before the full record was received. The timeout period is measured from when the first byte of data has arrived until the last byte of data has arrived. The timeout period is not reset until the full record has been received.
Check that the whole record was sent in the specified length of time. Review the end application to make sure it is sending full records, and, if it is, increase the timeout period to a value that is sufficient to allow all the data to arrive.
2- ( MB7BROKER.ny ) Exception condition detected on input node 'TCP_IPFlow.TCPIP Server Input'.
The input node 'TCP_IPFlow.TCPIP Server Input' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages. |
|
| Back to top |
|
|
| mona |
| Posted: Fri Mar 16, 2012 10:18 pm Post subject: |
|
|
Novice
Joined: 14 Mar 2012
Posts: 19
|
and after timeout :
TCPIP Input Server -------Failur/in---->MQ Output_1 (create message with data)
TCPIP Input Server -------open/in---->MQ Output_2 (create message without data) |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Mar 16, 2012 10:23 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Have you looked at how the Sample Flows that use TCPIP are configured?
Leaving the TCPIPServer node to use its defaults is not going to work.
For example, both the sender and receiver have to know that the 'Terminator' is.
TCP/IP is a data stream. There has to be some way for the two ends of the stream to know when they have reaced the end of the data to be sent and then at the other end, when they have received the end of the data.
Back in the days of Telex, you had a mechanism that used STX (start of Text) and ETX (end of Text) characters.
TCPIP is no different. Try configuring the terminator at both ends. You never know, it could be as something as simple as that.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
|
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
