voyent
port to 1.7.1 get icefacesContextEventTopic not bound  XML
Forum Index -> General Help
Author Message
akearns

Joined: 22/Nov/2006 00:00:00
Messages: 10
Offline


I took an existing application that uses AJAX push and updated my icefaces jars to user 1.7.1, previously I used 1.7.0 jars.

On deployment to jboss-4.2.3.GA I get the exception:
com.icesoft.net.messaging.MessageServiceException:
javax.naming.NameNotFoundException:
icefacesContextEventTopic not bound

What steps are needed to go from 1.7.0 to 1.7.1?
Another post referenced creating the topics:
http://www.icefaces.org/JForum/posts/list/9140.page

Full Exception follows:

Code:
 
 17:19:08,171 INFO  [JMSAdapter] Server Info: JBossWeb/2.0.1.GA
 17:19:08,171 INFO  [JMSAdapter] Messaging Properties: jboss_ha.properties, jboss.properties
 17:19:08,218 INFO  [JMSAdapter] Trying JMS Environment:
         java.naming.provider.url = localhost:1100
         java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
         java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces
 
 17:19:14,359 ERROR [JMSAdapter] Failed JMS Environment: Could not obtain connection to any of these urls: localhost:1100 and discovery failed with error: javax.
 naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
 17:19:14,359 INFO  [JMSAdapter] Trying JMS Environment:
         java.naming.provider.url = localhost:1099
         java.naming.factory.initial = org.jnp.interfaces.NamingContextFactory
         java.naming.factory.url.pkgs = org.jboss.naming:org.jnp.interfaces
 
 17:19:14,421 WARN  [MainServlet] Did not start Ajax Push JMS services:
 com.icesoft.net.messaging.MessageServiceException: javax.naming.NameNotFoundException: icefacesContextEventTopic not bound
         at com.icesoft.net.messaging.jms.JMSAdapter.subscribe(JMSAdapter.java:378)
         at com.icesoft.net.messaging.MessageServiceClient.subscribe(MessageServiceClient.java:791)
         at com.icesoft.net.messaging.MessageServiceClient.subscribe(MessageServiceClient.java:759)
         at com.icesoft.faces.webapp.http.servlet.MainServlet.setUpMessageServiceClient(MainServlet.java:121)
         at com.icesoft.faces.webapp.http.servlet.MainServlet.init(MainServlet.java:66)
         at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
 
 


deryk.sinotte


Joined: 26/Oct/2004 00:00:00
Messages: 1008
Offline


This is a known issue:

http://jira.icefaces.org/browse/ICE-3309

But I believe it should be harmless to the operation of your application. It's mostly doing some dynamic checking to see if JMS is configured properly (even if you are not using JMS).

We've already made some changes to the logging code to make a bit less dire-sounding but we'll probably tone it down even further for 1.7.2.

Deryk Sinotte
Team Lead
ICEsoft Technologies, Inc.
judy.guglielmin

Joined: 20/Feb/2007 00:00:00
Messages: 1396
Offline


This could be due to the fact that you have icefaces-ahs.jar in your deployed application and it hasn't been configured. If you aren't using icefaces-ahs.jar, then ensure that it is not on your server anywhere (this includes the temporary files...you will want to clean them out).
 
Forum Index -> General Help
Go to:   
Powered by JForum 2.1.7ice © JForum Team