Adam Bien's Weblog
Tuesday Jun 10, 2008
How To Get Rid Of: com.sun.messaging.jmq.io.Packet cannot be cast to com.sun.messaging.jms.ra.DirectPacket in Glassfish V2.X
If you are running Glassfish and using JMS (e.g. a Message Driven Bean), you probably saw already the following error in the log files: DirectConsumer:Caught Exception delivering messagecom.sun.messaging.jmq.io.Packet cannot be cast to com.sun.messaging.jms.ra.DirectPacket.
The error is caused by directly embedding the JMS-Host into Glassfish v2 - it can be easily fixed in the admin console:
- Open the admin console: http://localhost:4848
- Select: Configuration -> Java Message Service node in the tree on the left side.
- Change the type from "Embedded" into "Local". The doc says:
"Choose LOCAL (the default for the server-config configuration) to access the JMS service on the local host. The JMS service is started and managed by the Application Server." - Restart Glassfish
Posted at 10:08AM Jun 10, 2008 by Adam Bien in Java EE 5 Architectures And Idioms | Kommentare[2]
[This entry is based on / extends my books: Enterprise Architekturen, Leitfaden fuer effiziente Software-Entwicklung and: Java EE 5 Architekturen, Patterns und Idiome]


