Details
Improvement
Major
Description
When somebody unintentionally adds the icefaces-ahs.jar to a web application archive. It throws a bunch of exceptions when it is deployed and accessed. Exceptions like icefaces.responseTopic not bound and such (because JMS was not configured on the target application server). We should improve this exception report explaining that the icefaces-ahs.jar is included in the archive and that the JMS is not configured correctly. Suggesting that if it was intentionally included the user should refer to the ICEfaces Developer's Guide on how to configure JMS, and that if it was unintentionally included the user should remove it from the archive.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
A follow-up is created: ICE-2541
Show
Jack Van Ooststroom
added a comment - A follow-up is created: ICE-2541
Changed Fix Version to 1.7-Beta 1.
Show
Jack Van Ooststroom
added a comment - Changed Fix Version to 1.7-Beta 1.
The exception reporting is a bit improved in this particular case. Now whenever the icefaces-ahs.jar is included in the deployment, but the JMS is not configured on the application server, the following informative message is displayed in the log:
Failed to subscribe to topic: icefaces.responseTopic
Exception message: javax.naming.NameNotFoundException: icefaces.responseTopic not bound
Exception cause: javax.naming.NameNotFoundException: icefaces.responseTopic not bound
The icefaces-ahs.jar is included in the deployment, but the JMS topics are not
configured correctly on the application server. If you intended to use the
Asynchronous HTTP Server (AHS), please refer to the ICEfaces Developer's Guide
for instructions on how to configure the JMS topics on the application server.
If you did not intend to use AHS, please remove the icefaces-ahs.jar from your
deployment and try again.
Marking this one as FIXED.