One more feature:
When deploying project without topic's configs in JBoss - JBoss tells me, that
it can't find topic "topic/com/mysy."
But, if configs with "topic/com/mysy." are in JBoss "deploy" folder - on
deploying i get a message mentioned in the first post. About
"TOPIC.com/mysyst.
I replaced "jms" folder in 4.0.4 by analog from 4.0.2
And got the same.
Downloading of Jboss-messaging-1.0.1.CR2 have been finished.
Tomorrow will try to solve my trouble using it...
Is here nobody, who was confronted with these difficulties?
View the original post :
http://www.jboss.com/index.
It's not a mistake during deploy...
I think it's differences in JMS providers...
But how can i solve it?
JBoss documentation is silent about it. Or, maybe, i watch it not so closely...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955564#3955564
Reply to th
I've do it.
So, that's what i got^
[CODE]
16:38:12,445 WARN [JMSContainerInvoker] Could not find the topic
destination-jndi-name=topic/com/mysystem/mq/JobInvocationTopic
javax.naming.NameNotFoundException: com not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
I've got a problem during migration to v4.0.4
(There were a lot of problems, but i solved most. But this trouble)
I built project and deployed it.
Immediately, i got the folowing stacktrace:
| 18:49:58,232 WARN [JMSContainerInvoker] JMS provider failure detected for
SchedulerListenerBea
