[JBoss Messaging] - Re: Configuring a non-JBoss JMS Provider (Weblogic)
by jferraro＠ihc.com
Try it again...
Config scripts
jboss-service.xml
------------------------
foresight
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://foresight-prod.co.ihc.com:7001
java.naming.security.authentication=none
javax.naming.InitialContext
jms-ds.xml
--------------
ForeSightJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapter
foresight
foresight
<!-- The Foresight JMS …
[View More]connection factory -->
<no-tx-connection-factory>
<jndi-name>ForeSightJms</jndi-name>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/ForeSightJMSProvider</config-property>
<max-pool-size>20</max-pool-size>
</no-tx-connection-factory>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168049#4168049
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168049
[View Less]
16 years, 7 months
[JBoss Messaging] - Re: Configuring a non-JBoss JMS Provider (Weblogic)
by jferraro＠ihc.com
Config Scripts:
jboss-service.xml
-------------------------
foresight
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://foresight-prod.co.ihc.com:7001
java.naming.security.authentication=none
javax.naming.InitialContext
jms-ds.xml
----------------
ForeSightJMSProvider
org.jboss.jms.jndi.JNDIProviderAdapter
foresight
foresight
<!-- The Foresight JMS connection factory -->
…
[View More] <no-tx-connection-factory>
<jndi-name>ForeSightJms</jndi-name>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
<config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/ForeSightJMSProvider</config-property>
<max-pool-size>20</max-pool-size>
</no-tx-connection-factory>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168048#4168048
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168048
[View Less]
16 years, 7 months
[JBoss Messaging] - Configuring a non-JBoss JMS Provider (Weblogic)
by jferraro＠ihc.com
I am trying to configure access to a remote JMS Provider - that being Weblogic. It is a weblogic topic that I am trying to gain access too. I am using an EJB3 MDB in JBoss as a subscriber to the remote Weblogic topic. I think my problem is around the QueueFactoryRef: definition as I am trying to subscribe to a topic and it has no queue definition. I get the following error message (below) at JBoss startup. Under the error message are my configuration scripts. Anyone have any ideas ?
adapter.…
[View More]jms.inflow.JmsActivationSpec(a)a50a00(ra=org.jboss.resource.adapter.jms.Jm
sResourceAdapter@1fc7299 destination=foresight/ForeSightJMSTextReportsTopic isTo
pic=true tx=true durable=false reconnect=10 provider=java:/ForeSightJMSProvider
user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=60000 useDLQ=true D
LQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiNam
e=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: Object at 'foresight' in context {java.naming.fact
ory.initial=org.jnp.interfaces.NamingContextFactory, java.naming.factory.url.pkg
s=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces} is no
t an instance of [class=javax.jms.QueueConnectionFactory classloader=org.jboss.m
x.loading.UnifiedClassLoader3@11ff436{ url=null ,addedOrder=2} interfaces={inter
face=javax.jms.ConnectionFactory classloader=org.jboss.mx.loading.UnifiedClassLo
ader3@11ff436{ url=null ,addedOrder=2}}] object class is [class=$Proxy13 classlo
ader=org.jboss.mx.loading.UnifiedClassLoader3@11ff436{ url=null ,addedOrder=2} i
nterfaces={interface=javax.naming.Context classloader=null}]
at org.jboss.util.naming.Util.checkObject(Util.java:329)
at org.jboss.util.naming.Util.lookup(Util.java:216)
Config Scripts:
foresight
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://foresight-prod.co.ihc.com:7001
java.naming.security.authentication=none
javax.naming.InitialContext
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168047#4168047
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168047
[View Less]
16 years, 7 months
[Beginners Corner] - Re: JBoss API usage examples
by danishkhan
Hi Peter,
I developed the application and used the method that you provided, and it worked perfectly on my local machine. However when I am trying to run it on server, it is giving me an exception. I did change the url from local host to server ip in jndi.properties file. I also matched the jboss-service.xml file to see the contents of <mbean code="org.jboss.naming.NamingService"
and they are same for my machine and the server.
So can you please think of any other reason why its still …
[View More]unable to connect and throwing the following exception?
Thanks,
-Danish.
/******* EXCEPTION START *************/
javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:11
18)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1197)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:515)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:508)
at javax.naming.InitialContext.lookup(InitialContext.java:363)
at JBossStateReader.isMonitorItemFine(JBossStateReader.java:46)
at JBossStateReader.run(JBossStateReader.java:26)
at java.lang.Thread.run(Thread.java:810)
Caused by: java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java
:181)
at java.net.DatagramSocket.receive(DatagramSocket.java:724)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:10
88)
/******** EXCEPTION END **************/
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168046#4168046
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168046
[View Less]
16 years, 7 months
Delivery Failure
by Postmaster
---------------------------------------------------------------------------------
The message you sent to famocdepanel.com/trash50534137 was rejected because it would exceed the quota for the mailbox.
The subject of the message follows:
Subject: =?windows-1251?B?Mu7uOOMuLSDu7/Lo7Ojn4Pbo/yDn4PDv6+Dy7fv1IO3g6+7j7uIg8A==?=
---------------------------------------------------------------------------------
16 years, 7 months
