Menu
▾
▴
Re: [Obe-developer] Deployment problem
|
From: Adrian P. <ad...@bt...> - 2005-11-06 21:50:16
|
Good day all, I've just checked in a bunch more changes: - Rationalised JNDI names for resources and EJBs. - Eliminated some app-server-specific build properties. - Fixed some meta-data inheritance and repository life-cycle bugs. - GOT ALL 218 TESTS WORKING AGAIN! Most of the Castor-related problems are now solved, although I'm still seeing occasional weirdness when Castor claims it can't find field descriptors that it had no trouble with on a previous test run, or on a previous deployment cycle. I have no idea what's causing the trouble. Next steps will be: - Rationalise & centralise client configuration. - Complete documentation. best regards, Adrian. On Fri, 2005-11-04 at 22:51, Adrian Price wrote: > Good day Vicente, Mélanie and others, > > I'm sorry about the difficulties you've been experiencing with the > latest OBE sources. There have been some considerable changes in the > run-up to the first formal release which do represent improvements but > have caused some problems which I'm still working on. > > One very significant change was the introduction of an EJB-based > application event broker. The event broker requires EJB 2.1 timer > services which in turn mandates the use of JBoss 4.0.1+. If you really > need to use JBoss 3.x you'll have to revert to the older, non-persistent > basic application event broker implementation. > > There were also considerable changes to the repository schema in order > to make the XML markup more compact and expressive and to use XML > namespaces but I am still wrestling with the latest (buggy) > Castor-0.9.9. Have already had to patch one intractable bug. It would > seem that the same XML files load perfectly when using a local, embedded > OBE engine but fail when loaded in the J2EE environment. Right now I'm > in the middle of a long debugging session trying to figure out why. It's > something to do with the namespaces on attributes. > > Will post again when I have a resolution. In the meantime, be aware that > CVS HEAD is very much 'bleeding edge' while I nail recently introduced > problems. > > Best regards, > > Adrian. > > > On Fri, 2005-11-04 at 19:39, Vicente Grassi Filho wrote: > > Hi Mélanie: > > > > I did the same thing as you did(downloaded the last version, etc...) and I also had problems, I don't remember exactly if it was this one. How to solve this? I've upgrated to JBoss-4.0.1(running on JDK 1.5.0_04) and it works > > fine. If you can upgrade, do it! > > > > Vicente Grassi Filho > > > > > > > > On Fri, 4 Nov 2005 13:39:52 -0500, Mélanie Gauthier <mga...@tr...> escreveu: > > > > > De: Mélanie Gauthier <mga...@tr...> > > > Data: Fri, 4 Nov 2005 13:39:52 -0500 > > > Para: <obe...@li...> > > > Assunto: [Obe-developer] Deployment problem > > > > > > > > > > > > Hi all, > > > > > > I decided to take a fresh and clean version from CVS. I've updated CVS, built a new EAR (it builds properly), built a new data base with OBE user, copied the JBOSS (I'm working with version 3.2.3) configuration files (in conf and in deploy folders) , put the obeserver.ear in it (server/default/deploy). The snmp-adaptor.sar has been deleted. But when I start JBOSS, I received the following error when it tries to deploy the ear : > > > > > > ------------------- > > > 14:18:04,892 WARN [verifier] EJB spec violation: > > > Bean : EventSubscription > > > Section: 22.2 > > > Warning: The Bean Provider must specify the fully-qualified name of the Java cla > > > ss that implements the enterprise bean's business methods in the <ejb-class> ele > > > ment. > > > Info : Class not found on 'org.obe.server.j2ee.ejb.EventSubscriptionEJB': Unex > > > pected error during load of: org.obe.server.j2ee.ejb.EventSubscriptionEJB, msg=j > > > avax/ejb/TimedObject > > > > > > 14:18:04,970 WARN [verifier] EJB spec violation: > > > Bean : ApplicationEvent > > > Section: 22.2 > > > Warning: The Bean Provider must specify the fully-qualified name of the Java cla > > > ss that implements the enterprise bean's business methods in the <ejb-class> ele > > > ment. > > > Info : Class not found on 'org.obe.server.j2ee.ejb.ApplicationEventEJB': Unexp > > > ected error during load of: org.obe.server.j2ee.ejb.ApplicationEventEJB, msg=jav > > > ax/ejb/TimedObject > > > > > > 14:18:05,095 ERROR [MainDeployer] could not create deployment: file:/C:/java/jbo > > > ss-3.2.3/server/default/tmp/deploy/tmp44385obeserver.ear-contents/obeserver-ejb. > > > jar > > > org.jboss.deployment.DeploymentException: Verification of Enterprise Beans faile > > > d, see above for error messages. > > > at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:491) > > > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:786) > > > at org.jboss.deployment.MainDeployer.create(MainDeployer.java:778) > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641) > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) > > > at sun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source) > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > > sorImpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea > > > nDispatcher.java:284) > > > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > > > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > > > at $Proxy6.deploy(Unknown Source) > > > at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen > > > tScanner.java:302) > > > at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS > > > canner.java:476) > > > at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread. > > > doScan(AbstractDeploymentScanner.java:201) > > > at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A > > > bstractDeploymentScanner.java:274) > > > at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:1 > > > 92) > > > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > > sorImpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea > > > nDispatcher.java:284) > > > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > > > at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl > > > ler.java:976) > > > at $Proxy0.start(Unknown Source) > > > at org.jboss.system.ServiceController.start(ServiceController.java:394) > > > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > > sorImpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea > > > nDispatcher.java:284) > > > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > > > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > > > at $Proxy4.start(Unknown Source) > > > at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226) > > > at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832) > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642) > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605) > > > at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589) > > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > > > java:39) > > > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > > > sorImpl.java:25) > > > at java.lang.reflect.Method.invoke(Method.java:324) > > > at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBea > > > nDispatcher.java:284) > > > at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) > > > at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177) > > > at $Proxy5.deploy(Unknown Source) > > > at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384) > > > at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291) > > > at org.jboss.Main.boot(Main.java:150) > > > at org.jboss.Main$1.run(Main.java:395) > > > at java.lang.Thread.run(Thread.java:534) > > > ------------------- > > > > > > I've checked that the EAR does contain the files mentionned in the error log. If anyone has experienced that problem, I would appreciate your help! > > > > > > Thanks! > > > > > > > > > Mélanie > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > SF.Net email is sponsored by: > > Tame your development challenges with Apache's Geronimo App Server. Download > > it for free - -and be entered to win a 42" plasma tv or your very own > > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > > _______________________________________________ > > Obe-developer mailing list > > Obe...@li... > > https://lists.sourceforge.net/lists/listinfo/obe-developer > > > > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server. Download > it for free - -and be entered to win a 42" plasma tv or your very own > Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php > _______________________________________________ > Obe-developer mailing list > Obe...@li... > https://lists.sourceforge.net/lists/listinfo/obe-developer |
