[JBoss/Spring Integration] - NoSuchMethodError when trying to deploy sample ear
by rkapil
Any help would be appreciated.
11:15:36,350 INFO [EARDeployer] Init J2EE application: file:/C:/usr/jboss4.0.4/server/default/deploy/JBoss-Spring.
ear
11:15:36,541 INFO [CollectionFactory] JDK 1.4+ collections available
11:15:36,611 INFO [NamedXmlBeanDefinitionReader] Loading XML bean definitions from URL [jar:file:/C:/usr/jboss4.0.
4/server/default/tmp/deploy/tmp46789JBoss-Spring.ear-contents/spring-pojo.spring!/META-INF/jboss-spring.xml]
11:15:36,621 ERROR [MainDeployer] Could not create deployment: file:/C:/usr/jboss4.0.4/server/default/tmp/deploy/tm
p46789JBoss-Spring.ear-contents/spring-pojo.spring
java.lang.NoSuchMethodError: org.jboss.spring.factory.NamedXmlBeanDefinitionReader.createReaderContext(Lorg/springf
ramework/core/io/Resource;)Lorg/springframework/beans/factory/support/ReaderContext;
at org.jboss.spring.factory.NamedXmlBeanDefinitionReader.registerBeanDefinitions(NamedXmlBeanDefinitionRead
er.java:50)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionRea
der.java:406)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReade
r.java:360)
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReade
r.java:335)
at org.jboss.spring.factory.NamedXmlApplicationContext.loadBeanDefinitions(NamedXmlApplicationContext.java:
81)
at org.jboss.spring.factory.NamedXmlApplicationContext.loadBeanDefinitions(NamedXmlApplicationContext.java:
77)
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRef
reshableApplicationContext.java:94)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:2
94)
at org.jboss.spring.factory.NamedXmlApplicationContext.(NamedXmlApplicationContext.java:58)
at org.jboss.spring.factory.NamedXmlApplicationContext.(NamedXmlApplicationContext.java:48)
at org.jboss.spring.factory.ApplicationContextLoaderImpl.createBeanFactory(ApplicationContextLoaderImpl.jav
a:36)
at org.jboss.spring.factory.AbstractBeanFactoryLoader.create(AbstractBeanFactoryLoader.java:85)
at org.jboss.spring.deployment.SpringDeployer.create(SpringDeployer.java:116)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:943)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at sun.reflect.GeneratedMethodAccessor49.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 $Proxy8.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.ja
va: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.GeneratedMethodAccessor2.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.GeneratedMethodAccessor9.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:1007)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:808)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:755)
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:464)
at java.lang.Thread.run(Thread.java:595)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974963#3974963
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974963
19 years, 6 months
[Clustering/JBoss] - Network failure protection with JGroups/JBossCache
by kapilanand
hi
I am trying to use JBoss cache as a synchronously replicated cache inside jboss. There are other jboss/ejb applications running that rely on this replicated data.
I have couple of failure scenarios that I need to protect against.
1) first one is the simplest one: when the whole node goes down. This case is taken care of as other applications depending on the cache use only other nodes.
The other two scenarios are a bit complex:
2) If the nodes are running fine, but the connectivity between the JBossCache JGroup nodes is affected. That is other applications using the cache are not aware of this.
3) If the nodes are running fine, but only the multicast traffic amongst the JBossCache JGroup nodes is affected.
One possible solution to this problem is to invalidate all other cache replicas except one and then somehow route all application requests to that jboss instance. That would mean that if there are some EJBs that are clustered and they should be disabled on these invalidated cache nodes.
How can this be done?:
- Stateless session bean, since client stub participating in a different jgroup discovery might still see all the nodes alive and continue load-balancing. Is it possible to programmatically start/stop SLSB pool?
Or Stateless bean could check for cache invalidation and throw exception that hints the client to retry request, but it might still land up on the same node depending on the concurrency of requests and since stub is not aware of this exception.
- Message driven bean: Is it possible to programmatically start/stop MDB pools?
Or i guess (not sure) if MDB's could throw some exception in onMessage(), and the load-balancing logic in the external jms provider will try to route those messages to other MDBs.
Other possible solutions for high-availibilty through redundency:
(on top of the above)
Is it possible to configure a redundant network route for JGroups to fallback on?
Or is it possible to configure redundant multicast JGroups for one JBossCache and somehow bind these multicast address with different routes/nic?
Or is it possible to configure JGroups with two physical network interfaces, so it can decide to use either one of them.
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974959#3974959
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974959
19 years, 6 months
[Installation, Configuration & Deployment] - Small bugs in installer
by davidbalazic
Hi!
Should just submit them on JIRA ?
Here they are :
JBoss bugs
version : jboss-4.0.4.GA-Patch1-installer.jar
The installer wizard:
- The release notes are wider that the window, therefore hard to read.
(what is the reason for disallowing resizing of the window ?)
- clicking a link in the release notes takes you away, but there is no
(obvious) way back. The "Previous" button does not do that, for example.
- the table items in the "Install type" page are larger than the visible area.
As mentione, the windows can not be enlraged by the user to accomodate. There are
no scrollbars either.
- some pages have titles, some with icons, some multiples lines, each with icon,
some have nothing alike, almost each having a different font size. Not exactly "professional".
- The dialog, saying "This will cancel the installation!" has two buttons, Yes and No.
There is a question in the title, but the title is not the place to ask the user questions.
- At the end of the install wizard, the "Done" button has a red cross icon, like "Cancel".
It should be green or a similar "confirm" type.
Regards,
David
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974956#3974956
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974956
19 years, 6 months