-
1. Re: Error Using FindByPK
aloubyansky Oct 8, 2002 4:09 AM (in response to alexb)BigDecimal for primary key currently supported in Branch_3_0 (JBoss-3.0.4RC1). I am not sure whether it was in JBoss_3.0.2.
But JBossQL doesn't support BigDecimal for now.
And, btw, by the spec, numeric types are limited in size to long and double. -
2. Re: Error Using FindByPK
alexb Oct 8, 2002 9:58 AM (in response to alexb)Thanks for the reply, do you have a link that I can go to and download it. Thanks...
-
3. Re: Error Using FindByPK
aloubyansky Oct 8, 2002 11:37 AM (in response to alexb)Try jboss-3.0.3 at sf.net. I hope it supports it.
Or you can use cvs to fetch the sources:
cvs -z3 -d:pserver:anonymous@cvs.jboss.sourceforge.net:/cvsroot/jboss co -r Banch_3_0 jboss-all
OR
cvs -z3 -d:pserver:anonymous@cvs.jboss.sourceforge.net:/cvsroot/jboss co -r Banch_3_0 jboss-3.0 -> a jboss-3.0 directory -
4. Re: Error Using FindByPK
alexb Oct 8, 2002 4:47 PM (in response to alexb)I down loaded JBoss 3.0.3 and now when I try to deploy the same code that was deploying in JBoss 3.0.2 it gives me this error.....
15:52:59,245 INFO [EjbModule] Registration is not done -> destroy
15:52:59,275 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@43fb1228{ url=file:/C:/Boss3.0/jboss-3.0.3/server/default/deploy/bid-jboss-2.0.ear, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/C:/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar; - nested throwable: (javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EjbModule,url=file%/C%/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar already registered.)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:380)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
Can you steer me in the right direction with this it says that bid-jboss-2.0.ear is already registered...
Thanks again
Alex -
5. Re: Error Using FindByPK
alexb Oct 8, 2002 4:52 PM (in response to alexb)I down loaded JBoss 3.0.3 and now when I try to deploy the same code that was deploying in JBoss 3.0.2 it gives me this error.....
15:52:59,245 INFO [EjbModule] Registration is not done -> destroy
15:52:59,275 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@43fb1228{ url=file:/C:/Boss3.0/jboss-3.0.3/server/default/deploy/bid-jboss-2.0.ear, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/C:/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar; - nested throwable: (javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EjbModule,url=file%/C%/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar already registered.)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:380)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
Can you steer me in the right direction with this it says that bid-jboss-2.0.ear is already registered...
Thanks again
Alex -
6. Re: Error Using FindByPK
alexb Oct 8, 2002 5:27 PM (in response to alexb)I down loaded JBoss 3.0.3 and tried to deploy the code that I already deployed on JBoss 3.0.2 and now I get this error...
15:52:59,275 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@43fb1228{ url=file:/C:/Boss3.0/jboss-3.0.3/server/default/deploy/bid-jboss-2.0.ear, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: error in create of EjbModule: file:/C:/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar; - nested throwable: (javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EjbModule,url=file%/C%/Boss3.0/jboss-3.0.3/server/default/tmp/deploy/server/default/deploy/bid-jboss-2.0.ear/69.bid-jboss-2.0.ear-contents/entity-atd-common-ejb-2.0.jar already registered.)
at org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:380)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
Can you steer me in the right direction with this thanks
Alex... -
7. Re: Error Using FindByPK
aloubyansky Oct 9, 2002 5:39 AM (in response to alexb)It says you are deploying entity-atd-common-ejb-2.0.jar that is already deployed.
Is it right? -
8. Re: Error Using FindByPK
alexb Oct 9, 2002 12:12 PM (in response to alexb)thanks for your reply once again ... it seems weird to me that in jboss 3.0.2 this deploys but gives me an error on a findByPK using a bigDecimal ... Now that I'm using jboss 3.0.3 it doesn't even deploy. It seems that jboss is trying to deploy entity-atd-common-ejb-2.0 twice could this be a bug in jboss. The entity-atd-common-ejb-2.0 is in a ear file that I put in the server/default directory...
thanks once again....
Alex -
9. Re: Error Using FindByPK
aloubyansky Oct 9, 2002 1:31 PM (in response to alexb)I don't think there is such a bug.
Make sure you haven't deployed the jar separately and then trying to deploy the ear.
What else can be here?..
In application.xml
entity-atd-common-ejb-2.0.jar
is specified only once. I really think it's not a JBoss problem. -
10. Re: Error Using FindByPK
alexb Oct 9, 2002 4:18 PM (in response to alexb)Well I'm attaching my ear file that the jar file is in and I'm attaching my application.xml too.... This is a very frustrating bug thanks in advance for any help....
Alex -
11. Re: Error Using FindByPK
aloubyansky Oct 10, 2002 3:18 AM (in response to alexb)It seems to me I've figured it out, though I haven't tried to deploy the ear. I think the problem is in manifest Class-Path.
Suppose, second-ejb.jar has a Class-Path in manifest refering to first-ejb.jar.
first-ejb.jar is deployed first.
Then before the second-ejb.jar is deployed, its manifest is analysed and deployer tries to deploy all the jars Class-Path. Since first-ejb.jar is already deployed the exception is thrown.
To solve the problem, just remove all the Class-Path entries in the manifest. Each class in the ear will see others.
I haven't analysed all the jars but you can meet a deployment order problem. When some jar will be deployed before the jar that it depends on. To solve this there are some deployment sorters, say, based on names, i.e. the jars will be deployed in alphabetical order or you can prefix the names with digits.
I think it can be considered as a bug. If you think it is, then file a bug report.