[JBoss Messaging] - 1.2CR1 - AS 4.0.5 Install - ClassNotFoundException on Failov
by jeanbobby
Hello,
Im trying to setup 1.2CR1 on a 4.0.5 default.
Im running a co-located test sar that's already running with a 1.0.1SP4 / 4.0.5 install (to work with Tim on case 00014299).
It just requires a simple non clustered config and a test queue.
My 1.0.1SP4 / 4.0.5 install is the default patch with release-admin.xml.
I do the same with 1.2CR1 and when I deploy the test sar, I get :
16:50:38,986 WARN [JBossManagedConnectionPool] Throwable while attempting to get a new connection:
| null
| java.lang.RuntimeException: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.j
| ms.client.container.FailoverValveInterceptor
| at org.jboss.aop.advice.GenericAspectFactory.getClazz(GenericAspectFactory.java:141)
| at org.jboss.aop.advice.GenericAspectFactory.createPerInstance(GenericAspectFactory.java:182
| )
| at org.jboss.aop.InstanceAdvisorDelegate.initializeAspects(InstanceAdvisorDelegate.java:100)
|
| at org.jboss.aop.InstanceAdvisorDelegate.initialize(InstanceAdvisorDelegate.java:72)
| at org.jboss.aop.ClassInstanceAdvisor.<init>(ClassInstanceAdvisor.java:75)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate._getInstanceAdvisor(ClientConnecti
| onDelegate.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.setExceptionListener(ClientConnect
| ionDelegate.java)
| at org.jboss.jms.client.JBossConnection.setExceptionListener(JBossConnection.java:117)
| at org.jboss.resource.adapter.jms.JmsManagedConnection.setup(JmsManagedConnection.java:746)
| at org.jboss.resource.adapter.jms.JmsManagedConnection.<init>(JmsManagedConnection.java:184)
|
| at org.jboss.resource.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsMan
| agedConnectionFactory.java:106)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventL
| istener(InternalManagedConnectionPool.java:565)
| at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(Internal
| ManagedConnectionPool.java:250)
| at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JB
| ossManagedConnectionPool.java:491)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConn
| ectionManager2.java:341)
| at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectio
| nManager.java:301)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnec
| tionManager2.java:396)
| at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.alloca
| teConnection(BaseConnectionManager2.java:842)
| at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactory
| Impl.java:389)
| at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createSession(JmsSessionFactoryImpl.
| java:369)
| at com.digiplug.repository.transcoding.util.spring.JmsXAReceptionRunnable.doReceiveAndExecut
| e(JmsXAReceptionRunnable.java:80)
| at com.digiplug.repository.transcoding.util.spring.JmsXAReceptionRunnable.run(JmsXAReception
| Runnable.java:29)
| at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.client.contain
| er.FailoverValveInterceptor
| at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.aop.advice.AspectFactoryWithClassLoaderSupport.loadClass(AspectFactoryWithClass
| LoaderSupport.java:80)
| at org.jboss.aop.advice.GenericAspectFactory.getClazz(GenericAspectFactory.java:137)
| ... 24 more
|
|
Any particularities in the setup on this new version when using a non clusted config ?
Best regards
Olivier
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020642#4020642
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020642
19Â years, 2Â months
[JBoss Portal] - Management Portlet - Destroy Page
by hemmer
Hello,
I'm having the following problem with the jboss portal 2.4.1.
After deploying the portal server on Windows machine everything works out fine and I can use every function of the management portlet.
But if I copy exactly the same jboss server and jboss portal server on a linux machine some funtions of the management portlet don't have any effect any longer. For example the "Destroy" button, to destroy pages.
I changed the hibernate logging to very fine in order to find out if anything happens after clicking the destroy button. The result is: nothing happens, no hibernate logging, no exception, simply nothing!
I tried to change the locals of the linux system, I tested it with different java versions, but the problem still exists.
Does anyone have any clue what's wrong with the linux system/portal server???
I'm thankful for any reply.
Regards,
Kai
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020636#4020636
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020636
19Â years, 2Â months
[Performance Tuning] - Re: JBoss- How to big /incrase Heap size?
by PeterJ
I would advise against setting the heap to 5GB (or 10GB), because when you hit your first major garbage collection, you will find that it will take several minutes during which time all of the application processing will be suspended. (If you have multiple CPUs, you could look into the mostly-concurrent garbage collector, which would reduce the delay for garbage collection, and thus might allow a fairly large heap to be used. Note that this collector will slow down the overall throughput for the application.)
The best setting is to make the heap as large as you need it, but not any larger. The only way to find out what this ideal heap size is is to perform load testing on your application. I usually recommend the following setting to start your testing with, and then to adjust the setting based on usage:
-Xms1200M -Xmx1200m -XX:NewSize=300M -XX:MaxNewSize=300M
To analyze the heap usage, use the -verbose:gc or -XX:PrintHeapAtGC command line options, plotting the data that they give. That will tell you if you need to adjust the young generation or whole heap sizes.
Reference: http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4020635#4020635
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4020635
19Â years, 2Â months