[JBoss-user] [Persistence & CMP/JBoss] - Re: NullPointerException in JDBCCMP1xFieldBridge under heavy
We're using the following configuration: LMNK Standard CMP 1.x EntityBean org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager org.jboss.ejb.plugins.lock.NoLock C We've played around with 3.2.4 a little, but we had some other clustering issues that held us back from QA. So we rolled back to 3.2.3. We also have concerns about the frequency of last few releases and what that might say about the stability of the code... seems like 3.2.4, 3.2.5, and 3.2.6 are pretty closely spaced - like 3.2.4 had too many bugs and 3.2.5 and 3.2.6 are polishing it up a bit. Maybe 3.2.6 will be the next "stable" release. Regardless, we have not done performance testing with 3.2.4 or 3.2.5 at this point - we would really like to roll our code out to production using 3.2.3 since that's what we've done most of our testing with. Do you have any other suggestions? Perhaps some other container configurations to try? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3843257#3843257 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3843257 --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Persistence & CMP/JBoss] - NullPointerException in JDBCCMP1xFieldBridge under heavy loa
There's a workflow in our application that, when the server is under no stress (single user), completes successfully. Upon increasing the load, we get NullPointerExceptions in the JDBCCMP1xFieldBridge. We're running with version 3.2.3 (patched GlobalTxEntityMap because it was generating an Exception while attempting to throw an exception). Here's a copy of the stack trace: java.lang.NullPointerException at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP1xFieldBridge.getFieldState(JDBCCMP1xFieldBridge.java:181) at org.jboss.ejb.plugins.cmp.jdbc.bridge.JDBCCMP1xFieldBridge.setClean(JDBCCMP1xFieldBridge.java:135) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityCommand.execute(JDBCStoreEntityCommand.java:168) at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.storeEntity(JDBCStoreManager.java:627) at org.jboss.ejb.plugins.CMPPersistenceManager.storeEntity(CMPPersistenceManager.java:421) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.storeEntity(CachedConnectionInterceptor.java:387) at org.jboss.ejb.EntityContainer.storeEntity(EntityContainer.java:714) at org.jboss.ejb.GlobalTxEntityMap.synchronizeEntities(GlobalTxEntityMap.java:155) at org.jboss.ejb.EntityContainer.synchronizeEntitiesWithinTransaction(EntityContainer.java:119) at org.jboss.ejb.EntityContainer.find(EntityContainer.java:660) at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.ejb.EntityContainer$ContainerInterceptor.invokeHome(EntityContainer.java:1043) at org.jboss.ejb.plugins.EntitySynchronizationInterceptor.invokeHome(EntitySynchronizationInterceptor.java:197) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeHome(CachedConnectionInterceptor.java:214) at org.jboss.ejb.plugins.AbstractInterceptor.invokeHome(AbstractInterceptor.java:88) at org.jboss.ejb.plugins.EntityInstanceInterceptor.invokeHome(EntityInstanceInterceptor.java:89) at org.jboss.ejb.plugins.EntityLockInterceptor.invokeHome(EntityLockInterceptor.java:61) at org.jboss.ejb.plugins.EntityCreationInterceptor.invokeHome(EntityCreationInterceptor.java:28) at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:88) at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:267) at org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java:98) at org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor.java:92) at org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:120) at org.jboss.ejb.plugins.CleanShutdownInterceptor.invokeHome(CleanShutdownInterceptor.java:198) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invokeHome(ProxyFactoryFinderInterceptor.java:93) at org.jboss.ejb.EntityContainer.internalInvokeHome(EntityContainer.java:483) at org.jboss.ejb.Container.invoke(Container.java:720) at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546) at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:101) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:90) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:45) at org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:173) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:85) at $Proxy443.findByPKFields(Unknown Source) at com.isopia.ilms.ejb.messaging.messagingBroker.MessagingBrokerBean.getAllPersonDetail(MessagingBrokerBean.java:3856) at com.isopia.ilms.ejb.messaging.messagingBroker.MessagingBrokerBean.getOnsiteDisplayableMessages(MessagingBrokerBean.java:2615) 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:324) at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionContainer.java:683) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInte
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: 3.2.4 / JMS / Transacation is not active
Thanks for the help Adrian. I figured out what the problem was - it's a bug in the org.jboss.mq.pm.rollinglogged.PersistenceManager class. I filed a bug report #990315 in sourceforce - along with some changes that I made locally to fix it. It would be nice to see this fixed in the upcoming 3.2.6 release. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841899#3841899 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841899 --- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [Messaging, JMS & JBossMQ] - Re: 3.2.4 / JMS / Transacation is not active
Thank you for the quick reply - this fixed the problem for the POJO. I still have the "same" problem occurring in a stateless session bean. By "same" problem, I mean I still get "Transacation is not active" exceptions. It looks like the exceptions are being generated as part of the transaction attempting to commit. It appears as if there have been no other errors during the transaction, so the commit should succeed. Instead I get the exception. In the SSB I'm using, I'm running under "Required" semantics, using the default "java:/JmsXa" JMS connection factory. I'm still trying to use a transacted JMS session here because the logic is much more complicated than it was in the POJO - I need to rollback the JMS messages if there are any database errors. I'm also using an XA datasource wrapper around my oracle thin driver connection. Here's the stack trace: anonymous wrote : | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.SpyXAResource] End xid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=], flags=67108864 [EMAIL PROTECTED] txid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=] XA RUNNING [EMAIL PROTECTED]:ID:4/062d5ce3759294ec70cb3dc12f8327b6 rcvstate=STARTED]]] | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.SpySession] Unsetting current tx xid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=] previous: XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=] [EMAIL PROTECTED] txid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=] XA RUNNING [EMAIL PROTECTED]:ID:4/062d5ce3759294ec70cb3dc12f8327b6 rcvstate=STARTED]] | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.SpyXAResourceManager] Ending xid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=], success=true 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.SpyXAResource] Commit xid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=], onePhase=true [EMAIL PROTECTED] txid=null XA RUNNING [EMAIL PROTECTED]:ID:4/062d5ce3759294ec70cb3dc12f8327b6 rcvstate=STARTED]]] | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.SpyXAResourceManager] Commiting xid=XidImpl [FormatId=257, GlobalId=JDefelice1//6, BranchQual=], onePhase=true | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.Connection] Transact [EMAIL PROTECTED] [EMAIL PROTECTED]:ID:4/062d5ce3759294ec70cb3dc12f8327b6 rcvstate=STARTED] | 2004.06.30 08:58:08.578 GMT-05:00 TRACE [org.jboss.mq.il.uil2.SocketManager] Begin internalSendMessage, round-trip msg=org.jboss.mq.il.uil2.msgs.TransactMsg29651644[msgType: m_transact, msgID: -2147483571, error: null] | 2004.06.30 08:58:08.578 GMT-05:00 DEBUG [com.elementk.lms.khub.sys.email.MailSender] EmailTransportListener.messageDelivered: valid sent emails to 1 recipients | 2004.06.30 08:58:08.578 GMT-05:00 DEBUG [com.elementk.lms.khub.sys.email.MailSender] EmailTransportListener.messageDelivered: email addresses:[EMAIL PROTECTED] | | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.il.uil2.SocketManager] Write msg: org.jboss.mq.il.uil2.msgs.TransactMsg29651644[msgType: m_transact, msgID: -2147483571, error: null] | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.il.uil2.SocketManager] Read msgType: m_transact, msgID: -2147483571 | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.il.uil2.SocketManager] Read new msg: org.jboss.mq.il.uil2.msgs.TransactMsg14552258[msgType: m_transact, msgID: -2147483571, error: null] | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.il.uil2.ServerSocketManagerHandler] Begin handleMsg, msgType: 17 | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : transact | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.server.TracingInterceptor] ARG: [EMAIL PROTECTED] | 2004.06.30 08:58:08.609 GMT-05:00 TRACE [org.jboss.mq.server.BasicQueue] acknowledge AcknowledgementRequest:ACK,QUEUE.khubEmailQueue,ID:6-10886038859681 -9223372036854775806 [EMAIL PROTECTED] | 2004.06.30 08:58:08.609 GMT-05:00 DEBUG [org.jboss.mq.server.JMSDestinationManager] Exception occured, rolling back transaction: | javax.jms.JMSException: Transacation is not active. | at org.jboss.mq.pm.Tx.addPostRollbackTask(Tx.java:228) | at org.jboss.mq.pm.TxManager.addPostRollbackTask(TxManager.java:133) | at org.jboss.mq.server.BasicQueue.acknowledge(BasicQueue.java:530) | at org.jboss.mq.server.JMSQueue.acknowledge(JMSQueue.java:123) | at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:322) | at org.jboss.mq.server.JMSDestinationManager.acknowledge(JMSDestinationManager.java:524) | at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:436) | at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186) | at
[JBoss-user] [Messaging, JMS & JBossMQ] - 3.2.4 / JMS / Transacation is not active
We just upgraded from 3.2.3 to 3.2.4, and are now getting exceptions when trying to
send JMS messages.
We're using file-based message persistence, and a point-to-point transacted session.
Here's a snippet of stack trace:
2004.06.29 12:47:55.812 GMT-05:00 DEBUG [org.jboss.mq.server.JMSDestinationManager]
Exception occured, rolling back transaction:
javax.jms.JMSException: Transacation is not active.
at org.jboss.mq.pm.Tx.addPostRollbackTask(Tx.java:228)
at org.jboss.mq.pm.TxManager.addPostRollbackTask(TxManager.java:133)
at org.jboss.mq.server.BasicQueue.addMessage(BasicQueue.java:344)
at org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:40)
at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:131)
at
org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:402)
at
org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:428)
at
org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
at
org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:182)
at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:447)
at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
at
org.jboss.mq.il.uil2.ServerSocketManagerHandler.handleMsg(ServerSocketManagerHandler.java:166)
at
org.jboss.mq.il.uil2.SocketManager$ReadTask.handleMsg(SocketManager.java:356)
at org.jboss.mq.il.uil2.msgs.BaseMsg.run(BaseMsg.java:377)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
at java.lang.Thread.run(Thread.java:534)
Client code runs within a POJO, and looks like:
try {
Context context = ContextFactory.createContext();
QueueConnectionFactory factory =
(QueueConnectionFactory) context.lookup(ContextFactory.LMS_JMS);
QueueConnection conn = factory.createQueueConnection();
// since transacted_session=true (transacted mode), the 2nd arg is ignored
// and the session.commit() is required to delete the recieved message.
QueueSession session = conn.createQueueSession(true,
Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) context.lookup(ContextFactory.EVENT_QUEUE_NAME);
QueueSender sender = session.createSender(queue);
conn.start();
ObjectMessage objMsg = session.createObjectMessage();
objMsg.setJMSDeliveryMode( deliveryMode );
objMsg.setObject( this );
log.debug("send(): Sending event " + getClass().getName() );
sender.send( objMsg );
session.commit(); // required to delete the message after recieved
log.debug("send(): Sent & committed event " + this);
conn.close();
} catch ( Exception e ) {
log.error("send(): Failed to send JMS Message", e);
throw new RuntimeException("Failed to send JMS Message " + e.getMessage());
}
Here's what the jbossmq trace looks like before the exception:
2004.06.29 12:47:55.718 GMT-05:00 TRACE [org.jboss.mq.SpyXAResourceManager] Starting
tx with new xid=-9223372036854775806
2004.06.29 12:47:55.718 GMT-05:00 TRACE [org.jboss.mq.SpySession] New session [EMAIL
PROTECTED] txid=-9223372036854775806 RUNNING [EMAIL
PROTECTED]:ID:5/dda5f260f66ada4628aca68dbcac1da9 rcvstate=STARTED]]
2004.06.29 12:47:55.718 GMT-05:00 TRACE [org.jboss.mq.SpyMessageProducer] New message
producer [EMAIL PROTECTED] dest=QUEUE.khubEventQueue delivery=persist priority=4 ttl=0
disableMessageID=false disableTS=false [EMAIL PROTECTED] txid=-9223372036854775806
RUNNING [EMAIL PROTECTED]:ID:5/dda5f260f66ada4628aca68dbcac1da9 rcvstate=STARTED]]]
2004.06.29 12:47:55.718 GMT-05:00 TRACE [org.jboss.mq.SpySession] Adding producer
[EMAIL PROTECTED] dest=QUEUE.khubEventQueue delivery=persist priority=4 ttl=0
disableMessageID=false disableTS=false [EMAIL PROTECTED] txid=-9223372036854775806
RUNNING [EMAIL PROTECTED]:ID:5/dda5f260f66ada4628aca68dbcac1da9 rcvstate=STARTED]]]
2004.06.29 12:47:55.765 GMT-05:00 DEBUG [com.elementk.service.event.Event] send():
Sending event com.elementk.lms.khub.sys.email.GenerateEmailEvent
2004.06.29 12:47:55.765 GMT-05:00 TRACE [org.jboss.mq.SpyMessageProducer] Sending
message [EMAIL PROTECTED] dest=QUEUE.khubEventQueue delivery=persist priority=4 ttl=0
disableMessageID=false disableTS=false [EMAIL PROTECTED] txid=-9223372036854775806
RUNNING [EMAIL PROTECTED]:ID:5/dda5f260f66ada4628aca68dbcac1da9 rcvstate=STARTED]]]
org.jboss.mq.SpyObjectMessage {
Header {
jmsDestination : QUEUE.khubEventQueue
jmsDeliveryMode : 2
jmsExpiration : 0
jmsPriority : 4
jmsMessageID: ID:5-10885312757651
jmsTimeStamp: 1088531275765
jmsCorrelationID: null
jmsReplyTo : null
jmsType : null
jmsRedelivered : false
jmsProperties :
