| Author |
Message
|
| moi3 |
 Posted: Mon Apr 25, 2005 10:01 am Post subject: Receive Invalid file using MQ on mainframe |
 |
|
Novice
Joined: 05 Apr 2005
Posts: 24
|
I'm sending a xml file from HP-UX to mainframe using MQ 5.3 and JMS. The receiving queue on mainframe received the xml file alright, but in addition to it, it also received some invalid files. We don't know where these invalid files came from. We created a brand new queue to make sure it's the only one that we're using and it still received some invalid files along with the good ones. This is a sample of what an invalid file looks like. Just a bunch of weird characters. Do you have any ideas?
SMQ1 20050422134407 ?_ `/_/ / ?_/> | (
SMQ1 20050422134407 ?_ `/_/ / ?__?> _ / > ( / | ¦ Q
SMQ1 20050422134407 % / ! /> / /> / ?> ` < / /
SMQ1 20050422134407 ¦/ / % / ¦a . , $z L
SMQ1 20050422134407
SMQ1 20050422134407
SMQ1 20050422134407 |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Apr 25, 2005 4:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you sure you are clearing all the memory properly.
Sure there is no occurs clause in play ?
Looks to me like memory access to a non initialized memory area....
Not an MQ problem but an application problem....
Enjoy  |
|
| Back to top |
|
|
| moi3 |
| Posted: Mon Apr 25, 2005 4:43 pm Post subject: |
|
|
Novice
Joined: 05 Apr 2005
Posts: 24
|
Here's my jms code. I did close the connection. Do you see anything else that I need to do?
try {
InitialContext ctx = InitialContextFactory.getInitialContext();
QueueConnectionFactory factory = (QueueConnectionFactory) ctx.lookup("jms/myQCF");
con = factory.createQueueConnection();
QueueSession session = con.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ctx.lookup("jms/myQ");
QueueSender sender = session.createSender(queue);
TextMessage message = session.createTextMessage(textMessage);
sender.send(message);
} catch (Exception e) {
e.printStackTrace();
} finally {
try {
if (con != null) {
con.close();
}
} catch (JMSException jmse) {
jmse.printStackTrace();
}
} |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Apr 25, 2005 4:51 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| It's the mainframe code you need to look at. |
|
| Back to top |
|
|
| moi3 |
| Posted: Mon May 02, 2005 2:15 pm Post subject: |
|
|
Novice
Joined: 05 Apr 2005
Posts: 24
|
| I checked with the person who worked on the mainframe and he said everything is fine on his end. He's not using MQ 5.3 but only 5.X. We receive an invalid message every hour now instead of once a day before ever since we deploy it into production. Any ideas? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon May 02, 2005 2:46 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it exactly once an hour?
Then there is a scheduled job somewhere that is sending this.
MQ does not spontaneously produce or corrupt messages.
Someone in your organization has written code that is responsible for these messages.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
