[JBoss-user] In-ear .rar deployment - possible?
Hello, I have been unable to determine from my searches and reading of the documentation whether it is currently possible to deploy my .rar file inside an .ear on JBoss 3.2.3. Many posts seemed to imply that it would be available soon, but they were from about a year ago. I thought I'd give it a shot, but haven't been fully successful. Am I barking up the wrong tree? If it's possible, hopefully I'm doing something simple wrong. Specifically, I am trying to deploy hibernate as a .rar file inside my application's .ear. When I deploy the ear with a hibernate-ds.xml file in the META-INF of the .rar, it seems to unpack the rar quite happily, but never binds it to any jndi name. Naturally the bean's lookups of java:comp/env/hibernate/SessionFactory fail with javax.naming.NameNotFoundException: hibernate not bound messages. Below are the contents of my ra.xml, hibernate-ds.xml, and jboss-service.xml files. I've also added some output from when JBoss unpacks the rar, and finally portions of ejb-jar.xml and jboss.xml that refer to the connector. It's a lot of stuff, sorry. I figured it beats making you guys ask me for it :-) Note that in hibernate-ds.xml, I've tried no-tx-connection-factory, local-tx-connection-factory, and xa-tx-connection-factory, all to no avail. I've also tried a few names in the ejb-jar.xml and jboss.xml, but I'm not seeing it anywhere in JndiView (except references in bean namespaces), so I figured they wouldn't work anyway. Thanks for any advice you can offer, Ben [ra.xml] spec-version1.0/spec-version eis-typeHibernate Sessions/eis-type version2.0/version license descriptionLGPL/description license-requiredfalse/license-required /license resourceadapter managedconnectionfactory-classnet.sf.hibernate.jca.ManagedConnectionFactoryImpl/managedconnectionfactory-class connectionfactory-interfacenet.sf.hibernate.SessionFactory/connectionfactory-interface connectionfactory-impl-classnet.sf.hibernate.jca.JCASessionFactoryImpl/connectionfactory-impl-class connection-interfacenet.sf.hibernate.Session/connection-interface connection-impl-classnet.sf.hibernate.jca.JCASessionImpl/connection-impl-class transaction-supportXATransaction/transaction-support config-property config-property-nameDialect/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuenet.sf.hibernate.dialect.Oracle9Dialect/config-property-value /config-property config-property config-property-nameMapResources/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuecom/threedmt/testrar/Member.hbm.xml/config-property-value /config-property config-property config-property-nameDatasourceJndi/config-property-name config-property-typejava.lang.String/config-property-type config-property-valuejdbc/UserDataDS/config-property-value /config-property config-property config-property-nameHibernateProperties/config-property-name config-property-typejava.lang.String/config-property-type config-property-valueUseOuterJoin=false,ShowSql=false/config-property-value /config-property 1.0, 10.3.1 If no authentication mechanism is specified as part of the deployment descriptor, the resource adapter supports no standard security authentication mechanism as part of thesecurity contract. authentication-mechanism descriptionBasicPassword/description authentication-mechanism-typeBasicPassword/authentication-mechanism-type credential-interfacejavax.resource.security.PasswordCredential/credential-interface /authentication-mechanism -- reauthentication-supporttrue/reauthentication-support !-- JCA 1.0, 10.3.1 (what is that supposed to mean???) The security permissions listed in the deployment descriptor are different from those required by the default permission set (refer to Section 11.2 for more details on security permissions). security-permission description/description security-permission-spec /security-permission-spec /security-permission -- /resourceadapter /connector [hibernate-ds.xml] connection-factories local-tx-connection-factory jndi-namehibernate/SessionFactory/jndi-name adapter-display-nameHibernate Resource Adapter/adapter-display-name /local-tx-connection-factory /connection-factories [jboss-service.xml] ?xml version=1.0 encoding=UTF-8? !DOCTYPE server !-- Generated file - Do not edit! -- server mbean code=net.sf.hibernate.jmx.HibernateService name=jboss.jca:service=HibernateSplat
Re: [JBoss-user] Shutdown multiple instances
Rod Macpherson wrote: Has anyone mastered the intricacies of JBoss shutdown for multiple IPs? I kill the process. Does shutdown accept the --host switch? If not that should be added as a feature request for symmetry if nothing else. That's what I've been forced to resort to, as well. Have you come up with a clean way of doing this from an Ant build file? I'd like to create targets for all of my developers to be able to start and stop their instances of JBoss Thanks, Ben --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Re: Shutdown multiple instances
Thanks, Craig, for the response. Unfortunately, this doesn't work either. It just hangs, nothing in the server's log, and nothing on the console. I've also tried 1099 with the same effect. Any other ideas out there? Why is this difficult? Ben [EMAIL PROTECTED] wrote: Hi Ben and Tim, One of your attempts is close to what should work: shutdown.sh --server=bjc.mydomain.com:1098 assuming 1098 is the port on which the server is listening. Make sure you can ping bjc.mydomain.com from the same machine. Regards, Craig Johannsen Ludicorp Research and Development --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Shutdown multiple instances
Hello, We're using JBoss 3.2.0, and am trying to use multiple instances listening on different IPs. We set up a different IP on the same box for each instance (via an ifconfig alias), and gave each a hostname based on the name of the user who would be developing on that instance. For instance, bjc.mydomain.com for user bjc. We've also added these hostnames to our DNS, and they are resolving correctly. We have tried quite a few things, and looked around a lot, both in the for-pay docs and on the web, but have not yet been able to make one particular instance of JBoss shutdown. The things we have tried so far are listed at the bottom, as well as the results of each one. We really have no idea where to look next; is there anyone out there who can shed some light on this? Has anyone mastered the intricacies of JBoss shutdown for multiple IPs? Thanks in advance, Ben Cox Tim Ruppert Note - ###.###.###.### denotes an IP address. These two: * http://bjc.mydomain.com:8080/jmx-console/HtmlAdaptor?action=invokeOpByNamename=jboss.systemtype=servermethodName=shutdown * http://###.###.###.###:8080/jmx-console/HtmlAdaptor?action=invokeOpByNamename=jboss.systemtype=servermethodName=shutdown both produce a javax.management.MalformedObjectNameException: missing domain These two: * shutdown.sh bjc.mydomain.com 8080 * shutdown.sh ###.###.###.### 8080 both produce a javax.naming.CommunicationException: Failed to connect to server: localhost:1099. These five: * shutdown.sh -Djava.naming.provider.url=jnp://bjc.mydomain.com:1099 * shutdown.sh -Djava.naming.provider.url=rmi://bjc.mydomain.com:1098 * shutdown.sh -Djava.naming.provider.url=jnp://###.###.###.###:1099 * shutdown.sh --server=bjc.mydomain.com * shutdown.sh --server=###.###.###.### all produce a java.rmi.ConnectException: Connection refused to host: ###.###.###.### except that the last number is wrong: it's the original IP of the box. Could JBoss be ignoring the alias on some level? --- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] MySQL connector on 3.2.0RC2
Hello, I have just downloaded 3.2.0RC2 (the zip file, after building from source failed), and tried to set up two MySQL datasources. I copied the mysql-service.xml file from $JBOSS_HOME/docs/examples/jca/mysql-service.xml and modified the connection, etc. properties. When I ran JBoss, it complained with the following warning: 02:37:24,418 WARN [XATxConnectionManager] -- 02:37:24,418 WARN [XATxConnectionManager] -- 02:37:24,418 WARN [XATxConnectionManager] Please change your datasource setup to use TransactionManagerService with object name jboss.tm:service=TransactionManagerService 02:37:24,418 WARN [XATxConnectionManager] instead of TransactionManager with value java:/TransactionManager 02:37:24,419 WARN [XATxConnectionManager] -- 02:37:24,419 WARN [XATxConnectionManager] -- Trying to run anyway resulted in a lot of exceptions in my application, all indicating I didn't set up my datasources correctly. So, I followed the advice of the warning, and changed the line: attribute name=TransactionManagerjava:/TransactionManager/attribute to: attribute name=TransactionManagerServicejboss.tm:service=TransactionManagerService/attribute Running again, I received four copies of the following error (2 per datasource): 02:37:25,158 INFO [LocalTxConnectionManager] Starting 02:37:25,159 ERROR [LocalTxConnectionManager] Starting failed javax.management.InstanceNotFoundException: jboss.tm:service=TransactionManagerService is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:354) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:445) at org.jboss.resource.connectionmanager.TxConnectionManager.startService(TxConnectionManager.java:277) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966) at $Proxy11.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:392) at org.jboss.system.ServiceController.start(ServiceController.java:408) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy5.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:231) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:827) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:639) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:612) at sun.reflect.GeneratedMethodAccessor23.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174) at $Proxy7.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:404) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:545) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:195) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:268) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966) at $Proxy0.start(Unknown Source)
Re: [JBoss-user] CMP/BMP Performance
This is an interesting and informative article about that very topic: http://www.urbancode.com/projects/ejbbenchmark/testsAndResults.jsp Good luck, Ben NIELSEN JAN, Teliadk wrote: Hi All, I'm about to start implementation of a fairly large system, where performance is a big issure. Can any one give me a tip on what road I should select. Should I choose CMP, BMP or make a DAO layer where I'm using JDBC? Hope you can give me a hint :-) Cheers Jan --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBOSS 3.2RC2 - Connection Manager Info
I, too, was getting this error after following the advice in a previous posting regarding the TransactionManager attribute of the datasources' service.xml file. The advice was to ignore the log messages asking you to change it to jboss.tm:service=TransactionManagerService. By turning the log level up to DEBUG for my EJB classes, I got a more informative stack trace and found that there were, in fact, places in my code where the connection I had obtained was never closed. Previous versions of JBoss must have been smart enough to close them for us, but this promotes bad coding habits, so I'm just as happy they've changed this. It's kind of like Netscape not rendering badly formed tables anymore. If enough people are forced to comply with the specification, we can eventually be using XML-generated XHTML for everything. See if this is the case for you, as well. Search your code base for getConnection(), and find out where, if at all, that connection is closed. Good luck, Ben Corbin, James wrote: Hello, After moving from 3.2RC1 to 3.2RC2 I started receiving this information message in my server log. I verified I was closing the connection in my finally clauses, so I'm not sure why the CachedConnectionManager is complaining. Any suggestions? J.D. 13:21:50,683 INFO [CachedConnectionManager] Could not find a close method on alleged connection objects. Please close your own connections. java.lang.Exception: Stack Trace at org.jboss.resource.connectionmanager.CachedConnectionManager.closeAll(CachedConnectionManager.java:357) at org.jboss.resource.connectionmanager.CachedConnectionManager.popMetaAwareObject(CachedConnectionManager.java:199) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:190) at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstanceInterceptor.java:77) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:108) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:216) at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:104) at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:130) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:208) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:154) This electronic message transmission contains information from the Company that may be proprietary, confidential and/or privileged. The information is intended only for the use of the individual(s) or entity named above. If you are not the intended recipient, be aware that any disclosure, copying or distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender immediately by replying to the address listed in the "From:" field.
[JBoss-user] 3.2.0RC2... CVS or distribution?
I have seen a few email threads which indicate that problems people are having in the distributions of 3.2.0RC2 are not present in the CVS version of 3.2.0RC2. For example, hot deployment, the warning to change the TransactionManager attribute to jboss.tm:service=TransactionManagerService, etc. I am curious about whether any different, significant problems are likely to appear in the CVS version... will I trade the inability to hot deploy for a recently introduced bug that may be more fatal to my application? Is the development happening in the CVS version right now exclusively bug fixes for this release candidate, as I assume? If it _is_ wise to use the CVS version, what do I have to do to check it out? I couldn't find it by browsing the repository on Sourceforge. Thanks for the advice, Ben --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JBOSS 3.2RC2 - Connection Manager Info
Corbin, James wrote: Ben, I have verified wherever there is a getConnection that it is subsequently followed by a closeConnection(). Alas, I may have missed one and will keep looking. I don't know if it makes a difference, but I used java.sql.Connection.close() method, not the DataSource method. I think the line in your stack trace that says: "Please close your own connections." supports this theory. It may not hurt to try changing your closeConnection() calls to Connection.close() calls. Hope it helps, Ben
[JBoss-user] Problem with having multiple users and Postgres
hey, i'm having a weird problem where if only one person is hitting my site, it's fine, but as soon as two people hit it, jboss gives tons of errors and doesn't recover. i get the following error over and over. We're using REQUIRED and commit-option A, though we've tried other commit options to no avail. Any help would be GREATLY appreciated! thanks so much, rachel [MultipleChoiceSelection] XAException: tx=XidImpl [FormatId=257, GlobalId=botia.vireo.org//4252, BranchQual=] errorCode=XAER_NOTA [MultipleChoiceSelection] javax.transaction.xa.XAException [MultipleChoiceSelection] at org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl.start(XAResourceImpl.java:258) [MultipleChoiceSelection] at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1087) [MultipleChoiceSelection] at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:614) [MultipleChoiceSelection] at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:111) [MultipleChoiceSelection] at org.jboss.pool.jdbc.xa.XAConnectionFactory.prepareObject(XAConnectionFactory.java:269) [MultipleChoiceSelection] at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:548) [MultipleChoiceSelection] at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:521) [MultipleChoiceSelection] at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:165) [MultipleChoiceSelection] at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.getConnection(JDBCCommand.java:680) [MultipleChoiceSelection] at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:152) [MultipleChoiceSelection] at org.jboss.ejb.plugins.jaws.jdbc.JDBCStoreEntityCommand.execute(JDBCStoreEntityCommand.java:97) [MultipleChoiceSelection] at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.storeEntity(JAWSPersistenceManager.java:168) [MultipleChoiceSelection] at org.jboss.ejb.plugins.CMPPersistenceManager.storeEntity(CMPPersistenceManager.java:424) [MultipleChoiceSelection] at org.jboss.ejb.plugins.EntitySynchronizationInterceptor$InstanceSynchronization.beforeCompletion(EntitySynchronizationInterceptor.java:370) [MultipleChoiceSelection] at org.jboss.tm.TxCapsule.doBeforeCompletion(TxCapsule.java:1210) [MultipleChoiceSelection] at org.jboss.tm.TxCapsule.commit(TxCapsule.java:304) [MultipleChoiceSelection] at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:76) [MultipleChoiceSelection] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:355) [MultipleChoiceSelection] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:99) [MultipleChoiceSelection] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:190) [MultipleChoiceSelection] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195) [MultipleChoiceSelection] at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:338) [MultipleChoiceSelection] at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:390) [MultipleChoiceSelection] at java.lang.reflect.Method.invoke(Native Method) [MultipleChoiceSelection] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) [MultipleChoiceSelection] at sun.rmi.transport.Transport$1.run(Transport.java:142) [MultipleChoiceSelection] at java.security.AccessController.doPrivileged(Native Method) ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] problem with postgres and jboss
Hi all, I am new to EJBs, and I'm having problems deploying on postgres. I can start the server just fine, and create all the tables, and in the beginning everything works fine, but then after a little while, and randomly, I get the following exception. (see below). I believe I have my jboss.jcml set up right, but I will include it at the end as well... Has anyone else seen this exception? I get it very frequently... Thanks so much for your help!! Rachel [Client] XAException: tx=XidImpl [FormatId=257, GlobalId=botia.vireo.org//1003, BranchQual=] errorCode=XAER_NOTA [Client] javax.transaction.xa.XAException [Client]at org.opentools.minerva.jdbc.xa.wrapper.XAResourceImpl.start(XAResourceImpl.java:258) [Client]at org.jboss.tm.TxCapsule.startResource(TxCapsule.java:1087) [Client]at org.jboss.tm.TxCapsule.enlistResource(TxCapsule.java:614) [Client]at org.jboss.tm.TransactionImpl.enlistResource(TransactionImpl.java:111) [Client]at org.jboss.pool.jdbc.xa.XAConnectionFactory.prepareObject(XAConnectionFactory.java:269) [Client]at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:548) [Client]at org.jboss.pool.ObjectPool.getObject(ObjectPool.java:521) [Client]at org.jboss.pool.jdbc.xa.XAPoolDataSource.getConnection(XAPoolDataSource.java:165) [Client]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.getConnection(JDBCCommand.java:680) [Client]at org.jboss.ejb.plugins.jaws.jdbc.JDBCCommand.jdbcExecute(JDBCCommand.java:152) [Client]at org.jboss.ejb.plugins.jaws.jdbc.JDBCStoreEntityCommand.execute(JDBCStoreEntityCommand.java:97) [Client]at org.jboss.ejb.plugins.jaws.JAWSPersistenceManager.storeEntity(JAWSPersistenceManager.java:168) [Client]at org.jboss.ejb.plugins.CMPPersistenceManager.storeEntity(CMPPersistenceManager.java:424) [Client]at org.jboss.ejb.plugins.EntitySynchronizationInterceptor$InstanceSynchronization.beforeCompletion(EntitySynchronizationInterceptor.java:370) [Client]at org.jboss.tm.TxCapsule.doBeforeCompletion(TxCapsule.java:1210) [Client]at org.jboss.tm.TxCapsule.commit(TxCapsule.java:304) [Client]at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:76) [Client]at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:355) [Client]at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:99) [Client]at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:190) [Client]at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195) [Client]at org.jboss.ejb.EntityContainer.invoke(EntityContainer.java:338) [Client]at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPContainerInvoker.java:390) [Client]at java.lang.reflect.Method.invoke(Native Method) [Client]at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:241) [Client]at sun.rmi.transport.Transport$1.run(Transport.java:142) [Client]at java.security.AccessController.doPrivileged(Native Method) [Client]at sun.rmi.transport.Transport.serviceCall(Transport.java:139) [Client]at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:443) [Client]at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:643) [Client]at java.lang.Thread.run(Thread.java:484) --- jboss.jcml: - ?xml version=1.0 encoding=UTF-8? server !-- Classloading -- mbean code=org.jboss.web.WebService name=DefaultDomain:service=Webserver attribute name=Port8083/attribute /mbean !-- JNDI -- mbean code=org.jboss.naming.NamingService name=DefaultDomain:service=Naming attribute name=Port1099/attribute /mbean mbean code=org.jboss.naming.JNDIView name=DefaultDomain:service=JNDIView / !-- Transactions -- mbean code=org.jboss.tm.TransactionManagerService name=DefaultDomain:service=TransactionManager attribute name=TransactionTimeout300/attribute /mbean !-- JDBC -- mbean code=org.jboss.jdbc.JdbcProvider name=DefaultDomain:service=JdbcProvider attribute name=Driversorg.postgresql.Driver/attribute /mbean mbean code=org.jboss.mgt.ServerDataCollector name=Management:service=Collector attribute name=RefreshSleep5000/attribute /mbean mbean code=org.jboss.jdbc.XADataSourceLoader name=DefaultDomain:service=XADataSource,name=DefaultDS attribute name=Properties/attribute attribute name=PoolNameDefaultDS/attribute attribute
