8:58 a.m.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig) method,
but that seems to fail when executing the JMS detection on the original thread (that is
the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:58 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom updated JBAS-8895:
--------------------------------------
Attachment: jmstest.war
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:40 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
You'll have to setup a dependency to make sure that your topic is deployed before the
servlet is being initialized. See this for an example
http://community.jboss.org/message/582546#582546
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom commented on JBAS-8895:
-------------------------------------------
That's seem to require EJBs (org.jboss.ejb3.annotation.Depends). Is there a solution
to get around this problem without using EJBs or MDBs?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom edited comment on JBAS-8895 at 2/18/11 10:14 AM:
---------------------------------------------------------------------
That seems to require EJBs (org.jboss.ejb3.annotation.Depends). Is there a solution to get
around this problem without using EJBs or MDBs?
was (Author: oosie):
That's seem to require EJBs (org.jboss.ejb3.annotation.Depends). Is there a
solution to get around this problem without using EJBs or MDBs?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:01 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
See this example then http://community.jboss.org/message/588344#588344
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom commented on JBAS-8895:
-------------------------------------------
I created a jboss-web.xml with the following contents:
<jboss-web>
<depends>org.hornetq:module=JMS,name=test,type=Topic</depends>
</jboss-web>
After deploying and starting the JBoss AS 6.0.0.Final server, I get the following:
18:04:48,942 ERROR [ProfileServiceBootstrap] Failed to load profile::
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.web.deployment:war=/jmstest" is missing the following
dependencies:
Dependency "org.hornetq:module=JMS,name=test,type=Topic" (should be in state
"Create", but is actually in state "** NOT FOUND Depends on
'org.hornetq:module=JMS,name=test,type=Topic' **")
DEPLOYMENTS IN ERROR:
Deployment "org.hornetq:module=JMS,name=test,type=Topic" is in error due to
the following reason(s): ** NOT FOUND Depends on
'org.hornetq:module=JMS,name=test,type=Topic' **
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228)
[:2.2.0.GA]
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905)
[:2.2.0.GA]
at
org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87)
[:6.0.0.Final]
at
org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107)
[:0.2.2]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135)
[:6.0.0.Final]
at
org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56)
[:6.0.0.Final]
at
org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827)
[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at
org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417)
[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
at java.lang.Thread.run(Thread.java:680) [:1.6.0_22]
Am I missing something (else) in my jboss-web.xml?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:05 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Cédric ALCISIADI commented on JBAS-8895:
----------------------------------------
I have the same problem and I did a lot of tests.
I tried to add some "depends" in my jboss-web.xml and it didn't change
anything. I finally don't think this is the real problem because my initialisation
code finds the ConnectionFactory, the topic, and successes in creating the connection but
can't create any subscriber.
I tried to move this code in :
1. ServletContextListener.contextInitialized : doesn't work
2. MyOwnFilter.init : doesn't work
3. MyServlet.init : doesn't work if called because of "load-on-startup" in
web.wml but works if called because of the first call to the servlet. ( different context
I suppose )
If I desactivate the security in HornetQ : security-disabled=true in hornet-configuration
: everything works fine.
So my question is : is there something missing relative to the security in the deployer
thread and is there something to do to plug it in ?
I expect it helps.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:25 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Jack, your depends value is missing double quotes around the value for the name attribute.
Like I said, in this thread http://community.jboss.org/message/588344#588344 the double
quotes are necessary.
Try this:
<jboss-web>
<depends>org.hornetq:module=JMS,name="test",type=Topic</depends>
</jboss-web>
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:34 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Cédric ALCISIADI commented on JBAS-8895:
----------------------------------------
Hello,
I dug a bit deeper to solve the problem and I've finally found that Security
initialisation done by
org.jboss.as.integration.hornetq.deployers.HornetQCoreConfigRealDeployer is executed very
lately in the boot process. Before the JMS queues and topics are here but not fully
configured.
To solve the problem, I moved my webapp under deploy/deploy.last to delay its deployment
and it works like a charm.
I expect it will be the same for others who share my problem.
Best regards.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom commented on JBAS-8895:
-------------------------------------------
Sorry for my late reply. However, now I'm back on this again. I tried the double
quotes, but still get a similar error:
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "jboss.web.deployment:war=/jmstest" is missing the following
dependencies:
Dependency "org.hornetq:module=JMS,name="test",type=Topic" (should
be in state "Create", but is actually in state "** NOT FOUND Depends on
'org.hornetq:module=JMS,name="test",type=Topic' **")
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
henk de boer commented on JBAS-8895:
------------------------------------
I discussed the exact same issue here: http://community.jboss.org/message/590747
It seems like depending on the queue or topic doesn't work. I got the dependency right
and at first it seems to work, but later I found out this was due to the arbitrary timing
of initialization. A few restarts later, without having any code changed, I got the same
error again.
The exact same JMS code always works when the app is fully started (e.g. if I execute it
by pressing a button on some page in my app).
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Clebert Suconic commented on JBAS-8895:
---------------------------------------
I believe this is fixed on 2.2 (upcoming version) and on the integration at EAP (that will
be merged into AS7)
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:33 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom commented on JBAS-8895:
-------------------------------------------
What is the scheduled release for JBoss AS 7? (I see that only an alpha of 7 has been
released so far...) Are there no plans to include this fix in a JBoss AS 6 release?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:41 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
henk de boer commented on JBAS-8895:
------------------------------------
My guess would be that AS 7 is still some time away. The first upcoming release is 6.1. It
would be great if this fix could make it into that release.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Benoit Heinrich commented on JBAS-8895:
---------------------------------------
Jason, I'm not sure I understand your last post correctly.
Are you saying that JBoss AS6 is end-of-life?
I mean it's just been released with a 6.0.0.Final and I would assume that a 6.0.1.xxx
will come at some point with bug fixes.
Are you saying that for a production environment we should then use AS7? I'm already
struggling with a move from AS4 to AS6 :s
I hope I'm wrong, but can you please let me know what to do here...
Cheers,
/Benoit
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: No Release
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
See this http://community.jboss.org/thread/164407
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: No Release
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 a.m.
New subject: [JBoss JIRA] Reopened: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai reopened JBAS-8895:
--------------------------------
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: No Release
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:21 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai updated JBAS-8895:
-------------------------------
Fix Version/s: 6.1.0
(was: No Release)
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
AS6 trunk (r111114) has been upgraded to use 2.2.2.Final of HornetQ. From what I hear from
the HornetQ team, this version is expected to fix the dependency issues. Please give the
latest snapshot of JBoss AS a try (follow this thread
http://community.jboss.org/thread/161386) and let us know if it fixes your issue.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:32 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Benoit Heinrich commented on JBAS-8895:
---------------------------------------
I tried with latest snapshot from this morning and I still have the same problem.
I've also tried defining the dependencies on my MDB and it didn't work.
I'm not sure what else to do.
Thanks for the help.
Cheers,
/Benoit
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:40 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Did you pick up the snapshot from here
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/? What's the job
number and what's the revision number of the server?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:51 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Benoit Heinrich commented on JBAS-8895:
---------------------------------------
I took it from
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/last...
I assume this points to the latest and greatest ;)
I don't see the revision number from the logs, but I can see this:
[AbstractServer] Starting: JBossAS [6.1.0.SNAPSHOT "Neo"]
...
[HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started
So maybe it's not yet using 2.2.2.Final of HornetQ.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:18 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Looks like you picked up a snapshot before the latest one with this fix was published by
that hudson job. Download the snapshot from this run
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/34/ or later runs to
get the fix.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:32 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Benoit Heinrich commented on JBAS-8895:
---------------------------------------
The link doesn't work for me, the hudson.qa.jboss.com doesn't resolve.
I've also tried with
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/34/ but then I get a 404
:s
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Benoit Heinrich edited comment on JBAS-8895 at 4/7/11 7:33 AM:
---------------------------------------------------------------
I took it from
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/lastSuc...
I assume this points to the latest and greatest ;)
I don't see the revision number from the logs, but I can see this:
[AbstractServer] Starting: JBossAS [6.1.0.SNAPSHOT "Neo"]
...
[HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started
So maybe it's not yet using 2.2.2.Final of HornetQ.
was (Author: benoit.heinrich):
I took it from
http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/last...
I assume this points to the latest and greatest ;)
I don't see the revision number from the logs, but I can see this:
[AbstractServer] Starting: JBossAS [6.1.0.SNAPSHOT "Neo"]
...
[HornetQServerImpl] HornetQ Server version 2.1.2.Final (Colmeia, 120) started
So maybe it's not yet using 2.2.2.Final of HornetQ.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:42 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Ah yes, hudson.qa.jboss is internal instance. Let's wait for the
http://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-6.1.x/ job to publish this new
snapshot (later tonight I guess).
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:30 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Shelly McGowan commented on JBAS-8895:
--------------------------------------
I can see it's still waiting in the publishing queue. I'll check into this.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:07 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Vojtech Juranek commented on JBAS-8895:
---------------------------------------
Hi, we had some problems with publishing builds. Now it's fixed but there are a lot of
jobs in the queue waiting for publishing. I expect this build to be published in next 4-5
hours. I'm sorry for complications...
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Frank Langelage commented on JBAS-8895:
---------------------------------------
I checked out revision 111121
containing
22:45:30,612 INFO [HornetQServerImpl] HornetQ Server version 2.2.2.Final
(super-hornetq-fighter, 122) [f89ad33c-6157-11e0-a6cf-0003ba36314c] started.
I do not see the connect errors on startup anymore.
Thanks for fixing this.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Thanks for verifying this, Frank. I'm marking this issue as resolved now.
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:51 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai resolved JBAS-8895.
--------------------------------
Assignee: jaikiran pai
Resolution: Done
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Assignee: jaikiran pai
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:23 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
Jack van Ooststroom commented on JBAS-8895:
-------------------------------------------
I also tried the snapshot and verified things work now for the stand-alone case. However,
I also wanted to verify the cluster case, as we need to support that as well, but I
encounter the following warning message:
10:09:27,053 WARN [org.hornetq.core.cluster.impl.DiscoveryGroupImpl] There are more than
one servers on the network broadcasting the same node id. You will see this message
exactly once (per node) if a node is restarted, in which case it can be safely ignored.
But if it is logged continuously it means you really do have more than one node on the
same network active concurrently with the same node id. This could occur if you have a
backup node active at the same time as its live node.
nodeID=38438e5b-6bec-11e0-a63d-001a6411d7e1
I understand that the nodeID normally gets generated when first starting a node. I
downloaded the bundle separately on each node and started them individually. It looks
like they both use the same nodeID. I suspect this nodeID
(38438e5b-6bec-11e0-a63d-001a6411d7e1) to be part of the jboss-6.1.x.zip archive, as on
each machine I download this bundle to, the nodeID is always the same. This prevents me
to confirm the fix in a cluster environment. Is there a way I can enforce the
regeneration of the nodeID?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Assignee: jaikiran pai
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8895) Can't connect to JMS before server has started up completely
[
https://issues.jboss.org/browse/JBAS-8895?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on JBAS-8895:
------------------------------------
Jack, I haven't checked the details, but can you try deleting the
JBOSS_HOME/server/<servername>/data folder before starting the servers for the first
time?
Can't connect to JMS before server has started up completely
------------------------------------------------------------
Key: JBAS-8895
URL: https://issues.jboss.org/browse/JBAS-8895
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.Final
Environment: JBoss 6.0.0.Final with HornetQ configured
Reporter: Jack van Ooststroom
Assignee: jaikiran pai
Fix For: 6.1.0
Attachments: jmstest.war
It seems that with JBoss AS 6.0.0.Final I can't connect to JMS before the application
server itself has started up completely. I'm using the InitialContext approach as I
can't use Message Driven Beans in the project.
I created a JMS Topic in [jboss-home]/server/default/deploy/hornetq/hornetq-jms.xml as
follows:
<topic name="MyTopic">
<entry name="/topic/test"/>
</topic>
Next I'm trying to connect to JMS from my JMSServlet's init(ServletConfig)
method, but that seems to fail when executing the JMS detection on the original thread
(that is the thread supplied by the application server) as follows:
Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
I'd prefer not having to specify the user/password, but even if I do it fails in a
similar fashion:
Unable to validate user: guest for check type CREATE_NON_DURABLE_QUEUE for address
jms.topic.MyTopic
When I do the detection of JMS on a seperate thread it eventually seems to work, as long
as the application server started up completely. However, timing is then a bit
undeterministic. When running this test on earlier versions of JBoss AS, namely 5 and 4,
or other application servers the detection seems to succeed on the first try on the
original thread.
Why does JBoss AS 6.0.0.Final behave differently? Is there some configuration I am
missing? Is this a potential bug?
I'll attach my JMS Test application which tries to connect to JMS using 6 different
strategies:
* On original thread
* On original thread after sleep
* On spawned thread with await/signal
* On spawned thread with await/signal after sleep
* On spawned thread without await/signal
* On spawned thread without await/signal after sleep
The source is included in the jmstest.war file.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4881
days inactive
4977
days old
33 comments
9 participants
participants (9)
-
Benoit Heinrich (JIRA) -
Clebert Suconic (JIRA)
-
Cédric ALCISIADI (JIRA)
-
Frank Langelage (JIRA)
-
henk de boer (JIRA)
-
Jack van Ooststroom (JIRA)
-
jaikiran pai (JIRA)
-
Shelly McGowan (JIRA)
-
Vojtech Juranek (JIRA)