July 2008 - jboss-user - Jboss List Archives

[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  <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

15 years, 9 months

1
0
0 / 0

[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  <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

15 years, 9 months

1
0
0 / 0

[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.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

15 years, 9 months

1
0
0 / 0

[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 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

15 years, 9 months

1
0
0 / 0

[Beginners Corner] - Re: Application Error - Resource not Found

by PeterJ

Please post the log messages that deal with deploying the csa app. You do not, by any chance, have a context root set in meta-inf/jboss-web.xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168043#4168043 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168043

15 years, 9 months

1
0
0 / 0

[Tomcat, HTTPD, Servlets & JSP] - Re: Sun One web server JBoss issue serving static contents

by emmitt1219

I have been hearing that mod_jk for Sun One web server (Netscape) is not well supported. Could this problem with serving static contents a known issue? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168042#4168042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168042

15 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: ContextInstance of a non-null ProcessInstance is null

by coolex

I figured out that the rule (defined in the first Node) is triggered before the process instance was created. But this does not happen if I define the rule in the second node. In this case everything works fine. Can I define the process that way that the process-instance will be created before the rule (in the first task is triggered). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168041#4168041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168041

15 years, 9 months

1
0
0 / 0

[EJB 3.0] - Re: NullPointerException in JavaEEComponentHelper with JBoss

by tvanbuskirk

anonymous wrote : I'm getting this exception too. The ear contains a mixture of EJB2 modules and EJB3 ones. Some of the EJB3 beans depend on EJB2 ones (via ejb-local-refs). Could this be what's triggering the bug? I am getting this exception as well. All of mine are EJB3 beans, so I don't think it's a problem of a mixture of EJB2 and EJB3. The beans deploy fine on 4.2.2.GA and 5.0.0.Beta4. Also, if it helps, it seems that all of the EJBs that fail are injecting other EJBs inside the same ear. My EARs that have EJBs that inject EJBs inside different EARs seem to get deployed without problems, though I don't know if I can confirm that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168037#4168037 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168037

15 years, 9 months

1
0
0 / 0

[JBoss jBPM] - Re: ContextInstance of a non-null ProcessInstance is null

by coolex

Maybe the processdefinition will help: | <process-definition xmlns="" name="Ordering"> | | <start-state name="start"> | <transition to="FirstNode" name="firstNode"></transition> | </start-state> | | <task-node name="FirstNode"> | <task name="FirstNode"> | <assignment class="org.jboss.seam.drools.DroolsAssignmentHandler"> | <workingMemoryName>policyPricingWorkingMemory</workingMemoryName> | <assertObjects> | <element>#{actor}</element> | <element>#{processInstance}</element> | <element>#{processManager}</element> | </assertObjects> | </assignment> | </task> | <transition to="SecondNode" name="secondNode"></transition> | </task-node> | ... | </process-definition> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168036#4168036 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168036

15 years, 9 months

1
0
0 / 0

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==?= ---------------------------------------------------------------------------------

15 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2008