[JBoss AOP] - Several .aop archive in the same .ear
by djoukit
Hi all,
I use JBoss 4.2 and JBoss AOP dynamic weaving.
I tried to deploy several .aop archive in the same .ear and it worked well.
I have four .aop archive and I reference them in the META-INF/application.xml file of my ear.
...
| <module id="myeclipse.1176813227531">
| <ejb>myAopArchive_1.aop</ejb>
| </module>
| <module id="myeclipse.1177583403312">
| <ejb>myAopArchive_2.aop</ejb>
| </module>
| <module id="myeclipse.1180692708546">
| <ejb>myAopArchive_3.aop</ejb>
| </module>
| <module id="myeclipse.1180692708558">
| <ejb>myAopArchive_4.aop</ejb>
| </module>
| ...
When I deploy my .ear, everything works fine but the problem is that I may have several aspect inpacting the same method. Therefore I would like to be able to specify an order for the four .aop archive.
I tried to change the declaration order in the application.xml file but didn't get any results.
Is there a way to specify an order for my .aop archives ?
Thanks in advance for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077454#4077454
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077454
18Â years, 8Â months
[Performance Tuning] - Re: High Swap Utilization, lot's of RAM free
by Polaren
"PeterJ" wrote : What operating system? Windows tends to swap things out to disk even when it doesn't need to.
|
| What are your JVM heap settings?
|
| Also, you might get better performance if you limit the app server to running on 2, 3 or 4 of the Opterons(sockets). We have found that after 4 sockets that either you get no additional performance benefit or performance drops. And that some deployed apps run better on 2, others on 3, and others on 4 sockets.
Operating System is Windows Server 2k3, sorry forgot to specify that.
Where can I grab the heap settings from? Sorry I haven't needed to get that information before.
More info on the swapping is that as the amount of users sending their info to the database increases, the server uses more of the swap space. It's almost like it is storing client information, yet the server logically has nobody logged into it.
I'll look into the CPU performance problems.
Just looking for a solution to make it so that the server can handle more information as our user base is becoming larger. I am assuming right now that JBoss and that server are not functioning properly, as it is quite powerful for what it is doing.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077452#4077452
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077452
18Â years, 8Â months
[Installation, Configuration & DEPLOYMENT] - 4.2.1.GA: ClassLoader Isolation & EJB2.1 MDB Spec Violation
by JBOSSKumar
Hi,
- I have configured jboss-app.xml to have separate class loader repository.
Similar to :
<jboss-app>
<loader-repository>
com.example:loader=unique-archive-name
<loader-repository-config>
java2ParentDelegation=false
</loader-repository-config>
</loader-repository>
</jboss-app>
- I have build an .ear with the EJB2.1 Spec with MDB. The EAR successfully deploys in JBOSS 3.2.7 but throws EJBDeployer exception.
11:23:36,614 WARN [verifier] EJB spec violation:
Bean : EQBean
Section: 15.7.4
Warning: The message driven bean must declare one onMessage() method.
11:23:36,629 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.1.GA/server/default/tmp/deploy/tmp55961myportal.ear-contents/myportalEjb.jar
org.jboss.deployment.DeploymentException: Verification of Enterprise Beans failed, see above for error messages.
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:610)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:73)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy32.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:959)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor18.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy9.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:417)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
at org.jboss.Main.boot(Main.java:200)
at org.jboss.Main$1.run(Main.java:508)
at java.lang.Thread.run(Thread.java:595)
11:23:36,629 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Is anyone familiar with the problem & solution.
Responce is very much appreciated.
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077445#4077445
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077445
18Â years, 8Â months
[Performance Tuning] - High Swap Utilization, lot's of RAM free
by Polaren
Hey guys,
Alright, so I have a server I am monitoring 8 Opteron dual cores, 28GB of ram, and a decent amount of SCSI HD space, not in a raid configuration though.
Essentially it uses Jboss application server with a program that writes SQL statements commits them.etc.etc to the database(Sybase). The database is not being maxed at all. Although this server is for some reason utilizing tons of swap space. So we say okay it is maxing out 28GB of RAM? It's not as it is utilizing around 14GB , with another 14GB committed. I have no idea why it is swapping so much, it doesn't make much sense when it has 14GB of memory free. It's almost almost as though it doesn't know how to utilize the remaining memory, yet somedays it will use up to around 20GB. When it get's into heavy load it will not use the extra memory it has, if we lower the available memory to it (as it is not using it) we get memory exception errors. 28GB committed has been the only way it is working properly.
I am not a Jboss expert in anyway, I monitor the performance and utilization of the servers. Any advice or input would be appreciated. If you need more info, I'd be happy to provide it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4077441#4077441
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4077441
18Â years, 8Â months