-
1. Re: Build HornetQ for fix to HORNETQ-133
timfox Oct 6, 2009 7:55 AM (in response to rnicholson10)Not really sure what you're asking here, but we make no guarantees that TRUNK is stable!
We don't make any guarantees that beta is stable either.
Please see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161188&postdays=0&postorder=asc&start=10
and http://www.jboss.org/community/wiki/HornetQSourceLocation
Did you make sure you completely re-installed everything after building (you can't just overwrite the jars)? -
2. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 9:33 AM (in response to rnicholson10)Hehe, I overwrite the jars and used loads of wishful thinking!!!
Ok, so I'll do a full build and reconfigure. -
3. Re: Build HornetQ for fix to HORNETQ-133
timfox Oct 6, 2009 9:36 AM (in response to rnicholson10)"rnicholson10" wrote:
Hehe, I overwrite the jars and used loads of wishful thinking!!!
Ok, so I'll do a full build and reconfigure.
Yeah, with TRUNK we're changing things around all the time, so the safest thing to do is re-install each time.
Even then no guarantees, although *hopefully* you should be ok ;)
Basically, the only requirement with TRUNK is the test suite runs. -
4. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 1:49 PM (in response to rnicholson10)May I ask a question that I'm sure you asked all the time???
When do you think the next release will be? Whether it be a beta, candidate release etc. I don't see any dates on the JIRA Roadmap. -
5. Re: Build HornetQ for fix to HORNETQ-133
clebert.suconic Oct 6, 2009 2:03 PM (in response to rnicholson10)I always answer this:
- Not a promise, but we are trying between 4 to 6 weeks.
I have been answering this since last week.. so... 4 to 5 now hopefully.
But again.. that's a tentative. -
6. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 2:16 PM (in response to rnicholson10)4 to 5 weeks is not bad, even a tentative 4 to 5 weeks!
I'll start crossing my fingers now... -
7. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 4:12 PM (in response to rnicholson10)Do you tag nightly builds?
Is it possible to check out a build that is slightly more stable? -
8. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 4:30 PM (in response to rnicholson10)The reason I ask is I get the following error when doing a full reinstall of the build I checked out yesterday. This occurs when MDBs attempt to access the queue.
The same as the Beta5 I only modified 2 files, hornetq-configuration.xml and hornetq-jms.xml.
Or does anyone have a quick fix for what's happening here?2009-10-06 20:34:51,229 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@2db068f5(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@24e337cd destination=queue/phaseQueueFromEngine destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) javax.naming.NameNotFoundException: XAConnectionFactory 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.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.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:131) at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83) at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:413) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:351) 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:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)
Or should I just do daily checkouts until I get one that works? -
9. Re: Build HornetQ for fix to HORNETQ-133
timfox Oct 6, 2009 4:33 PM (in response to rnicholson10)Your're not using the HornetQ resource adaptor, that can be seen in the trace (btw there was another thread about this the other day).
Andy recently made some changes.
I guess you can't have re-installed from clean into a clean JBoss AS properly, otherwise you'd be using the correct RA. -
10. Re: Build HornetQ for fix to HORNETQ-133
timfox Oct 6, 2009 4:34 PM (in response to rnicholson10)If you want to use TRUNK, you must build the distro from TRUNK and use that to install into a fresh JBoss AS.
You can't copy and paste files piece-meal or try and tweak an existing config. -
11. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 6, 2009 5:12 PM (in response to rnicholson10)Ah, what I did was use a fresh default directory copied into JBoss AS and then ran the install.
My local wiki is getting loads of new data today!!!
I will try again tomorrow with a completely fresh JBoss AS and see where I get too.
Rockin... -
12. Re: Build HornetQ for fix to HORNETQ-133
ataylor Oct 7, 2009 3:45 AM (in response to rnicholson10)After you have built the distro, take a look at the app server integration chapter in the user manual. basically you will need to adjust your MDB deployment descriptor or add an annotation.
-
13. Re: Build HornetQ for fix to HORNETQ-133
rnicholson10 Oct 7, 2009 6:47 AM (in response to rnicholson10)I'm guessing this is the: @ResourceAdapter("hornetq-ra.rar") annotation for MDB's.
Whenever I send messages I don't use ejbs. Do I need to somehow specify this when not in an ejb? Or is a simple JNDI lookup using the an InitialContext sufficient in this case? -
14. Re: Build HornetQ for fix to HORNETQ-133
ataylor Oct 7, 2009 8:23 AM (in response to rnicholson10)Yesm just use the jndi name specified in the jms-ds.xml file