[JBoss JIRA] Created: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
11:18 a.m.
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.3.GA
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Tim Fox
Fix For: 1.4.3.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:57 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1546:
-----------------------------------------
Hi, JBM 1.4.3.GA is released specifically for JBOSS AS 5.1. Can you check the version of
your JBoss AS? Thanks.
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.3.GA
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Tim Fox
Fix For: 1.4.3.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:59 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
devarshi pathak commented on JBMESSAGING-1546:
----------------------------------------------
Hi
This is what I see when i run this command
Looks like my Jboss Version is JBoss 4.3.0.GA_CP02
/usr/local/jboss/bin/run.sh --version | grep CP
JBoss 4.3.0.GA_CP02 (build: SVNTag=JBPAPP_4_3_0_GA_CP02 date=200808051050)
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.3.GA
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Tim Fox
Fix For: 1.4.3.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1546:
-----------------------------------------
So I think you are using the EAP version, this version has JBM 1.4.0.SP3-CP03 built in.
You should be able to see something similar to the following line have appeared in your
console:
09:46:16,709 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP03 server [0] started
Supposed you are using the correct version as indicated above, the problem seems your
network has something blocking your application. Did you check the connection or firewall
settings?
If the network is OK. can you please upload the piece of code by which you are looking for
the connection factory? Also if you have an EAP support account, you can also raise the
issue through the support channel, I believe you will get more help on this, and fast. :)
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Tim Fox
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 p.m.
New subject: [JBoss JIRA] Updated: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao updated JBMESSAGING-1546:
------------------------------------
Fix Version/s: 1.4.0.SP3.CP08
1.4.4.GA
(was: 1.4.3.GA)
Affects Version/s: 1.4.0.SP3_CP03
(was: 1.4.3.GA)
Assignee: Howard Gao (was: Tim Fox)
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:12 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
devarshi pathak commented on JBMESSAGING-1546:
----------------------------------------------
Hi
I am new to Jboss, sorry
will you please tell me where do i find it
and what should be in connection factory. Please let me know the path and file name in
Jboss 4.3
1. file path
2. file name
3. what should be the content.
if i put that will it resolve my issue?
thanks
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 p.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1546:
-----------------------------------------
Check those files in your jboss home, like
/usr/local/jboss/default/deploy/jboss-messaging.sar/, these files are very important. The
connection-factories.xml is the one you configure connection factories.
If you don't know the files before, I recommend you read the doc first, it will answer
many of your questions and let you start with JBM quickly. Also, if you have questions
like that, first you can put them to the forum:
http://www.jboss.org/index.html?module=bb&op=viewforum&f=238
A lot of people there will share and help. Thanks.
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:59 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
devarshi pathak commented on JBMESSAGING-1546:
----------------------------------------------
Thanks You !
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:23 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
devarshi pathak commented on JBMESSAGING-1546:
----------------------------------------------
does it related to the error that i am getting? how do i fix or re-configure this
connection-factories-service.xml file to resolve my issue?
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:22 a.m.
New subject: [JBoss JIRA] Commented: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1546:
-----------------------------------------
Hi Devarshi,
I'm closing this jira as I think the better place to answer your questions is the
user's forum. Please go there and we can continue if you like.
Howard
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 a.m.
New subject: [JBoss JIRA] Closed: (JBMESSAGING-1546) ERROR [util.JMSFactory] Could not lookup connection factory
[
https://jira.jboss.org/jira/browse/JBMESSAGING-1546?page=com.atlassian.ji...
]
Howard Gao closed JBMESSAGING-1546.
-----------------------------------
Resolution: Rejected
ERROR [util.JMSFactory] Could not lookup connection factory
-----------------------------------------------------------
Key: JBMESSAGING-1546
URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1546
Project: JBoss Messaging
Issue Type: Task
Components: JMS Clustering
Affects Versions: 1.4.0.SP3_CP03
Environment: RedHat Linux
Reporter: devarshi pathak
Assignee: Howard Gao
Fix For: 1.4.0.SP3.CP08, 1.4.4.GA
Getting this error after upgrade from 4.0.3 to 4.3.0 in JMS Cluster environment.
2009-03-12 13:27:45,304 ERROR [com.xxx.util.JMSFactory] Could not lookup connection
factory
javax.naming.CommunicationException: Receive timed out [Root exception is
java.net.SocketTimeoutException: Receive timed out]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5766
days inactive
5780
days old
10 comments
2 participants
participants (2)
-
devarshi pathak (JIRA) -
Howard Gao (JIRA)