voyent
AHS and JBoss 4.2  XML
Forum Index -> Async HTTP Server
Author Message
zzzz8

Joined: 07/Dec/2005 00:00:00
Messages: 270
Offline


How should one configure AHS with JBoss 4.2 (e.g. 4.2.2)? Also, how do things change with JBossWeb?
jack.van.ooststroom


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


Hi Lawrence,

There shouldn't be any difference between configuring AHS with JBoss 4.2.x and JBoss 4.0 as mentioned in the documentation of AHS. What is your concern with JBossWeb?

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


Hi there!
I'm trying to configure AHS with JBoss 4.2.2 (no clustering). I made the following steps, according to the documentation:
1. I set up in my application
Code:
<context-param>
     <param-name>com.icesoft.faces.async.server</param-name>
     <param-value>true</param-value>
 </context-param>
 

2. I deployed the async-http-server.war in /server/default/deploy
3. I added the two mbeans to the jbossmq-destinations-service.xml
Code:
<mbean code="org.jboss.mq.server.jmx.Topic" name="jboss.mq.destination:service=Topic,name=icefaces.contextEventTopic">
     <depends optional-attribute-name="DestinationManager">
         jboss.mq:service=DestinationManager
     </depends>
     <depends optional-attribute-name="SecurityManager">
         jboss.mq:service=SecurityManager
     </depends>
     <attribute name="SecurityConf">
         <security>
             <role name="guest" read="true" write="true" create="true"/>
         </security>
     </attribute>
 </mbean>
 <mbean code="org.jboss.mq.server.jmx.Topic" name="jboss.mq.destination:service=Topic,name=icefaces.responseTopic">
     <depends optional-attribute-name="DestinationManager">
         jboss.mq:service=DestinationManager
     </depends>
     <depends optional-attribute-name="SecurityManager">
         jboss.mq:service=SecurityManager
     </depends>
     <attribute name="SecurityConf">
         <security>
             <role name="guest" read="true" write="true" create="true"/>
         </security>
     </attribute>
 </mbean>

Now, when the server starts I get some nasty
12:12:38,321 FATAL [MessagingContextEventPublisher] Failed to subscribe to topic: icefaces.contextEventTopic
com.icesoft.net.messaging.MessageServiceException: javax.naming.NameNotFoundException: icefaces.contextEventTopic not bound
at com.icesoft.net.messaging.jms.JMSAdapter.subscribe(JMSAdapter.java:310)
at com.icesoft.net.messaging.MessageServiceClient.subscribe(MessageServiceClient.java:791) 

exceptions in the stacktrace and the application is not working.
I tried with and without
Code:
	<context-param>
 		<param-name>
 			com.icesoft.util.net.messaging.properties
 		</param-name>
 		<param-value>jboss.properties</param-value>
 	</context-param>

in my web.xml, but to no avail.
Any help available?

Thanx,
Eduard Korenschi
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


After defining
<context-param>
<param-name>com.icesoft.net.messaging.properties</param-name>
<param-value>jboss.properties</param-value>
</context-param> 

in my application's web.xml I get the following stack trace when starting jboss:
15:57:21,954 INFO [TomcatDeployer] deploy, ctxPath=/async-http-server, warUrl=.../tmp/deploy/tmp46834async-http-server-exp.war/
15:57:22,391 INFO [D2DViewHandler]
ICEsoft Technologies, Inc.
ICEfaces x.x.x
Build number: x
Revision: x

15:57:22,548 INFO [JMSAdapter] 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

15:57:22,610 INFO [ThreadFactory] New thread: MessageReceiver Thread [1]
15:57:22,610 INFO [JMSSubscriberConnection$MessageReceiver] MessageReceiver [message_type = 'BufferedContextEvents' OR message_type = 'ContextEvent'] started.
15:57:22,626 INFO [ThreadFactory] New thread: MessageReceiver Thread [2]
15:57:22,626 INFO [JMSSubscriberConnection$MessageReceiver] MessageReceiver [message_type = 'Announcement' OR message_type = 'Purge' OR message_type = 'UpdatedViews' AND (destination_nodeAddress IS NULL OR destination_nodeAddress = '192.168.33.104')] started.
15:57:22,673 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
15:57:22,985 INFO [TomcatDeployer] deploy, ctxPath=/otpprojectreloaded, warUrl=.../deploy/otpprojectreloaded.war/
15:57:23,251 INFO [JMSAdapter] 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

15:57:23,266 FATAL [MessagingContextEventPublisher] Failed to subscribe to topic: icefaces.contextEventTopic
com.icesoft.net.messaging.MessageServiceException: javax.naming.NameNotFoundException: icefaces.contextEventTopic not bound
at com.icesoft.net.messaging.jms.JMSAdapter.subscribe(JMSAdapter.java:310)
at com.icesoft.net.messaging.MessageServiceClient.subscribe(MessageServiceClient.java:791)
at com.icesoft.net.messaging.MessageServiceClient.subscribe(MessageServiceClient.java:759)
at com.icesoft.faces.util.event.servlet.MessagingContextEventPublisher.setUpMessageServiceClient(MessagingContextEventPublisher.java:146)
at com.icesoft.faces.util.event.servlet.MessagingContextEventPublisher.publish(MessagingContextEventPublisher.java:86)
at com.icesoft.faces.util.event.servlet.ContextEventRepeater.contextInitialized(ContextEventRepeater.java:180)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.apache.catalina.core.StandardContext.init(StandardContext.java:5312)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:301)
at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104)
at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
at org.jboss.web.WebModule.startModule(WebModule.java:83)
at org.jboss.web.WebModule.startService(WebModule.java:61)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy44.start(Unknown Source)
at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy45.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Unknown Source)
Caused by: javax.naming.NameNotFoundException: icefaces.contextEventTopic not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source)
at sun.rmi.transport.Transport$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)
at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)
at sun.rmi.server.UnicastRef.invoke(Unknown Source)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.icesoft.net.messaging.jms.JMSAdapter.lookUpTopic(JMSAdapter.java:413)
at com.icesoft.net.messaging.jms.JMSAdapter.subscribe(JMSAdapter.java:303)
... 140 more 

So it looks like the ahs starts ok, but my application doesn't find those mbeans defined in jms.

Eduard
jack.van.ooststroom


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


Hi Eduard,

Just to verify, are you using ICEfaces and AHS from the trunk?

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


yup, december 06 build

Eduard
jack.van.ooststroom


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


We recently moved and refactored the AHS into the ICEfaces core product. We are currently in the process of testing it in various deployments and configurations, and updating the documentation to reflect these changes. Basically, it is not stable yet. I would like to suggest to either use the 1.6.1a version of AHS, which is tested with ICEfaces 1.6.x versions, or wait for the ICEfaces 1.7-DR#3 release.

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
edykory


Joined: 27/Nov/2006 00:00:00
Messages: 332
Offline


Ok, thanx, I think I'll just wait for the 1.7DR#3 release. Is there any release schedule available, or it's more like it's ready when it's ready?

Eduard
ken.fyten

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


Eduard,

We're shooting to have it out prior to xmas.

Regards,
Ken

Ken Fyten
VP Product Development
ICEsoft Technologies, Inc.
shauii

Joined: 29/Oct/2007 00:00:00
Messages: 15
Offline


Hi,

Is there an update on this issue? I'm having the same error as Eduard. I'm trying with Icefaces 1.7 RC1 release, JBoss 4.2.2GA and Apache HTTP Server 2.2. I have followed the Icefaces Dev Guide in setting up the AHS.

Here's the stacktrace:
-------------------
Code:
19:08:28,003 INFO  [TomcatDeployer] deploy, ctxPath=/async-http-server, warUrl=.../tmp/deploy/tmp5489async-http-server-exp.war/
 19:08:28,299 INFO  [JMSAdapter] 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
 
 19:08:28,548 FATAL [MessageService] 
 
 Failed to subscribe to topic: icefacesContextEventTopic
     Exception message: javax.naming.NameNotFoundException: icefacesContextEventTopic not bound
     Exception cause: javax.naming.NameNotFoundException: icefacesContextEventTopic 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.
 
 19:08:28,565 FATAL [MessageService] 
 
 Failed to subscribe to topic: icefacesResponseTopic
     Exception message: javax.naming.NameNotFoundException: icefacesResponseTopic not bound
     Exception cause: javax.naming.NameNotFoundException: icefacesResponseTopic 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.
 
 19:08:28,570 INFO  [AsyncHttpServlet] Starting the Asynchronous HTTP Server in servlet-mode...

-----------------------------

Thanks for the help.
jack.van.ooststroom


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


Hi,

It looks like the JMS Topics aren't configured correctly on your JBoss AS. Depending on how you start up your server either edit your [jboss-home]/server/default/deploy/jms/jbossmq-destinations-service.xml or [jboss-home]/server/default/all/deploy-hasingleton/jms/jbossmq-destinations.servive.xml by adding the following snippet (I usually insert it right before the defined testTopic):

Code:
   <mbean code="org.jboss.mq.server.jmx.Topic"
          name="jboss.mq.destination:service=Topic,name=icefacesContextEventTopic">
     <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
     <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
     <attribute name="SecurityConf">
       <security>
         <role name="guest" read="true" write="true"/>
         <role name="publisher" read="true" write="true" create="false"/>
         <role name="durpublisher" read="true" write="true" create="true"/>
       </security>
     </attribute>
   </mbean>
 
   <mbean code="org.jboss.mq.server.jmx.Topic"
          name="jboss.mq.destination:service=Topic,name=icefacesResponseEventTopic">
     <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
     <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
     <attribute name="SecurityConf">
       <security>
         <role name="guest" read="true" write="true"/>
         <role name="publisher" read="true" write="true" create="false"/>
         <role name="durpublisher" read="true" write="true" create="true"/>
       </security>
     </attribute>
   </mbean>

Please note that starting up the JBoss AS in minimal does not give you JMS functionality.

I hope this helps.

Regards,

Jack van Ooststroom
Senior Developer
ICEsoft Technologies, Inc.
[Email]
shauii

Joined: 29/Oct/2007 00:00:00
Messages: 15
Offline


Hi Jack,

Thanks for the reply. I have placed the configuration on both files. icefacesContextEventTopic is ok, but icefacesResponseTopic is not.

Code:
11:52:53,617 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
 11:52:53,947 INFO  [TomcatDeployer] deploy, ctxPath=/async-http-server, warUrl=.../tmp/deploy/tmp15277async-http-server-exp.war/
 11:52:54,205 INFO  [JMSAdapter] 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
 
 11:52:54,579 INFO  [ThreadFactory] New thread: MessageReceiver Thread [1]
 11:52:54,589 INFO  [JMSSubscriberConnection$MessageReceiver] MessageReceiver [message_type = 'BufferedContextEvents' OR message_type = 'ContextEvent'] started.
 11:52:54,600 FATAL [MessageService] 
 
 Failed to subscribe to topic: icefacesResponseTopic
     Exception message: javax.naming.NameNotFoundException: icefacesResponseTopic not bound
     Exception cause: javax.naming.NameNotFoundException: icefacesResponseTopic 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.
 
 11:52:54,606 INFO  [AsyncHttpServlet] Starting the Asynchronous HTTP Server in servlet-mode...


Thanks again.

Sharon
shauii

Joined: 29/Oct/2007 00:00:00
Messages: 15
Offline


Hi,

Changed the Code:
name=icefacesResponseEventTopic 
to Code:
name=icefacesResponseTopic
. It's working great now.

Thanks!

Sharon
 
Forum Index -> Async HTTP Server
Go to:   
Powered by JForum 2.1.7ice © JForum Team