[Persistence, JBoss/CMP, Hibernate, Database] - deployment problem with CMP (1:n relation)
by y0ur1
Hi, im using:
- EJB21
- JBoss 4.2.2.GA
- Java 1.5.0.14
I have a one-to-many relationship: Customer - Books, very straightforward. I keep getting the following error when i deploy my application:
| org.jboss.deployment.DeploymentException: Configuration found in jbosscmp-jdbc.xml for relation Customer-Book but relation is not a jbosscmp-jdbc-managed relation in ejb-jar.xml
|
When i don't use jbosscmp-jdbc.xml it deploys but the table books doesnt contain a foreign key with the customerid. Is there anyone who can help me with this problem?
Here is my ejb-jar.xml
| <?xml version="1.0" encoding="UTF-8"?>
|
| <ejb-jar
| xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
| http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
| version="2.1">
|
| <enterprise-beans>
| <entity>
| <ejb-name>Book</ejb-name>
| <home>BookHome</home>
| <remote>Book</remote>
| <ejb-class>BookEntity</ejb-class>
| <persistence-type>Container</persistence-type>
| <prim-key-class>java.lang.Integer</prim-key-class>
| <reentrant>false</reentrant>
| <cmp-version>2.x</cmp-version>
| <abstract-schema-name>Book</abstract-schema-name>
| <cmp-field>
| <field-name>bookid</field-name>
| </cmp-field>
| <cmp-field>
| <field-name>title</field-name>
| </cmp-field>
|
| <primkey-field>bookid</primkey-field>
| </entity>
|
| <entity>
| <ejb-name>Customer</ejb-name>
| <home>CustomerHome</home>
| <remote>Customer</remote>
| <ejb-class>CustomerEntity</ejb-class>
| <persistence-type>Container</persistence-type>
| <prim-key-class>java.lang.Integer</prim-key-class>
| <reentrant>false</reentrant>
| <cmp-version>2.x</cmp-version>
| <abstract-schema-name>Customer</abstract-schema-name>
| <cmp-field>
| <field-name>customerid</field-name>
| </cmp-field>
| <cmp-field>
| <field-name>name</field-name>
| </cmp-field>
|
| <primkey-field>customerid</primkey-field>
| </entity>
|
|
| <relationships>
| <ejb-relation>
| <ejb-relation-name>Customer-Book</ejb-relation-name>
|
| <ejb-relationship-role>
| <ejb-relationship-role-name>Book-has-customer</ejb-relationship-role-name>
| <multiplicity>Many</multiplicity>
| <relationship-role-source>
| <ejb-name>BookEntity</ejb-name>
| </relationship-role-source>
| <cmr-field>
| <cmr-field-name>customerid</cmr-field-name>
| </cmr-field>
| </ejb-relationship-role>
|
| <ejb-relationship-role>
| <ejb-relationship-role-name>Customer-has-books</ejb-relationship-role-name>
| <multiplicity>One</multiplicity>
| <relationship-role-source>
| <ejb-name>CustomerEntity</ejb-name>
| </relationship-role-source>
| <cmr-field>
| <cmr-field-name>books</cmr-field-name>
| <cmr-field-type>java.util.Collection</cmr-field-type>
| </cmr-field>
| </ejb-relationship-role>
| </ejb-relation>
| </relationships>
| </enterprise-beans>
| </ejb-jar>
|
jbosscmp-jdbc.xml:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <jbosscmp-jdbc>
| <relationships>
| <ejb-relation>
| <ejb-relation-name>Customer-Book</ejb-relation-name>
| <foreign-key-mapping/>
| </ejb-relation>
| </relationships>
|
| </jbosscmp-jdbc>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135273#4135273
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135273
18 years, 1 month
[JBossCache] - FetchInMemoryState && InitialStateRetrievalTimeout
by Sancheski
Hi guys
I am facing a problem when trying to get the state from cache in a 2-clustered cache enviroment. What a I get from the node which is starting and trying to get the state from another node in the cluster is:
2008-03-10 11:01:20,630 WARN [org.jboss.system.ServiceController] Problem starting service jboss.cache:service=ServicesDataCache
| org.jboss.cache.CacheException: Initial state transfer failed: Channel.getState() returned false
As I saw in http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheTroubleshooting I increased the InitialStateRetrievalTimeout parameter in the cache configuration file and everything worked fine.
Then, I wanted to test setting the parameter FetchInMemoryState to false so I could test a different solution (in my case, I do not care using a cold loading cache) What I got from this test is that some cache attributes (around 55000) were transferred to the cache that is starting (there are around 90000 attributes in the other node)
Perhaps, I am missing some configuration parameter. I am using Jboss Cache 1.4.1.SP8 and JbossAS 4.2.2.GA. Here is my cache config file:
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!-- ===================================================================== -->
| <!-- -->
| <!-- ServicesCache Service Configuration -->
| <!-- -->
| <!-- ===================================================================== -->
|
| <server>
|
| <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar" />
|
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
|
|
| <mbean code="org.jboss.cache.TreeCache"
| name="jboss.cache:service=ServicesDataCache">
|
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
|
| <attribute name="TransactionManagerLookupClass">
| org.jboss.cache.JBossTransactionManagerLookup
| </attribute>
|
| <!--
| Isolation level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">NONE</attribute>
|
| <!--
| Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| INVALIDATION_ASYNC
| INVALIDATION_SYNC
| -->
| <attribute name="CacheMode">REPL_SYNC</attribute>
|
| <!--
| Just used for async repl: use a replication queue
| -->
| <attribute name="UseReplQueue">false</attribute>
|
| <!--
| Replication interval for replication queue (in ms)
| -->
| <attribute name="ReplQueueInterval">0</attribute>
|
| <!--
| Max number of elements which trigger replication
| -->
| <attribute name="ReplQueueMaxElements">0</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other
| -->
| <attribute name="ClusterName">
| SOMServicesCache-Cluster
| </attribute>
|
| <!-- JGroups protocol stack properties. Can also be a URL,
| e.g. file:/home/bela/default.xml
| <attribute name="ClusterProperties"></attribute>
| -->
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address, e.g bind_addr="192.168.0.2"
| -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true -->
| <UDP
| mcast_addr="${jboss.cache.ServicesCache.addr:228.1.2.3}"
| mcast_port="${jboss.cache.ServicesCache.port:48866}" ip_ttl="64"
| ip_mcast="true" mcast_send_buf_size="150000"
| mcast_recv_buf_size="80000" ucast_send_buf_size="150000"
| ucast_recv_buf_size="80000" loopback="false" />
| <PING timeout="2000" num_initial_members="3"
| up_thread="false" down_thread="false" />
| <MERGE2 min_interval="10000" max_interval="20000" />
| <!-- <FD shun="true" up_thread="true" down_thread="true" />-->
| <FD_SOCK />
| <VERIFY_SUSPECT timeout="1500" up_thread="false"
| down_thread="false" />
| <pbcast.NAKACK gc_lag="50"
| retransmit_timeout="600,1200,2400,4800" max_xmit_size="8192"
| up_thread="false" down_thread="false" />
| <UNICAST timeout="600,1200,2400" down_thread="false" />
| <pbcast.STABLE desired_avg_gossip="20000"
| up_thread="false" down_thread="false" />
| <FRAG frag_size="8192" down_thread="false"
| up_thread="false" />
| <pbcast.GMS join_timeout="5000"
| join_retry_timeout="2000" shun="true" print_local_addr="true" />
| <pbcast.STATE_TRANSFER up_thread="true"
| down_thread="true" />
| </config>
| </attribute>
|
|
| <!--
| Whether or not to fetch state on joining a cluster
| NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
| -->
| <attribute name="FetchInMemoryState">false</attribute>
|
| <!--
| The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">15000</attribute>
|
| <!--
| Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">15000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">10000</attribute>
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass">
| org.jboss.cache.eviction.LRUPolicy
| </attribute>
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <!-- This attribute will be share by all eviction policies -->
| <attribute name="wakeUpIntervalSeconds">30</attribute>
| <!-- Cache wide default 86400-->
| <region name="/_default_">
| <attribute name="maxNodes">100000</attribute>
| <attribute name="timeToLiveSeconds">86400</attribute>
| </region>
| </config>
| </attribute>
|
|
| <!--
| Indicate whether to use region based marshalling or not. Set this to true if you are running under a scoped
| class loader, e.g., inside an application server. Default is "false".
| -->
|
| <attribute name="UseRegionBasedMarshalling">true</attribute>
| <attribute name="InactiveOnStartup">false</attribute>
|
| <attribute name="CacheLoaderConfiguration">
| <config>
| <passivation>false</passivation>
| <preload>/</preload>
| <shared>true</shared>
|
| <cacheloader>
| <class>
| org.jboss.cache.loader.ClusteredCacheLoader
| </class>
| <properties>timeout=1000</properties>
| <async>true</async>
| <fetchPersistentState>false</fetchPersistentState>
| <ignoreModifications>false</ignoreModifications>
|
| </cacheloader>
|
| </config>
| </attribute>
|
|
| </mbean>
|
|
| <!-- Uncomment to get a graphical view of the TreeCache MBean above -->
| <!-- <mbean code="org.jboss.cache.TreeCacheView" name="jboss.cache:service=TreeCacheView">-->
| <!-- <depends>jboss.cache:service=TreeCache</depends>-->
| <!-- <attribute name="CacheService">jboss.cache:service=TreeCache</attribute>-->
| <!-- </mbean>-->
|
|
| </server>
|
|
Hope you could help me.
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135263#4135263
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135263
18 years, 1 month