[jboss-user] [JBoss Messaging Users] - Cannot insert duplicate key JBM_MSG_REF
I have a process as part of my application which generates large number of messages. During testing we encountered the exception below. From a clean start of JBoss we started the process which generated several thousand messages. Two minutes into the process we got this error. Previously we only encountered this problem when using 8 clustered JBoss instances clustered and then we addressed it by using non-consecutive Peer Ids. However in this instance there was only a single JBoss instance involved. A quick look online only brought us to a similar, yet different issue https://jira.jboss.org/jira/browse/JBMESSAGING-1062 which has already been fixed. Does anybody know if this is a know problem and fixed in the latest GA release. We are using JBoss 4.2.3 GA with JBoss Messaging 1.4.2.GA-SP1 Exception | 10:26:01,467 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 | 10:26:01,514 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009 | 10:26:01,514 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 3m:31s:994ms | 10:40:52,036 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,036 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,036 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,036 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,051 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,051 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:40:52,051 WARN [SpoolProcessorBean] spool cannot be deleted when status=CLOSED | 10:42:29,138 WARN [JDBCSupport] SQLException caught, SQLState 23000 code:2627- assuming deadlock detected, try:1 | java.sql.SQLException: Violation of PRIMARY KEY constraint 'PK__JBM_MSG_REF__2057CCD0'. Cannot insert duplicate key in object 'dbo.JBM_MSG_REF'. | at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) | at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) | at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224) | at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628) | at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525) | at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487) | at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:421) | at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95) | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365) | at org.jboss.messaging.core.impl.JDBCPersistenceManager$1HandleBeforePrepareRunner.doTransaction(JDBCPersistenceManager.java:1972) | at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474) | at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.executeWithRetry(JDBCSupport.java:512) | at org.jboss.messaging.core.impl.JDBCPersistenceManager.handleBeforePrepare(JDBCPersistenceManager.java:2063) | at org.jboss.messaging.core.impl.JDBCPersistenceManager$TransactionCallback.beforePrepare(JDBCPersistenceManager.java:2984) | at org.jboss.messaging.core.impl.tx.Transaction.prepare(Transaction.java:265) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:498) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at
[jboss-user] [JBoss Messaging Users] - Re: Cannot insert duplicate key JBM_MSG_REF
I restarted JBoss and ran the same process again, reproducing the same exception: These links refer to similar and maybe related issues and suggested using non-consecutive NodeIDs https://jira.jboss.org/jira/browse/JBMESSAGING-1682 View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4266727#4266727 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4266727 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0 Users] - NullPointerException using BLOBs with DB2 (Hibernate EJB3)
When trying to read a entity containing a BLOB from DB2 I get a NullPointerException. I haven't quite narrowed the exact size limit down, but it's about at 1MB. Content smaller then this barrier and there is no problem. My guess is that this is some strange driver issue, but searching the web has not produced any results. Using the same application with SQL Server 2005 works fine. I am using JBoss 4.2.3 with DB2 9.5. The type 4 driver breaks DB2 and causes it to shutdown, so I am using the type 2 driver. Any suggestion on what I could do to further narrow down are welcome. Thanks in advance Alex anonymous wrote : java.lang.NullPointerException | at com.ibm.db2.jcc.uw.UWConnection.a(UWConnection.java:959) | at com.ibm.db2.jcc.a.p.e(p.java:281) | at com.ibm.db2.jcc.t4.a.e(a.java:451) | at com.ibm.db2.jcc.a.gl.a(gl.java:4792) | at com.ibm.db2.jcc.a.eg.a(eg.java:292) | at com.ibm.db2.jcc.a.eg.b(eg.java:248) | at com.ibm.db2.jcc.a.ce.a(ce.java:277) | at com.ibm.db2.jcc.a.be.getBytes(be.java:99) | at com.ibm.db2.jcc.a.ce.getBytes(ce.java:136) | at org.hibernate.type.ByteArrayBlobType.get(ByteArrayBlobType.java:90) | at org.hibernate.type.AbstractLobType.nullSafeGet(AbstractLobType.java:46) | at org.hibernate.type.AbstractType.hydrate(AbstractType.java:81) | at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2096) | at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1380) | at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1308) | at org.hibernate.loader.Loader.getRow(Loader.java:1206) | at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:580) | at org.hibernate.loader.Loader.doQuery(Loader.java:701) | at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) | at org.hibernate.loader.Loader.doList(Loader.java:2220) | at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) | at org.hibernate.loader.Loader.list(Loader.java:2099) | at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378) | at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) | at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) | at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) | at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) | at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:64) | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4257874#4257874 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4257874 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Error on clustered nodes on startup
My cluster consist of 8 JBoss instances. Using JBoss Messaging 1.4.2 GA SP1 most things work fine, however every so often an exception is thrown while trying to insert a duplicate row into the JBM_TX table anonymous wrote : | 16:16:08,155 WARN [JDBCSupport] SQLException caught, SQLState 23000 code:2627- assuming deadlock detected, try:1 | java.sql.SQLException: Violation of PRIMARY KEY constraint 'PK__JBM_TX__0C46B282'. Cannot insert duplicate key in object 'dbo.JBM_TX'. | at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) | at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) | at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224) | at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628) | at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525) | at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487) | at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:421) | at org.jboss.resource.adapter.jdbc.CachedPreparedStatement.executeUpdate(CachedPreparedStatement.java:95) | at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365) | at org.jboss.messaging.core.impl.JDBCPersistenceManager.addTXRecord(JDBCPersistenceManager.java:2161) | at org.jboss.messaging.core.impl.JDBCPersistenceManager$1HandleBeforePrepareRunner.doTransaction(JDBCPersistenceManager.java:1953) | at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner2.execute(JDBCSupport.java:474) | I haven't found this issue reported anywhere else, but found some fixes relating to clustering in the release notes for 1.4.4. After upgrading to 1.4.4 I am no longer able to start all my cluster nodes. The following exception is reported during startup of either the 3rd or 4th node in the cluster. At this point this error happens while trying to deploy the examples without my own application being deployed. Tests with my own application produces similar results. anonymous wrote : | 14:05:58,688 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has | on how to do this. | 14:05:58,704 INFO [ServerPeer] JBoss Messaging 1.4.4.GA server [3] started | 14:05:58,750 INFO [STDOUT] | --- | GMS: address is 192.168.2.84:3820 | --- | 14:05:58,813 INFO [GroupMember] org.jboss.messaging.core.impl.postoffice.groupmember$controlmembershipliste...@4b83a223 got new view [192.168.2.81:3911|3] [192.168.2.81:3911, 192. | 14:05:58,813 INFO [GroupMember] I am (192.168.2.84:3820) | 14:05:58,829 INFO [GroupMember] New Members : 4 ([192.168.2.81:3911, 192.168.2.82:3969, 192.168.2.83:3767, 192.168.2.84:3820]) | 14:05:58,829 INFO [GroupMember] All Members : 4 ([192.168.2.81:3911, 192.168.2.82:3969, 192.168.2.83:3767, 192.168.2.84:3820]) | 14:05:59,454 INFO [STDOUT] | --- | GMS: address is 192.168.2.84:7900 | --- | 14:05:59,876 INFO [ConnectionFactory] Connector bisocket://192.168.2.84:4457 has leasing enabled, lease period 1 milliseconds | 14:05:59,876 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.connectionfact...@7578f526 started | 14:06:09,048 INFO [ConnectionFactory] Connector bisocket://192.168.2.84:4457 has leasing enabled, lease period 1 milliseconds | 14:06:09,048 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.connectionfact...@5430b40a started | 14:06:10,063 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has | on how to do this. | 14:06:10,313 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has | on how to do this. | 14:06:10,313 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has | on how to do this. | 14:06:40,158 ERROR [ExceptionUtil] org.jboss.jms.server.connectionfactory.connectionfact...@655fb6e0 startService | java.lang.IllegalStateException: org.jboss.messaging.core.impl.postoffice.groupmem...@3832c852 response not received from 192.168.2.81:3911 - there may be others | at org.jboss.messaging.core.impl.postoffice.GroupMember.multicastControl(GroupMember.java:268) | at
[jboss-user] [JBoss Messaging] - Re: JBM 1.4 and container transactions
Please have a look at this thread : http://www.jboss.org/index.html?module=bbop=viewtopict=137334 Using java:/JmsXA for both should give you the behaviour you are after. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4247594#4247594 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247594 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Error on clustered nodes on startup
Thanks Tim for the link. It doesn't explicitly list 1.4.2 GA SP1 as an affected version. Do you know if there is a batch to 1.4.2 or 1.4.4 available. I haven't seen the 1.4.5 build available for download, so I am assuming that's still to come. anonymous wrote : | Affects Version/s: 1.4.0.SP3.CP02, 1.4.0.SP3_CP03, 1.4.0.SP3.CP04, 1.4.0.SP3.CP05, 1.4.0.SP3.CP06, 1.4.0.SP3.CP07, 1.4.0.SP3.CP08, 1.4.4.GA | Fix Version/s: 1.4.5.GA, 1.4.0.SP3.CP09 | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4247600#4247600 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247600 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4 and container transactions
I am also using 1.4.2 GA SP1 and have found that using JmsXA works and support XA transactions, at the cost of distribution. It still distributes the messages once all beans in the pool on one node are exhausted. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4247604#4247604 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247604 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: JBM 1.4 and container transactions
I am injecting my connection factory using | @Resource(name = jms/ConnectionFactory) | protected ConnectionFactory m_factory; | and then in jboss.xml I am mapping it to the actual connection factory : | resource-ref | res-ref-namejms/ConnectionFactory/res-ref-name | jndi-namejava:/JmsXA/jndi-name | /resource-ref | You can of course also inject the JmsXA connection factory directly. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4247619#4247619 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247619 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Error on clustered nodes on startup
I had a look at this link : anonymous wrote : | It's in JIRA https://jira.jboss.org/jira/browse/JBMESSAGING-1682 | Does this only happen when consecutive numbers are used for NodeIDs. I am busy trying using 10, 20, 30 and 40 instead of 1,2,3 and 4 and so far have not encountered this issue. Also do you have any input on my problem with 1.4.4 ? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4247640#4247640 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4247640 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Defining a distributed / clustered queue
Do you have an example of how one create a clustered temporary queue. Maybe an explanation of why a standard clustered queue does not work. Not being able to receive responses in a consistent way on our external client it a major problem for us. I have had a look the distributed queue example, however this does something quite different to what we do in our application. Do you mean we must create a clustered temporary queue from the session like this : session.createTemporaryQueue(); This would break our entire design. Currently the client and the MDB are only coupled by the queue name which is pre-defined. Do you know if there is a bug / jira raised on this issue ? or do you have any further details on why this works the way it does. I am guessing this is affecting 4.3 EAP as well ? Grateful for any input on this. Regard Alex View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4245583#4245583 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4245583 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Defining a distributed / clustered queue
I have this issue with not being able to receive responses which I reported in this thread http://www.jboss.org/index.html?module=bbop=viewtopict=158725. In one of the responses the suggestion was made to define a distributed queue. I though this was done using the CLUSTERED=TRUE parameter in the jbm serivces XML file. Is there any additional configuration required ? The linked thread contains my example configuration. Thanks in advance Alex View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4245475#4245475 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4245475 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clustered messages not being received by external client
I am defining the destinations in abc-services.xml which is referenced in the jboss-app.xml file. Both these are included in the EAR file containing the MDBs. This application is deployed into the farm folder of the JBoss nodes in the cluster. My assumption is that since the destinations are set to be clustered and the application is deployed into the cluster wide farm folder JBoss would be able to figure it out. Any messages sent to JBoss are distributed across the clustered nodes, so it seems to work for receiving messaged inside JBoss. The JMX console also only shows a single destination, which is what I would have expected. | ?xml version=1.0 encoding=UTF-8? | server | ... | mbean code=org.jboss.jms.server.destination.QueueService | name=jboss.messaging.destination:service=Queue,name=Responses | xmbean-dd=xmdesc/Queue-xmbean.xml | attribute name=JNDINamequeue/abc/Responses/attribute | depends optional-attribute-name=ServerPeerjboss.messaging:service=ServerPeer/depends | dependsjboss.messaging:service=PostOffice/depends | attribute name=Clusteredtrue/attribute | /mbean | /server | The problem is only apparent when the receiving client is a stand-alone application running outside the application server. This is the code I use to receive the messages. | InitialContext jndiContext = new InitialContext(props); | | // connect to JNDI to get JMS Queue Factory | QueueConnectionFactory qFactory = (QueueConnectionFactory) jndiContext.lookup(ClusteredConnectionFactory); // e.g. javax.jms.QueueConnectionFactory | | | // look up and connect to Response Queue | System.out.println(Connecting to JMS Response Queue: + props.getProperty(jmsResponseQueue)); | Queue responseQ = (Queue) jndiContext.lookup(queue/abc/Responses); | QueueConnection responseQconn = qFactory.createQueueConnection(); | QueueSession responseQSession = responseQconn.createQueueSession(false, Session.AUTO_ACKNOWLEDGE); | QueueReceiver responseQrecv = responseQSession.createReceiver(responseQ); | System.out.println(Ready to receive messages); | responseQconn.start(); | | Message msg = responseQrecv.receive(6); | ... | Thanks in advance. Alex View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4244875#4244875 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244875 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clustered messages not being received by external client
Surely this can't be the case. It would be a big problem for me if I were not able to deliver outbound messages to external clients. It is not viable for the client to know which cluster node will respond. Not even sure if this is possible since the messages are distributed at random / round robin. Has this been resolved in release 2.x of JBoss Messaging and can I integrate that release into JBoss 4.2.3 / JBoss EAP ? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4244784#4244784 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4244784 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Clustered node keeps on processing after CTRL+C
Our cluster consist of 2 nodes and we are using JBoss 4.2.3 with JBoss Messaging 1.4.2.GA-SP1. Our application consists of a series of EJB3 message driven beans. When we submit a request to beans, they start processing. If we then press CTRL+C on the console on one of the nodes, the PostOffice is immediately switched over to the other node, which promptly re-processed the message. However the node on which we pressed CTRL+C continuous to process for a little while. This leads to two threads, one on each node doing the same, or very similar work which leads to duplication on the persistence tier. We have already added extra code to be able to resume the process and skip already complete items, however since two thread now process the same work, this happens continuously and my message is eventually abandoned to DLQ. Do you have any suggestions on how I could handle this situation better. Ideally I would like to stop the work on one node and have it continue / resume on the other node, however right now, it fails over to the other node, while continuing to process on the node which is stopping. This presents a rather interesting problem. I could keep state of the process in the database and set a stopping / stopped flag. However in case of a real failure (power / network etc), my code would not be executed and the flag would not be set. The same goes for locking the records which I am processing in the database. Any suggestions on this are appreciated. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4241148#4241148 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4241148 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Persistence, JBoss/CMP, Hibernate, Database] - Re: xa-datasource issue
I am having the same issue connecting to the same database using 3 datasources, one XA and two no-tx-datasources with different transaction isolation levels. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4232503#4232503 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232503 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Could not find new XAResource to use for recovering non-
Thanks. That worked View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4232509#4232509 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232509 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Oracle 10g with Jboss 4.2.3 Entity Manager / Hibernate
My application uses 3 different datasources all going to the same database. One with XA support is used via the JNDI name by the entity manager configured in persistence.xml. The other two are no-tx-datasources. I am able to access certain aspects using the datasources however as soon as I try to make a change via entity manager I get the error shown below. Any suggestions on what I am doing wrong. The same application works fine using SQL Server 2005. anonymous wrote : | 4:47:40,170 INFO [ConnectionProviderFactory] Initializing connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider | 4:47:40,170 INFO [InjectedDataSourceConnectionProvider] Using provided datasource | 4:47:40,342 INFO [SettingsFactory] RDBMS: Oracle, version: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production | ith the Partitioning, OLAP, Data Mining and Real Application Testing options | 4:47:40,342 INFO [SettingsFactory] JDBC driver: Oracle JDBC driver, version: 10.2.0.4.0 | 4:47:40,389 INFO [Dialect] Using dialect: org.hibernate.dialect.Oracle10gDialect | 4:47:40,404 INFO [TransactionFactoryFactory] Transaction strategy: org.hibernate.ejb.transaction.JoinableCMTTransactionFactory | 4:47:40,404 INFO [TransactionManagerLookupFactory] instantiating TransactionManagerLookup: org.hibernate.transaction.JBossTransactionManagerLookup | 4:47:40,420 INFO [TransactionManagerLookupFactory] instantiated TransactionManagerLookup and then later anonymous wrote : | 14:47:48,920 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009 | 14:47:48,951 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 1m:4s:969ms | 14:48:03,342 WARN [PageNotFound] No mapping for [/diagnostics/spring/j_security_check] in DispatcherServlet with name 'thunderhead' | 14:48:35,092 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: null | 14:48:35,092 ERROR [JDBCExceptionReporter] Transaction is not active: tx=TransactionImple ac, BasicAction: -3f57fdd7:cf6:4a155b48:d1 status: ActionStatus.ABORT_ONLY ; - nested throwable: (javax.resource.ResourceException: Transaction is not active: tx=TransactionImple ac, BasicAction: -3f57fdd7 | :cf6:4a155b48:d1 status: ActionStatus.ABORT_ONLY ) | 14:48:35,092 INFO [DefaultLoadEventListener] Error performing load command | org.hibernate.exception.GenericJDBCException: Cannot open connection | at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) | at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) | at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) | at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29) | at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:426) | at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144) | at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:139) | at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1547) | at org.hibernate.loader.Loader.doQuery(Loader.java:673) | at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) | at org.hibernate.loader.Loader.loadEntity(Loader.java:1860) | at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) | at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) | at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044) | at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395) | at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375) | at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139) | at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195) | at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) | at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) | at org.hibernate.impl.SessionImpl.get(SessionImpl.java:815) | at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4232512#4232512 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232512 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: @PersistenceContext annotation in an abstract superclass
I know this thread goes back quite a while. Yet I am facing the same issue. I have declared and inject a PersistenceContact in an abstract superclass, which is extended by serveral concrete MDBs and SLSBs. However when I deploy this I get the following error : anonymous wrote : | ObjectName: jboss.j2ee:ear=ThunderheadEJB.ear,jar=ThunderheadEJB.jar,name=BatchJobListener,service=EJB3 | | State: FAILED | | Reason: java.lang.RuntimeException: An exception occurred initialising interceptors for class com.thunderhead.backend. | | jobs.BatchJobListener.init | | I Depend On: | | persistence.units:ear=ThunderheadEJB.ear,jar=ThunderheadEJB.jar,unitName=entityManager | | | | ObjectName: jboss.j2ee:ear=ThunderheadEJB.ear,jar=ThunderheadEJB.jar,name=BinListener,service=EJB3 | | State: FAILED | | Reason: java.lang.RuntimeException: An exception occurred initialising interceptors for class com.thunderhead.backend. | | jobs.BinListener.init | | I Depend On: | persistence.units:ear=ThunderheadEJB.ear,jar=ThunderheadEJB.jar,unitName=entityManager | any ideas if this is supposed to work. I am aware of the work around to declare an abstract getter in the superclass, and then inject in the concrete subclasses and access the injected context via the getter. It would be nice to to be able to inherit the injected Persistence Context though, which as Bill suggests, seems to be possible. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4182082#4182082 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4182082 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Security JAAS/JBoss] - Kerberos / JBoss Negotiate issues and questions
I have deployed JBoss Negotiate onto JBoss 4.2.3. Initially I tried to create the server users account using a generic name such as JBoss instead of the hostname of the machine. I couldn't get this working. After creating a username whose name matched the hostname of the JBoss server I was able to complete the Basic Negotiation and the Security Domain Test from another client. I am still not able to perform those from the server itself. IE works from the other clients, but neither IE, nor Firefox work on my client. I read some suggestions to clear the cache, but I haven't found instructions on doing this. When I try the Secured test I get the exception below. I wonder if there is a problem on my system which also runs the JBoss server which could be causing this ? | 09:54:39,905 TRACE [UsersRolesLoginModule] Properties file=file:/C:/jboss-4.2.3.GA/server/default/conf/props/spnego-roles.properties, defaults=null | 09:54:39,905 DEBUG [UsersRolesLoginModule] Loaded properties, users=[operator, [EMAIL PROTECTED], [EMAIL PROTECTED], user, [EMAIL PROTECTED], [EMAIL PROTECTED], other, [EMAIL PROTECTED], [EMAIL PROTECTED], sysop] | 09:54:39,905 TRACE [UsersRolesLoginModule] abort | 09:54:39,920 TRACE [SPNEGO] Login failure | javax.security.auth.login.LoginException: Continuation Required. | at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:156) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) | at javax.security.auth.login.LoginContext.login(LoginContext.java:579) | at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603) | at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344) | at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491) | at org.jboss.security.negotiation.spnego.SPNEGOAuthenticator.authenticate(SPNEGOAuthenticator.java:103) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | 09:54:40,030 TRACE [SPNEGO] End isValid, false | 09:54:40,030 DEBUG [SPNEGOAuthenticator] authenticated principal = null | 09:54:40,030 TRACE [SPNEGOContext] clear 31752641 | 09:54:40,030 TRACE [SecurityAssociation] clear, server=true | 09:54:40,045 TRACE [SPNEGOAuthenticator] Authenticating user | 09:54:40,045 INFO [SPNEGOAuthenticator] Header - Negotiate oYIF2zCCBdeiggXTBIIFz2CCBcsGCSqGSIb3EgECAgEAboIFujCCBbagAwIBBaEDAgEOogcDBQAgo4IE5WGCBOEwggTdoAMCAQWhChsIVEguTE9DQUyiITAfoAMCAQKhGDAWGwRI | ... | 0xcf 0x0e 0x1a 0x1b 0xbd 0xaa 0xa1 0x63 | 09:54:40,546 DEBUG [SPNEGOLoginModule] Creating new GSSContext. | 09:54:40,686 TRACE [SPNEGOLoginModule] Result - GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC) | 09:54:40,686 ERROR [SPNEGOLoginModule] Unable to authenticate | GSSException: Failure unspecified at GSS-API level (Mechanism level: Invalid argument (400) - Cannot find key of appropriate type to decrypt AP REP - RC4 with HMAC) | at
[jboss-user] [Security JAAS/JBoss] - Re: Kerberos / JBoss Negotiate issues and questions
One of the problems was that I did not install the latest tools from http://go.microsoft.com/fwlink/?LinkId=100114 The default tools used DES-CBC-MD5 and also set DES-only encryption on the account. After installing the updated tools the ktpass command completed as shown in the user guide. I disable DES on the user account and re-ran the ktpass and ktab command. After restarting JBoss I am still not able to complete the secure test. The following exception is raised. anonymous wrote : | 14:24:20,835 TRACE [UsersRolesLoginModule] abort | 14:24:20,835 TRACE [SPNEGO] Login failure | javax.security.auth.login.LoginException: Continuation Required. | at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:156) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) | at javax.security.auth.login.LoginContext.login(LoginContext.java:579) | at org.jboss.security.plugins.JaasSecurityManager.defaultLogin(JaasSecurityManager.java:603) | at org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:537) | at org.jboss.security.plugins.JaasSecurityManager.isValid(JaasSecurityManager.java:344) | at org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:491) | at org.jboss.security.negotiation.spnego.SPNEGOAuthenticator.authenticate(SPNEGOAuthenticator.java:103) | at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:490) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | 14:24:20,944 TRACE [SPNEGO] End isValid, false | 14:24:20,960 DEBUG [SPNEGOAuthenticator] authenticated principal = null | 14:24:20,960 TRACE [SPNEGOContext] clear 20096223 | 14:24:20,960 TRACE [SecurityAssociation] clear, server=true | 14:24:20,975 TRACE [SPNEGOAuthenticator] Authenticating user | ... | 14:24:21,507 TRACE [SPNEGOLoginModule] Result - java.io.IOException: Unexpected message type | 14:24:21,507 ERROR [SPNEGOLoginModule] Unable to authenticate | java.io.IOException: Unexpected message type | at org.jboss.security.negotiation.spnego.encoding.NegTokenTargDecoder.decodeNegTokenTargSequence(NegTokenTargDecoder.java:121) | at org.jboss.security.negotiation.spnego.encoding.NegTokenTargDecoder.decode(NegTokenTargDecoder.java:137) | at org.jboss.security.negotiation.spnego.SPNEGOLoginModule$AcceptSecContext.run(SPNEGOLoginModule.java:261) | at java.security.AccessController.doPrivileged(Native Method) | at javax.security.auth.Subject.doAs(Subject.java:337) | at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:113) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) | at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) | at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) | at
[jboss-user] [JBoss Messaging] - NullPointerException during commit / persist
We have recently upgraded to Jboss 4.2.3. During one of our tests I received the following exception. I am not sure what to make from it. Any suggestions where to start looking at the cause of this. I am not able to reproduce it yet. anonymous wrote : | 11:07:51,321 ERROR [ServerInvokerCallbackHandler] Error handling callback | java.lang.NullPointerException | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.persistCallback(ServerInvokerCallbackHandler.java:863) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallback(ServerInvokerCallbackHandler.java:751) | at org.jboss.remoting.callback.ServerInvokerCallbackHandler.handleCallbackOneway(ServerInvokerCallbackHandler.java:697) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.performDelivery(ServerSessionEndpoint.java:1432) | at org.jboss.jms.server.endpoint.ServerSessionEndpoint.handleDelivery(ServerSessionEndpoint.java:1344) | at org.jboss.jms.server.endpoint.ServerConsumerEndpoint.handle(ServerConsumerEndpoint.java:322) | at org.jboss.messaging.core.impl.RoundRobinDistributor.handle(RoundRobinDistributor.java:119) | at org.jboss.messaging.core.impl.MessagingQueue$DistributorWrapper.handle(MessagingQueue.java:582) | at org.jboss.messaging.core.impl.ClusterRoundRobinDistributor.handle(ClusterRoundRobinDistributor.java:79) | at org.jboss.messaging.core.impl.ChannelSupport.deliverInternal(ChannelSupport.java:606) | at org.jboss.messaging.core.impl.MessagingQueue.deliverInternal(MessagingQueue.java:505) | at org.jboss.messaging.core.impl.ChannelSupport$InMemoryCallback.afterCommit(ChannelSupport.java:935) | at org.jboss.messaging.core.impl.tx.Transaction.commit(Transaction.java:228) | at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:490) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) | at sun.reflect.GeneratedMethodAccessor467.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N326865078927536.invokeNext(ConnectionAdvised$sendTransaction_N326865078927536.java) | at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.sendTransaction(ConnectionAdvised.java) | at org.jboss.jms.wireformat.ConnectionSendTransactionRequest.serverInvoke(ConnectionSendTransactionRequest.java:82) | at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) | at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.remoting.Client.invoke(Client.java:536) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189) | at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160) | at org.jboss.jms.client.delegate.ClientConnectionDelegate.org$jboss$jms$client$delegate$ClientConnectionDelegate$sendTransaction$aop(ClientConnectionDelegate.java:221) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92) | at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) | at org.jboss.jms.client.delegate.ClientConnectionDelegate$sendTransaction_N326865078927536.invokeNext(ClientConnectionDelegate$sendTransaction_N326865078927536.java) | at
[jboss-user] [JBoss Messaging] - Integrating Websphere MQ with JBoss
I have deployed the JCA Resource Adaptor for Websphere MQ on JBoss and able to
pull messages of a queue. However currently the MQ hostname is configured
either via annotations as shown below. Since I also specify these setting in
the wmq.jmsra-ds.xml file (see below) I was hoping to proxy the MQQueue and
access it as an standard jms destination. This would allow me to keep my code
and descriptors separate from the MQ configuration (Queue Manager, Hostname,
Port etc). However trying this I got
anonymous wrote :
| java.lang.ClassCastException: com.ibm.mq.jms.MQQueue cannot be cast to
org.jboss.jms.destination.JBossDestination
| at
org.jboss.jms.client.container.SessionAspect.handleCreateConnectionConsumer(SessionAspect.java:737)
| at
org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect1.invoke(SessionAspect1.java)
After adding the reference to the resource adaptor used (wmq.jmsra.rar) back
in, this problem disappeared, but it ask for the MQ configuration again.
Ideally I would like to configure the MQ Queue / ConnectionFactory in the
application server and access it from my application as a standard JMS
destination. This would allow me to keep my code portable.
If you have any suggestion on how this can be achieved, please let me know.
Thanks in advance
Alex
| @MessageDriven(name = MQRequestListener, activationConfig = {
| @ActivationConfigProperty(propertyName = acknowledgeMode,
propertyValue = Auto-acknowledge),
| @ActivationConfigProperty(propertyName = maxSession, propertyValue =
10),
| @ActivationConfigProperty(propertyName = subscriptionDurability,
propertyValue = Non-Durable),
| @ActivationConfigProperty(propertyName = destinationType,
propertyValue = javax.jms.Queue),
| @ActivationConfigProperty(propertyName = destination, propertyValue =
queue/thunderhead/MQRequests)
| @ActivationConfigProperty(propertyName = channel, propertyValue =
SYSTEM.DEF.SVRCONN),
| @ActivationConfigProperty(propertyName = hostName, propertyValue =
zeta),
| @ActivationConfigProperty(propertyName = port, propertyValue =
5001),
| })
| @org.jboss.annotation.ejb.ResourceAdapter(value=wmq.jmsra.rar)
|
or in the deployment descriptor :
| ...
| activation-config-property
|
activation-config-property-namedestinationType/activation-config-property-name
|
activation-config-property-valuejavax.jms.Queue/activation-config-property-value
| /activation-config-property
| activation-config-property
|
activation-config-property-namedestination/activation-config-property-name
|
activation-config-property-valueWASQueue1/activation-config-property-value
| /activation-config-property
| activation-config-property
|
activation-config-property-namechannel/activation-config-property-name
|
activation-config-property-valueSYSTEM.DEF.SVRCONN/activation-config-property-value
| /activation-config-property
| activation-config-property
|
activation-config-property-namehostName/activation-config-property-name
|
activation-config-property-valuezeta/activation-config-property-value
| /activation-config-property
| activation-config-property
| activation-config-property-nameport/activation-config-property-name
|
activation-config-property-value5001/activation-config-property-value
| /activation-config-property
| activation-config-property
|
activation-config-property-namequeueManager/activation-config-property-name
|
activation-config-property-valueQM_Thunderhead/activation-config-property-value
| /activation-config-property
| activation-config-property
|
activation-config-property-nametransportType/activation-config-property-name
|
activation-config-property-valueCLIENT/activation-config-property-value
| /activation-config-property
| ...
|
WebSphere MQ adaptor configuration
| ?xml version=1.0 encoding=UTF-8?
|
| connection-factories
|
| !-- mbeans defining JCA administered objects --
| mbean code=org.jboss.resource.deployment.AdminObject
name=jboss.jca:service=WASDestination,name=MQRequests
|
| !-- Bind this AdminObject with the JNDI name IVTQueue --
| attribute name=JNDINamequeue/thunderhead/MQRequests/attribute
|
| !-- this MBean depends on the WebSphere MQ resource adapter --
| depends
optional-attribute-name=RARNamejboss.jca:service=RARDeployment,name='wmq.jmsra.rar'/depends
|
| !-- this admin object is a javax.jms.Queue --
| attribute name=Typejavax.jms.Queue/attribute
|
| !--
| Configuration for Queue TEST.QUEUE on queue manager ExampleQM. All
messages sent
| to this queue will have their expiry time overridden so that
messages never expire
| --
| attribute name=Properties
| baseQueueManagerName=QM_Thunderhead
| baseQueueName=WASQueue1
|
[jboss-user] [JBoss Messaging] - Re: ClusteredConnectionFactory vs JmsXA
timfox wrote : | Using a clustered connection factory means subsequent create connection attempts will round robin - this is typically not what you want with MDBs. | But this is exactly what we want. We would like our messages to be distributed using RoundRobin accross the nodes in the cluster. Does that mean I should change the default connection factory used in hajndi-jms-ds.xml to ClusteredXAConnectionFactory? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4158643#4158643 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158643 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: ClusteredConnectionFactory vs JmsXA
In our case we have one message coming into the cluster from an external JMS client. This message is then processed by a chain of MDB. Each node in the cluster has the same MDBs deployed. (Like you said). Our problem is that one incoming message results in several (sometimes 100 / 1000) individual messages to be send to the other MDBs in the chain. So one message comes in, and many go to the next MDB. The current behavior we are observing is hat messages only get distributed to other nodes in the cluster, when the local bean pool is exhausted. I appreciate the overhead of always distributing messages to other nodes, but would like to verify that this behavior is as intended and if there are any configuration options I can use to alter it. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4158692#4158692 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158692 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: ClusteredConnectionFactory vs JmsXA
That depends how one looks at it. I completely accept your argument on using resources optimally. However the bean pool size might not be the best measure. If we deploy our application onto a cluster of nodes using single core CPU, a smaller bean pool is required to get optimal distribution, while if each node were a fancy quad core, a large bean pool would work just as well. I was hoping for an option to always distribute the work on a round robin basis. This would allow me to configure a standard bean pool, aiming to prevent overloading the system, rather then tuning the been pool size according to the hardware configuration of the cluster. Maybe I misunderstand how load and idle periods are determined. Just from my observation it seems to be driven by the pool size. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4158823#4158823 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4158823 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: ClusteredConnectionFactory vs JmsXA
I see your point now. Do you have any further information on why the message distribution when using JmsXA differs from ClusteredXAConnectionFactory ? I am observing that messages are only distributed to other nodes in the cluster once the MDB pool is exhausted. Is this the correct / intended behaviour ? Are there any configuration options to alter the message distribution between nodes ? Thanks in advance View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157898#4157898 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157898 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Could not find new XAResource to use for recovering non-
No, not yet View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157727#4157727 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157727 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - ClusteredConnectionFactory vs JmsXA
My application consists of a number of EJB3 MDBs, which pull messages off a number of queues and topics. The application is deployed on a cluster of 2 identical nodes. I have installed JBM 1.4(SP3) on JB 4.2.2. When I inject the ClusteredXAConnectionFactory the application work, but the messages are not treated i the same transaction as the rest of the work done in my MDB. For example, I would like to persist an Entity as well as forward a message to anther MDB. The other MDB is dependent on the entity being persistent and available in the database. However with ClusteredXAConnectionFactory it seems that message is sent outside the transactional context. Rather frequently it happens that the message arrives at the next bean, but the persistence has't finnished. The messages are however distributed evenly across both nodes. After a little research online, I found several posts suggestion to use JmsXA instead of ClusteredXAConnectionFactory. This resolved my transaction problem nicely, however since the switch the messages are no longer distributed evenly. It seems to only use the other node, when all MDBs in the pool on one node are exhausted. I am wondering if this is by design, as clustered XA transactions must be quite expensive, surely. So maybe messages are only distributed to the other nodes when one nodes bean pool is exhausted. Please let me know if this is the correct behaviour, or what I should look at to correct the distribution. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157742#4157742 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157742 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Clearing up confussion
Maybe I didn't explain is correctly. I am sending a message as well as persisting and entity. Since I would like to use XA, I'd expect both to succeed. For this to be the case the entity should be persisted and the message should be placed on the queue. However the message is already being received on the other end by the next bean, while the entity is not yet persisted. I am not too concerned about the order these happen in, as long as they happen as one unit of work. As soon as I use the JmsXA factory this problem goes away, which seem to me like the correct behaviour. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157787#4157787 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157787 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Clearing up confussion
But then it wouldn't be atomic, nor consistent or durable. What happens in this case if 3 should fail and the transaction has to be rolled back ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4157792#4157792 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157792 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Using custom principal class with JBossWS
I would like to use my own Principal class with my own LoginModule. I
configured the LoginModule in login-config.xml and annotated by SLSB as follows
:
| @Stateless(name=JobAPIWeb)
| @WebService(name=JobAPIWeb, portName=...Port,
serviceName=JobAPIWebService, targetNamespace=...)
| @EndpointConfig(configName = Standard WSSecurity Endpoint)
| @SecurityDomain(value=THZone)
| @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use =
SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.BARE)
| public class JobAPIWeb implements JobAPIWebRemote {
| ...
|
Authentication takes place, however when I try to access the principal via
| m_sessionContext.getCallerPrincipal().getClass().getName()
|
it presents me with a org.jboss.ws.extensions.security.SimplePrincipal, rather
then my own class returned in the LoginModules commit method.
My search so far led me to ReceiveUsernameOperation in which the UserNameToken
is converted to a SimplePrincipal.
http://fisheye.jboss.com/browse/JBossWS/trunk/jbossws-core/src/main/java/org/jboss/ws/extensions/security/ReceiveUsernameOperation.java?r=4023
Are there any configuration options which would allow me to access the
principal object as it is returned by my LoginModule.
Thanks in advance.
Alex
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4133910#4133910
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4133910
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Timer Service
could you please also post the table definition for the TIMERS table. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4128384#4128384 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4128384 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: ClassCastException within an EAR deployment
Maybe have a look at the EJB3 specification Section EE 8.2. It describes the mechanism for packaging utility classes within EAR files. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4128381#4128381 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4128381 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Inherit @Resources fails
I would like to enherit common resources from an abstract superclass
| public abstract class AbstractManagedBean {
|@Resource(name = jms/ConnectionFactory)
|protected ConnectionFactory m_factory;
|@Resource(name = topic/thunderhead/ConsoleMessages)
|protected Topic m_consoleMessagesTopic;
| }
|
In the ejb-jar.xml and jboss.xml files I have added the appropriate
declarations for all concrete subclasses of this class.
ejb-jar.xml
| !-- JobRequest Listener MDB --
| message-driven
| ejb-nameJobRequestListener/ejb-name
| ejb-classcom.thunderhead.backend.jobs.JobRequestListener/ejb-class
| message-destination-linkJobRequests/message-destination-link
| !--Inherited From AbstractManagedBean --
| resource-ref
| res-ref-namejms/ConnectionFactory/res-ref-name
| res-typejavax.jms.ConnectionFactory/res-type
| res-authContainer/res-auth
| /resource-ref
| message-destination-ref
|
message-destination-ref-nametopic/thunderhead/ConsoleMessages/message-destination-ref-name
| message-destination-typejavax.jms.Topic/message-destination-type
| message-destination-usageProduces/message-destination-usage
| message-destination-linkConsoleMessages/message-destination-link
| /message-destination-ref
| !--Local Resources --
| /message-driven
|
jboss.xml
| !-- Job Request Listener MDB --
| message-driven
| ejb-nameJobRequestListener/ejb-name
|
destination-jndi-namequeue/thunderhead/JobRequests/destination-jndi-name
| !--Inherited From AbstractManagedBean --
| resource-ref
| res-ref-namejms/ConnectionFactory/res-ref-name
| jndi-namejava:/JmsXA/jndi-name
| /resource-ref
| message-destination-ref
|
message-destination-ref-nametopic/thunderhead/ConsoleMessages/message-destination-ref-name
| message-destination-typejavax.jms.Topic/message-destination-type
| message-destination-usageProduces/message-destination-usage
| message-destination-linkConsoleMessages/message-destination-link
|
jndi-namejnp://localhost:1100/topic/thunderhead/ConsoleMessages/jndi-name
| /message-destination-ref
| !--Local Resources --
| /message-driven
|
However during deployment the following errors are reported. Any ideas what I
have to add to the deployment descriptors to get this working. Since it's an
abstract bean it doesn't seem to make sense to add it.
I have already tried changing the @Resource annotation to use mappedName and
this resolves the problem, however I need to defer the mapping to the real
JNDI name to the deployment descriptor, as java:/JmsXA only works with JBoss
and not other application servers.
anonymous wrote :
| java.lang.RuntimeException: You did not specify a @Resource.mappedName() on
protected javax.jms.Topic
com.thunderhead.backend.AbstractManagedBean.m_consoleMessagesTopic and there is
no binding for enc name env/topic/thunderhead/ConsoleMessages in XML
| at
org.jboss.injection.ResourceHandler.handlePropertyAnnotation(ResourceHandler.java:506)
| at
org.jboss.injection.ResourceHandler.handleFieldAnnotations(ResourceHandler.java:325)
| at
org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:137)
| at
org.jboss.injection.InjectionUtil.processFieldAnnotations(InjectionUtil.java:143)
| at
org.jboss.injection.InjectionUtil.processAnnotations(InjectionUtil.java:174)
| at
org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:358)
| at
org.jboss.ejb3.SessionContainer.processMetadata(SessionContainer.java:140)
| at
org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:292)
| at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:356)
| at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
| at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at
[jboss-user] [Clustering/JBoss] - Load Balancing Policy
I am trying to get an application deployed on a cluster of 3 machines of different configuration. Once of the machines is a QuadCore and the others a P4's. When I submit a large number of messages to the cluster both P4 are running at 100% CPU utilisation which the QuadCode is merely sitting at 25% utilisation. It seems that every node in the cluster is allocated the same number of messages on a Round Robin basis. In Chapter 8 on the 1.3 documentation there are several configuration options available. http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.3.0.GA/html/c_configuration.html However in 1.4 none of these options are included in the documentation. http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP1/html/configuration.html#conf.connectionfactory.attributes.loadbalancingfactory What is the best method to configure a load balanceing policy for clusters like the one I am working on. thanks in advance Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4112517#4112517 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4112517 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Basic Authentication with WSSecureEndpoint on JBoss 4.2.
I think in the end I had to make changes in my LoginModule for it to work. This
is my complete login module.
Hope it helps
Alex
/*
| * SimpleLoginModule.java
| *
| * Created on 24 June 2005, 10:45
| *
| */
| package com.thunderhead.backend.security;
| import java.io.IOException;
| import java.security.acl.Group;
| import java.util.Map;
| import javax.security.auth.Subject;
| import javax.security.auth.callback.Callback;
| import javax.security.auth.callback.CallbackHandler;
| import javax.security.auth.callback.NameCallback;
| import javax.security.auth.callback.PasswordCallback;
| import javax.security.auth.callback.UnsupportedCallbackException;
| import javax.security.auth.login.LoginException;
| import javax.security.auth.spi.LoginModule;
|
| /**
| *
| * pCopyright: Copyright (c) 2007/p
| * pCompany: Thunderhead/p
| * @author ahartner
| * @version 1
| */
| public class SimpleLoginModule implements LoginModule {
| private Subject m_subject;
| private CallbackHandler m_callbackHandler;
| private String m_userid;
| private String m_password;
|
| /**
|* Creates a new instance of SimpleLoginModule
|*/
| public SimpleLoginModule() {
| }
|
| public boolean abort() throws LoginException {
| return true;
| }
|
| public boolean commit() throws LoginException {
| JAASUser user = new JAASUser(1,m_userid);
|
| Group grp = new JAASGroup(Roles);
| grp.addMember(new JAASRole(friend));
| grp.addMember(new JAASRole(friends));
|
| m_subject.getPrincipals().add(user);
| m_subject.getPrincipals().add(grp);
| return true;
| }
|
| public void initialize(Subject subject, CallbackHandler callbackHandler,
Map state, Map options) {
| m_subject = subject;
| m_callbackHandler=callbackHandler;
| }
|
| public boolean login() throws LoginException {
| NameCallback nameCallback = new NameCallback(User Name);
| PasswordCallback passwordCallback = new PasswordCallback(User
Password, false);
| Callback[] callbacks = new Callback[2];
| callbacks[0] = nameCallback;
| callbacks[1] = passwordCallback;
| try {
| m_callbackHandler.handle(callbacks);
| } catch (UnsupportedCallbackException ex) {
| ex.printStackTrace();
| } catch (IOException ex) {
| ex.printStackTrace();
| }
| try {
| if (nameCallback.getName() != null) {
| m_userid = nameCallback.getName();
| }
| if (passwordCallback.getPassword() != null) {
| m_password = new String(passwordCallback.getPassword());
| }
| passwordCallback.clearPassword();
| } catch (Exception e) {
| e.printStackTrace();
| }
| if (!m_userid.equals(user) || !m_password.equals(password))
| {
| return false;
| }
| else
| {
| return true;
| }
| }
|
| public boolean logout() throws LoginException {
| m_subject.getPrincipals().clear();
| return true;
| }
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4110914#4110914
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110914
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Load Balance EJB3 MDB in cluster
I am trying to get an application deployed on a cluster of 3 machines of different configuration. Once of the machines is a QuadCore and the others a P4's. When I submit a large number of messages to the cluster both P4 are running at 100% CPU utilisation which the QuadCode is merely sitting at 25% utilisation. It seems that every node in the cluster is allocated the same number of messages on a Round Robin basis. What is the best method to configure a load balanceing policy for clusters like the one I am working on. I am using JBoss 4.2.2 and EJB3 MDBs. thanks in advance Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4110916#4110916 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4110916 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Configure Queue Max Depth
But this configuration option says that messages beyound the set value will be dropped. Ideally I would like the JMS client to block and wait until there is space in the Queue again. anonymous wrote : 6.6.3.1.10. MaxSize | | A maximum size (in number of messages) can be specified for a topic subscription. Any messages that arrive beyond this point will be dropped. The default is -1 which is unbounded. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109380#4109380 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109380 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Configure Queue Max Depth
In Jboss MQ there was an option to configure the max depth of a queue as well as various others, such as InMemory. http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigQueue Is there similar options available on JBoss Messaging and where can I find them. I already searched the manual for the depth configuration, but it seems that this feature has been replaced with the new paging mechanism. Thanks Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109357#4109357 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109357 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Load Balancing Policy
I am trying to get an application deployed on a cluster of 3 machines of different configuration. Once of the machines is a QuadCore and the others a P4's. When I submit a large number of messages to the cluster both P4 are running at 100% CPU utilisation which the QuadCode is merely sitting at 25% utilisation. It seems that every node in the cluster is allocated the same number of messages on a Round Robin basis. In Chapter 8 on the 1.3 documentation there are several configuration options available. http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.3.0.GA/html/c_configuration.html However in 1.4 none of these options are included in the documentation. http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/userguide-1.4.0.SP1/html/configuration.html#conf.connectionfactory.attributes.loadbalancingfactory What is the best method to configure a load balanceing policy for clusters like the one I am working on. thanks in advance Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4109332#4109332 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4109332 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: MDB pool configuration EJB3
I am having a problem following your suggestion. I increased by session size to 20 using : @ActivationConfigProperty(propertyName = maxSession, propertyValue = 20 but now I get the following exception : anonymous wrote : Failed to acquire the pool semaphore, strictTimeout=1 A search on the forum suggestion that I need to increase my MDB pool size to boyond the number of the sessions. http://www.jboss.org/index.html?module=bbop=viewtopict=58293 However you suggest that this is not the way to go. I tried it and it didn't work. It complained about the jboss.xml file not being correct. Is there another solution to the Failed to acquire the pool semaphore, strictTimeout=1 ? Thanks Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4107064#4107064 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4107064 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Beginners Corner] - Application Specific Log4J configuration
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged. Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR. In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100679#4100679 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100679 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Installation, Configuration DEPLOYMENT] - Application Specific Log4J configuration
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged. Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR. In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100677#4100677 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100677 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Clustering/JBoss] - Clustered Logging using Log4J
I would like to consolidate all log messages from several nodes into a central database. At first I tried using the JMSAppender, but quickly ran into problems during startup. As the Appender is initiallised pretty early on in the startup sequence the Topic has not yet been created which result in nothing being logged. Since I am only really interested in the log messages originating from my application I though about packaging log4j together with my application. I tried added the log4j.jar file to the ear and modify the manifest of the EAR as well as the JAR. In the end I could not get this working either. It seems to me that I would have to implement my own buffered appender to store messages until a connection to the database (or the topic) is available. This feels a bit like re-inventing the wheel. Please let me know if there is a better (more generic) solution. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4100675#4100675 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4100675 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: UsernameToken and Basic Auth
Thanks this worked. Added the xml file below to my EJB3 jar file resolved my problem. | ?xml version=1.0 encoding=UTF-8? | jboss-ws-security xmlns=http://www.jboss.com/ws-security/config; |xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; | xsi:schemaLocation=http://www.jboss.com/ws-security/config http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd; | config | username/ | /config | /jboss-ws-security | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098710#4098710 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098710 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: UsernameToken and Basic Auth
I have specified the loginModule to use via @SecurityDomain(value=THZone) in my bean. I have also configured the login module in login-config.xml as shown below. I am not able to log in and authenticate, but the roles are not passed through. Where can I configure how the roles are obtained. @RolesAllowed(friends) or System.out.println(Principal is a friend :+context.isUserInRole(friends)); Currently don't seem to work. I also tried to implement my own login module return my own implementations of Principal and had the same problem as using the org.jboss.security.auth.spi.UsersRolesLoginModule on. The results are that the principal is passed through and accessible through the context, but the roles are not. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098717#4098717 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098717 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Security JAAS/JBoss] - Re: Custom Principal propagation
How do you do this. What files to you configure for this. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098723#4098723 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098723 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Security JAAS/JBoss] - Accessing Roles from Custom LoginModule return NULL
I have implemented my own login module and configure the login-config.xml file.
I am able to authenticate users. However when I try to access the principal's
roles it always returns null. Tomcat requires the developer to configure
different classes for users and roles and uses the class to differentiate.
However in JBoss I have not found the configuration for this. I am trying to
use this LoginModule to secure web servers and ejb's.
I am guessing that this is my problem.
| import java.io.IOException;
| import java.security.acl.Group;
| import java.util.Map;
| import javax.security.auth.Subject;
| import javax.security.auth.callback.Callback;
| import javax.security.auth.callback.CallbackHandler;
| import javax.security.auth.callback.NameCallback;
| import javax.security.auth.callback.PasswordCallback;
| import javax.security.auth.callback.UnsupportedCallbackException;
| import javax.security.auth.login.LoginException;
| import javax.security.auth.spi.LoginModule;
| import org.apache.log4j.Logger;
|
| public class SimpleLoginModule implements LoginModule {
| private Logger logger = Logger.getLogger(SimpleLoginModule.class);
| private Subject subject;
| private CallbackHandler callbackHandler;
|
| public SimpleLoginModule() {
| logger.info(Constructed new CIELogingModule);
| }
|
| public boolean abort() throws LoginException {
| logger.info(Aborted);
| return true;
| }
|
| public boolean commit() throws LoginException {
| logger.info(Granted Permissions);
| return true;
| }
|
| public void initialize(Subject subject, CallbackHandler callbackHandler,
Map state, Map options) {
| logger.info(Initialise : +options);
| this.subject = subject;
| this.callbackHandler=callbackHandler;
| }
|
| public boolean login() throws LoginException {
| logger.info(Login);
| NameCallback nameCallback = new NameCallback(User Name);
| PasswordCallback passwordCallback = new PasswordCallback(User
Password, false);
| Callback[] callbacks = new Callback[2];
| callbacks[0] = nameCallback;
| callbacks[1] = passwordCallback;
| logger.info(Configured callbacks);
| try {
| logger.info(Handling callbacks);
| callbackHandler.handle(callbacks);
| logger.info(Handled callbacks);
| } catch (UnsupportedCallbackException ex) {
| ex.printStackTrace();
| } catch (IOException ex) {
| ex.printStackTrace();
| }
| String userid = default;
| String password = default;
| try {
| if (nameCallback.getName() != null) {
| userid = nameCallback.getName();
| }
| if (passwordCallback.getPassword() != null) {
| password = new String(passwordCallback.getPassword());
| }
| logger.info(Processed callbacks);
| passwordCallback.clearPassword();
| logger.info(Attempt to login with :+userid+ and +password);
| } catch (Exception e) {
| e.printStackTrace();
| }
| JAASUser user = new JAASUser(1,userid);
| JAASRole role = new JAASRole(friends);
| subject.getPrincipals().add(user);
| subject.getPrincipals().add(role);
| return true;
| }
|
| public boolean logout() throws LoginException {
| logger.info(Logout);
| subject.getPrincipals().clear();
| return true;
| }
| }
|
I tried adding the getRoleSets method as shown below which I got from an
example in this forum, but this did not make any difference.
| public Group[] getRoleSets() throws LoginException {
| Group grp = new JAASGroup(Roles);
| grp.addMember(new JAASRole(friend));
| grp.addMember(new JAASRole(friends));
| return new Group[]{grp};
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4098752#4098752
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098752
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Security JAAS/JBoss] - Re: Accessing Roles from Custom LoginModule return NULL
I have managed to resolve this problem by correctly implementing the commit
method as :
| public boolean commit() throws LoginException {
| logger.info(Granted Permissions);
| JAASUser user = new JAASUser(1,userid);
| JAASRole role = new JAASRole(friends);
| Group grp = new JAASGroup(Roles);
| grp.addMember(new JAASRole(friend));
| grp.addMember(new JAASRole(friends));
|
| subject.getPrincipals().add(user);
| subject.getPrincipals().add(role);
| subject.getPrincipals().add(grp);
| return true;
| }
|
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4098767#4098767
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098767
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Basic Authentication with WSSecureEndpoint on JBoss 4.2.2GA
I want to use Username Tokens to authenticate with a webservice provided by a Session Bean as shows: @Stateless | @WebService | @EndpointConfig(configName=Standard WSSecurity Endpoint) | @SecurityDomain(java:/jaas/THZone) | @RolesAllowed(friend) | @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, | use=SOAPBinding.Use.LITERAL, | parameterStyle=SOAPBinding.ParameterStyle.BARE) I searched the forum and found several references to : http://wiki.jboss.org/wiki/Wiki.jsp?page=WSSecureEndpoint which points to the user guide. I configured the login module in conf/login-config.xml to use a properties file to test the configuration. However when I try to access the principal I get a null back. Since added the RolesAllowed annotation the service fails with : anonymous wrote : | 11:46:07,984 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[friend], principalRoles=[] | 11:46:07,984 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.ejb.EJBAccessException: Authorization failure | at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:120) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:619) | It seems that I am just missing the right configuration. Any pointers on what to configure would help me a great deal. Tx Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098251#4098251 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098251 ___ jboss-user mailing
[jboss-user] [JBossWS] - Re: WSSecurity Username token
Did you ever this the resolved. I am having the same problem using JBoss 4.2.2 wich included a new build of JBossWS. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098254#4098254 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098254 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: UsernameToken and Basic Auth
Could you please explain how you set up Username Token Authentication. In which file does this XML go ? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098363#4098363 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098363 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Web seervice with authentication and wsconsume
where can one find those examples I looked in jbossws-native-2.0.1.GA, jbossws-src-2.0.1.GA as well as JBoss4.2.2GA. I am looking for a basic example on Username Token authentication. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4098379#4098379 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098379 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: Basic Authentication with WSSecureEndpoint on JBoss 4.2.
I added a custom login module to debug this problem. It seems that the user and
password are never passed to the login module.
| public boolean login() throws LoginException {
| logger.info(Login);
| NameCallback nameCallback = new NameCallback(User Name);
| PasswordCallback passwordCallback = new PasswordCallback(User
Password, false);
| Callback[] callbacks = new Callback[2];
| callbacks[0] = nameCallback;
| callbacks[1] = passwordCallback;
| logger.info(Configured callbacks);
| try {
| logger.info(Handling callbacks);
| callbackHandler.handle(callbacks);
| logger.info(Handled callbacks);
| } catch (UnsupportedCallbackException ex) {
| ex.printStackTrace();
| } catch (IOException ex) {
| ex.printStackTrace();
| }
| String userid = default;
| String password = default;
| userid = nameCallback.getName();
| password = new String(passwordCallback.getPassword());
| logger.info(Processed callbacks);
| passwordCallback.clearPassword();
| logger.info(Attempt to login with :+userid+ and +password);
| JAASUser user = new JAASUser(1,userid);
| JAASRole role = new JAASRole(friends);
| subject.getPrincipals().add(user);
| subject.getPrincipals().add(role);
| return true;
| }
|
I am still a little confused on where I am supposed to configure which
Principal implementation is a User or a Role.
I also tried adding a WebContext, but this resulted in a The request failed
with HTTP status 401: Unauthorized. error without invoking the Login Module.
Removing the WebContext annocation resulted in the Login Module being called,
but without User / Password.
@WebContext(authMethod = BASIC, transportGuarantee=NONE, secureWSDLAccess =
false)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4098385#4098385
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4098385
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: Using DeliveryMode.NON_PERSISTENT
You are absolutely correct. I was just surprised by the unexpected results. I would have thought that without persistence messages would be processed faster. However it seems that in my case it is irrelevent wether the message is persisted or not. It's like you said. The bottleneck must be elsewhere. Thanks for your help with this Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4097392#4097392 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4097392 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Using DeliveryMode.NON_PERSISTENT
I have a MDB configured as shown below. I am sending a large number of messages
to the MDB and do not require persistent queue. Searching the forum I found
several suggestion to set DeliveryMode.NON_PERSISTENT, yet when I use the HSQL
Database Manager I still find entries created in the JMS_Messages table.
Ideally I would like to avoid any kind of persistence to achieve a performance
gain. My requirements do not require persistence for this service.
| ...
| @MessageDriven(name =
LogMessageProcessor,mappedName=LogMessageProcessor, activationConfig = {
| @ActivationConfigProperty(propertyName = acknowledgeMode,
propertyValue = Auto-acknowledge),
| @ActivationConfigProperty(propertyName = destinationType,
propertyValue = javax.jms.Queue),
| @ActivationConfigProperty(propertyName = destination, propertyValue =
queue/LogMessageProcessors),
| @ActivationConfigProperty(propertyName = maxSession, propertyValue =
5),
| @ActivationConfigProperty(propertyName = maxMessages,
propertyValue=5),
| @ActivationConfigProperty(propertyName = subscriptionDurability,
propertyValue=Non-Durable)
| })
| public class LogMessageProcessor implements MessageListener
| ...
|
| Properties properties = new Properties();
| properties.put(Context.INITIAL_CONTEXT_FACTORY,
org.jnp.interfaces.NamingContextFactory);
| properties.put(Context.URL_PKG_PREFIXES, jboss.naming:org.jnp.interfaces);
| properties.put(Context.PROVIDER_URL, jnp://localhost:1100);
| InitialContext ctx = new InitialContext(properties);
| Queue queue = (Queue) ctx.lookup(/queue/LogMessageProcessors);
|
| QueueConnectionFactory factory = (QueueConnectionFactory)
ctx.lookup(ConnectionFactory);
| cnn = factory.createQueueConnection();
| sess = cnn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
| MapMessage msg = sess.createMapMessage();
|
| QueueConnection connection = factory.createQueueConnection();
| QueueSession session = connection.createQueueSession(false,
QueueSession.AUTO_ACKNOWLEDGE);
| QueueSender sender = session.createSender(queue);
| sender.setDeliveryMode(DeliveryMode.NON_PERSISTENT);
| for (int index=0; index2000; index++)
| {
| ObjectMessage message = session.createObjectMessage();
| LogMessage logMessage = new LogMessage();
| logMessage.setMessage(Log Message : +System.currentTimeMillis());
| message.setObject(logMessage);
| message.setJMSDeliveryMode(DeliveryMode.NON_PERSISTENT);
| sender.send(message,DeliveryMode.NON_PERSISTENT,10,2);
| //logger.log(Level.INFO,Dispatched message :
+logMessage.getMessage());
| }
|
| sender.close();
| session.close();
| connection.close();
|
Any assistance in improving the performance and avoid persisting the messages
will help me a lot. Thanks in advance.
alex
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4096021#4096021
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4096021
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: Using DeliveryMode.NON_PERSISTENT
I had a look at the FAQ at http://wiki.jboss.org/wiki/Wiki.jsp?page=FAQJBossMQ but didn't find a solution to the DeliveryMode problem. Which post on the FAQ are you refering to. Regards Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4096069#4096069 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4096069 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: Using DeliveryMode.NON_PERSISTENT
I changed the High and Max Memory thresholds and now the messages are now longer stored in Hypersonic. This link describes this in detail http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigMessageCache Thanks for the pointer to the FAQ Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4096073#4096073 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4096073 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Messaging, JMS JBossMQ] - Re: Using DeliveryMode.NON_PERSISTENT
Now that I have it working without writing it to the interim cache database I would have expected a performance improvement, yet there doesn't seem to be one. To dispatch 4000 messages still takes around 12 seconds with or without persistence. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4096077#4096077 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4096077 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: How to print SQL values in debug Log
You can use the following properties : hibernate.show_sql hibernate.format_sql hibernate.use_sql_comments Take a look at the hiberante documentation for more details: http://www.hibernate.org/hib_docs/reference/en/html/session-configuration.html View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4094046#4094046 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4094046 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Portable Resource mapping to JNDI Name
I would like to use a symbolic name to link to the Connection factory so using the mapped name attribute in the code does not seem an option. | //MappedName does not seem portable | //@Resource(mappedName=ConnectionFactory) | @Resource(name=jms/ConnectionFactory2) | private QueueConnectionFactory factory; | Then I added the following to my deployment descriptors ejb-jar.xml | message-driven | ejb-nameBatchJobProcessor/ejb-name | ejb-classcom.thunderhead.backend.BatchJobProcessor/ejb-class | transaction-typeBean/transaction-type | resource-ref | description/ | res-ref-namejms/ConnectionFactory2/res-ref-name | res-typejavax.jms.QueueConnectionFactory/res-type | res-authContainer/res-auth | !--mapped-namejnp://localhost:1100/ConnectionFactory/mapped-name-- | /resource-ref | resource-ref | description/ | res-ref-namequeue/TransactionProcessors/res-ref-name | res-typejavax.jms.Queue/res-type | res-authContainer/res-auth | mapped-namejnp://localhost:1100/queue/TransactionProcessors/mapped-name | /resource-ref | /message-driven | Again specifying the real JNDI name in the ejb-jar.xml file works, but does not provide me with suitable abstraction and portability. I was hoping to place all the JBoss specific JNDI mapping in the jboss.xml file like this. jboss.xml | message-driven | ejb-nameBatchJobProcessor/ejb-name | destination-jndi-namequeue/BatchJobProcessors/destination-jndi-name | resource-ref | res-ref-namejms/ConnectionFactory2/res-ref-name | jndi-namejnp://localhost:1100/ConnectionFactory/jndi-name | /resource-ref | resource-ref | res-ref-namequeue/TransactionProcessors/res-ref-name | jndi-namejnp://localhost:1100/queue/TransactionProcessors/jndi-name | /resource-ref | /message-driven | However during deployment the following error occurs: anonymous wrote : | 3:17:54,453 WARN [JmxKernelAbstraction] persistence.units:ear=ThunderheadEJB_1178.ear,jar=ThunderheadEJB.jar,unitName=ThunderheadPU is not registered | 3:17:54,453 WARN [ServiceController] Problem starting service jboss.j2ee:service=EJB3,module=ThunderheadEJB.jar | ava.lang.RuntimeException: mapped-name is required for jms/ConnectionFactory2 of deployment BatchJobProcessor |at org.jboss.injection.ResourceHandler.loadXmlResourceRefs(ResourceHandler.java:94) |at org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:167) |at org.jboss.ejb3.EJBContainer.processMetadata(EJBContainer.java:352) |at org.jboss.ejb3.Ejb3Deployment.processEJBContainerMetadata(Ejb3Deployment.java:292) |at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:356) |at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91) |at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) |at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) |at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) |at java.lang.reflect.Method.invoke(Method.java:597) |at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) |at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) |at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) |at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) |at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) |at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) |at $Proxy0.start(Unknown Source) |at org.jboss.system.ServiceController.start(ServiceController.java:417) |at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) |at java.lang.reflect.Method.invoke(Method.java:597) |at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) |at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) |at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) |at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) |at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) |at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) |at $Proxy33.start(Unknown Source) |at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:512) |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) |
[jboss-user] [EJB 3.0] - Clustered MDB configuration
I have 3 MDBs configures in a chain BatchJobProcessor TransactionProcessor OutputProcessor which I have deployed into a cluster. My aim is to maintain as much portability as possible in my code and defer the JNI configuration to the deployment descriptors: I tried configuring the Qs using a services file but it seems to only deploy the Qs on the first node and fail on all other nodes. The error reported on the other nodes was that the DestinationManager was missing, but was a requirement for the Q. If there is a better way to do this please let me know. | ?xml version=1.0 encoding=UTF-8? | server | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=BatchJobProcessorMDB | attribute name=JNDINamequeue/BatchJobProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=TransactionProcessorsMDB | attribute name=JNDINamequeue/TransactionProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=OutputProcessorsMDB | attribute name=JNDINamequeue/OutputProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | /server | So I gave up on the option of using a services file and rely on the container to create teh queues for me. In BatchJobProcessor : | @Resource(name=jms/ConnectionFactory) | private QueueConnectionFactory factory; | | @Resource(name=queue/TransactionProcessors) | private Queue queue; | In TransactionProcessor : | @Resource(name=jms/ConnectionFactory) | private QueueConnectionFactory factory; | | @Resource(name=queue/OutputProcessors) | private Queue queue; | Then I added the following to my ejb-jar.xml | message-driven | ejb-nameBatchJobProcessor/ejb-name | ejb-classcom.thunderhead.backend.BatchJobProcessor/ejb-class | transaction-typeBean/transaction-type | resource-ref | description/ | res-ref-namejms/ConnectionFactory/res-ref-name | res-typejavax.jms.QueueConnectionFactory/res-type | res-authContainer/res-auth | mapped-namejnp://localhost:1100/ConnectionFactory/mapped-name | /resource-ref | resource-ref | description/ | res-ref-namequeue/TransactionProcessors/res-ref-name | res-typejavax.jms.Queue/res-type | res-authContainer/res-auth | mapped-namejnp://localhost:1100/queue/TransactionProcessors/mapped-name | /resource-ref | /message-driven | I was hoping to do the final mapping to the real JNDI name in the jboss.xml file, however during deployment an error require me to add the mapped Name element. It seems to me that message servers (factories and queue) only exist in the HAJNDI context and need to be looked up via jnp://localhost:1100/... My attempt to look up those services in the local JNDI context failed so far. I do have the jboss.xml file configured, but it does not seem to have any effect. I wonder what I missed as I would prefer to keep the jboss specific binding to the real jndi name in a jboss specific configuration file. | message-driven | ejb-nameBatchJobProcessor/ejb-name | destination-jndi-namequeue/BatchJobProcessors/destination-jndi-name | resource-ref | res-ref-namejms/ConnectionFactory/res-ref-name | jndi-namejnp://localhost:1100/ConnectionFactory/jndi-name | /resource-ref | resource-ref | res-ref-namequeue/TransactionProcessors/res-ref-name | jndi-namejnp://localhost:1100/queue/TransactionProcessors/jndi-name | /resource-ref | /message-driven | Thanks in advance Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4093031#4093031 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093031 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Could not find new XAResource to use for recovering non-seri
I was trying out some standard user transactions using EJB3 entities and persistent message queues. During my tests I encountered several application exceptions which were caused by my code, which I was able to resolved. However since then I am getting continous stream of messages on the console. Searching the forum revealed that I need to write a recovery module. Seeing that I was merely using EJB3 I am wondering if there is a standard recovery model. anonymous wrote : | [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource 131075, 30, 28, 1--3f57fdc4:68f:46f90760:8c5d6-3f57fdc4:68 | I'd be happy if I could get just rid of those messages as the cause of the problem has been resolved. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4093035#4093035 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093035 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: How to connect multiple databases at same time?
You need to configure multiple persistent units withing the persistence.xml file and annotate your entities appropriately. There is an example in the Jboss TrailBlazer. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4093063#4093063 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4093063 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJB3 Entity doing Batch Insert fails with transaction re
Managing the transaction in the bean allowed me to define the scope and duration of the TX. This solved my problem. Thanks for the links Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4088301#4088301 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088301 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: resource-ref problem
It has been a while since you post, but did you ever get this resolved. I am currently encoutering the same probem in a cluster of 2 VMs. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4087879#4087879 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4087879 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Clustered MDB configuration / JNDI problem
I am trying to deply an EJB3 MDB into a cluster of 2 nodes. Running the bean on a single VM works well without any problems, however I am not able to bring the second VM online. During the startup the following error is reported : anonymous wrote : | 15:21:26,484 ERROR [FarmMemberService] Incomplete Deployment listing: | | --- MBeans waiting for other MBeans --- | ObjectName: jboss.mq.destination:service=Queue,name=BatchJobProcessorMDB | State: CONFIGURED | I Depend On: | jboss.mq:service=DestinationManager | | ObjectName: jboss.mq.destination:service=Queue,name=TransactionProcessorsMDB | State: CONFIGURED | I Depend On: | jboss.mq:service=DestinationManager | | ObjectName: jboss.mq.destination:service=Queue,name=OutputProcessorsMDB | State: CONFIGURED | I Depend On: | jboss.mq:service=DestinationManager | | --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- | ObjectName: jboss.mq:service=DestinationManager | State: NOTYETINSTALLED | Depends On Me: | jboss.mq.destination:service=Queue,name=BatchJobProcessorMDB | jboss.mq.destination:service=Queue,name=TransactionProcessorsMDB | jboss.mq.destination:service=Queue,name=OutputProcessorsMDB | on the second node. It is always the second node started. The first one alwasy succeeds. I found that the JNDI context on the second node is much smaller then the context on the first one. The Destination Manager as well as most standard Queues aren't listed on the JMX-console. I tried to configure the queue deploying this services file into the all/farm folder: | ?xml version=1.0 encoding=UTF-8? | server | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=BatchJobProcessorMDB | attribute name=JNDINamequeue/BatchJobProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=TransactionProcessorsMDB | attribute name=JNDINamequeue/TransactionProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | mbean code=org.jboss.mq.server.jmx.Queue | name=jboss.mq.destination:service=Queue,name=OutputProcessorsMDB | attribute name=JNDINamequeue/OutputProcessors/attribute | depends optional-attribute-name=DestinationManagerjboss.mq:service=DestinationManager/depends | /mbean | /server | If you have any suggestion on how I can get MDB working in a JBoss cluster and how I can fix the JNDI issue please let me know Thanks in advance Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4087950#4087950 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4087950 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Unable to inject jndi dependency: env/.../queue into propert
Deploying the beans without defining the queues via the services succeeds, but
during the execution the following errors are reported on the second node :
anonymous wrote :
| 15:46:02,000 INFO [EJB3Deployer] Deployed:
file:/C:/jboss-4.2.1.GA/server/all/farm/ThunderheadEJB.jar
| 15:48:28,703 INFO [BatchJobProcessor] Instantiating BatchJobProcessors
| 15:48:28,718 ERROR [JmsServerSession] Unexpected error delivering message
org.jboss.mq.SpyMapMessage {
| Header {
|jmsDestination : QUEUE.BatchJobProcessors
|jmsDeliveryMode : 2
|jmsExpiration : 0
|jmsPriority : 4
|jmsMessageID: ID:13-11906453102031
|jmsTimeStamp: 1190645310203
|jmsCorrelationID: null
|jmsReplyTo : null
|jmsType : null
|jmsRedelivered : false
|jmsProperties : {}
|jmsPropReadWrite: false
|msgReadOnly : true
|producerClientId: ID:13
| }
| }
| java.lang.RuntimeException: Unable to inject jndi dependency:
env/com.thunderhead.backend.BatchJobProcessor/queue into property
com.thunderhead.backend.BatchJobProcessor.queue: queue not bound
| at
org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:76)
| at
org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:88)
| at
org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:83)
| at
org.jboss.injection.JndiPropertyInjector.inject(JndiPropertyInjector.java:55)
| at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:111)
| at org.jboss.ejb3.StrictMaxPool.get(StrictMaxPool.java:141)
| at
org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54)
| at
org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| at
org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245)
| at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268)
| at
org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138)
| at $Proxy98.onMessage(Unknown Source)
| at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
| at
org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891)
| at
org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170)
| at org.jboss.mq.SpySession.run(SpySession.java:323)
| at
org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at
org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:619)
| Caused by: javax.naming.NamingException: Could not dereference object [Root
exception is javax.naming.NameNotFoundException: queue not bound]
| at
org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1069)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:702)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
| at
org.jboss.injection.JndiPropertyInjector.lookup(JndiPropertyInjector.java:69)
| ... 20 more
| Caused by: javax.naming.NameNotFoundException: queue not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
| at
org.jnp.interfaces.NamingContext.resolveLink(NamingContext.java:1063)
| ... 23 more
| 15:48:28,859 INFO [BatchJobProcessor] Instantiating BatchJobProcessors
| 15:48:28,859 ERROR [JmsServerSession] Unexpected error delivering message
org.jboss.mq.SpyMapMessage {
| Header {
|jmsDestination : QUEUE.BatchJobProcessors
|jmsDeliveryMode : 2
|jmsExpiration : 0
|jmsPriority : 4
|jmsMessageID: ID:13-11906453102031
|jmsTimeStamp: 1190645310203
|jmsCorrelationID: null
|jmsReplyTo : null
|jmsType : null
|jmsRedelivered : true
|jmsProperties : {JMS_JBOSS_REDELIVERY_COUNT=1}
|jmsPropReadWrite: false
|msgReadOnly : true
|producerClientId: ID:13
| }
| }
| java.lang.RuntimeException: Unable to inject
[jboss-user] [EJB 3.0] - Re: Exception during passivation : Caused by: java.lang.NoCl
It turned out that one of the member did not implement serialisable (I think). View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4087977#4087977 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4087977 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - EJB3 Entity doing Batch Insert fails with transaction requir
I am reading a rather large XML file, split it into a large number of segments and would like to insert each segment into a database. The segments fit nicely into entities, so please don't tell me about prepared statement etc. Currently I have MDB which received the file descriptor and begins reading the file and processing it. When using smaller files (30Mb) everything seems to work really well. The files are loaded quickly and without errors. However as soon as the I try to load the large file the process failes with : anonymous wrote : | javax.persistence.TransactionRequiredException: EntityManager must be access within a transaction |at org.jboss.ejb3.entity.ManagedEntityManagerFactory.verifyInTx(ManagedEntityManagerFactory.java:150) |at org.jboss.ejb3.entity.TransactionScopedEntityManager.persist(TransactionScopedEntityManager.java:181) |at com.thunderhead.backend.BatchJobDevider.segmentCompleted(BatchJobDevider.java:56) |at com.thunderhead.backend.utilities.XMLSegmenter.notifyListeners(XMLSegmenter.java:61) |at com.thunderhead.backend.utilities.XMLSegmenter.segment(XMLSegmenter.java:51) |at com.thunderhead.backend.BatchJobProcessor.onMessage(BatchJobProcessor.java:85) |at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) |at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) |at java.lang.reflect.Method.invoke(Method.java:597) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) |at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) |at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) |at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) |at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) |at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) |at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) |at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) |at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) |at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245) |at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) |at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) |at $Proxy99.onMessage(Unknown Source) |at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178) |at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:891) |at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170) |at org.jboss.mq.SpySession.run(SpySession.java:323) |at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237) |at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) |at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) |at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) |at java.lang.Thread.run(Thread.java:619) | Currently I don't have any transaction attributes defined on my onMessage method. At first I thought it might be the database connection pool timing out, so I increased the timeout. However I now get this failure before the timeout period elapsed. It seems that the transaction constructed by the server is exceeding some limit and then enters into a no transaction available state. Any suggestions on how to resolve this without using a prepared statement and inserting it directly into the database. Thanks Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4088029#4088029 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088029 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJB3 Entity doing Batch Insert fails with transaction re
I don't have the code in front of me, but I will post it when I get to the office. But I can describe it briefly as it's pretty standard. It's a basic MDB with container managed transactions. Withing my onMessage method, I am calling the entityManager repeatedly asking it to persist a large number of objects. From the links you sent it seems that the timeout of 300 seconds (default) could well be the cause of my problem. I will run some more tests tomorrow and get back to you. Thanks for the link to the information. Regards Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4088232#4088232 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4088232 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - JAX-WS from Sessions Bean fails due to missing org/jboss/log
I have a standalone client jar which using JAX-WS in JDK1.6 is able to consume a webservice. I would like to invoke the webservice from a session bean, so I added the webservice client JAR to my ear file and updated the application.xml file. The problem is that when I try to invoce the client from within JBoss I get the following error. A search in the forums and the web makes suggestions to include the jboss-common-clients.jar in the classpath. I tried added this jar to the /server/default/lib folder as well as include it within the EAR / application.xml, of which neiter worked. If JAX-WS client is not supported what other libraries can I use to consume a web service from a Session Bean. anonymous wrote : | java.lang.NoClassDefFoundError: org/jboss/logging/Logger | at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47) | at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64) | at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:120) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254) | at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75) | at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1550) | at org.jboss.remoting.Client.invoke(Client.java:530) | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:171) | at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:322) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:230) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4075829#4075829 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4075829 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - JAX-WS from Sessions Bean fails due to missing org/jboss/log
I have a standalone client jar which using JAX-WS in JDK1.6 is able to consume a webservice. I would like to invoke the webservice from a session bean, so I added the webservice client JAR to my ear file and updated the application.xml file. The problem is that when I try to invoce the client from within JBoss I get the following error. A search in the forums and the web makes suggestions to include the jboss-common-clients.jar in the classpath. I tried added this jar to the /server/default/lib folder as well as include it within the EAR / application.xml, of which neiter worked. If JAX-WS client is not supported what other libraries can I use to consume a web service from a Session Bean. anonymous wrote : | java.lang.NoClassDefFoundError: org/jboss/logging/Logger | at javax.xml.soap.FactoryLoader.(FactoryLoader.java:47) | at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:64) | at org.jboss.ws.core.soap.SOAPFactoryImpl.createElement(SOAPFactoryImpl.java:120) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:116) | at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:85) | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:254) | at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:75) | at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:472) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:304) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1550) | at org.jboss.remoting.Client.invoke(Client.java:530) | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:171) | at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:322) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:230) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4075830#4075830 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4075830 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Equals and hashCode on Entities fails due to javassist
On a recent project we thought it would be a good idea to inherit a generic implementation of equals and hashCode, as well as the primariy key from an abstract entity. In the equals method we evaluate the class as well as the primary key. In most cases this worked really well for us, but in certain cases equality was not evaluated correctly. After looking further into the problem we found that in the cases it did not evaluate correctly the problem was caused by the classes not matching. It tried to compare one class (Test for example) against another (Test_$$_javassist_), which didn't equate and produces a false response. I am guessing that the javassist originates from entities being loaded LAZY. Is there a better way of achieving what we are trying to do ? We are using JBoss 4.0.5 with EJB3 RC9. Any suggestions welcome Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4071016#4071016 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4071016 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: anyway to findout which ejbs are available remotely/loca
You could browse the JNDI tree in the same way the JMX console does. Then use either REMOTE or LOCAL to see the type of service. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069613#4069613 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069613 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Equals method on entity failes to evaluate correctly due to
On a recent project we thought it would be a good idea to inherit a generic implementation of equals and hashCode, as well as the primariy key from an abstract entity. In the equals method we evaluate the class as well as the primary key. In most cases this worked really well for us, but in certain cases equality was not evaluated correctly. After looking further into the problem we found that in the cases it did not evaluate correctly the problem was caused by the classes not matching. It tried to compare one class (Test for example) against another (Test_$$_javassist_), which didn't equate and produces a false response. I am guessing that the javassist originates from entities being loaded LAZY. Is there a better way of achieving what we are trying to do ? We are using JBoss 4.0.5 with EJB3 RC9. Any suggestions welcome Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069607#4069607 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069607 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJBs and XML-RPCs
I suggest you take a look at chapter 16 in the Final EJB3 Specification. (ejb-3_0-fr-spec-ejbcore.pdf) | enterprise-beans | session | ... | ejb-nameEmployeeService/ejb-name | ejb-classcom.wombat.empl.EmployeeServiceBean/ejb-class | ... | env-entry | description | The maximum number of tax exemptions | allowed to be set. | /description | env-entry-namemaxExemptions/env-entry-name | env-entry-typejava.lang.Integer/env-entry-type | env-entry-value15/env-entry-value | /env-entry | env-entry | description | The minimum number of tax exemptions | allowed to be set. | /description | env-entry-nameminExemptions/env-entry-name | env-entry-typejava.lang.Integer/env-entry-type | env-entry-value1/env-entry-value | /env-entry | env-entry | env-entry-namefoo/name1/env-entry-name | env-entry-typejava.lang.String/env-entry-type | env-entry-valuevalue1/env-entry-value | /env-entry | env-entry | env-entry-namefoo/bar/name2/env-entry-name | env-entry-typejava.lang.Boolean/env-entry-type | env-entry-valuetrue/env-entry-value | /env-entry | env-entry | descriptionSome description./description | env-entry-namename3/env-entry-name | env-entry-typejava.lang.Integer/env-entry-type | /env-entry | env-entry | env-entry-namefoo/name4/env-entry-name | env-entry-typejava.lang.Integer/env-entry-type | env-entry-value10/env-entry-value | /env-entry | ... | /session | /enterprise-beans | and then access it as | // Obtain the enterprise bean?s environment naming context. | Context initCtx = new InitialContext(); | Context myEnv = (Context)initCtx.lookup(java:comp/env); | // Obtain the maximum number of tax exemptions | // configured by the Deployer. | Integer maxExemptions = | (Integer)myEnv.lookup(?maxExemptions?); | // Obtain the minimum number of tax exemptions | // configured by the Deployer. | Integer minExemptions = | (Integer)myEnv.lookup(?minExemptions?); | // Use the environment entries to customize business logic. | if (numberOfExeptions maxExemptions || | numberOfExemptions minExemptions) | throw new InvalidNumberOfExemptionsException(); | // Get some more environment entries. These environment | // entries are stored in subcontexts. | String val1 = (String)myEnv.lookup(?foo/name1?); | Boolean val2 = (Boolean)myEnv.lookup(?foo/bar/name2?); | // The enterprise bean can also lookup using full pathnames. | Integer val3 = (Integer) | initCtx.lookup(java:comp/env/name3); | Integer val4 = (Integer) | initCtx.lookup(java:comp/env/foo/name4); | Hope this helps Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069628#4069628 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069628 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: anyway to findout which ejbs are available remotely/loca
Get the InitialContext and work your way down using JNDI. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069646#4069646 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069646 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: Remote invocation with 4.0.5.GA + RC9
Could you please post your code and describe how you construct your classpath. It is likely to be a configuration problem as remote invocation working View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069620#4069620 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069620 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Environment variable in EJB3 (was EJBs and XML-RPCs)
Changed the title of the message. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069632#4069632 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069632 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJBs and XML-RPCs
I am using NB5.5, but we assemble the JAR using our own ANT script. Have a look if there is an ejb-jar.xml file in the constructed JAR file. If there is then you could look in the Files tab and might find it. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069648#4069648 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069648 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: service=EJB3 + is already registered
We just migrated from 4.0.5 to 4.2.1 and are experiencing the same problem. Any other suggestions. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069662#4069662 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069662 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: EJBs and XML-RPCs
EJB3 does not need a deployment descriptor to work, but certain aspects are still configurable via a deployment descriptor. After you deployed the JAR containing the ejb-jar.xml file you can look in the JNDI List within the JMX console to browse the JNDI tree. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4069664#4069664 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4069664 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - Re: JNDI Naming question with EJB3 in JBoss: how to include
Take a look at the mappedName and Name attributes on the Stateful and Stateless annotations. Alex http://ejb3workshop.com View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4003248#4003248 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4003248 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [EJB 3.0] - java.lang.NoClassDefFoundError: org/jaxen/VariableContext du
When my Session Beans are being passivated the following exception is thrown. I had a look for the jaxen libraries and even tried added new ones I downloaded to the lib folder. Yet the problem did not go away. There doesn't seem to be any impact from this, but it would be nice if passivation would work. How can I get rid of the these exceptions. anonymous wrote : | javax.ejb.EJBException: Could not passivate; failed to save state | at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:363) | at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:196) | at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129) | Caused by: java.io.IOException | at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:129) | at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:86) | at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206) | at org.jboss.serial.persister.ArrayPersister.saveObjectArray(ArrayPersister.java:110) | at org.jboss.serial.persister.ArrayPersister.writeData(ArrayPersister.java:101) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206) | at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322) | at org.jboss.serial.io.MarshalledObject.(MarshalledObject.java:51) | at org.jboss.ejb3.stateful.StatefulBeanContext.writeExternal(StatefulBeanContext.java:405) | at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206) | at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:322) | at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager.java:347) | ... 2 more | Caused by: java.lang.reflect.InvocationTargetException | at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:597) | at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:120) | ... 20 more | Caused by: java.io.IOException | at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:129) | at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:86) | at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206) | at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithFields(RegularObjectPersister.java:182) | at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:90) | at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) | at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:276) | at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:206) | at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithFields(RegularObjectPersister.java:182) | at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:90) | at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) | at
[jboss-user] [EJB 3.0] - Exception during passivation : Caused by: java.lang.NoClassD
I am using JBoss 4.0.4 GA with EJB3 RC 8. Most of my statefull session bean throw the following exception during passivation. There seams to be little or no impact to the application, but still not very nice. Any idea how I can fix this problem. I already tried added jaxen to the lib directory, but it still does not work. anonymous wrote : | 16:07:03,561 ERROR [SimpleStatefulCache] problem passivation thread | javax.ejb.EJBException: Could not passivate; failed to save state |at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager. |at org.jboss.ejb3.cache.simple.SimpleStatefulCache.passivate(SimpleStatefulCache.java:194) |at org.jboss.ejb3.cache.simple.SimpleStatefulCache$SessionTimeoutTask.run(SimpleStatefulCache.java:129) | Caused by: java.io.IOException |at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:129) |at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:86) |at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) |at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) |at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) |at org.jboss.serial.persister.ArrayPersister.saveObjectArray(ArrayPersister.java:110) |at org.jboss.serial.persister.ArrayPersister.writeData(ArrayPersister.java:101) |at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) |at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) |at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181) |at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287) |at org.jboss.serial.io.MarshalledObject.(MarshalledObject.java:51) |at org.jboss.ejb3.stateful.StatefulBeanContext.writeExternal(StatefulBeanContext.java:401) |at org.jboss.serial.persister.ExternalizePersister.writeData(ExternalizePersister.java:58) |at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) |at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) |at org.jboss.serial.io.JBossObjectOutputStream.writeObjectOverride(JBossObjectOutputStream.java:181) |at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:287) |at org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager.passivateSession(StatefulSessionFilePersistenceManager. |... 2 more | Caused by: java.lang.reflect.InvocationTargetException |at sun.reflect.GeneratedMethodAccessor334.invoke(Unknown Source) |at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) |at java.lang.reflect.Method.invoke(Method.java:585) |at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:120) |... 20 more | Caused by: java.io.IOException |at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithMethod(RegularObjectPersister.java:129) |at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:86) |at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) |at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) |at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) |at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithFields(RegularObjectPersister.java:182) |at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:90) |at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) |at org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.describeObject(ObjectDescriptorFactory.java:275) |at org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectOutput.writeObject(DataContainer.java:202) |at org.jboss.serial.persister.RegularObjectPersister.writeSlotWithFields(RegularObjectPersister.java:182) |at org.jboss.serial.persister.RegularObjectPersister.defaultWrite(RegularObjectPersister.java:90) |at org.jboss.serial.persister.RegularObjectPersister.writeData(RegularObjectPersister.java:62) |at
