That's not really a HornetQ question.. It's more an admin question.. I wouldn't so share the same journal between Linux and Windows anyways.. you will probably use SMB???
We usually recommend against NFS on Linux, NFS on Samba? Whoa.. be careful man!
Anyway.. I don't see how I could help you here.. you should look for an admin guy on how to setup your network configuration properly on sharing Disks. (if you still want to pursue that)
Thank you for your answer.
But i still think it is a HornetQ problem.
I use Samba and setup a sharing folder will full authority.
I can create a file and modify it and delete it at both two machines.
But when i start the HornetQ, the journal file can not write to the Samba sharing folder.
Clebert is right, it will be an admin problem, all HornetQ does is create a new file.
Sorry, the information I mentioned was wrong.
HornetQ can create the journal file to the sharing folder , but can not read it .(HornetQ will throw out the exception that *can not open the file *)
The detailed error message :
Server [HonetQServerImpl] Failure in initailistaion
HornetQException [errorCode = 205 message = Cannot open file]
sounds like an administration issue to me
I also found that there is tmp file generated to the shared folder...
* [main] 22-Jun 19:13:13,552 INFO [AIOFileLockNodeManager] Live Server Obtained live lock
* [main] 22-Jun 19:13:13,652 WARNING [JournalImpl] Temporary files were left unnatended after a crash on journal directory, deleting invalid files now
* [main] 22-Jun 19:13:13,652 WARNING [JournalImpl] Deleting unnatended file hornetq-data-1.hq.tmp
* [main] 22-Jun 19:13:13,663 WARNING [HornetQServerImpl] Critical IO Error, shutting down the server. code=6, message=Can't open file
* [main] 22-Jun 19:13:13,663 SEVERE [HornetQServerImpl] Failure in initialisation
HornetQException[errorCode=205 message=Can't open file]
If iles cant be created/accessed or read then its an administration issue, try writing your own test to see
The generated journal file can be read / access / deleted from the OS manually, but just the journal file can not open by the HornetQ. So I think it is not an administration issue.
we do nothing special just create files and read/write to them, if there is an issue its almost always an admin issue, writeyour own java code to see what happens.
Based on your advise , i create a test program.
Create the file to the samba sharing folder and then delete it.
Both create and delete process were successful.
I cannot explain why this matter is just happen in HornetQ ? Can you explain it for me ?
did you do this from 2 different processes like a live/backup would and also try reading and writing to it.
All I can suggest is you debug the HQ source to see what th eunderlying exception is.
I managed to implement NSF to realize the shared folder.
But still have problem in samba.
Thank you for your advice.