May 2009 - jboss-user - Jboss List Archives

[Installation, Configuration & DEPLOYMENT] - Re: Whats the difference in Jboss version 4 and 5?

by jaikiran

There have been a lot of changes to the deployment framework in AS5. Please post more details about the issue that you are running into, including the exact version of the AS and the version of Java and also your application packaging. Please post the relevant exception stacktrace too. While posting logs or xml content or code, please remember to wrap it in a code block by using the Code button in the message editor window. Please use the Preview button to ensure that your post is correctly formatted. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228514#4228514 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228514

16 years, 11 months

1
0
0 / 0

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

by jaikiran

"japase" wrote : Hi, | | After restructuring the application as suggested I could finally deploy it (even the "big" one I've initially started with). | That's good news :) "japase" wrote : | But I have now another, run time, problem - our EJBs access data sources and I get now authorization error when accessing a data source. The same application works on 4.3 (I'm using the same versions of data source definition files and login-config.xml in both versions). | Shall I start a new thread or supply more details here? | Sure, create a new thread in this forum with all the details including any relevant xml files or code and exception stacktraces. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228513#4228513 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228513

16 years, 11 months

1
0
0 / 0

[Security & JAAS/JBoss] - JAAS on remote (standalone) Tomcat with JBoss SEAM - identit

by lbalint

Good morning, I use JBoss AS 5.0.1 and separate Apache Tomcat 6.0.18 with the newest version of JBoss Seam - and now the problem: JBoss Seam uses its own Seam identity - because it's remote EJB calling, I have to use ClientLoginModule to associate principal and credential with tomcat thread ... Can you explain me how is SecurityAssociation propagated to the server side? After seam identity login method calling is LoginContext.login() called to (ClientLoginModule) On the server side is all protected by security domain with non-null unauthenticated prinicpal (anonymous) ... after my first seam login is all set correctly, but after my second login will the right identity missing and authentication is set to anonymous prinicipal even if SecurityAssociation on client side corresponds with a valid user. Very strange behavior. JBoss seam doesn't work correctly with LoginContext - this context should be called in seam identity logout too (it's a bug) Thanks for your answers and ideas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228512#4228512 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228512

16 years, 11 months

1
0
0 / 0

[Beginners Corner] - Re: Cant deply an .ear file into the JBOSS.

by jaikiran

anonymous wrote : :/usr/jboss/jboss-5.0.0.GA/server/default/deploy/application1.ear/webapp1.war/WEB-INF/classes/META-INF/application.xml Looks like you have the application.xml at the wrong place (WEB-INF/classes/META-INF/application.xml). The application.xml should be at .ear/META-INF/application.xml View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228511#4228511 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228511

16 years, 11 months

1
0
0 / 0

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

by japase

Hi, After restructuring the application as suggested I could finally deploy it (even the "big" one I've initially started with). But I have now another, run time, problem - our EJBs access data sources and I get now authorization error when accessing a data source. The same application works on 4.3 (I'm using the same versions of data source definition files and login-config.xml in both versions). Shall I start a new thread or supply more details here? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228510#4228510 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228510

16 years, 11 months

1
0
0 / 0

[EJB 3.0] - Re: EJBTHREE-1800

by jaikiran

"hilmer" wrote : | If there is anything else I can provide you with of information, please ask. | | --Soren | If possible, can you attach this app to EJBTHREE-1800? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228509#4228509 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228509

16 years, 11 months

1
0
0 / 0

[EJB 3.0] - Re: EJBTHREE-1800

by hilmer

Hi Jaikiran A little more info. This is our startup log on 5.1.0 CR1. If it can help you. If there is anything else I can provide you with of information, please ask. --Soren ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /opt/jboss-5.1.0.CR1 JAVA: java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dxb.builder.useUnorderedSequence=true CLASSPATH: /opt/jboss-5.1.0.CR1/bin/run.jar ========================================================================= 09:21:00,832 INFO [ServerImpl] Starting JBoss (Microcontainer)... 09:21:00,832 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904290912) 09:21:00,833 INFO [ServerImpl] Bootstrap URL: null 09:21:00,833 INFO [ServerImpl] Home Dir: /opt/jboss-5.1.0.CR1 09:21:00,833 INFO [ServerImpl] Home URL: file:/opt/jboss-5.1.0.CR1/ 09:21:00,833 INFO [ServerImpl] Library URL: file:/opt/jboss-5.1.0.CR1/lib/ 09:21:00,833 INFO [ServerImpl] Patch URL: null 09:21:00,833 INFO [ServerImpl] Common Base URL: file:/opt/jboss-5.1.0.CR1/common/ 09:21:00,833 INFO [ServerImpl] Common Library URL: file:/opt/jboss-5.1.0.CR1/common/lib/ 09:21:00,834 INFO [ServerImpl] Server Name: ampep 09:21:00,834 INFO [ServerImpl] Server Base Dir: /opt/jboss-5.1.0.CR1/server 09:21:00,834 INFO [ServerImpl] Server Base URL: file:/opt/jboss-5.1.0.CR1/server/ 09:21:00,834 INFO [ServerImpl] Server Config URL: file:/opt/jboss-5.1.0.CR1/server/ampep/conf/ 09:21:00,834 INFO [ServerImpl] Server Home Dir: /opt/jboss-5.1.0.CR1/server/ampep 09:21:00,834 INFO [ServerImpl] Server Home URL: file:/opt/jboss-5.1.0.CR1/server/ampep/ 09:21:00,834 INFO [ServerImpl] Server Data Dir: /opt/jboss-5.1.0.CR1/server/ampep/data 09:21:00,834 INFO [ServerImpl] Server Library URL: file:/opt/jboss-5.1.0.CR1/server/ampep/lib/ 09:21:00,834 INFO [ServerImpl] Server Log Dir: /opt/jboss-5.1.0.CR1/server/ampep/log 09:21:00,834 INFO [ServerImpl] Server Native Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp/native 09:21:00,834 INFO [ServerImpl] Server Temp Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp 09:21:00,834 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp/deploy 09:21:01,256 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss-5.1.0.CR1/server/ampep/conf/bootstrap.xml 09:21:01,637 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache] 09:21:01,639 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]] 09:21:01,848 INFO [CopyMechanism] VFS temp dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp 09:21:01,848 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled. 09:21:02,824 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc. 09:21:02,824 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_07-b06) 09:21:02,824 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc. 09:21:02,824 INFO [ServerInfo] OS-System: Linux 2.6.24-23-generic,i386 09:21:02,824 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dxb.builder.useUnorderedSequence=true -Djava.endorsed.dirs=/opt/jboss-5.1.0.CR1/lib/endorsed 09:21:02,901 INFO [JMXKernel] Legacy JMX core initialized 09:21:05,235 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1747e0f[domain=default, server=default, name=ampep] 09:21:26,054 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 09:21:26,068 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 09:21:26,147 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 09:21:28,768 WARN [TransactionManagerService] XAExceptionFormatters are not supported by the JBossTS Transaction Service - this warning can safely be ignored 09:21:34,501 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1a28371 09:21:34,515 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1a28371 09:21:35,310 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34 09:21:35,311 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34 09:21:35,315 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34 09:21:35,316 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34 09:21:35,470 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,471 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,472 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,473 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,474 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,475 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,476 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,487 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,488 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,490 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,491 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,491 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,493 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,493 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7 09:21:35,601 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,603 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,608 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,610 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb 09:21:35,712 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,742 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,743 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,743 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,749 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,750 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,750 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,751 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe 09:21:35,768 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917 09:21:35,769 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917 09:21:35,773 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917 09:21:35,774 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917 09:21:35,915 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78 09:21:35,915 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78 09:21:35,921 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78 09:21:35,921 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78 09:21:35,945 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@b24245 09:21:35,948 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@b24245 09:21:36,065 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1ee970 09:21:36,071 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1ee970 09:21:36,192 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,194 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,194 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,199 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,200 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,200 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792 09:21:36,466 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@7db532 09:21:36,470 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@7db532 09:21:36,694 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f613c 09:21:36,698 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f613c 09:21:36,901 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,902 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,902 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,903 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,903 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,908 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,908 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979 09:21:39,515 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@12030cd 09:21:39,518 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@12030cd 09:21:39,678 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@9533f5 09:21:39,685 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@9533f5 09:21:41,249 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e 09:21:41,250 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e 09:21:41,252 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e 09:21:41,252 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e 09:21:41,425 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@326c52 09:21:41,427 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@326c52 09:21:41,705 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@18a6420 09:21:41,707 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@18a6420 09:21:47,947 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. 09:21:49,266 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext 09:21:58,377 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,378 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,564 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,564 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,631 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,631 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,671 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,671 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,799 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,799 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,857 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,858 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,895 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,895 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,932 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,932 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,971 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:58,972 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:59,008 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:21:59,008 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container 09:22:09,149 ERROR [SmsManager] No scan dir was found. Stopping reader View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228504#4228504 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228504

16 years, 11 months

1
0
0 / 0

[Persistence, JBoss/CMP, Hibernate, Database] - Which folder does hibernate.jar, hibernate-annotations.jar,

by ezanih

Hi there I am using Hibernate with JBoss 4.2.2GA and JDK5 Release11. I am using a collection of Hibernate jars which include hibernate.jar, hibernate-annotations.jar, hibernate-common-annotations.jar, hibernate-entitymanager.jar and hibernate-validator.java. I am unsure where to save all these Hibernate jar files. Do I save them in jboss-4.2.2.GA/server/default/lib -or- jboss-4.2.2.GA/lib -or- jboss-4.2.2.GA/client or jdk1.5.0_14\lib -or- jdk1.5.0_14jre\lib and why ? Many thanks for your help! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228503#4228503 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228503

16 years, 11 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: java.net.BindException: Address already in use: JVM_Bind

by MalcolmShen

Many applications would randomly pick some available ports to use. I have also experienced this issue before. Here is how I solve this issue: I'm using windows. For linux, you may find similar commands. 1. In MS-DOS, send command "netstat -ao". You can get network information for all processes. 2. Find out the one using port 1098, get the PID. 3. Find out the process with the PID you just got from windows task manager and shut it down. 4. Restart JBoss. 5. Restart the application you've just shutdown. Hope this helps. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228502#4228502 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228502

16 years, 11 months

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - Re: java.net.BindException: Address already in use: JVM_Bind

by FrankTheTank

>From my exp MS Office or MS OfficeCommunicator will steal these ports at random times. My solution is to shut down these two programs, then start up JBoss again and restart them. Then it will work fine for another 26853 +/- 68952 starts. ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228501#4228501 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228501

16 years, 11 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 May 2009