April 2008 - jboss-user - Jboss List Archives

[EJB 3.0] - Re: Problem with EJB call EJB

by jaikiran

Are you sure there were no errors during deployment? anonymous wrote : @EJB(beanName = "org.jboss.ws.hello.HelloBean") | private HelloBean h; This should have been: @EJB(beanName = "HelloBean") | private HelloBean h; or even this should work: @EJB | private HelloBean h; And by the way, you don't need the ejb-jar.xml for any of this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146999#4146999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146999

17 years, 12 months

1
0
0 / 0

[JBoss jBPM] - Re: problem with jbpm3.2 and jboss SA 4.2.1GA

by salaboy21

anonymous wrote : | -- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS | State: NOTYETINSTALLED | Depends On Me: | jboss.ejb:service=EJBTimerService,persistencePolicy=database | jboss:service=KeyGeneratorFactory,type=HiLo | jboss.mq:service=StateManager | jboss.mq:service=PersistenceManager It very simple.. you need to configure a default Data Source. You can do that by creating an xml named *-ds.xml (* means any name) in your deploy directory. You also can obtain samples of DataSource Configuration in the jboss_install_dir/docs/jca/examples.. or something similar... Hope it helps.. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146998#4146998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146998

17 years, 12 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Re: Seam 2.0: EntityManager must be access within a transact

by jaikiran

That's not the file where the transaction timeout is configured. There's a jboss-service.xml file in %JBOSS_HOME%\server\default\conf folder which contains this: |  | <mbean code="com.arjuna.ats.jbossatx.jta.TransactionManagerService" | name="jboss:service=TransactionManager"> | <attribute name="TransactionTimeout">300</attribute> | <attribute name="ObjectStoreDir">${jboss.server.data.dir}/tx-object-store</attribute> | </mbean> 300 is the default value. Change it to an appropriate value. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146996#4146996 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146996

17 years, 12 months

1
0
0 / 0

[EJB/JBoss] - Re: Accessing Applet behind NAT firewall [EJB application]

by SandeepDJboss

Guys - now i am completely using RMI over HTTP solution implemented using the following URL http://wiki.jboss.org/wiki/EJBOverHTTPWithLegacyInvoker But the problem still persists The problem is that I want to have diffrent customers using my application. If they connect directly to the IP then ther is no problem. But some of them do Client Side NAT. It is very important for me to have Client Connect URL to be determind/ Changed at the Applet VM level. I want to change this value depending upon what client is connecting whether NAT or direct. Hardcoding the InvokerURL does not work for me as I have mulitple clients connect to it. I need a solution which will allow me to form the URL's from the client end using NAT IP at the runtime; if this can be done the same JBOSS instance can be used by all clients - thos who NAT and those who do not NAT as well. Please suggest a way out if you have come across similar issue where you need to support many clients out of the same domain and some of them NAT the IP's on client side. Any help on this will be very much appreciated !! Thank you Sandeep View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146995#4146995 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146995

17 years, 12 months

1
0
0 / 0

[JNDI/Naming/Network] - Re: Accessing Applet behind NAT firewall [EJB application]

by SandeepDJboss

Guys - now i am completely using RMI over HTTP solution implemented using the following URL http://wiki.jboss.org/wiki/EJBOverHTTPWithLegacyInvoker But the problem still persists The problem is that I want to have diffrent customers using my application. If they connect directly to the IP then ther is no problem. But some of them do Client Side NAT. It is very important for me to have Client Connect URL to be determind/ Changed at the Applet VM level. I want to change this value depending upon what client is connecting whether NAT or direct. Hardcoding the InvokerURL does not work for me as I have mulitple clients connect to it. I need a solution which will allow me to form the URL's from the client end using NAT IP at the runtime; if this can be done the same JBOSS instance can be used by all clients - thos who NAT and those who do not NAT as well. Please suggest a way out if you have come across similar issue where you need to support many clients out of the same domain and some of them NAT the IP's on client side. Any help on this will be very much appreciated !! Thank you Sandeep View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146994#4146994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146994

17 years, 12 months

1
0
0 / 0

[JNDI/Naming/Network] - RMI over HTTP -- Invoker URL at runtime ?

by SandeepDJboss

Hi Everyone, I have used http-invkoer.sar to use the RMI over HTTP for EJB communication. http://wiki.jboss.org/wiki/EJBOverHTTPWithLegacyInvoker The problem is that I want to have diffrent customers using my application. If they connect directly to the IP then ther is no problem. But some of them do Client Side NAT. It is very important for me to have Client Connect URL to be determind/ Changed at the Applet VM level. I want to change this value depending upon what client is connecting whether NAT or direct. Hardcoding the InvokerURL does not work for me as I have mulitple clients connect to it. I need a solution which will allow me to form the URL's from the client end using NAT IP at the runtime; if this can be done the same JBOSS instance can be used by all clients - thos who NAT and those who do not NAT as well. Please suggest a way out if you have come across similar issue where you need to support many clients out of the same domain and some of them NAT the IP's on client side. Any help on this will be very much appreciated !! Thank you Sandeep View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146993#4146993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146993

17 years, 12 months

1
0
0 / 0

[JBoss Messaging] - Re: ConnectionNotifier is produced: java.lang.NullPointerExc

by timfox

The stack trace shows this is in jboss remoting. Have you tried asking in the jboss remoting forum? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146991#4146991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146991

17 years, 12 months

1
0
0 / 0

[JBoss Messaging] - Re: JBoss Messaging JMS connection usage leading to problems

by timfox

"harish43" wrote : I am not certain whether we are using the JCA connection pool. Assuming that we are not using the connection pool is there a fix for the issue mentioned by Kevin Conner? It's slightly worrying that you don't know if your using the JCA managed conection factory or not, since this will have a big effect on your applications operation. See the wiki for more details on how to configure this. If you want to know when a particular issues was fixed please look in JIRA - all the information is there. :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146990#4146990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146990

17 years, 12 months

1
0
0 / 0

[EJB 3.0] - Re: serialVersionUID mismatch using remote client and jboss-

by Thomaskm

Could anyone please paste all the required jar files for running ejb3 project on jboss server and invoking the same using a java client? Thanks and Regards, Thomas View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146989#4146989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146989

17 years, 12 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - help : WARN [UDP] failed to join /224.0.0.75:7500

by j-root

Dearz , i'm facing a problem when i startup jboss 4.2.2 over RHEL , i'm getting this warnings : 11:34:24,351 INFO [Server] Starting JBoss (MX MicroKernel)... 11:34:24,352 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) 11:34:24,354 INFO [Server] Home Dir: /JB/jboss-4.2.2 11:34:24,354 INFO [Server] Home URL: file:/JB/jboss-4.2.2/ 11:34:24,355 INFO [Server] Patch URL: null 11:34:24,355 INFO [Server] Server Name: all 11:34:24,355 INFO [Server] Server Home Dir: /JB/jboss-4.2.2/server/all 11:34:24,356 INFO [Server] Server Home URL: file:/JB/jboss-4.2.2/server/all/ 11:34:24,356 INFO [Server] Server Log Dir: /JB/jboss-4.2.2/server/all/log 11:34:24,356 INFO [Server] Server Temp Dir: /JB/jboss-4.2.2/server/all/tmp 11:34:24,357 INFO [Server] Root Deployment Filename: jboss-service.xml 11:34:24,742 INFO [ServerInfo] Java version: 1.6.0_06,Sun Microsystems Inc. 11:34:24,743 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b22,Sun Microsystems Inc. 11:34:24,743 INFO [ServerInfo] OS-System: Linux 2.6.9-5.ELsmp,i386 11:34:25,354 INFO [Server] Core system initialized 11:34:28,624 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/ 11:34:28,627 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml 11:34:29,227 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc. 11:34:29,227 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer 11:34:29,496 INFO [TransactionManagerService] Starting recovery manager 11:34:29,605 INFO [TransactionManagerService] Recovery manager started 11:34:29,605 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference 11:34:33,278 INFO [EJB3Deployer] Starting java:comp multiplexer 11:34:34,435 WARN [UDP] failed to join /224.0.0.75:7500 on eth0: java.net.SocketException: Address already in use 11:34:34,436 WARN [UDP] failed to join /224.0.0.75:7500 on bond0: java.net.SocketException: Address already in use FYI , configured network bonding on the nw interfaces i googled but no solution :-( . ur help is appreciated . j . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146988#4146988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146988

17 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user April 2008