why having the problem with 3.0.0RC1 but not Alpha?

[taiwubrian]

Hi,
I have used 3.0.0alpha for a long time. I can deploy my jar
file on it without major problems. Unfortunately, I got
serious problems with RC1. Following are excepts from the log
file. I had similar problems with Persistent Manager before I
giving up on using it. It seemed it was due to improper
ejb-jar.xml. However, the same jar can be deployed on Alpha.

The datadource is postgresql 7.1.3. Jboss started it properly.
I am using Mandrake Linux 8.2.
Please help.

I want to buy the up-to-'minute' documents, or at least 3.0.0RC1. Where can I find it.

Brian

2002-04-21 14:11:45,740 DEBUG [org.jboss.ejb.EJBDeployer] Verifying file:/home/ffargloryhq/jboss-3.0.0RC1/server/default/deploy/frontdesk.jar
2002-04-21 14:11:45,914 INFO [org.jboss.ejb.EJBDeployer]
Bean : company
Method : public String ejbCreate()
Section: 10.6.4
Warning: The throws clause must define the javax.ejb.CreateException.

2002-04-21 14:11:45,915 INFO [org.jboss.ejb.EJBDeployer]
Bean : company
Method : public String ejbCreate(String)
Section: 10.6.4
Warning: The throws clause must define the javax.ejb.CreateException.

2002-04-21 14:11:45,916 INFO [org.jboss.ejb.EJBDeployer]
Bean : company
Method : public String ejbCreate(CompanyVO)
Section: 10.6.4
Warning: The throws clause must define the javax.ejb.CreateException.
.....
2002-04-21 14:11:48,902 ERROR [org.jboss.ejb.EntityContainer] Exception in service lifecyle operation: create
org.jboss.deployment.DeploymentException: expected one strategy tag
at org.jboss.metadata.MetaData.getUniqueChild(MetaData.java:95)
at org.jboss.metadata.MetaData.getUniqueChildContent(MetaData.java:202)
at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCReadAheadMetaData.(JDBCReadAheadMetaData.java:109)
at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCEntityMetaData.(JDBCEntityMetaData.java:512)
at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCApplicationMetaData.(JDBCApplicationMetaData.java:237)
at org.jboss.ejb.plugins.cmp.jdbc.metadata.JDBCXmlFileLoader.load(JDBCXmlFileLoader.java:75)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.loadJDBCEntityMetaData(JDBCStoreManager.java:595)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.create(JDBCStoreManager.java:322)
at org.jboss.ejb.plugins.CMPPersistenceManager.create(CMPPersistenceManager.java:155)
at org.jboss.ejb.EntityContainer.create(EntityContainer.java:337)
at org.jboss.ejb.Container.invoke(Container.java:790)
at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:1055)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:867)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:271)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy15.create(Unknown Source)
at org.jboss.ejb.EjbModule.createService(EjbModule.java:381)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:134)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:867)
at $Proxy0.create(Unknown Source)
at org.jboss.system.ServiceController.create(ServiceController.java:271)
at org.jboss.system.ServiceController.create(ServiceController.java:211)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy5.create(Unknown Source)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:376)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:626)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:506)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:470)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy4.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:350)
at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:530)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:410)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:237)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:867)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:341)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
at $Proxy3.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:281)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:665)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:507)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:470)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:452)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:492)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:320)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:218)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:479)
....

[davidjencks]

The jbosscmp-jdbc dtd has changed quite a bit from alpha. You'll need to update your xml config files to match.

Dain's working as fast as he can on updated cmp2 docs.

[taiwubrian]

Hi, David,

Thanks for the info. Is there a mailing list for notifying the coming of updated docs?

BTW, many users and I run across a same problem which is not interesting anyone to advise.

java.rmi.ServerException:Could not passivate;...
.....
java.io.NotSerializableException: ...

This was due to Stateful session beans. I have no remote entity beans exposed to any users bur session beans.

Please kindly hint on any possible solutions.

Best Regards,

Brian

[davidjencks]

I'm sure new docs will be announced on the Announcements forum when they are available.

I think the passivation problem was fixed 2 or 3 days ago in cvs, both 3.0 and 3.1. Maybe its almost time for rc2;-)

[tom.baeyens]

I have the same problem.
(Only I have not deployed on the alpha version)
Could you explain a little bit more what you mean by "You'll need to update your xml config files to match"
I'm a developer using JBoss, not a developer of JBoss.

[davidjencks]

Assuming "same problem" means the one about strategy tags, by updating your dds to match, I mean getting the current jbosscmp-jdbc.dtd, and changing your jbosscmp-jdbc.xml deployment descriptor so it is valid according to the jbosscmp-jdbc.dtd.

[tom.baeyens]

Thanks !
Your assumption was correct.
You just helped me deploy my first cmp bean.
It felt real good, I think I've become a real man now !