strange problems viewing and deleting messages

amir

Hi,

Using MEC-AS2 1.0 build 23

I've got a strange problem with the AS2 server. I am using it with the following JVM on Linux RHEL4.

java version "1.6.0_01"
Java(TM) SE Runtime Environment (build 1.6.0_01-b06)
Java HotSpot(TM) Server VM (build 1.6.0_01-b06, mixed mode)

Problem 1

I cant delete any of the messages in the GUI. I click on the delete button, click on "yes" in the confirmation dialog box and then it goes away and nothing happens, the files remain in the GUI and they are still there in _rawincoming.

Problem 2

I cant view message detail of any files. When I double click the message I see an exception in the xterm. I have attached the log file for you to examine.

Problem 3 (maybe not an error)

Lots of exceptions firing on exit from HSQLDB (see attachment)

AttachmentSize
log.txt6.56 KB


crownedgrouse
crownedgrouse's picture
May be right access ?

Verify first it is not a right access problem.
in particular a umask on file creation.
if files are 555 or 550 or 500, they can be created and read, but not deleted !
Same things for databases files.



amir
pretty sure they are not

AHA, our trading partner has sent a new message to us and I think i see the problem.

The first message(s) had no message id, so mec-as2 cant do anything to them, the message i got this morning had a message id and i can double click that without issue. Seems there is a case where you can get messages and mec-as2 cant deal with them and gets confused.

You can replicate this by posting a file to the server using something like curl with the following

curl -X POST -H "Content-Type: application/xml" -H "AS2-From: " -H "AS-To: " -d@test.txt "https:///mec_as2/HttpReceiver"

This will get the file to the server, but it will remain in _rawincoming and you wont be able to examine the contents, or delete the message(s).



amir
it wasnt a permissions issue

see above :-)



heller
heller's picture
amir, we had this issue

amir,

we had this issue already (http://mec-community.com/node/273) and I thought I fixed it but it seems still to exist. There is a system maintenance process that will try to delete old messages after a 30 days period (could be configured in the server preferences). That means that in 30 days you will receive a periodic message that the message without the message id could not be deleted.

But thank you for the command, I will reproduce it and hopefully this is fixed in the next release.

Regards
Heller



amir
thanks for all the help, to

thanks for all the help, to everyone that responded. Btw I noticed my curl example was stripped of "<" and ">" commands.

its supposed to look like this


curl -X POST -H "Content-Type: application/xml" -H "AS2-From: PUTAS2SenderIdHere" -H "AS-To: PutReceiverIdHere" -d@test.txt "https://PutAS2ServerHere/mec_as2/HttpReceiver"

Looking forward to the bugfix, in the meantime how can i clear the entries from the database?. Its annoying seeing them in the console and the other thread omits the details of the process :-(



heller
heller's picture
amir, is deleting the

amir,

is deleting the database an option because it is not productive yet?

Regards
Heller



amir
Yes I can delete the

Yes I can delete the database.

What worries me is that at some point this will be production so that wont be an option :)



heller
heller's picture
amir, I see. You could just

amir,

I see. You could just connect to the underlaying database, it's a hsqldb.

I would recommend Squirrel SQL.

Please perform the following steps after installation and start:

*If there is no hsql driver in the list, goto "Drivers-New Driver" and add the file hsqldb.jar found in jlib
*Add an alias: driver "hsqldb server", URL "jdbc:hsqldb:hsql://localhost:3333/as2db", User "sa", Password none
*Establish the connection (m-e-c as2 must run), the table where the message references are stored in is called "messages"
*Check for messages with no message id: "SELECT * FROM messages WHERE messageid IS NULL"
*Delete these entries: "DELETE FROM messages WHERE messageid IS NULL"

Regards
Heller



heller
heller's picture
amir, thanks for your curl

amir,

thanks for your curl command. I fixed this issue, it should no longer occur in the next release.

Regards
Heller



amir
Great, looking forward to

Great, looking forward to the new build.



crownedgrouse
crownedgrouse's picture
In addition to this

A partner sent me a message with a new MDN URL, but he didn't test that we can access to this URL.
The MDN was stored under name error13038.raw.

I didn't see any manual retry for MDN, so I finally do also a curl command to send this MDN to the partner, when he cleared the firewall rules for me.



amir
Just to let everyone know

Just to let everyone know that the Squirrel SQL that heller describes works great to clear the tables.

Thanks Heller!




© 1999-2008 mendelson-e-commerce GmbH. All right reserved.