SpyJMSException, FileNotFoundException in JBoss3.0.0Beta2 on

[johnmul]

Hi,

I'm trying to deploy an MDB on beta2.
I have a SLSB client sending a message to queue/testQueue which my MBD should read. However, on the send a 'SpyJMSException' exception is thrown. I believe it is due to a semi-colon being present in the file name -

java.io.FileNotFoundException: C:\app_servers\jboss-3.0.0beta2\server\default\db\jbossmq\file\QUEUE.
testQueue\ID:102-10183476038731 (The filename, directory name, or volume label syntax is incorrect)

as obviously this would present a problem to the Windows OS.

So my question is, does anyone have a fix/workaround/anything for this problem?

thanks in advance
John

The stack trace is;

-------------
11:20:03,863 DEBUG [EmailDispatcherImpl] start sendEmail [{body=hello world, fromAddress=testuser@em
use-tech.com, subject=msg from test user, toAddress=[e-mail]}]
11:20:03,883 WARN [OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not write to the tranaction log.
at org.jboss.mq.pm.file.MessageLog.throwJMSException(MessageLog.java:250)
at org.jboss.mq.pm.file.MessageLog.add(MessageLog.java:131)
at org.jboss.mq.pm.file.PersistenceManager.add(PersistenceManager.java:417)
at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:47)
at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:111)
at org.jboss.mq.server.JMSServer.addMessage(JMSServer.java:439)
at org.jboss.mq.server.JMSServer.addMessage(JMSServer.java:417)
at org.jboss.mq.server.JMSServerInvokerSupport.addMessage(JMSServerInvokerSupport.java:127)
at org.jboss.mq.security.ServerSecurityInvoker.addMessage(ServerSecurityInvoker.java:155)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:232)
at java.lang.Thread.run(Thread.java:484)
linked exception is:
java.io.FileNotFoundException: C:\app_servers\jboss-3.0.0beta2\server\default\db\jbossmq\file\QUEUE.
testQueue\ID:102-10183476038731 (The filename, directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:102)
at java.io.FileOutputStream.(FileOutputStream.java:62)
at java.io.FileOutputStream.(FileOutputStream.java:132)
at org.jboss.mq.pm.file.MessageLog.writeMessageToFile(MessageLog.java:226)
at org.jboss.mq.pm.file.MessageLog.add(MessageLog.java:127)
at org.jboss.mq.pm.file.PersistenceManager.add(PersistenceManager.java:417)
at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:47)
at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:111)
at org.jboss.mq.server.JMSServer.addMessage(JMSServer.java:439)
at org.jboss.mq.server.JMSServer.addMessage(JMSServer.java:417)
at org.jboss.mq.server.JMSServerInvokerSupport.addMessage(JMSServerInvokerSupport.java:127)
at org.jboss.mq.security.ServerSecurityInvoker.addMessage(ServerSecurityInvoker.java:155)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:232)
at java.lang.Thread.run(Thread.java:484)
11:20:04,024 ERROR [EmailDispatcherImpl] sendEmail has generated an JMSException:
org.jboss.mq.SpyJMSException: Could not write to the tranaction log.
<<no stack trace available>>

[lqd107]

this is a known bug and has been fixed. get a newer version from CVS or wait for the next jboss 3.0 beta binary to appear.

[hchirino]

You may want to try using the new JDBC persistence manager in the CVS, it has no naming restrictions on queue names.