[JBoss Messaging Development] - Queue\Topic not bound
by Sudhakar Pandey
Sudhakar Pandey [http://community.jboss.org/people/spandey1982] created the discussion
"Queue\Topic not bound"
To view the discussion, visit: http://community.jboss.org/message/553862#553862
--------------------------------------------------------------
We are trying to replace default HSQL with Oracle. After resolving couple of issues, we have replaced HSQL with Oracle. However, now exception is coming post core startup while binding MDB to Queue/Topic. Everything seems to be correct.
<EXCEPTION>
+15:12:00,113 ERROR [JmsActivation] Unable to reconnect mailto:org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4ba03f(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@9f629c org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@4ba03f(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)9f629c destination=topic/Tran+
+sactionCategorisationTopic destinationType=javax.jms.Topic tx=true durable=true reconnect=10 provider=DefaultJMSProvider user=mqm pass=<not shown> maxMessages=1 minSession=1 maxSession=15 keepAlive=30+
+000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=10)+
+javax.naming.NameNotFoundException: TransactionCategorisationTopic not bound+
+ at org.jnp.server.NamingServer.getBinding(NamingServer.java:771)+
+ at org.jnp.server.NamingServer.getBinding(NamingServer.java:779)+
+ at org.jnp.server.NamingServer.getObject(NamingServer.java:785)+
+ at org.jnp.server.NamingServer.lookup(NamingServer.java:443)+
+ at org.jnp.server.NamingServer.lookup(NamingServer.java:399)+
+ at sun.reflect.GeneratedMethodAccessor233.invoke(Unknown Source)+
+ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
+ at java.lang.reflect.Method.invoke(Method.java:597)+
+ at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)+
+ at sun.rmi.transport.Transport$1.run(Transport.java:159)+
+ at java.security.AccessController.doPrivileged(Native Method)+
+ at sun.rmi.transport.Transport.serviceCall(Transport.java:155)+
+ at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)+
+ at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)+
+ at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)+
+ at java.lang.Thread.run(Thread.java:619)+
+ at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)+
+ at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)+
+ at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)+
+ at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)+
+ at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726)+
+ at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)+
+ at javax.naming.InitialContext.lookup(InitialContext.java:392)+
+ at org.jboss.util.naming.Util.lookup(Util.java:222)+
+ at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464)+
+ at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352)+
+ at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:292)+
+ at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:733)+
+ at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)+
+ at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)+
+ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)+
</EXCEPTION>
I am getting above exception for all the queues and topics.
*Changes done:*
1. Copy oracle-persistence-service.xml file from <JBoss 5.1 installation>\docs\examples\jms
2. Removed <depends optional-attribute-name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</depends> from oracle-persisence-service.xml file. Bean not defined. After commenting the line issue got resolved.
3. We have defined our own JMSProvider for all our Queues and Topics. I have declared the JMSProvider information in a new xml file and placed it under a new folder "JMS" under deploy folder. JMSProvider declaration is attached herewith.
I am not sure what exact details I should provide to get the appropriate answer. So please let me know in case you need any other detail.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/553862#553862]
Start a new discussion in JBoss Messaging Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month
Re: [jboss-dev-forums] [JBoss Microcontainer Development] - Benchmarking classloaders
by Kabir Khan
Kabir Khan [http://community.jboss.org/people/kabir.khan%40jboss.com] replied to the discussion
"Benchmarking classloaders"
To view the discussion, visit: http://community.jboss.org/message/553790#553790
--------------------------------------------------------------
I have got some basic benchmarks working. Instead of using AS classes, I am now generating my own using Chiba's ClassFileWriter to have better control over what exists where. The classes are only generated if the target/generated-classes and target/generated-jars directories don't exist already. You tell it how many jars to create, how many packages per jar and how many classes per package. If you change these numbers, be sure to delete the target/generated-* directories. So, if 2 is selected for each of these it then creates the following jars:
interface0.jar:
org.jboss.test.interface0.pkg0.Interface0.class
org.jboss.test.interface0.pkg0.Interface1.class
org.jboss.test.interface0.pkg1.Interface0.class
org.jboss.test.interface0.pkg1.Interface1.class
interface1.jar:
org.jboss.test.interface1.pkg0.Interface0.class
org.jboss.test.interface1.pkg0.Interface1.class
org.jboss.test.interface1.pkg1.Interface0.class
org.jboss.test.interface1.pkg1.Interface1.class
abstract0.jar:
org.jboss.test.abstract0.pkg0.Abstract0.class
org.jboss.test.abstract0.pkg0.Abstract1.class
org.jboss.test.abstract0.pkg1.Abstract0.class
org.jboss.test.abstract0.pkg1.Abstract1.class
abstract1.jar:
org.jboss.test.abstract1.pkg0.Abstract0.class
org.jboss.test.abstract1.pkg0.Abstract1.class
org.jboss.test.abstract1.pkg1.Abstract0.class
org.jboss.test.abstract1.pkg1.Abstract1.class
impl0.jar:
org.jboss.test.impl0.pkg0.Impl0.class
org.jboss.test.impl0.pkg0.Impl1.class
org.jboss.test.impl0.pkg1.Impl0.class
org.jboss.test.impl0.pkg1.Impl1.class
impl1.jar:
org.jboss.test.impl1.pkg0.Impl0.class
org.jboss.test.impl1.pkg0.Impl1.class
org.jboss.test.impl1.pkg1.Impl0.class
org.jboss.test.impl1.pkg1.Impl1.class
An example of the expected inheritance hierarchies is:
class org.jboss.test.impl1.pkg1.Impl1 extends org.jboss.test.abstract1.pkg1.Abstract1{}
class org.jboss.test.abstract1.pkg1.Abstract1 implements org.jboss.test.interface1.pkg1.Interface1{}
I then create a classloader for each jar, with different classloading rules per test and try to load the Impl classes from the implx.jar loaders, which triggers searches for the superclasses/interfaces in the other classloaders.
Ales, can you take a look at how I am setting up the VFSClassLoaderFactories? I do this in the TestCase classes. The thing I found strange was that for the Module test I had to specify the packages as a capability as well as the module, but I'm not that familiar with how this works so maybe that's how it should be.
Running this a few times on a set of 50 jars with 10 packages per jar and 10 classes per package, I get the following results.:
Import/Export packages:
Deploying the VFSClassLoaderFactories and creating the loaders: 1862ms 1693ms 1847ms 1725ms 1706ms
Loading the classes: 5008ms 4883ms 4744ms 4893ms 5012ms
Export/ImportAll:
Deploying the VFSClassLoaderFactories and creating the loaders: 1657ms 1627ms 1659ms 1720ms 1573ms
Loading the classes: 4858ms 4693ms 4796ms 4714ms 4899ms
Import/Export module:
Deploying the VFSClassLoaderFactories and creating the loaders: 1785ms 1736ms 1766ms 1819ms 1901ms
Loading the classes: 4992ms 5609ms 5510ms 4991ms 5626ms
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/553790#553790]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 1 month