activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio D'Errico (JIRA)" <>
Subject [jira] [Created] (AMQ-3844) NullPointerException when removing connection info
Date Wed, 16 May 2012 09:57:02 GMT
Antonio D'Errico created AMQ-3844:

             Summary: NullPointerException when removing connection info
                 Key: AMQ-3844
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.1, 5.4.3
         Environment: Linux 2.6.18-274.12.1.el5 #1 SMP Tue Nov 29 13:37:35 EST 2011 i686 athlon
i386 GNU/Linux, Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
            Reporter: Antonio D'Errico

Sometimes off and on the KahaDB maintains some old transactions that try to recovery. So at
start up these transactions are added to the {{xaTransactions}} inside {{TransactionBroker}}
with a null {{ConnectionId}}.

This is the stack trace of the recovery 
	TransactionBroker.beginTransaction(ConnectionContext, TransactionId) line: 152	
	TransactionBroker$1.recover(XATransactionId, Message[], MessageAck[]) line: 92	
	KahaDBTransactionStore.recover(TransactionRecoveryListener) line: 317	
	TransactionBroker.start() line: 89	
	BrokerService$3.start() line: 1781	
	XBeanBrokerService(BrokerService).start() line: 489	
	XBeanBrokerService.afterPropertiesSet() line: 60	
	NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]

	NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39	
	DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25	
	Method.invoke(Object, Object...) line: 597	
Object, RootBeanDefinition) line: 1536	
Object, RootBeanDefinition) line: 1477	
	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).initializeBean(String, Object,
RootBeanDefinition) line: 1409	
	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).doCreateBean(String, RootBeanDefinition,
Object[]) line: 519	
	DefaultListableBeanFactory(AbstractAutowireCapableBeanFactory).createBean(String, RootBeanDefinition,
Object[]) line: 456	
	AbstractBeanFactory$1.getObject() line: 291	
	DefaultListableBeanFactory(DefaultSingletonBeanRegistry).getSingleton(String, ObjectFactory)
line: 222	
	DefaultListableBeanFactory(AbstractBeanFactory).doGetBean(String, Class<T>, Object[],
boolean) line: 288	
	DefaultListableBeanFactory(AbstractBeanFactory).getBean(String) line: 190	
	DefaultListableBeanFactory.preInstantiateSingletons() line: 574	
line: 895	
	XBeanBrokerFactory$1(AbstractApplicationContext).refresh() line: 425	
	XBeanBrokerFactory$1(ResourceXmlApplicationContext).<init>(Resource, List) line: 64

	XBeanBrokerFactory$1(ResourceXmlApplicationContext).<init>(Resource) line: 52	
	XBeanBrokerFactory$1.<init>(XBeanBrokerFactory, Resource) line: 115	
	XBeanBrokerFactory.createApplicationContext(String) line: 115	
	XBeanBrokerFactory.createBroker(URI) line: 71	
	BrokerFactory.createBroker(URI, boolean) line: 71	
	BrokerFactory.createBroker(URI) line: 54	
	StartCommand.startBroker(URI) line: 115	
	StartCommand.runTask(List<String>) line: 74	
	StartCommand(AbstractCommand).execute(List<String>) line: 57	
	ShellCommand.runTask(List<String>) line: 143	
	ShellCommand(AbstractCommand).execute(List<String>) line: 57	
	ShellCommand.main(String[], InputStream, PrintStream) line: 85	
	NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]

	NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39	
	DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25	
	Method.invoke(Object, Object...) line: 597	
	Main.runTaskClass(List<String>) line: 251	
	Main.main(String[]) line: 107	 

after during execution the client add and remove connection and sometimes the removeConnection
throws a NPE because there are these transactions without ConnectionID

    public void removeConnection(ConnectionContext context, ConnectionInfo info, Throwable
error) throws Exception {
        for (Iterator<Transaction> iter = context.getTransactions().values().iterator();
iter.hasNext();) {
            try {
                Transaction transaction =;
            } catch (Exception e) {
                LOG.warn("ERROR Rolling back disconnected client's transactions: ", e);

        synchronized (xaTransactions) {
            // first find all txs that belongs to the connection
            ArrayList<XATransaction> txs = new ArrayList<XATransaction>();
            for (XATransaction tx : xaTransactions.values()) {
                if (tx.getConnectionId().equals(info.getConnectionId()) && !tx.isPrepared())

            // then remove them
            // two steps needed to avoid ConcurrentModificationException, from removeTransaction()
            for (XATransaction tx : txs) {
                try {
                } catch (Exception e) {
                    LOG.warn("ERROR Rolling back disconnected client's xa transactions: ",

        next.removeConnection(context, info, error);

as you can see inside the loop there is a check for {{tx.getConnectionId().equals(info.getConnectionId())}}
that throws the NPE so the connection isn't removed but this information isn't shared with
the client that the next time that try to resend client information to server obtain (under
jBoss) this error {{javax.transaction.xa.XAException: Broker: AMQ - Client: ID:srv001-47592-1336730655955-64:2
already connected from /}}
that can be bound to the server fails.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message