[JBoss Messaging] - JMSServerControl.createQueue() fails when there are any page
by jbmuser
Hi,
I am using JMSServerControl.createQueue() to create queues on the fly (programatically) as discussed in http://www.jboss.org/index.html?module=bb&op=viewtopic&t=157444. This works fine and the API creates the Queue or just binds the queue to JNDI if queue already exists. However, this fails as soon as there are any messages paged in the Queue. i.e. If I am trying to use this API for a Queue which already exists and has some messages paged, subsequent calls to this API fails with following Exception. Any help would be highly appreciated.
java.lang.Exception: did not receive reply for message org.jboss.messaging.core.client.impl.ClientMessageImpl@18e613d
| at org.jboss.messaging.core.management.impl.ReplicationOperationInvokerImpl.invoke(ReplicationOperationInvokerImpl.java:115)
| at org.jboss.messaging.core.management.jmx.impl.ReplicationAwareStandardMBeanWrapper.replicationAwareInvoke(ReplicationAwareStandardMBeanWrapper.java:75)
| at org.jboss.messaging.jms.server.management.jmx.impl.ReplicationAwareJMSServerControlWrapper.createQueue(ReplicationAwareJMSServerControlWrapper.java:499)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
| at javax.management.StandardMBean.invoke(StandardMBean.java:323)
| at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
| at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
| at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
| at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
| at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
| at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
| at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
| at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1343)
| at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
| at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
| at sun.rmi.transport.Transport$1.run(Transport.java:153)
| at java.security.AccessController.doPrivileged(Native Method)
| at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
| at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
| at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
| at java.lang.Thread.run(Thread.java:595)
Thanks
Bijith
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247150#4247150
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247150
17 years, 1 month
[Microcontainer] - Re: Injecting a classloader
by jaikiran
"david.lloyd(a)jboss.com" wrote : do nested JARs which are just libraries qualify as deployment units?
|
No, they are not considered deployment units. Although i don't exactly know how such jars are represented or accessed from a deployment unit. Probably they end up as some kind of metadata? Ales?
"david.lloyd(a)jboss.com" wrote :
| And, how can I get access to the DeploymentUnit instance from my deployer?
Through your deployer, you tell the deployer framework about the deployment units you are interested in and the stage when you are interested in:
| public MyDeployer()
| {
| setInput(SomeMetadata.class);
| setStage(POST_CLASSLOADER);
| }
|
The deployer framework is then responsible for passing any such matching deployment units to the deploy(DeploymentUnit du) method of the deployer:
| /**
| * Deploy a deployment
| *
| * @param unit the unit
| * @throws DeploymentException for any error
| */
| void deploy(DeploymentUnit unit) throws DeploymentException;
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247140#4247140
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4247140
17 years, 1 month