[jira] [Closed] (GERONIMO-6153) activemq broker is creating var/activemq in current directory, not server root
[ https://issues.apache.org/jira/browse/GERONIMO-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radim Kolar closed GERONIMO-6153. - Resolution: Not A Problem > activemq broker is creating var/activemq in current directory, not server root > -- > > Key: GERONIMO-6153 > URL: https://issues.apache.org/jira/browse/GERONIMO-6153 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0-M1 > Environment: windows xp >Reporter: Radim Kolar > Labels: activemq, broker > > activemq broker is creating his database in directory relative to current > directory not to server root directory. > When server is launched from bin (bin is current directory when running > startup.bat) then it creates > \bin\var\activemq\journal (etc) instead of \var\activemq as other server > components -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6333) Unable to create JMS broker from admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia resolved GERONIMO-6333. --- Resolution: Duplicate duplicated with geronimo-5960 > Unable to create JMS broker from admin console > -- > > Key: GERONIMO-6333 > URL: https://issues.apache.org/jira/browse/GERONIMO-6333 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0-beta-1 > Environment: Linux (Debian testing, x64), IBM J9 1.6, Geronimo > 3.0-beta-1 >Reporter: Moritz Hoffmann > > The documentation says that an ActiveMQ JMS broker can be created from the > console. See > https://cwiki.apache.org/GMOxDOC30/configuring-the-jms-server.html > When I run Geronimo, I do not see the "Add JMS Broker" link that is shown in > the documentation, thus I cannot create a new broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6333) Unable to create JMS broker from admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259091#comment-13259091 ] Kevan Miller commented on GERONIMO-6333: ActiveMQ config is updated in 3.0. Don't think we have the same level of admin console support as we had in earlier releases. To do this right now, you could edit repository/org/apache/geronimo/configs/activemq-broker-blueprint/3.0-beta-1/activemq-broker-blueprint-3.0-beta-1.car And update the to look something like: After updating, you'll need to clear var/cache and start/restart the server. E.g. './geronimo run --clean' > Unable to create JMS broker from admin console > -- > > Key: GERONIMO-6333 > URL: https://issues.apache.org/jira/browse/GERONIMO-6333 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0-beta-1 > Environment: Linux (Debian testing, x64), IBM J9 1.6, Geronimo > 3.0-beta-1 >Reporter: Moritz Hoffmann > > The documentation says that an ActiveMQ JMS broker can be created from the > console. See > https://cwiki.apache.org/GMOxDOC30/configuring-the-jms-server.html > When I run Geronimo, I do not see the "Add JMS Broker" link that is shown in > the documentation, thus I cannot create a new broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6333) Unable to create JMS broker from admin console
Moritz Hoffmann created GERONIMO-6333: - Summary: Unable to create JMS broker from admin console Key: GERONIMO-6333 URL: https://issues.apache.org/jira/browse/GERONIMO-6333 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 3.0-beta-1 Environment: Linux (Debian testing, x64), IBM J9 1.6, Geronimo 3.0-beta-1 Reporter: Moritz Hoffmann The documentation says that an ActiveMQ JMS broker can be created from the console. See https://cwiki.apache.org/GMOxDOC30/configuring-the-jms-server.html When I run Geronimo, I do not see the "Add JMS Broker" link that is shown in the documentation, thus I cannot create a new broker. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-5960) Enable the functionality of add, edit, delete & start/stop a broker in JMS portlets
[ https://issues.apache.org/jira/browse/GERONIMO-5960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240380#comment-13240380 ] Forrest Xia commented on GERONIMO-5960: --- Turning ActiveMQ module from blueprint back to the old way could be resolution to this issue. > Enable the functionality of add, edit, delete & start/stop a broker in JMS > portlets > --- > > Key: GERONIMO-5960 > URL: https://issues.apache.org/jira/browse/GERONIMO-5960 > Project: Geronimo > Issue Type: Task > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shenghao Fang >Priority: Minor > > Enable the functionality of add, edit, delete & start/stop a broker in JMS > portlets. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6153) activemq broker is creating var/activemq in current directory, not server root
activemq broker is creating var/activemq in current directory, not server root -- Key: GERONIMO-6153 URL: https://issues.apache.org/jira/browse/GERONIMO-6153 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 3.0-M1 Environment: windows xp Reporter: Radim Kolar activemq broker is creating his database in directory relative to current directory not to server root directory. When server is launched from bin (bin is current directory when running startup.bat) then it creates \bin\var\activemq\journal (etc) instead of \var\activemq as other server components -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu closed GERONIMO-5559. -- close it > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.ConnectionInfo@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) > ... 12 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) > at
[jira] [Resolved] (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-5559. --- Resolution: Duplicate GERONIMO-5987 will be used to track this. > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.ConnectionInfo@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) > ... 12 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:
[jira] [Created] (GERONIMO-5960) Enable the functionality of add, edit, delete & start/stop a broker in JMS portlets
Enable the functionality of add, edit, delete & start/stop a broker in JMS portlets --- Key: GERONIMO-5960 URL: https://issues.apache.org/jira/browse/GERONIMO-5960 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: console Affects Versions: 3.0 Reporter: Shenghao Fang Assignee: Shenghao Fang Priority: Minor Enable the functionality of add, edit, delete & start/stop a broker in JMS portlets. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008856#comment-13008856 ] Marcin Rzeźnicki commented on GERONIMO-5559: ... and the mighty stupid idea of setting the default value of activemq.data to a *relative* path means that you cannot start geronimo server from wherever you want - you have to specifically cd to a directory it owns or else it crashes complaining that it cannot create 'activemq' directory. > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.ConnectionInfo@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) > ... 12 more > Caused by: java.net.ConnectException: Connection refused: con
[jira] Commented: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008804#comment-13008804 ] Marcin Rzeźnicki commented on GERONIMO-5559: Except that it is not reading the configuration file: activemq.brokerName=activemq activemq.data=/usr/local/geronimo/var/activemq serverHostname=xxx.xxx.xxx activemq.port=61616 portOffset=0 # netstat -nlp | grep 20550 snip tcp0 0 127.0.0.1:61616 0.0.0.0:* LISTEN 20550/java > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.ConnectionInfo@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) > ... 12 more > Caused by: java.net.ConnectExcepti
[jira] Issue Comment Edited: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008804#comment-13008804 ] Marcin Rzeźnicki edited comment on GERONIMO-5559 at 3/19/11 6:06 PM: - Except that it is not reading the configuration file: activemq.brokerName=activemq activemq.data=/usr/local/geronimo/var/activemq serverHostname=xxx.xxx.xxx activemq.port=61616 portOffset=0 *netstat -nlp | grep 20550* snip tcp0 0 127.0.0.1:61616 0.0.0.0:* LISTEN 20550/java was (Author: rzeznik): Except that it is not reading the configuration file: activemq.brokerName=activemq activemq.data=/usr/local/geronimo/var/activemq serverHostname=xxx.xxx.xxx activemq.port=61616 portOffset=0 # netstat -nlp | grep 20550 snip tcp0 0 127.0.0.1:61616 0.0.0.0:* LISTEN 20550/java > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.ConnectionInfo@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apa
Re: How to support add a new broker in Geronimo 3.0
>From the responses in the user mail list, we do find that there is people using it. Our default ActiveMQ broker only contains some basic configurations, it seems to me just like a demo. But I agree that this is not of high priority, we might wait for some time to decide how to implement it after some changes in Geronimo kernel. For now, think that we could just try to make those broker info is listed, such as connector info, broker name, etc. 2011/3/17 Kevan Miller > > On Mar 16, 2011, at 4:19 AM, Ivan wrote: > > > Hi, > > Now, in Geronimo 3.0, blueprint configuration has been used for > ActiveMQ broker. Now we might be facing the problem how to add a new broker, > which is totally different from the way in Geronimo 2.2. > > One possible way is to use the similar way in Geronimo 2.2, place a > template configuration file in the var/activemq folder, and while users add > a new broker on the admin console, still use that existed big edit box for > the users to display the copied configuration file, then package it as > bundle, save it in the repository and start it. > > Also, an ActiveMQ broker management configuration is required to > record all the added brokers, so that we could list all the started and > stopped brokers. > > Not sure whether there is a more OSGi-friendly way to do it. > Thoughts ? > > I confess that I didn't know/had forgotten that we had this capability. I > don't know why it was added or anybody who's actually used it. I also don't > know anyone who is running multiple brokers in the same server. Multiple > brokers may be a nice feature to have, but I'm not sure why we need admin > console support for it. > > Personally, I'd be fine if the admin console only supported management of > the default broker. Creation and configuration of additional brokers could > be outside the scope of the admin console. I have no problem with having a > general technique for creating/managing all brokers, but that would be low > on my personal priority list... > > --kevan -- Ivan
Re: How to support add a new broker in Geronimo 3.0
On Mar 16, 2011, at 4:19 AM, Ivan wrote: > Hi, > Now, in Geronimo 3.0, blueprint configuration has been used for ActiveMQ > broker. Now we might be facing the problem how to add a new broker, which is > totally different from the way in Geronimo 2.2. > One possible way is to use the similar way in Geronimo 2.2, place a > template configuration file in the var/activemq folder, and while users add a > new broker on the admin console, still use that existed big edit box for the > users to display the copied configuration file, then package it as bundle, > save it in the repository and start it. > Also, an ActiveMQ broker management configuration is required to record > all the added brokers, so that we could list all the started and stopped > brokers. > Not sure whether there is a more OSGi-friendly way to do it. Thoughts ? I confess that I didn't know/had forgotten that we had this capability. I don't know why it was added or anybody who's actually used it. I also don't know anyone who is running multiple brokers in the same server. Multiple brokers may be a nice feature to have, but I'm not sure why we need admin console support for it. Personally, I'd be fine if the admin console only supported management of the default broker. Creation and configuration of additional brokers could be outside the scope of the admin console. I have no problem with having a general technique for creating/managing all brokers, but that would be low on my personal priority list... --kevan
How to support add a new broker in Geronimo 3.0
Hi, Now, in Geronimo 3.0, blueprint configuration has been used for ActiveMQ broker. Now we might be facing the problem how to add a new broker, which is totally different from the way in Geronimo 2.2. One possible way is to use the similar way in Geronimo 2.2, place a template configuration file in the var/activemq folder, and while users add a new broker on the admin console, still use that existed big edit box for the users to display the copied configuration file, then package it as bundle, save it in the repository and start it. Also, an ActiveMQ broker management configuration is required to record all the added brokers, so that we could list all the started and stopped brokers. Not sure whether there is a more OSGi-friendly way to do it. Thoughts ? -- Ivan
Re: svn commit: r963176 - in /geronimo/server/branches/2.2/plugins/activemq/activemq-broker/src/main/resources: activemq-template.xml activemq.xml
On Jul 11, 2010, at 10:43 PM, genspr...@apache.org wrote: > Author: genspring > Date: Mon Jul 12 02:43:22 2010 > New Revision: 963176 > > URL: http://svn.apache.org/viewvc?rev=963176&view=rev > Log: > Revert "GERONIMO-5372 - change the default adapter in geronimo to kahaDB". > Because it's causing a jms tck failure. Since persistentAdapter is also > working well per GERONIMO-5426. we need to revert this back. Hi Shawn, Do we have information on the failures that kahaDB caused? If this is a problem with the kahaDB persistence adapter, we should pass this information along to the ActiveMQ community so that the problem can be fixed. Would it be possible to recreate this problem? --kevan
[jira] Commented: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904113#action_12904113 ] viola.lu commented on GERONIMO-5559: Currently activemq-broker module is registered as blueprint service, its properties are set by file:$(karaf.base)/etc/blueprint-activemq-placeholder.cfg not by reading config-substitutions.properties file under $geronimo_home/var/config/, in future, config-substitutions.properties will be run as config-admin service, so this bug will be fixed after config-admin function is ready. > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.connectioni...@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.cre
[jira] Assigned: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
[ https://issues.apache.org/jira/browse/GERONIMO-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu reassigned GERONIMO-5559: -- Assignee: viola.lu > "javax.jms.JMSException: Could not connect to broker URL" server startup > error exists after change default PortOffset value > --- > > Key: GERONIMO-5559 > URL: https://issues.apache.org/jira/browse/GERONIMO-5559 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 3.0 > Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 >Reporter: viola.lu >Assignee: viola.lu >Priority: Minor > Fix For: 3.0 > > > 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ > var/config/config-substitutions.properties > 2.Startup server, start successfully, but a lot of erros popup: > 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not > get XAResource for recovery for mcf: > geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory > 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred > creating ManagedConnection for > org.apache.geronimo.connector.outbound.connectioni...@5de7f1 > javax.resource.ResourceException: Could not create connection. > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) > at > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) > at > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) > at > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) > at > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) > at > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) > at > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) > at > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) > at > org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) > at > org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) > at > org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: javax.jms.JMSException: Could not connect to broker URL: > tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: > connect > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) > at > org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) > at > org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) > at > org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) > at > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) > ... 12 more > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksS
[jira] Created: (GERONIMO-5559) "javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value
"javax.jms.JMSException: Could not connect to broker URL" server startup error exists after change default PortOffset value --- Key: GERONIMO-5559 URL: https://issues.apache.org/jira/browse/GERONIMO-5559 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 3.0 Environment: winxp, suse 10 sp2, jdk : jdk 1.6.0_22 Reporter: viola.lu Priority: Minor Fix For: 3.0 1. Change PortOffset=0 to PortOffset=1 under $geronimo_home/ var/config/config-substitutions.properties 2.Startup server, start successfully, but a lot of erros popup: 2010-08-27 17:26:05,859 ERROR [RecoveryController] Recovery error: Could not get XAResource for recovery for mcf: geronimo:J2EEApplication=null,J2EEServer=geronimo,JCAConnectionFactory=DefaultActiveMQConnectionFactory,JCAManagedConnectionFactory=DefaultActiveMQConnectionFactory,JCAResource=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapter=geronimo-activemq-ra-3.0-SNAPSHOT,ResourceAdapterModule=org.apache.geronimo.configs/activemq-ra/3.0-SNAPSHOT/car,j2eeType=JCAConnectionManager,name=DefaultActiveMQConnectionFactory 2010-08-27 17:27:10,937 ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for org.apache.geronimo.connector.outbound.connectioni...@5de7f1 javax.resource.ResourceException: Could not create connection. at org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:171) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(MCFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnection(XAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internalGetConnection(SinglePoolConnectionInterceptor.java:69) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor.getConnection(AbstractSinglePoolConnectionInterceptor.java:80) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConnection(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnection(TransactionCachingInterceptor.java:103) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterceptor.java:39) at org.apache.geronimo.connector.outbound.OutboundNamedXAResourceFactory.getNamedXAResource(OutboundNamedXAResourceFactory.java:56) at org.apache.geronimo.transaction.manager.RecoverTask.run(RecoverTask.java:49) at org.apache.geronimo.transaction.manager.ExponentialtIntervalRetryScheduler$TaskWrapper.run(ExponentialtIntervalRetryScheduler.java:50) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61617. Reason: java.net.ConnectException: Connection refused: connect at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:35) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:286) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:185) at org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:79) at org.apache.activemq.ra.ActiveMQConnectionSupport.makeConnection(ActiveMQConnectionSupport.java:61) at org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection(ActiveMQManagedConnectionFactory.java:169) ... 12 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at org.apache.activemq.transport.tcp.TcpTransport.connect(TcpTransport.java:483) at org.apache.activemq.transport.tcp.TcpTransport.doStart(TcpTransport.java:446) at org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:53) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58) at org.apache.activemq.transport.TransportFilter.start(TransportFilter.java:58) at org.apache.activemq.transport.WireFormatNegoti
[jira] Created: (GERONIMO-5271) Classes in the activemq-broker should not be exposed to applications deployed in Geronimo
Classes in the activemq-broker should not be exposed to applications deployed
in Geronimo
--
Key: GERONIMO-5271
URL: https://issues.apache.org/jira/browse/GERONIMO-5271
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: ActiveMQ
Affects Versions: 2.2
Reporter: Bruce Snyder
In the process of deploying a web application in Geronimo that makes use of the
activemq-broker Geronimo plugin, I had to use the {{}} element
in the geronimo-web.xml to prevent the Spring jars in the activemq-broker being
exposed to the web application. This should not be a requirement as the
activemq-broker should not expose any of its dependencies to applications
deployed in Geronimo. Geronimo should just hide all of the activemq-broker
dependencies from leaking into the web app classloader by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r926991 - /geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
Yes, I agree. How about merge server-security-config car into
j2ee-security(actually I think we should rename the car as server-security)?
Will open a jira to track this.
2010/3/24 Kevan Miller
> Thanks Rex. Makes sense.
>
> I guess that's consistent with our treatment of server-security-config
> dependencies, but I'm not convinced we're handling them correctly. Pretty
> certain that we can build alternate assemblies with the same basic
> problem...
>
> --kevan
>
> On Mar 24, 2010, at 5:40 AM, rwo...@apache.org wrote:
>
> > Author: rwonly
> > Date: Wed Mar 24 09:40:12 2010
> > New Revision: 926991
> >
> > URL: http://svn.apache.org/viewvc?rev=926991&view=rev
> > Log:
> > GERONIMO-5024 var/security/keystores seems to be a required directory,
> but is not being created for custom assemblies
> >
> > Modified:
> >geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> >
> > Modified:
> geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> > URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml?rev=926991&r1=926990&r2=926991&view=diff
> >
> ==
> > --- geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> (original)
> > +++ geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> Wed Mar 24 09:40:12 2010
> > @@ -51,7 +51,14 @@
> > ${version}
> > car
> >
> > -
> > +
> > +
> > +org.apache.geronimo.framework
> > +server-security-config
> > +${version}
> > +car
> > +
> > +
> >
> > org.apache.geronimo.modules
> > geronimo-activemq
> >
> >
>
>
--
Lei Wang (Rex)
rwonly AT apache.org
Re: svn commit: r926991 - /geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
Thanks Rex. Makes sense.
I guess that's consistent with our treatment of server-security-config
dependencies, but I'm not convinced we're handling them correctly. Pretty
certain that we can build alternate assemblies with the same basic problem...
--kevan
On Mar 24, 2010, at 5:40 AM, rwo...@apache.org wrote:
> Author: rwonly
> Date: Wed Mar 24 09:40:12 2010
> New Revision: 926991
>
> URL: http://svn.apache.org/viewvc?rev=926991&view=rev
> Log:
> GERONIMO-5024 var/security/keystores seems to be a required directory, but is
> not being created for custom assemblies
>
> Modified:
>geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
>
> Modified:
> geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> URL:
> http://svn.apache.org/viewvc/geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml?rev=926991&r1=926990&r2=926991&view=diff
> ======
> --- geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml
> (original)
> +++ geronimo/server/branches/2.2/plugins/activemq/activemq-broker/pom.xml Wed
> Mar 24 09:40:12 2010
> @@ -51,7 +51,14 @@
> ${version}
> car
>
> -
> +
> +
> +org.apache.geronimo.framework
> +server-security-config
> +${version}
> +car
> +
> +
>
> org.apache.geronimo.modules
> geronimo-activemq
>
>
[jira] Closed: (GERONIMO-4806) improvement about ssl in JMS broker
[
https://issues.apache.org/jira/browse/GERONIMO-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He closed GERONIMO-4806.
Resolution: Fixed
Fix Version/s: 2.2
Jeff has updated the doc.
> improvement about ssl in JMS broker
>
>
> Key: GERONIMO-4806
> URL: https://issues.apache.org/jira/browse/GERONIMO-4806
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: documentation
>Affects Versions: 2.2
>Reporter: Bin He
> Fix For: 2.2
>
> Attachments: testBroker.xml
>
>
> 1、click "JMS Server" porlet
> 2、click "Add JMS Broker"
> 3、input "testBroker" as broker name
> 4、I need to update this xml file like this:
>
>
> uri="ssl://${ServerHostname}:${60009 + ${PortOffset}}"/>
>
>
>
> keyStorePassword="secret"
> trustStore="file:${activemq.data}/a.ks"
> trustStorePassword="secret"/>
>
>
> 5、 I need to copy any keystore file(geronimo-default or any other keystore
> file that I have created) in /var/security/keystores/ to
> /var/activemq/data/$brokerName/
> and rename this keystore file.(It's not compulsory to copy or rename,it's
> just for convinence.In a word , I have to make this keystore in sslContext
> link to a keystore file which has existed. )
> (Note in this case the brokerName is testBroker and the name of the
> keystore file in /var/activemq/data/$brokerName/ is "a.ks").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4806) improvement about ssl in JMS broker
[
https://issues.apache.org/jira/browse/GERONIMO-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750348#action_12750348
]
Chi Runhua commented on GERONIMO-4806:
--
Doc updated accordingly for 2.2
http://cwiki.apache.org/GMOxDOC22/configuring-the-jms-server.html
Any questions, please let me know.
Jeff C
> improvement about ssl in JMS broker
>
>
> Key: GERONIMO-4806
> URL: https://issues.apache.org/jira/browse/GERONIMO-4806
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: documentation
>Affects Versions: 2.2
>Reporter: Bin He
> Attachments: testBroker.xml
>
>
> 1、click "JMS Server" porlet
> 2、click "Add JMS Broker"
> 3、input "testBroker" as broker name
> 4、I need to update this xml file like this:
>
>
> uri="ssl://${ServerHostname}:${60009 + ${PortOffset}}"/>
>
>
>
> keyStorePassword="secret"
> trustStore="file:${activemq.data}/a.ks"
> trustStorePassword="secret"/>
>
>
> 5、 I need to copy any keystore file(geronimo-default or any other keystore
> file that I have created) in /var/security/keystores/ to
> /var/activemq/data/$brokerName/
> and rename this keystore file.(It's not compulsory to copy or rename,it's
> just for convinence.In a word , I have to make this keystore in sslContext
> link to a keystore file which has existed. )
> (Note in this case the brokerName is testBroker and the name of the
> keystore file in /var/activemq/data/$brokerName/ is "a.ks").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4806) improvement about ssl in JMS broker
[
https://issues.apache.org/jira/browse/GERONIMO-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He updated GERONIMO-4806:
-
Description:
1、click "JMS Server" porlet
2、click "Add JMS Broker"
3、input "testBroker" as broker name
4、I need to update this xml file like this:
5、 I need to copy any keystore file(geronimo-default or any other keystore
file that I have created) in /var/security/keystores/ to
/var/activemq/data/$brokerName/
and rename this keystore file.(It's not compulsory to copy or rename,it's
just for convinence.In a word , I have to make this keystore in sslContext
link to a keystore file which has existed. )
(Note in this case the brokerName is testBroker and the name of the keystore
file in /var/activemq/data/$brokerName/ is "a.ks").
was:
1、click "JMS Server" porlet
2、click "Add JMS Broker"
3、input "testBroker" as broker name
4、I need to update this xml file like this:
5、 I need to copy any keystore file(geronimo-default or any other keystore
file that I have created) in /var/security/keystores/ to
/var/activemq/data/$brokerName/
and rename this keystore file.(It's not compulsory) to copy or rename,it's
just for convinence.In a word , I have to make this keystore in sslContext
link to a keystore file which has existed. )
(Note in this case the brokerName is testBroker and the name of the keystore
file in /var/activemq/data/$brokerName/ is "a.ks").
> improvement about ssl in JMS broker
>
>
> Key: GERONIMO-4806
> URL: https://issues.apache.org/jira/browse/GERONIMO-4806
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: documentation
>Affects Versions: 2.2
>Reporter: Bin He
> Attachments: testBroker.xml
>
>
> 1、click "JMS Server" porlet
> 2、click "Add JMS Broker"
> 3、input "testBroker" as broker name
> 4、I need to update this xml file like this:
>
>
> uri="ssl://${ServerHostname}:${60009 + ${PortOffset}}"/>
>
>
>
> keyStorePassword="secret"
> trustStore="file:${activemq.data}/a.ks"
> trustStorePassword="secret"/>
>
>
> 5、 I need to copy any keystore file(geronimo-default or any other keystore
> file that I have created) in /var/security/keystores/ to
> /var/activemq/data/$brokerName/
> and rename this keystore file.(It's not compulsory to copy or rename,it's
> just for convinence.In a word , I have to make this keystore in sslContext
> link to a keystore file which has existed. )
> (Note in this case the brokerName is testBroker and the name of the
> keystore file in /var/activemq/data/$brokerName/ is "a.ks").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4806) improvement about ssl in JMS broker
[
https://issues.apache.org/jira/browse/GERONIMO-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He updated GERONIMO-4806:
-
Description:
1、click "JMS Server" porlet
2、click "Add JMS Broker"
3、input "testBroker" as broker name
4、I need to update this xml file like this:
5、 I need to copy any keystore file(geronimo-default or any other keystore
file that I have created) in /var/security/keystores/ to
/var/activemq/data/$brokerName/
and rename this keystore file.(It's not compulsory) to copy or rename,it's
just for convinence.In a word , I have to make this keystore in sslContext
link to a keystore file which has existed. )
(Note in this case the brokerName is testBroker and the name of the keystore
file in /var/activemq/data/$brokerName/ is "a.ks").
was:
1、click "JMS Server" porlet
2、click "Add JMS Broker"
3、input "testBroker" as broker name
4、I need to update this xml file like this:
5、 I need to copy any keystore file(geronimo-default or any other keystore
file that I have created) in /var/security/keystores/ to
/var/activemq/data/$brokerName/
and rename this keystore file as "a.ks".(Note in this case the brokerName is
testBroker).
> improvement about ssl in JMS broker
>
>
> Key: GERONIMO-4806
> URL: https://issues.apache.org/jira/browse/GERONIMO-4806
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: documentation
>Affects Versions: 2.2
> Reporter: Bin He
> Attachments: testBroker.xml
>
>
> 1、click "JMS Server" porlet
> 2、click "Add JMS Broker"
> 3、input "testBroker" as broker name
> 4、I need to update this xml file like this:
>
>
> uri="ssl://${ServerHostname}:${60009 + ${PortOffset}}"/>
>
>
>
> keyStorePassword="secret"
> trustStore="file:${activemq.data}/a.ks"
> trustStorePassword="secret"/>
>
>
> 5、 I need to copy any keystore file(geronimo-default or any other keystore
> file that I have created) in /var/security/keystores/ to
> /var/activemq/data/$brokerName/
> and rename this keystore file.(It's not compulsory) to copy or rename,it's
> just for convinence.In a word , I have to make this keystore in sslContext
> link to a keystore file which has existed. )
> (Note in this case the brokerName is testBroker and the name of the
> keystore file in /var/activemq/data/$brokerName/ is "a.ks").
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4806) improvement about ssl in JMS broker
[
https://issues.apache.org/jira/browse/GERONIMO-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bin He updated GERONIMO-4806:
-
Attachment: testBroker.xml
> improvement about ssl in JMS broker
>
>
> Key: GERONIMO-4806
> URL: https://issues.apache.org/jira/browse/GERONIMO-4806
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: documentation
>Affects Versions: 2.2
>Reporter: Bin He
> Attachments: testBroker.xml
>
>
> 1、click "JMS Server" porlet
> 2、click "Add JMS Broker"
> 3、input "testBroker" as broker name
> 4、I need to update this xml file like this:
>
>
> uri="ssl://${ServerHostname}:${60009 + ${PortOffset}}"/>
>
>
>
> keyStorePassword="secret"
> trustStore="file:${activemq.data}/a.ks"
> trustStorePassword="secret"/>
>
>
> 5、 I need to copy any keystore file(geronimo-default or any other keystore
> file that I have created) in /var/security/keystores/ to
> /var/activemq/data/$brokerName/
> and rename this keystore file as "a.ks".(Note in this case the brokerName
> is testBroker).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4806) improvement about ssl in JMS broker
improvement about ssl in JMS broker Key: GERONIMO-4806 URL: https://issues.apache.org/jira/browse/GERONIMO-4806 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: documentation Affects Versions: 2.2 Reporter: Bin He 1、click "JMS Server" porlet 2、click "Add JMS Broker" 3、input "testBroker" as broker name 4、I need to update this xml file like this: 5、 I need to copy any keystore file(geronimo-default or any other keystore file that I have created) in /var/security/keystores/ to /var/activemq/data/$brokerName/ and rename this keystore file as "a.ks".(Note in this case the brokerName is testBroker). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728586#action_12728586 ] Forrest Xia commented on GERONIMO-4475: --- A bug found: if stopped a new created broker, the JMS resources page will show nothing, even the default broker is still running! Moreover, the jms connector module which depends on the new created broker is still in running state. But we should expect it in stopped state. > Improve JMS portlet for AMQ 5.3 Broker configuration > > > Key: GERONIMO-4475 > URL: https://issues.apache.org/jira/browse/GERONIMO-4475 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > Attachments: G4475-activemq-broker-00.patch, > G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch, > G4475-geronimo-activemq.patch, G4475-geronimo-management.patch > > > Currently in the administrator console, the users could not add another embed > broker. Also, they could not edit the broker through administrator console. > I list the features that I could see : > 1. While creating the broker, let the use upload a configuration file. > 2. While editing the broker, show a text area, so that the user could edit > the spring XML file in it. Shall we give the user a more friendly interface, > so that they do not need the edit the XML file directly. I am not sure how it > should look like. > 3. Update the connector port let, so that while creating a new connector, > the user could specify the broker that it belongs to. > Please help to give some comments ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4494) Add and remove connectors for broker do not work
[ https://issues.apache.org/jira/browse/GERONIMO-4494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-4494: --- Fix Version/s: Wish List > Add and remove connectors for broker do not work > > > Key: GERONIMO-4494 > URL: https://issues.apache.org/jira/browse/GERONIMO-4494 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: Wish List > > > After migrating to ActiveMQ 5.2, the implementation for adding and removing > connectors for brokers are removed. > For in 2.2, we wish to add the support for adding and editing a broker, and > the way in plan is to give the end user a textarea to show the configuration > xml files. > For the configurations for connectors are included in the same configuration > files. I wonder whether we need to provide another entry point for editing > connectors. > IMO, I would like remove the connector functions and only list all the > connectors in all the brokers. In the future, we have a GUI like EJB portlet, > then recover it. > Thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4610) Can not create a broker on Linux platform
[ https://issues.apache.org/jira/browse/GERONIMO-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4610. Resolution: Fixed Fix Version/s: 2.2 Commit the changes to trunk at revision: 761212 > Can not create a broker on Linux platform > - > > Key: GERONIMO-4610 > URL: https://issues.apache.org/jira/browse/GERONIMO-4610 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 2.2 > Environment: Ubuntu 8.04 > JDK 1.6 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > > Could not create a new broker while Geronimo 2.2 is running on Linux platform. > Report error /var/activemq/conf/sdfsadf.xml (No such file or directory) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4610) Can not create a broker on Linux platform
Can not create a broker on Linux platform - Key: GERONIMO-4610 URL: https://issues.apache.org/jira/browse/GERONIMO-4610 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 2.2 Environment: Ubuntu 8.04 JDK 1.6 Reporter: Ivan Assignee: Ivan Could not create a new broker while Geronimo 2.2 is running on Linux platform. Report error /var/activemq/conf/sdfsadf.xml (No such file or directory) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan resolved GERONIMO-4475. Resolution: Fixed I run the testcases failed in the comment of Donald, it passes. Commit changes to trunk revision: 754635 Update the temp storage path and the binding host name with the values in the config-substitution.properties. > Improve JMS portlet for AMQ 5.3 Broker configuration > > > Key: GERONIMO-4475 > URL: https://issues.apache.org/jira/browse/GERONIMO-4475 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > Attachments: G4475-activemq-broker-00.patch, > G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch, > G4475-geronimo-activemq.patch, G4475-geronimo-management.patch > > > Currently in the administrator console, the users could not add another embed > broker. Also, they could not edit the broker through administrator console. > I list the features that I could see : > 1. While creating the broker, let the use upload a configuration file. > 2. While editing the broker, show a text area, so that the user could edit > the spring XML file in it. Shall we give the user a more friendly interface, > so that they do not need the edit the XML file directly. I am not sure how it > should look like. > 3. Update the connector port let, so that while creating a new connector, > the user could specify the broker that it belongs to. > Please help to give some comments ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4475) Improve JMS portlet for AMQ 5.3 Broker configuration
[ https://issues.apache.org/jira/browse/GERONIMO-4475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Sisson updated GERONIMO-4475: -- Summary: Improve JMS portlet for AMQ 5.3 Broker configuration (was: Improve JMS portlet for AMQ 5.3 Borker configuration) Corrected description > Improve JMS portlet for AMQ 5.3 Broker configuration > > > Key: GERONIMO-4475 > URL: https://issues.apache.org/jira/browse/GERONIMO-4475 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > Attachments: G4475-activemq-broker-00.patch, > G4475-activemq-broker.patch, G4475-activemq-portlet-update-02.patch, > G4475-geronimo-activemq.patch, G4475-geronimo-management.patch > > > Currently in the administrator console, the users could not add another embed > broker. Also, they could not edit the broker through administrator console. > I list the features that I could see : > 1. While creating the broker, let the use upload a configuration file. > 2. While editing the broker, show a text area, so that the user could edit > the spring XML file in it. Shall we give the user a more friendly interface, > so that they do not need the edit the XML file directly. I am not sure how it > should look like. > 3. Update the connector port let, so that while creating a new connector, > the user could specify the broker that it belongs to. > Please help to give some comments ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4494) Add and remove connectors for broker do not work
Add and remove connectors for broker do not work Key: GERONIMO-4494 URL: https://issues.apache.org/jira/browse/GERONIMO-4494 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Assignee: Ivan After migrating to ActiveMQ 5.2, the implementation for adding and removing connectors for brokers are removed. For in 2.2, we wish to add the support for adding and editing a broker, and the way in plan is to give the end user a textarea to show the configuration xml files. For the configurations for connectors are included in the same configuration files. I wonder whether we need to provide another entry point for editing connectors. IMO, I would like remove the connector functions and only list all the connectors in all the brokers. In the future, we have a GUI like EJB portlet, then recover it. Thanks for any comment ! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3148.
--
Resolution: Duplicate
Assignee: David Jencks
This is getting fixed in 2.2 as part of the move to activemq 5.2 (GERONIMO-4337)
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
>Assignee: David Jencks
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2918) Have the ActiveMQ broker configured from an external configuration file by default
[ https://issues.apache.org/jira/browse/GERONIMO-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-2918. -- Resolution: Duplicate Assignee: David Jencks This is getting "fixed" in 2.2 as we upgrade to amq 5.2. I doubt the initial implementation will allow any editing of the amq config file: we might add some later. > Have the ActiveMQ broker configured from an external configuration file by > default > -- > > Key: GERONIMO-2918 > URL: https://issues.apache.org/jira/browse/GERONIMO-2918 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 1.2 >Reporter: Aman Nanner >Assignee: David Jencks >Priority: Minor > Fix For: 1.2 > > Attachments: activemq-config.patch > > > Currently, the org.apache.activemq.gbean.BrokerServiceGBeanImpl GBean is > configured in the activemq-broker config and is thus built into a serialized > configuration during the build process. Looking at the plan.xml, there is a > commented-out section that specifies an external configuration file to be > used. Enabling this section allows for the broker to be configured by an > external file. > This configuration should be changed so that the activemq-broker > configuration refers to an external file by default, rather than being > internally configured in the plan. This external file can exist somewhere in > the geronimo folder hieracy (e.g. var/config/activemq.xml). This external > file should contain the same minimal configuration that is currently > specified in the GBean descriptor in the plan.xml. > The benefit of having an external file by default is that the activemq broker > can be configured without having to rebuild Geronimo. This makes the > ActiveMQ configuration much easier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r712197 - in /geronimo/server/trunk/plugins/activemq5: activemq5-broker/src/main/history/ activemq5-broker/src/main/plan/ activemq5-broker/src/main/resources/ geronimo-activemq5/ geron
Hi Bruce... where the heck you been?
:-P
--jason
On Nov 8, 2008, at 12:02 AM, [EMAIL PROTECTED] wrote:
Author: bsnyder
Date: Fri Nov 7 09:01:53 2008
New Revision: 712197
URL: http://svn.apache.org/viewvc?rev=712197&view=rev
Log:
GERONIMO-4337 - Upgrade to activeMQ 5.1.0
Added:
geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/
resources/
geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/
resources/activemq.xml (with props)
Removed:
geronimo/server/trunk/plugins/activemq5/geronimo-activemq5/src/
main/java/org/apache/geronimo/activemq/
TransportConnectorGBeanImpl.java
Modified:
geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/
history/dependencies.xml
geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/
plan/plan.xml
geronimo/server/trunk/plugins/activemq5/geronimo-activemq5/pom.xml
geronimo/server/trunk/plugins/activemq5/geronimo-activemq5/src/
main/java/org/apache/geronimo/activemq/BrokerServiceGBeanImpl.java
geronimo/server/trunk/plugins/activemq5/geronimo-activemq5/src/
main/java/org/apache/geronimo/activemq/management/
ActiveMQManagerGBean.java
geronimo/server/trunk/plugins/activemq5/geronimo-activemq5/src/
test/java/org/apache/geronimo/activemq/ConnectorTest.java
Modified: geronimo/server/trunk/plugins/activemq5/activemq5-broker/
src/main/history/dependencies.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/history/dependencies.xml?rev=712197&r1=712196&r2=712197&view=diff
=
=
=
=
=
=
=
=
==
--- geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/history/dependencies.xml (original)
+++ geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/history/dependencies.xml Fri Nov 7 09:01:53 2008
@@ -7,18 +7,33 @@
car
+org.apache.activemq
+activeio-core
+jar
+
+
backport-util-concurrent
backport-util-concurrent
jar
-org.apache.activemq
-activeio-core
+org.apache.camel
+camel-core
jar
-org.apache.activemq
-activemq-core
+commons-logging
+commons-logging
+jar
+
+
+org.springframework
+spring-core
+jar
+
+
+javax.servlet
+servlet-api
jar
@@ -27,6 +42,21 @@
car
+logkit
+logkit
+jar
+
+
+avalon-framework
+avalon-framework
+jar
+
+
+org.apache.activemq
+activemq-core
+jar
+
+
org.apache.geronimo.modules
geronimo-activemq5
jar
@@ -36,4 +66,9 @@
geronimo-activemq5-management
jar
+
+org.apache.activemq
+activeio-core
+test-jar
+
Modified: geronimo/server/trunk/plugins/activemq5/activemq5-broker/
src/main/plan/plan.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/plan/plan.xml?rev=712197&r1=712196&r2=712197&view=diff
=
=
=
=
=
=
=
=
==
--- geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/plan/plan.xml (original)
+++ geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/plan/plan.xml Fri Nov 7 09:01:53 2008
@@ -20,49 +20,22 @@
http://geronimo.apache.org/xml/ns/deployment-$
{geronimoSchemaVersion}">
-class="org.apache.geronimo.activemq.management.ActiveMQManagerGBean"/>
+
class="org.apache.geronimo.activemq.BrokerServiceGBeanImpl">
-
-
+var/activemq
+data
+conf/activemq.xml
false
-var/activemq
-
+
+
ServerInfo
-
+
MBeanServerReference
-class="org.apache.geronimo.activemq.TransportConnectorGBeanImpl">
-tcp
-localhost
-61616
-
-ActiveMQ
-
-
-
-class="org.apache.geronimo.activemq.TransportConnectorGBeanImpl">
-stomp
-localhost
-61613
-
- ActiveMQ
-
-
-
Added: geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/resources/activemq.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/main/resources/activemq.xml?rev=712197&view=auto
=
=
=
=
=
=
=
=
======
--- geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/resources/activemq.xml (added)
+++ geronimo/server/trunk/plugins/activemq5/activemq5-broker/src/
main/resources/activemq.xm
[jira] Closed: (GERONIMO-1818) ActiveMQ broker is shutting down before the rest of the server
[ https://issues.apache.org/jira/browse/GERONIMO-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller closed GERONIMO-1818. -- > ActiveMQ broker is shutting down before the rest of the server > -- > > Key: GERONIMO-1818 > URL: https://issues.apache.org/jira/browse/GERONIMO-1818 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: kernel >Affects Versions: 1.1 >Reporter: Kevan Miller >Assignee: Kevan Miller > Fix For: 1.1 > > > The ActiveMQ broker is shutting down before the rest of the Geronimo server. > This can result in several errors (deadlock and infinite recursion) as well > as annoying info messages like: > Server shutdown begun > 13:49:11,666 INFO [ActiveMQAsfEndpointWorker] Endpoint connection to JMS > broker failed: Initialization of TcpTransportChannel failed. URI was: > tcp://localhost:61616 Reason: java.net.ConnectException: Connection refused > 13:49:11,666 INFO [ActiveMQAsfEndpointWorker] Endpoint will try to reconnect > to the JMS broker in 30 seconds > Server shutdown completed > In the past, these problems have been avoided by the following in the > activemq-broker config plan: > class="org.apache.geronimo.system.properties.SystemProperties"> > > activemq.broker.disable-clean-shutdown=true > > > However, it doesn't seem to be working. Seem to be 3 possible explanations: > 1) The SystemProperties GBean is not working. > 2) The order of GBean shutdown has been changed and the broker is being > stopped before clients are stopped. > 3) ActiveMQ 3.2.4 disable-clean-shutdown processing is broken. > Most likely explanation is 1) or 2)... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r589918 - in /geronimo/server/trunk/configs: activemq-broker/src/main/ activemq-ra/src/main/ axis-deployer/src/main/ axis/src/main/ axis2-deployer/src/main/ axis2-ejb-deployer/src/main
Vamsi, you have removed the wrong plan. This is THE actual plan. The plan to be removed is the one under src/plan http://www.nabble.com/forum/ViewPost.jtp?post=13435934&framed=y&skin=134 Cheers Prasad On 10/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: vamsic007 > Date: Mon Oct 29 17:36:56 2007 > New Revision: 589918 > > URL: http://svn.apache.org/viewvc?rev=589918&view=rev > Log: > GERONIMO-3563 Remove duplicate plan.xml files under configs > o Removed the "trivial" ones where the plan.xml under src/plan is not > significantly different from the one under src/main/plan except for some > formatting etc. > > Removed: > geronimo/server/trunk/configs/activemq-broker/src/main/ > geronimo/server/trunk/configs/activemq-ra/src/main/ > geronimo/server/trunk/configs/axis-deployer/src/main/ > geronimo/server/trunk/configs/axis/src/main/ > geronimo/server/trunk/configs/axis2-deployer/src/main/ > geronimo/server/trunk/configs/axis2-ejb-deployer/src/main/ > geronimo/server/trunk/configs/axis2-ejb/src/main/ > geronimo/server/trunk/configs/axis2/src/main/ > geronimo/server/trunk/configs/ca-helper-jetty/src/main/ > geronimo/server/trunk/configs/ca-helper-tomcat/src/main/ > geronimo/server/trunk/configs/client-corba-yoko/src/main/ > geronimo/server/trunk/configs/client-deployer/src/main/ > geronimo/server/trunk/configs/client-security/src/main/ > geronimo/server/trunk/configs/client-system/src/main/plan/ > geronimo/server/trunk/configs/client-transaction/src/main/ > geronimo/server/trunk/configs/client/src/main/ > geronimo/server/trunk/configs/clustering/src/main/ > geronimo/server/trunk/configs/connector-deployer/src/main/ > geronimo/server/trunk/configs/cxf-deployer/src/main/ > geronimo/server/trunk/configs/cxf-ejb-deployer/src/main/ > geronimo/server/trunk/configs/cxf-ejb/src/main/ > geronimo/server/trunk/configs/cxf/src/main/ > geronimo/server/trunk/configs/dojo-jetty6/src/main/ > geronimo/server/trunk/configs/dojo-tomcat/src/main/ > geronimo/server/trunk/configs/hot-deployer/src/main/ > geronimo/server/trunk/configs/j2ee-corba-yoko/src/main/ > geronimo/server/trunk/configs/j2ee-deployer/src/main/ > geronimo/server/trunk/configs/j2ee-security/src/main/ > geronimo/server/trunk/configs/j2ee-server/src/main/ > geronimo/server/trunk/configs/j2ee-system/src/main/plan/ > geronimo/server/trunk/configs/jasper-deployer/src/main/ > geronimo/server/trunk/configs/jasper/src/main/ > geronimo/server/trunk/configs/jaxws-deployer/src/main/plan/ > geronimo/server/trunk/configs/jaxws-ejb-deployer/src/main/ > geronimo/server/trunk/configs/jee-specs/src/main/ > geronimo/server/trunk/configs/jetty6-clustering-builder-wadi/src/main/ > geronimo/server/trunk/configs/jetty6-clustering-wadi/src/main/ > geronimo/server/trunk/configs/jetty6/src/main/ > geronimo/server/trunk/configs/jsr88-cli/src/main/ > geronimo/server/trunk/configs/jsr88-deploymentfactory/src/main/plan/ > geronimo/server/trunk/configs/mejb/src/main/ > geronimo/server/trunk/configs/myfaces-deployer/src/main/ > geronimo/server/trunk/configs/myfaces/src/main/ > geronimo/server/trunk/configs/online-deployer/src/main/plan/ > geronimo/server/trunk/configs/openejb-corba-deployer/src/main/ > geronimo/server/trunk/configs/openejb/src/main/ > geronimo/server/trunk/configs/persistence-jpa10-deployer/src/main/ > geronimo/server/trunk/configs/remote-deploy-jetty/src/main/ > geronimo/server/trunk/configs/remote-deploy-tomcat/src/main/ > geronimo/server/trunk/configs/rmi-naming/src/main/ > geronimo/server/trunk/configs/server-security-config/src/main/ > geronimo/server/trunk/configs/sharedlib/src/main/ > geronimo/server/trunk/configs/shutdown/src/main/plan/ > geronimo/server/trunk/configs/spring/src/main/ > geronimo/server/trunk/configs/tomcat6-deployer/src/main/ > geronimo/server/trunk/configs/tomcat6/src/main/ > geronimo/server/trunk/configs/transaction/src/main/ > geronimo/server/trunk/configs/transformer-agent/src/main/plan/ > geronimo/server/trunk/configs/wadi-clustering/src/main/ > geronimo/server/trunk/configs/webservices-common/src/main/ > geronimo/server/trunk/configs/welcome-jetty/src/main/ > geronimo/server/trunk/configs/welcome-tomcat/src/main/ > geronimo/server/trunk/configs/xmlbeans/src/main/ > >
[jira] Commented: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508040
]
Donald Woods commented on GERONIMO-3148:
Committed revision 550660.
Fixed comment in the plan.xml on how to use brokerUri, but did not include the
missing Spring dependencies for now...
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated GERONIMO-3148:
---
Component/s: ActiveMQ
set the right component
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
[
https://issues.apache.org/jira/browse/GERONIMO-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Koehler updated GERONIMO-3148:
---
Attachment: active-mq-broker.patch
> ActiveMQ Broker config is missing some dependencies
> ---
>
> Key: GERONIMO-3148
> URL: https://issues.apache.org/jira/browse/GERONIMO-3148
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: ActiveMQ
>Affects Versions: 2.0-M6
>Reporter: Kristian Koehler
> Attachments: active-mq-broker.patch
>
>
> Hi
> I tried to use an external config file for the embedded ActiveMQ broker. For
> this scenario the BrokerServiceGBeanImpl provides an attribute called
> 'brokerUri' where you can give an activemq.xml ('spring based') configuration.
> By setting this value ClassNotFound Exceptions are thrown because some spring
> and xbean libs are not configured correctly within the ActiveMQ broker
> configuration.
> The attached patch fixes the dependency problem and a smaller typo within the
> plan.xml.
> Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3148) ActiveMQ Broker config is missing some dependencies
ActiveMQ Broker config is missing some dependencies
---
Key: GERONIMO-3148
URL: https://issues.apache.org/jira/browse/GERONIMO-3148
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Affects Versions: 2.0-M6
Reporter: Kristian Koehler
Hi
I tried to use an external config file for the embedded ActiveMQ broker. For
this scenario the BrokerServiceGBeanImpl provides an attribute called
'brokerUri' where you can give an activemq.xml ('spring based') configuration.
By setting this value ClassNotFound Exceptions are thrown because some spring
and xbean libs are not configured correctly within the ActiveMQ broker
configuration.
The attached patch fixes the dependency problem and a smaller typo within the
plan.xml.
Kristian
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-946) Upgrade loan-broker-bpel example to use Apache Ode
[ https://issues.apache.org/activemq/browse/SM-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-946. Resolution: Fixed URL: http://svn.apache.org/viewvc?view=rev&rev=535211 URL: http://svn.apache.org/viewvc?view=rev&rev=535212 > Upgrade loan-broker-bpel example to use Apache Ode > -- > > Key: SM-946 > URL: https://issues.apache.org/activemq/browse/SM-946 > Project: ServiceMix > Issue Type: Task > Components: servicemix-assembly >Affects Versions: 3.1 >Reporter: Guillaume Nodet > Assigned To: Guillaume Nodet > Fix For: 3.1.1, 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
embedded activemq broker
I need help and information setting up an embedded broker in Geronimo. My final goal is to setup an embedded broker with JAAS or a custom security plugin for authentication / authorization. What I am looking for is an example (or multiple examples) of an xml file that I can use to deply a broker with. The available documentation on using the xml file to create an embedded broker seems really thin. Help!!! -- View this message in context: http://www.nabble.com/embedded-activemq-broker-tf3642461s134.html#a10172544 Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: activemq-broker
>> .internal > >>>>> GetConnection(SinglePoolConnectionInterceptor.java:66) > >>>>> at > >>>>> > >>>> > >>> > >> > > > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt > >>>> > >>>>> erceptor. > >>>>> getConnection(AbstractSinglePoolConnectionInterceptor.java:78) > >>>>> at > >>>>> > >>>> > >>> > >> > > > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor > >>>> > >>>>> .getConne > >>>>> ction(TransactionEnlistingInterceptor.java:46) > >>>>> at > >>>>> > >>>> > >>> > >> > > > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g > >>>> > >>>>> etConnect > >>>>> ion(TransactionCachingInterceptor.java:95) > >>>>> at > >>>>> > >>>> > >> > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection > >>>>> (TCCLInterc > >>>>> eptor.java:39) > >>>>> at > >>>>> > >>>> > >>> > >> > > > org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe > >>>> > >>>>> coveryXAR > >>>>> esource(AbstractConnectionManager.java:98) > >>>>> at > >>>>> > org.apache.geronimo.connector.outbound.AbstractConnectionManager$ > >>>>> $FastClassByCG > >>>>> LIB$$80012030.invoke() > >>>>> at > >>>> net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > >>>>> ... > >>>>> .. > >>>>> > >>>>> at > >>>>> org.apache.geronimo.system.main.Daemon.(Daemon.java:74) > >>>>> at > >> org.apache.geronimo.system.main.Daemon.main(Daemon.java: > >>>> > >>>>> 342) > >>>>> Caused by: javax.jms.JMSException: Could not connect to broker > >> URL: > >>>>> tcp://0.0.0.0:61616. R > >>>>> eason: java.net.ConnectException: Connection refused: connect > >>>>> at > >>>>> org.apache.activemq.util.JMSExceptionSupport.create > >>>>> (JMSExceptionSupport.java:33 > === message truncated === Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097
Re: activemq-broker
All the config-properties specified in ra.xml for the resource
adapter class and the outbound ManagedConnectionFactory and IIRC the
admin objects are turned into dynamic attributes for the wrapper
gbeans so they can be set through the gbean mechanism, exposed to
management, overridden in config.xml, etc.
So, this isn't an attribute of ResourceAdapterWrapperGBean itself,
but any activemq resource adapter wrapper gbean instance should have
it.
thanks
david jencks
On Apr 10, 2007, at 6:25 AM, Anita Kulshreshtha wrote:
Thanks David! I could not find a ServerUrl attribute in
ResourceAdapterWrapper gbean. Do we need to add one? If yes, how?
Thanks
Anita
--- David Jencks <[EMAIL PROTECTED]> wrote:
This gets turned into a gbean attribute called ServerUrl on the
ResourceAdapterWrapper gbean so it should be possible to override it
that way in config.xml.
thanks
david jencks
On Apr 9, 2007, at 7:48 PM, Anita Kulshreshtha wrote:
Kevan,
The plan for activemq-ra config is using 61616:
ActiveMQ
RA
tcp://${PlanServerHostname}:${PlanActiveMQPort}
Any idea how to make this configurable?
Thanks
Anita
--- Kevan Miller <[EMAIL PROTECTED]> wrote:
On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
I get following exception while starting an instance of g
using
port
61626 instead of 61616. Where is 61616 coming from?
Hi Anita,
61616 is the ActiveMQ's default port. So, we're establishing this
internal connection to ActiveMQ without specifying a port number
(and
activemq is defaulting). Or, we're using the wrong port number.
How are you configuring this?
--kevan
Thanks
Anita
Starting Geronimo Application Server v2.0-SNAPSHOT
[*> ] 34% 18s Starting
org.apache.geronim...10:27:08,953 ERROR [
MCFConnectionInterceptor] Error occurred creating
ManagedConnection
for
org.apache.geronim
[EMAIL PROTECTED]
javax.resource.ResourceException: Could not create connection.
at
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC
onnection
(ActiveMQManagedConnectionFactory.java:112)
at
org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon
nection(M
CFConnectionInterceptor.java:48)
at
org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.
getConnec
tion(XAResourceInsertionInterceptor.java:41)
at
org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
.internal
GetConnection(SinglePoolConnectionInterceptor.java:66)
at
org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt
erceptor.
getConnection(AbstractSinglePoolConnectionInterceptor.java:78)
at
org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor
.getConne
ction(TransactionEnlistingInterceptor.java:46)
at
org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g
etConnect
ion(TransactionCachingInterceptor.java:95)
at
org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection
(TCCLInterc
eptor.java:39)
at
org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe
coveryXAR
esource(AbstractConnectionManager.java:98)
at
org.apache.geronimo.connector.outbound.AbstractConnectionManager$
$FastClassByCG
LIB$$80012030.invoke()
at
net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
...
..
at
org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
at
org.apache.geronimo.system.main.Daemon.main(Daemon.java:
342)
Caused by: javax.jms.JMSException: Could not connect to broker
URL:
tcp://0.0.0.0:61616. R
eason: java.net.ConnectException: Connection refused: connect
at
org.apache.activemq.util.JMSExceptionSupport.create
(JMSExceptionSupport.java:33
__
__
The fish are biting.
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
__
__
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
__
__
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265
Re: activemq-broker
Thanks David! I could not find a ServerUrl attribute in
ResourceAdapterWrapper gbean. Do we need to add one? If yes, how?
Thanks
Anita
--- David Jencks <[EMAIL PROTECTED]> wrote:
> This gets turned into a gbean attribute called ServerUrl on the
> ResourceAdapterWrapper gbean so it should be possible to override it
>
> that way in config.xml.
>
> thanks
> david jencks
>
> On Apr 9, 2007, at 7:48 PM, Anita Kulshreshtha wrote:
>
> > Kevan,
> >The plan for activemq-ra config is using 61616:
> >
> >
> > ActiveMQ
> RA
> > > name="ServerUrl">tcp://${PlanServerHostname}:${PlanActiveMQPort} > config-property-setting>
> >
> >
> >
> >Any idea how to make this configurable?
> >
> > Thanks
> > Anita
> >
> > --- Kevan Miller <[EMAIL PROTECTED]> wrote:
> >
> >>
> >> On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
> >>
> >>>I get following exception while starting an instance of g
> using
> >>
> >>> port
> >>> 61626 instead of 61616. Where is 61616 coming from?
> >>
> >> Hi Anita,
> >> 61616 is the ActiveMQ's default port. So, we're establishing this
> >> internal connection to ActiveMQ without specifying a port number
> (and
> >>
> >> activemq is defaulting). Or, we're using the wrong port number.
> >>
> >> How are you configuring this?
> >>
> >> --kevan
> >>
> >>>
> >>> Thanks
> >>> Anita
> >>>
> >>> Starting Geronimo Application Server v2.0-SNAPSHOT
> >>> [*> ] 34% 18s Starting
> >>> org.apache.geronim...10:27:08,953 ERROR [
> >>> MCFConnectionInterceptor] Error occurred creating
> ManagedConnection
> >>
> >>> for
> >>> org.apache.geronim
> >>> [EMAIL PROTECTED]
> >>> javax.resource.ResourceException: Could not create connection.
> >>> at
> >>>
> >>
> >
>
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC
> >>
> >>> onnection
> >>> (ActiveMQManagedConnectionFactory.java:112)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon
> >>
> >>> nection(M
> >>> CFConnectionInterceptor.java:48)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.
> >>
> >>> getConnec
> >>> tion(XAResourceInsertionInterceptor.java:41)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
> >>
> >>> .internal
> >>> GetConnection(SinglePoolConnectionInterceptor.java:66)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt
> >>
> >>> erceptor.
> >>> getConnection(AbstractSinglePoolConnectionInterceptor.java:78)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor
> >>
> >>> .getConne
> >>> ction(TransactionEnlistingInterceptor.java:46)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g
> >>
> >>> etConnect
> >>> ion(TransactionCachingInterceptor.java:95)
> >>> at
> >>>
> >>
> org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection
> >>> (TCCLInterc
> >>> eptor.java:39)
> >>> at
> >>>
> >>
> >
>
org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe
> >>
> >>> coveryXAR
> >>> esource(AbstractConnectionManager.java:98)
> >>> at
> >>> org.apache.geronimo.connector.outbound.AbstractConnectionManager$
> >>> $FastClassByCG
> >>> LIB$$80012030.invoke()
> >>> at
> >> net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> >>> ...
> >>> ..
> >>>
> >>> at
> >>> org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
> >>> at
> org.apache.geronimo.system.main.Daemon.main(Daemon.java:
> >>
> >>> 342)
> >>> Caused by: javax.jms.JMSException: Could not connect to broker
> URL:
> >>> tcp://0.0.0.0:61616. R
> >>> eason: java.net.ConnectException: Connection refused: connect
> >>> at
> >>> org.apache.activemq.util.JMSExceptionSupport.create
> >>> (JMSExceptionSupport.java:33
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >
>
__
> >>
> >>> __
> >>> The fish are biting.
> >>> Get more visitors on your site using Yahoo! Search Marketing.
> >>> http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
> >>
> >>
> >
> >
> >
> >
> >
>
__
>
> > __
> > Expecting? Get great news right away with email Auto-Check.
> > Try the Yahoo! Mail Beta.
> > http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
>
>
We won't tell. Get more on shows you hate to love
(and love to hate): Yahoo! TV's Guilty Pleasures list.
http://tv.yahoo.com/collections/265
Re: activemq-broker
This gets turned into a gbean attribute called ServerUrl on the
ResourceAdapterWrapper gbean so it should be possible to override it
that way in config.xml.
thanks
david jencks
On Apr 9, 2007, at 7:48 PM, Anita Kulshreshtha wrote:
Kevan,
The plan for activemq-ra config is using 61616:
ActiveMQ RA
name="ServerUrl">tcp://${PlanServerHostname}:${PlanActiveMQPort}config-property-setting>
Any idea how to make this configurable?
Thanks
Anita
--- Kevan Miller <[EMAIL PROTECTED]> wrote:
On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
I get following exception while starting an instance of g using
port
61626 instead of 61616. Where is 61616 coming from?
Hi Anita,
61616 is the ActiveMQ's default port. So, we're establishing this
internal connection to ActiveMQ without specifying a port number (and
activemq is defaulting). Or, we're using the wrong port number.
How are you configuring this?
--kevan
Thanks
Anita
Starting Geronimo Application Server v2.0-SNAPSHOT
[*> ] 34% 18s Starting
org.apache.geronim...10:27:08,953 ERROR [
MCFConnectionInterceptor] Error occurred creating ManagedConnection
for
org.apache.geronim
[EMAIL PROTECTED]
javax.resource.ResourceException: Could not create connection.
at
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC
onnection
(ActiveMQManagedConnectionFactory.java:112)
at
org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon
nection(M
CFConnectionInterceptor.java:48)
at
org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.
getConnec
tion(XAResourceInsertionInterceptor.java:41)
at
org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
.internal
GetConnection(SinglePoolConnectionInterceptor.java:66)
at
org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt
erceptor.
getConnection(AbstractSinglePoolConnectionInterceptor.java:78)
at
org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor
.getConne
ction(TransactionEnlistingInterceptor.java:46)
at
org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g
etConnect
ion(TransactionCachingInterceptor.java:95)
at
org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection
(TCCLInterc
eptor.java:39)
at
org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe
coveryXAR
esource(AbstractConnectionManager.java:98)
at
org.apache.geronimo.connector.outbound.AbstractConnectionManager$
$FastClassByCG
LIB$$80012030.invoke()
at
net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
...
..
at
org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:
342)
Caused by: javax.jms.JMSException: Could not connect to broker URL:
tcp://0.0.0.0:61616. R
eason: java.net.ConnectException: Connection refused: connect
at
org.apache.activemq.util.JMSExceptionSupport.create
(JMSExceptionSupport.java:33
__
__
The fish are biting.
Get more visitors on your site using Yahoo! Search Marketing.
http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
__
__
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
Re: activemq-broker
Kevan,
The plan for activemq-ra config is using 61616:
ActiveMQ RA
tcp://${PlanServerHostname}:${PlanActiveMQPort}
Any idea how to make this configurable?
Thanks
Anita
--- Kevan Miller <[EMAIL PROTECTED]> wrote:
>
> On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote:
>
> >I get following exception while starting an instance of g using
>
> > port
> > 61626 instead of 61616. Where is 61616 coming from?
>
> Hi Anita,
> 61616 is the ActiveMQ's default port. So, we're establishing this
> internal connection to ActiveMQ without specifying a port number (and
>
> activemq is defaulting). Or, we're using the wrong port number.
>
> How are you configuring this?
>
> --kevan
>
> >
> > Thanks
> > Anita
> >
> > Starting Geronimo Application Server v2.0-SNAPSHOT
> > [*> ] 34% 18s Starting
> > org.apache.geronim...10:27:08,953 ERROR [
> > MCFConnectionInterceptor] Error occurred creating ManagedConnection
>
> > for
> > org.apache.geronim
> > [EMAIL PROTECTED]
> > javax.resource.ResourceException: Could not create connection.
> > at
> >
>
org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC
>
> > onnection
> > (ActiveMQManagedConnectionFactory.java:112)
> > at
> >
>
org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon
>
> > nection(M
> > CFConnectionInterceptor.java:48)
> > at
> >
>
org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.
>
> > getConnec
> > tion(XAResourceInsertionInterceptor.java:41)
> > at
> >
>
org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor
>
> > .internal
> > GetConnection(SinglePoolConnectionInterceptor.java:66)
> > at
> >
>
org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt
>
> > erceptor.
> > getConnection(AbstractSinglePoolConnectionInterceptor.java:78)
> > at
> >
>
org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor
>
> > .getConne
> > ction(TransactionEnlistingInterceptor.java:46)
> > at
> >
>
org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g
>
> > etConnect
> > ion(TransactionCachingInterceptor.java:95)
> > at
> >
> org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection
> > (TCCLInterc
> > eptor.java:39)
> > at
> >
>
org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe
>
> > coveryXAR
> > esource(AbstractConnectionManager.java:98)
> > at
> > org.apache.geronimo.connector.outbound.AbstractConnectionManager$
> > $FastClassByCG
> > LIB$$80012030.invoke()
> > at
> net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
> > ...
> > ..
> >
> > at
> > org.apache.geronimo.system.main.Daemon.(Daemon.java:74)
> > at org.apache.geronimo.system.main.Daemon.main(Daemon.java:
>
> > 342)
> > Caused by: javax.jms.JMSException: Could not connect to broker URL:
> > tcp://0.0.0.0:61616. R
> > eason: java.net.ConnectException: Connection refused: connect
> > at
> > org.apache.activemq.util.JMSExceptionSupport.create
> > (JMSExceptionSupport.java:33
> >
> >
> >
> >
> >
>
__
>
> > __
> > The fish are biting.
> > Get more visitors on your site using Yahoo! Search Marketing.
> > http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
>
>
Expecting? Get great news right away with email Auto-Check.
Try the Yahoo! Mail Beta.
http://advision.webevents.yahoo.com/mailbeta/newmail_tools.html
Re: activemq-broker
--- Kevan Miller <[EMAIL PROTECTED]> wrote: So, we're establishing this > internal connection to ActiveMQ without specifying a port number (and > > activemq is defaulting). This seems more likely... (rev 521546) > Or, we're using the wrong port number. Server reports the correct port no: [**] 100% 35s Startup complete Listening on Ports: 1089 0.0.0.0 RMI Naming 1517 0.0.0.0 Derby Connector 4201 0.0.0.0 org.apache.geronimo.openejb.EjbDaemonGBean 4232 0.0.0.0 Remote Login Listener 8019 0.0.0.0 Tomcat Connector AJP 8070 0.0.0.0 Tomcat Connector HTTP 8433 0.0.0.0 Tomcat Connector HTTPS 9989 0.0.0.0 JMX Remoting Connector 61606 0.0.0.0 ActiveMQ Transport Connector 61613 0.0.0.0 ActiveMQ Transport Connector Thanks Anita p.s. now I am using 61606. > > How are you configuring this? > > --kevan > > Caused by: javax.jms.JMSException: Could not connect to broker URL: > > tcp://0.0.0.0:61616. R > > eason: java.net.ConnectException: Connection refused: connect > > at > > org.apache.activemq.util.JMSExceptionSupport.create > > (JMSExceptionSupport.java:33 > > > > > > > > > > > __ > > > __ > > The fish are biting. > > Get more visitors on your site using Yahoo! Search Marketing. > > http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php > > Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097
Re: activemq-broker
--- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote: > > >I get following exception while starting an instance of g using > > > port > > 61626 instead of 61616. Where is 61616 coming from? > > Hi Anita, > 61616 is the ActiveMQ's default port. So, we're establishing this > internal connection to ActiveMQ without specifying a port number (and > > activemq is defaulting). Or, we're using the wrong port number. > > How are you configuring this? I am running an instance of G from g1 directory usng java -D bin\server. I changed the port no. for ActiveMQ.tcp.default gbean in g1/var/config/config.xml. The server starts despite the exception and lists the correct port no, i.e. 61626. I had to modify BrokerServiceGBeanImpl to create activemq dir in g1/var. Not sure where the old value is coming from.. Thanks Anita > > --kevan > > > > > Thanks > > Anita > > > > Starting Geronimo Application Server v2.0-SNAPSHOT > > [*> ] 34% 18s Starting > > org.apache.geronim...10:27:08,953 ERROR [ > > MCFConnectionInterceptor] Error occurred creating ManagedConnection > > > for > > org.apache.geronim > > [EMAIL PROTECTED] > > javax.resource.ResourceException: Could not create connection. > > at > > > org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC > > > onnection > > (ActiveMQManagedConnectionFactory.java:112) > > at > > > org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon > > > nection(M > > CFConnectionInterceptor.java:48) > > at > > > org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor. > > > getConnec > > tion(XAResourceInsertionInterceptor.java:41) > > at > > > org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor > > > .internal > > GetConnection(SinglePoolConnectionInterceptor.java:66) > > at > > > org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt > > > erceptor. > > getConnection(AbstractSinglePoolConnectionInterceptor.java:78) > > at > > > org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor > > > .getConne > > ction(TransactionEnlistingInterceptor.java:46) > > at > > > org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g > > > etConnect > > ion(TransactionCachingInterceptor.java:95) > > at > > > org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection > > (TCCLInterc > > eptor.java:39) > > at > > > org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe > > > coveryXAR > > esource(AbstractConnectionManager.java:98) > > at > > org.apache.geronimo.connector.outbound.AbstractConnectionManager$ > > $FastClassByCG > > LIB$$80012030.invoke() > > at > net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > > ... > > .. > > > > at > > org.apache.geronimo.system.main.Daemon.(Daemon.java:74) > > at org.apache.geronimo.system.main.Daemon.main(Daemon.java: > > > 342) > > Caused by: javax.jms.JMSException: Could not connect to broker URL: > > tcp://0.0.0.0:61616. R > > eason: java.net.ConnectException: Connection refused: connect > > at > > org.apache.activemq.util.JMSExceptionSupport.create > > (JMSExceptionSupport.java:33 > > > > > > > > > > > __ > > > __ > > The fish are biting. > > Get more visitors on your site using Yahoo! Search Marketing. > > http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php > > Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
Re: activemq-broker
On Mar 22, 2007, at 10:39 AM, Anita Kulshreshtha wrote: I get following exception while starting an instance of g using port 61626 instead of 61616. Where is 61616 coming from? Hi Anita, 61616 is the ActiveMQ's default port. So, we're establishing this internal connection to ActiveMQ without specifying a port number (and activemq is defaulting). Or, we're using the wrong port number. How are you configuring this? --kevan Thanks Anita Starting Geronimo Application Server v2.0-SNAPSHOT [*> ] 34% 18s Starting org.apache.geronim...10:27:08,953 ERROR [ MCFConnectionInterceptor] Error occurred creating ManagedConnection for org.apache.geronim [EMAIL PROTECTED] javax.resource.ResourceException: Could not create connection. at org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedC onnection (ActiveMQManagedConnectionFactory.java:112) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getCon nection(M CFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor. getConnec tion(XAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor .internal GetConnection(SinglePoolConnectionInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInt erceptor. getConnection(AbstractSinglePoolConnectionInterceptor.java:78) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor .getConne ction(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.g etConnect ion(TransactionCachingInterceptor.java:95) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection (TCCLInterc eptor.java:39) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRe coveryXAR esource(AbstractConnectionManager.java:98) at org.apache.geronimo.connector.outbound.AbstractConnectionManager$ $FastClassByCG LIB$$80012030.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) ... .. at org.apache.geronimo.system.main.Daemon.(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java: 342) Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://0.0.0.0:61616. R eason: java.net.ConnectException: Connection refused: connect at org.apache.activemq.util.JMSExceptionSupport.create (JMSExceptionSupport.java:33 __ __ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
activemq-broker
I get following exception while starting an instance of g using port 61626 instead of 61616. Where is 61616 coming from? Thanks Anita Starting Geronimo Application Server v2.0-SNAPSHOT [*> ] 34% 18s Starting org.apache.geronim...10:27:08,953 ERROR [ MCFConnectionInterceptor] Error occurred creating ManagedConnection for org.apache.geronim [EMAIL PROTECTED] javax.resource.ResourceException: Could not create connection. at org.apache.activemq.ra.ActiveMQManagedConnectionFactory.createManagedConnection (ActiveMQManagedConnectionFactory.java:112) at org.apache.geronimo.connector.outbound.MCFConnectionInterceptor.getConnection(M CFConnectionInterceptor.java:48) at org.apache.geronimo.connector.outbound.XAResourceInsertionInterceptor.getConnec tion(XAResourceInsertionInterceptor.java:41) at org.apache.geronimo.connector.outbound.SinglePoolConnectionInterceptor.internal GetConnection(SinglePoolConnectionInterceptor.java:66) at org.apache.geronimo.connector.outbound.AbstractSinglePoolConnectionInterceptor. getConnection(AbstractSinglePoolConnectionInterceptor.java:78) at org.apache.geronimo.connector.outbound.TransactionEnlistingInterceptor.getConne ction(TransactionEnlistingInterceptor.java:46) at org.apache.geronimo.connector.outbound.TransactionCachingInterceptor.getConnect ion(TransactionCachingInterceptor.java:95) at org.apache.geronimo.connector.outbound.TCCLInterceptor.getConnection(TCCLInterc eptor.java:39) at org.apache.geronimo.connector.outbound.AbstractConnectionManager.getRecoveryXAR esource(AbstractConnectionManager.java:98) at org.apache.geronimo.connector.outbound.AbstractConnectionManager$$FastClassByCG LIB$$80012030.invoke() at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) ... .. at org.apache.geronimo.system.main.Daemon.(Daemon.java:74) at org.apache.geronimo.system.main.Daemon.main(Daemon.java:342) Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://0.0.0.0:61616. R eason: java.net.ConnectException: Connection refused: connect at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33 The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
[jira] Commented: (GERONIMO-2918) Have the ActiveMQ broker configured from an external configuration file by default
[ https://issues.apache.org/jira/browse/GERONIMO-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479775 ] Jason Dillon commented on GERONIMO-2918: I think the only way this would fly is if we can get the console bits which add connectors/etc to update the configuration file, so that one can still use the console to add muck and it will retain them over a restart. Perhaps, also, the console might need a simple text-based editor thingy to edit the activemq.xml Additionally, we may want to consider including the activemq-web-console... > Have the ActiveMQ broker configured from an external configuration file by > default > -- > > Key: GERONIMO-2918 > URL: https://issues.apache.org/jira/browse/GERONIMO-2918 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: activemq-config.patch > > > Currently, the org.apache.activemq.gbean.BrokerServiceGBeanImpl GBean is > configured in the activemq-broker config and is thus built into a serialized > configuration during the build process. Looking at the plan.xml, there is a > commented-out section that specifies an external configuration file to be > used. Enabling this section allows for the broker to be configured by an > external file. > This configuration should be changed so that the activemq-broker > configuration refers to an external file by default, rather than being > internally configured in the plan. This external file can exist somewhere in > the geronimo folder hieracy (e.g. var/config/activemq.xml). This external > file should contain the same minimal configuration that is currently > specified in the GBean descriptor in the plan.xml. > The benefit of having an external file by default is that the activemq broker > can be configured without having to rebuild Geronimo. This makes the > ActiveMQ configuration much easier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2918) Have the ActiveMQ broker configured from an external configuration file by default
[ https://issues.apache.org/jira/browse/GERONIMO-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aman Nanner updated GERONIMO-2918: -- Attachment: activemq-config.patch Here is a patch that addresses this issue (and also addresses Geronimo 2927). There some comments in the activemq-broker pom.xml that can be removed. > Have the ActiveMQ broker configured from an external configuration file by > default > -- > > Key: GERONIMO-2918 > URL: https://issues.apache.org/jira/browse/GERONIMO-2918 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: ActiveMQ >Affects Versions: 1.2 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: activemq-config.patch > > > Currently, the org.apache.activemq.gbean.BrokerServiceGBeanImpl GBean is > configured in the activemq-broker config and is thus built into a serialized > configuration during the build process. Looking at the plan.xml, there is a > commented-out section that specifies an external configuration file to be > used. Enabling this section allows for the broker to be configured by an > external file. > This configuration should be changed so that the activemq-broker > configuration refers to an external file by default, rather than being > internally configured in the plan. This external file can exist somewhere in > the geronimo folder hieracy (e.g. var/config/activemq.xml). This external > file should contain the same minimal configuration that is currently > specified in the GBean descriptor in the plan.xml. > The benefit of having an external file by default is that the activemq broker > can be configured without having to rebuild Geronimo. This makes the > ActiveMQ configuration much easier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-2918) Have the ActiveMQ broker configured from an external configuration file by default
Have the ActiveMQ broker configured from an external configuration file by default -- Key: GERONIMO-2918 URL: https://issues.apache.org/jira/browse/GERONIMO-2918 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: ActiveMQ Affects Versions: 1.2 Reporter: Aman Nanner Priority: Minor Fix For: 1.2 Currently, the org.apache.activemq.gbean.BrokerServiceGBeanImpl GBean is configured in the activemq-broker config and is thus built into a serialized configuration during the build process. Looking at the plan.xml, there is a commented-out section that specifies an external configuration file to be used. Enabling this section allows for the broker to be configured by an external file. This configuration should be changed so that the activemq-broker configuration refers to an external file by default, rather than being internally configured in the plan. This external file can exist somewhere in the geronimo folder hieracy (e.g. var/config/activemq.xml). This external file should contain the same minimal configuration that is currently specified in the GBean descriptor in the plan.xml. The benefit of having an external file by default is that the activemq broker can be configured without having to rebuild Geronimo. This makes the ActiveMQ configuration much easier. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-826) Add client for loan-broker-bpel
[ https://issues.apache.org/activemq/browse/SM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-826. Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Wed Feb 14 09:17:09 2007 New Revision: 507632 URL: http://svn.apache.org/viewvc?view=rev&rev=507632 Log: SM-828: Add a client for the loan-broker-bpel demo. Patch provided by Gregoire Autric, thx \! Added: incubator/servicemix/trunk/samples/loan-broker/build.xml (with props) incubator/servicemix/trunk/samples/loan-broker/src/main/java/ incubator/servicemix/trunk/samples/loan-broker/src/main/java/JMSClient.java (with props) Modified: incubator/servicemix/trunk/samples/loan-broker/README.txt incubator/servicemix/trunk/samples/loan-broker/src/main/assembly/src.xml > Add client for loan-broker-bpel > --- > > Key: SM-826 > URL: https://issues.apache.org/activemq/browse/SM-826 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-bpe >Affects Versions: incubation > Environment: all platforms >Reporter: Grégoire A. > Assigned To: Guillaume Nodet >Priority: Minor > Fix For: 3.2 > > Attachments: JMSClientBPEL.java, loan-broker.diff > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > add client test for loan-broker-bpel > i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-833) into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not understand pattern: null
[ https://issues.apache.org/activemq/browse/SM-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-833. Resolution: Fixed Fix Version/s: 3.2 > into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not > understand pattern: null > -- > > Key: SM-833 > URL: https://issues.apache.org/activemq/browse/SM-833 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-bpe >Affects Versions: 3.1 > Environment: all >Reporter: Grégoire A. > Fix For: 3.2 > > Attachments: xbean.xml.diff > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Do not understand pattern: null > when calling the sample throw the jms endpoint > i add the defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; into jms endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-843) The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo
[ https://issues.apache.org/activemq/browse/SM-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-843. Resolution: Fixed Author: gnodet Date: Wed Feb 14 09:12:14 2007 New Revision: 507629 URL: http://svn.apache.org/viewvc?view=rev&rev=507629 Log: SM-843: The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo Modified: incubator/servicemix/trunk/samples/loan-broker/loan-broker-jms-su/src/main/resources/xbean.xml Author: gnodet Date: Wed Feb 14 09:17:00 2007 New Revision: 507631 URL: http://svn.apache.org/viewvc?view=rev&rev=507631 Log: SM-843: The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo Modified: incubator/servicemix/branches/servicemix-3.1/samples/loan-broker/loan-broker-jms-su/src/main/resources/xbean.xml > The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel > demo > > > Key: SM-843 > URL: https://issues.apache.org/activemq/browse/SM-843 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-assembly >Affects Versions: 3.1 >Reporter: Guillaume Nodet > Assigned To: Guillaume Nodet > Fix For: 3.1.1, 3.2 > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-843) The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo
The defaultMep attribute is missing on the jms endpoint in loan-broker-bpel demo Key: SM-843 URL: https://issues.apache.org/activemq/browse/SM-843 Project: ServiceMix Issue Type: Bug Components: servicemix-assembly Affects Versions: 3.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-826) Add client for loan-broker-bpel
[ https://issues.apache.org/activemq/browse/SM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-826: --- Fix Version/s: (was: 3.1) 3.2 > Add client for loan-broker-bpel > --- > > Key: SM-826 > URL: https://issues.apache.org/activemq/browse/SM-826 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-bpe >Affects Versions: incubation > Environment: all platforms >Reporter: Grégoire A. >Priority: Minor > Fix For: 3.2 > > Attachments: JMSClientBPEL.java, loan-broker.diff > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > add client test for loan-broker-bpel > i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-833) into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not understand pattern: null
[ https://issues.apache.org/activemq/browse/SM-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38481 ] Guillaume Nodet commented on SM-833: We need to throw a better exception i think. The problem happens usually when the incoming xml is not valid wrt to the wsdl. I.e.: the root tag does not match any operation, so the component can not find the wsdl operation and can not deduce the MEP. A meaninful exception should be thrown instead ... > into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not > understand pattern: null > -- > > Key: SM-833 > URL: https://issues.apache.org/activemq/browse/SM-833 > Project: ServiceMix > Issue Type: Bug > Components: servicemix-bpe >Affects Versions: 3.1 > Environment: all >Reporter: Grégoire A. > Attachments: xbean.xml.diff > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > Do not understand pattern: null > when calling the sample throw the jms endpoint > i add the defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; into jms endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-833) into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not understand pattern: null
into loan-broker-bpel sample - javax.jbi.messaging.MessagingException: Do not understand pattern: null -- Key: SM-833 URL: https://issues.apache.org/activemq/browse/SM-833 Project: ServiceMix Issue Type: Bug Components: servicemix-bpe Affects Versions: 3.1 Environment: all Reporter: Grégoire A. Attachments: xbean.xml.diff Do not understand pattern: null when calling the sample throw the jms endpoint i add the defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; into jms endpoint -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-826) Add client for loan-broker-bpel
[ https://issues.apache.org/activemq/browse/SM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38455 ] Grégoire A. commented on SM-826: the JMSClientBPEL.java file is now useless > Add client for loan-broker-bpel > --- > > Key: SM-826 > URL: https://issues.apache.org/activemq/browse/SM-826 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-bpe >Affects Versions: incubation > Environment: all platforms >Reporter: Grégoire A. >Priority: Minor > Fix For: 3.1 > > Attachments: JMSClientBPEL.java, loan-broker.diff > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > add client test for loan-broker-bpel > i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-826) Add client for loan-broker-bpel
[ https://issues.apache.org/activemq/browse/SM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grégoire A. updated SM-826: --- Attachment: loan-broker.diff please get this diff, it includes all needs to add client for loan-broker-bpel > Add client for loan-broker-bpel > --- > > Key: SM-826 > URL: https://issues.apache.org/activemq/browse/SM-826 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-bpe >Affects Versions: incubation > Environment: all platforms >Reporter: Grégoire A. >Priority: Minor > Fix For: 3.1 > > Attachments: JMSClientBPEL.java, loan-broker.diff > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > add client test for loan-broker-bpel > i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-826) Add client for loan-broker-bpel
[ https://issues.apache.org/activemq/browse/SM-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38430 ] Grégoire A. commented on SM-826: i found a bpe-jms-client compliant into trunk source $SMX_TRUNK/distributions/apache-servicemix/src/sandbox/bpel-bpe i use it for my client in all sincerity : i don't know how to integrate it correctly into $SMX_TRUNK/samples/loan-broker I am ready to learn ;-) > Add client for loan-broker-bpel > --- > > Key: SM-826 > URL: https://issues.apache.org/activemq/browse/SM-826 > Project: ServiceMix > Issue Type: New Feature > Components: servicemix-bpe >Affects Versions: incubation > Environment: all platforms >Reporter: Grégoire A. >Priority: Minor > Fix For: 3.1 > > Attachments: JMSClientBPEL.java > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > add client test for loan-broker-bpel > i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Vijlbrief updated AMQ-724: -- Attachment: patchInactivityMonitor.txt Patch for pending OpenWire connections > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: dumpemu4.png, patch.txt, patchInactivityMonitor.txt, > SessionState.patch, StompScriptComplete.txt, StompScriptNoDisconnect.txt, > StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[
https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38428
]
Tom Vijlbrief commented on AMQ-724:
---
I'm confused. When I try the netcat example with NoDisconnect in the current
SVN version
everything is rock solid.
When I interrupt a C++ OpenWire client than I get non closed connections.
I found a possible cure for the last problem. The InactivityMonitor code reads:
public void onException(IOException error) {
if( monitorStarted.get() ) {
stopMonitorThreads();
getTransportListener().onException(error);
}
}
So if monitorStarted is false the EOFException is completely ignored!
I assume it should be:
public void onException(IOException error) {
if( monitorStarted.get() ) {
stopMonitorThreads();
}
getTransportListener().onException(error); // tom.vijlbrief
}
Attached a patch. With this patch the OpenWire sessions are closed.
> Stomp client is not removed from the broker on client disconnect
>
>
> Key: AMQ-724
> URL: https://issues.apache.org/activemq/browse/AMQ-724
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
>Affects Versions: 4.0
> Environment: Linux, Java 1.5.0_06
>Reporter: Danielius Jurna
> Assigned To: james strachan
> Fix For: 4.0.2, 4.1.0
>
> Attachments: dumpemu4.png, patch.txt, SessionState.patch,
> StompScriptComplete.txt, StompScriptNoDisconnect.txt,
> StompSubscriptionRemoveTest.java
>
>
> If Stomp client crashes (or disconnects unexpectedly) when there are
> unconsumed messages in the broker, the subscriptions are not removed from the
> broker and some phantom consumer is still consuming messages. If you connect
> other client, it receives only half messages (other half messages goes to
> that phantom consumer still left afrter client disconnect). There are no
> error logs in activemq logs. We are using stomp client, whith client
> acknowledge mode, so on broker restart, all messages are delivered properly.
> You can also see in jmx console, that subscription still exists whithout any
> connection left.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38031 ] Tom Vijlbrief commented on AMQ-724: --- Retried the tests without the patch applied but see no difference now, so you can ignore it. Apparently a fix was already in the SVN version, my patch is a no-op. :-/ Terminating the Stomp connections in the current SVN version seems to work OK. Terminating OpenWire connections from a CPP client still leaves connections hanging. I'll try to investigate this problem further. > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: dumpemu4.png, patch.txt, SessionState.patch, > StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Vijlbrief updated AMQ-724: -- Attachment: patch.txt PATCH == Not sure if it is this simple but this patch seems to work OK. The connections are now freeed when a fresh client connects... > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: dumpemu4.png, patch.txt, SessionState.patch, > StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SM-826) Add client for loan-broker-bpel
Add client for loan-broker-bpel --- Key: SM-826 URL: https://issues.apache.org/activemq/browse/SM-826 Project: ServiceMix Issue Type: New Feature Components: servicemix-bpe Affects Versions: incubation Environment: all platforms Reporter: Grégoire A. Priority: Minor Fix For: 3.1 Attachments: JMSClientBPEL.java add client test for loan-broker-bpel i add the class code, i should be work fine !!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1134) stomp connections in the broker don't get cleared up if the socket dies
[ https://issues.apache.org/activemq/browse/AMQ-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved AMQ-1134. - Resolution: Fixed > stomp connections in the broker don't get cleared up if the socket dies > --- > > Key: AMQ-1134 > URL: https://issues.apache.org/activemq/browse/AMQ-1134 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Reporter: james strachan > Assigned To: james strachan > Fix For: 4.1.1, 4.2.0 > > > it looks like there's a bug causing the connection to keep around -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1134) stomp connections in the broker don't get cleared up if the socket dies
stomp connections in the broker don't get cleared up if the socket dies --- Key: AMQ-1134 URL: https://issues.apache.org/activemq/browse/AMQ-1134 Project: ActiveMQ Issue Type: Bug Components: Broker Reporter: james strachan Assigned To: james strachan Fix For: 4.1.1, 4.2.0 it looks like there's a bug causing the connection to keep around -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37903 ] Danielius Jurna commented on AMQ-724: - Is is possible for the provided patch to be applied for 4.2 version? > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: SessionState.patch, StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-38) Async error on broker when running integration tests
[ https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Mittler updated AMQCPP-38: - Fix Version/s: (was: 1.1) 2.0 Moving to release 2.0 - the current thought is that this may be an issue with the broker. > Async error on broker when running integration tests > > > Key: AMQCPP-38 > URL: https://issues.apache.org/activemq/browse/AMQCPP-38 > Project: ActiveMQ C++ Client > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Albert Strasheim > Assigned To: Nathan Mittler > Fix For: 2.0 > > > Brought over from the comments in AMQCPP-28. > Sometimes when running the integration tests against the AMQ broker from > trunk, ones sees the following message from the broker: > ERROR Service - Async error occurred: > java.lang.IllegalStateException: Cannot remove a consumer that had not been > registered: ID:xxx-36153-1166305227288-5:16:-1:1 > at > org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:593) > at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64) > at > org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:287) > at > org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:178) > at > org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65) > at > org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) > at > org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74) > at > org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119) > at > org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379) > at > org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151) > at > org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64) > at > org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84) > at org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137) > at java.lang.Thread.run(Thread.java:595) > Using the default activemq.xml, I can reproduce the IllegalStateException > quite reliabily: > 1. Start a fresh copy of the broker (4.2 from yesterday's trunk) > 2. Run the integration test under Valgrind > 3. IllegalStateException happens at the end of > integration::durable::DurableTester::test or at the start of > integration::expiration::ExpirationTest::testExpired. > Subsequent test runs don't yield the error, until the broker is restarted. I > don't know if this issue could be time-dependent - if it is, it could explain > why I only see it when running under Valgrind. > On Linux, I also just got the following test failure for the first time (not > running under Valgrind): > 1) test: integration::durable::DurableTester::test (E) > uncaught exception of unknown type -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1020) Slow consumer terminally blocks both client and broker
[ https://issues.apache.org/activemq/browse/AMQ-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies resolved AMQ-1020. - Resolution: Fixed Fix Version/s: 4.2.0 This is fixed by the default use of cursors and the spooling to disk for non-durable slow topic consumers > Slow consumer terminally blocks both client and broker > -- > > Key: AMQ-1020 > URL: https://issues.apache.org/activemq/browse/AMQ-1020 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.2 > Environment: Broker: Windows XP, Sun JDK1.5 Client: activemq-dotnet > (Trunk) >Reporter: Rob Lugt > Assigned To: Rob Davies > Fix For: 4.2.0 > > > I have a multi-threaded client (client1) which is acting as both a publisher > (Topic1) and subscriber (Topic2) using a single session. There is another > client process (client2) which publishes on Topic2. > I have witnessed the following repeatable scenario where both clients get > stuck, which can only be rectified by restarting the broker! :- > Client1 publishes messages to Topic1 (rate = about 30 msgs/sec). > Client2 publishes bursts of messages to Topic2 (rate = 500 msgs/sec) > Client1 is a slow subscriber on Topic2 > After running in this scenario for a couple of seconds, Client1 and Client2 > become stuck. Looking at a stack trace for Client1 I can see that it's > read_loop is stuck waiting for input, and it's publisher thread is stuck > waiting for an acknowledgement to the synchronous message send (the > acknowledgement never arrives because the broker won't sent any more > messages). > Client2 is also stuck waiting for an acknowledgement to a synchronous send. > My perception is that it appears the broker is throttling the connection > because the consumer is running slowly, but for some reason it gets into a > state where all message flow stops (even though the consumer is automatically > acknowledging messages, albeit slowly). Furthermore, if I kill Client1 the > broker doesn't recover (using a JMX console the connection remains visible). > The broker uses a vanilla configuration (i.e. no policies are set for the > topics in quedtion). > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1020) Slow consumer terminally blocks both client and broker
[ https://issues.apache.org/activemq/browse/AMQ-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Davies reassigned AMQ-1020: --- Assignee: Rob Davies > Slow consumer terminally blocks both client and broker > -- > > Key: AMQ-1020 > URL: https://issues.apache.org/activemq/browse/AMQ-1020 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.2 > Environment: Broker: Windows XP, Sun JDK1.5 Client: activemq-dotnet > (Trunk) >Reporter: Rob Lugt > Assigned To: Rob Davies > > I have a multi-threaded client (client1) which is acting as both a publisher > (Topic1) and subscriber (Topic2) using a single session. There is another > client process (client2) which publishes on Topic2. > I have witnessed the following repeatable scenario where both clients get > stuck, which can only be rectified by restarting the broker! :- > Client1 publishes messages to Topic1 (rate = about 30 msgs/sec). > Client2 publishes bursts of messages to Topic2 (rate = 500 msgs/sec) > Client1 is a slow subscriber on Topic2 > After running in this scenario for a couple of seconds, Client1 and Client2 > become stuck. Looking at a stack trace for Client1 I can see that it's > read_loop is stuck waiting for input, and it's publisher thread is stuck > waiting for an acknowledgement to the synchronous message send (the > acknowledgement never arrives because the broker won't sent any more > messages). > Client2 is also stuck waiting for an acknowledgement to a synchronous send. > My perception is that it appears the broker is throttling the connection > because the consumer is running slowly, but for some reason it gets into a > state where all message flow stops (even though the consumer is automatically > acknowledging messages, albeit slowly). Furthermore, if I kill Client1 the > broker doesn't recover (using a JMX console the connection remains visible). > The broker uses a vanilla configuration (i.e. no policies are set for the > topics in quedtion). > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1071) Activemq connection factory silently ignores the erroneous arguments in broker url
[ https://issues.apache.org/activemq/browse/AMQ-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Co reassigned AMQ-1071: -- Assignee: Adrian Co > Activemq connection factory silently ignores the erroneous arguments in > broker url > -- > > Key: AMQ-1071 > URL: https://issues.apache.org/activemq/browse/AMQ-1071 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Environment: Linux >Reporter: Dileepan K > Assigned To: Adrian Co >Priority: Minor > > When an erroneous argument is passed to the broker url with failover, > activemq connection factory ignores the error. However if failover is > removed, it does throw exception. > Here is the example > 1. > failover:(tcp://localhost:62012)?jms.prefetchPolicy.all=10&wireFormat.maxInactivityDuration=0&jms.optimizeAcknowledge=false > 2. > tcp://localhost:62012?jms.prefetchPolicy.all=10&wireFormat.maxInactivityDuration=0&jms.optimizeAcknowledge=false > Only the # 2 throws exception as jms.prefetchPolicy.all is an invalid > argument here -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQCPP-38) Async error on broker when running integration tests
[
https://issues.apache.org/activemq/browse/AMQCPP-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37828
]
Albert Strasheim commented on AMQCPP-38:
Built a brand new AMQ 4.2, revision 493766. Also running AMQCPP from revision
493766. Using the default activemq.xml that gets included in the tarball made
by the AMQ build.
Running on Fedora Core 6 x86 Linux with Sun Java SDK 1.5.0_10. Hardware wise
I'm running a Intel P4 2.8 GHz with HT enabled with 2 GB RAM.
All the unit tests pass. The integration tests also pass, but I still get the
error on the broker the first time I run the integration tests after broker
startup. Not running under Valgrind or anything like that.
Stacktrace says:
{noformat}
java.lang.IllegalStateException: Cannot remove a consumer that had not been
registered: ID:xxx-40938-1168188574402-5:0:-1:1
at
org.apache.activemq.broker.TransportConnection.processRemoveConsumer(TransportConnection.java:552)
at org.apache.activemq.command.RemoveInfo.visit(RemoveInfo.java:64)
at
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:258)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:164)
at
org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:65)
at
org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:122)
at
org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:74)
at
org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:119)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompUnsubscribe(ProtocolConverter.java:379)
at
org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommad(ProtocolConverter.java:151)
at
org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:64)
at
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
at
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:137)
at java.lang.Thread.run(Thread.java:595)
{noformat}
As you can see, the line numbers have changed slightly from the previous
stacktrace.
The second time I run the integration tests (without restarting the broker), I
get this:
{noformat}
[EMAIL PROTECTED] test-integration]$ ./activemq-test-integration
integration::durable::DurableTester::test. : errorE
integration::expiration::ExpirationTest::testExpired.b928ada1-656d-47c3-b1ee-5e6b5eb6954b
: OK
integration::expiration::ExpirationTest::testNotExpired.943b9129-9147-46f0-8016-414389f0ca5e
: OK
integration::simple::SimpleTester::test. : OK
integration::transactional::TransactionTester::test. : OK
integration::various::SimpleRollbackTest::test. : OK
!!!FAILURES!!!
Test Results:
Run: 6 Failures: 0 Errors: 1
1) test: integration::durable::DurableTester::test (E)
uncaught exception of unknown type
{noformat}
No stacktrace on the broker though. The third time I run the tests, another
failure appears:
{noformat}
[EMAIL PROTECTED] test-integration]$ ./activemq-test-integration
integration::durable::DurableTester::test. : errorE
integration::expiration::ExpirationTest::testExpired.3036ea6e-b22c-4daf-8446-53c17e6995f4
: OK
integration::expiration::ExpirationTest::testNotExpired.0577f611-aa2b-452f-9aa4-42d654375b78
: OK
integration::simple::SimpleTester::test. : OK
integration::transactional::TransactionTester::test. : errorE
integration::various::SimpleRollbackTest::test. : OK
!!!FAILURES!!!
Test Results:
Run: 6 Failures: 0 Errors: 2
1) test: integration::durable::DurableTester::test (E)
uncaught exception of unknown type
2) test: integration::transactional::TransactionTester::test (E)
uncaught exception of unknown type
{noformat}
On the next run, TransactionTester passes again.
Just restarted the broker and ran the integration tests again -- no
IllegalStateException stacktrace this time. Noticed this in the broker log on
startup the second time round:
{noformat}
INFO JournalPersistenceAdapter - Journal Recovered: 1 message(s) in
transactions recovered.
{noformat}
Ran the tests again against the second instance of the broker. Everything went
fine again. Next run after that yielded a DurableTester failure again, but no
stacktrace on the broker.
> Async error on broker when running integration tests
>
>
> Key: AMQCPP-38
> URL: https://issues.apache.org/activemq/browse/AMQCPP-38
> Project: ActiveMQ C++ Client
> Issue Type: Bug
>Affects Versions: 1.1
>Reporter: Albert Strasheim
> Assigned To: Nathan Mittler
> Fix For: 1.1
>
>
> Brought o
[jira] Created: (AMQ-1118) dangling thread after shutdown broker with a managed transport
dangling thread after shutdown broker with a managed transport -- Key: AMQ-1118 URL: https://issues.apache.org/activemq/browse/AMQ-1118 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.0.2, 4.0.1, 4.0 Environment: Windows XP, demand forwarding, failover == true Reporter: Chris Hofstaedter I ran into a problem in which I end up with an orphaned thread every time I bounce a broker with a managed transport. I realize this may not be a big deal in many scenarios, but we may end up bouncing our broker everytime a user changes some configuration settings in our application and we need the app to run indefinitely. So orphaned threads are a concern to me. I traced it down to BrokerService.startTransportConnector(). In this function, if isUseJmx() returns true, the connector is decorated/replaced through a call to connector.asManagedConnector(). Turns out the broker never stores the reference to the newly created managed connector anywhere. I added transportConnectors.add(connector) to add the new managed connector to the broker's container of connectors and it seems to work in that all threads are shutdown cleanly even when the transport connector is managed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-1116) deadlock when shutting down client that is configured with failover=true and is presently disconnected from broker
deadlock when shutting down client that is configured with failover=true and is
presently disconnected from broker
--
Key: AMQ-1116
URL: https://issues.apache.org/activemq/browse/AMQ-1116
Project: ActiveMQ
Issue Type: Bug
Components: Transport
Affects Versions: 4.0.2
Reporter: Chris Hofstaedter
Sounds like a great idea to me :) Please go ahead and submit a jira with the
patch and we'll get it integrated ASAP
On 1/4/07, Chris Hofstaedter <[EMAIL PROTECTED]> wrote:
> I ran into this issue as well on <= 4.0.2. I never tested it against
> 4.1.The FailoverTransport doesn't shutdown if it is disconnected at
> the time of the shutdown.
>
> I believe that the root cause is in the
> FailoverTransport.oneway(Command
> command) function which will hold onto the command and keep trying to
> reconnect until the message is sent or the transport is disposed.
>
> I applied a local patch that seems to solve the problem. Note that
> I've only tested the patch against 4.0.2.
>
> Specifically, I early return from the oneway function if the command
> is ShutdownInfo and the connectedTransport is null. This seems to
> solve the problem in that I get clean shutdowns on the client when
> failover is true and the client is presently disconnected.
>
> Does this seem like a reasonable patch? Should I create a JIRA with
> this info?
>
>
>
> -Original Message-
> From: James Strachan [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, December 12, 2006 4:46 AM
> To: activemq-users@geronimo.apache.org
> Subject: Re: failover mode and client shutdown
>
> There could be a bug relating to closes with the failover transport
> possibly, but the ActiveMQConnection does wait up to the closeTimeout
> for a close to succeed before shutting down - so you could try reduce
> the timeout.
>
> http://incubator.apache.org/activemq/maven/activemq-core/apidocs/org/a
> pa
> che/activemq/ActiveMQConnection.html#setCloseTimeout(int)
>
>
> On 12/12/06, Keith Irwin <[EMAIL PROTECTED]> wrote:
> > Folks--
> >
> > When we have clients running and we take down AMQ (<= 4.1.0), then
> > attempt to shutdown the clients with Control-C (rather than kill the
> > JVM with a -9), the clients won't shut down. It's as if a "close"
> > on the failover connection never reaches the amq client classes.
> >
> > I note that in the 4.1.0 release notes, this issue is referenced,
> > and the advice is to set the maxReconnectAttempts (or similar)
> > property to something non-zero.
> >
> > The problem is that we don't want there to be a max number of
> > attempts. Unless we specifically want to take down the client (say,
> > for an apt-get package upgrade), we want it to keep on trying
> > forever.
> >
> > SO, my question: Is there an architectural reason for not being able
> > to close a failover connection if AMQ is down?
> >
> > If it isn't impossible due to tradeoffs elsewhere in the code base,
> > we might be willing to submit a patch to fix the issue.
> >
> > Our only other recourse is to attempt to close the connections in
> > separate threads, then timeout those threads after a while and fall
> > out the end of the java process.
> >
> > For instance:
> >
> > Thread th = new Thread(new Runnable() {
> > public void run() {
> > connection.close();
> > }
> >});
> >th.start();
> >
> >// give up after 2 seconds
> >Thread.currentThread().join(2000);
> >
> > I guess this is do-able, but it seems, you know, some how, well,
> wrong.
> >
> > So, is it worth investigating a patch to AMQ?
> >
> > Keith
> >
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Activemq broker set as windows service
I had configure to start activemq server as windows service but why when I start the Jconsole and it couldn't find any MBean (in this case is activemq) to be connected to? Thanks -- View this message in context: http://www.nabble.com/Activemq-broker-set-as-windows-service-tf2916869.html#a8151563 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Broker Fails
Thanks for reply. Is there any way to start and stop the broker using JMX console. I want to reset and set the flag saying activeBroker using JMX console . Is this possible. I want to do it manually ans such that i should be able to access that flag inside my application to know whethar the broker is running or not. Any help on this will be really appreciated garima015 wrote: > > I am not using network of brokers.I have a scenario in which if my running > broker fails or get shutdown what is going to happen with the > messages.Also if broker shutdown where my application will send the > message in order to restore them once the borker will start again. Also > how the restarted borker will resume with the undelivered messages > can somebody please help me in suggesting any solution. It is very urgent > > Thanks in advance > -- View this message in context: http://www.nabble.com/Broker-Fails-tf2908315.html#a8142855 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Broker Fails
Thanks for reply. Is there any way to start and stop the broker using JMX console. I want to reset and set the flag saying activeBroker using JMX console . Is this possible. I want to do it manually ans such that i should be able to access that flag inside my application to know whethar the broker is running or not. Any help on this will be really appreciated. garima015 wrote: > > I am not using network of brokers.I have a scenario in which if my running > broker fails or get shutdown what is going to happen with the > messages.Also if broker shutdown where my application will send the > message in order to restore them once the borker will start again. Also > how the restarted borker will resume with the undelivered messages > can somebody please help me in suggesting any solution. It is very urgent > > Thanks in advance > -- View this message in context: http://www.nabble.com/Broker-Fails-tf2908315.html#a8142802 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Broker Fails
You will need to switch to persistent messages to avoid any loss on broker restart as mentioned below. garima015 wrote: I am using NON PERSISTENT message delivery ... Please suggest me something to avoid any loss of message James.Strachan wrote: On 1/2/07, garima015 <[EMAIL PROTECTED]> wrote: I am not using network of brokers.I have a scenario in which if my running broker fails or get shutdown what is going to happen with the messages. If they are sent using persistent message delivery they will be on disk / in the database and redelivered on restart. Also if broker shutdown where my application will send the message in order to restore them once the borker will start again. Also how the restarted borker will resume with the undelivered messages can somebody please help me in suggesting any solution. It is very urgent If you are using auto-reconnection then the jms client will handle brokers being restarted or will failover to a new broker instance etc. http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html -- James --- http://radio.weblogs.com/0112098/
Re: Broker Fails
I am using NON PERSISTENT message delivery ... Please suggest me something to avoid any loss of message James.Strachan wrote: > > On 1/2/07, garima015 <[EMAIL PROTECTED]> wrote: >> >> I am not using network of brokers.I have a scenario in which if my >> running >> broker fails or get shutdown what is going to happen with the messages. > > If they are sent using persistent message delivery they will be on > disk / in the database and redelivered on restart. > >> Also >> if broker shutdown where my application will send the message in order to >> restore them once the borker will start again. Also how the restarted >> borker >> will resume with the undelivered messages >> can somebody please help me in suggesting any solution. It is very urgent > > If you are using auto-reconnection then the jms client will handle > brokers being restarted or will failover to a new broker instance etc. > > http://incubator.apache.org/activemq/how-can-i-support-auto-reconnection.html > -- > > James > --- > http://radio.weblogs.com/0112098/ > > -- View this message in context: http://www.nabble.com/Broker-Fails-tf2908315.html#a8130549 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: error when start broker
Oh,I will wait... Please replay when you can figure out how to do it with sybase. Hiram Chirino wrote: > > every DB is slightly different we just need to figure out how to do it > with sybase. > > On 12/19/06, rain.xk <[EMAIL PROTECTED]> wrote: >> >> I have not used a pessimistic lock on database record in sybase ASE 12.5. >> :( >> Is this the sybase's defect? >> >> >> Hiram Chirino wrote: >> > >> > How do you do a pessimistic lock on database record in sybase ASE >> 12.5?? >> > >> > On 12/19/06, rain.xk <[EMAIL PROTECTED]> wrote: >> >> >> >> Hi, >> >> My database is sybaseASE12.5,and I use the activemq4.1.0. >> >> The following is the series of messages when I start broker: >> >> >> >> - ActiveMQ 4.1.0-incubator JMS Message Broker (xuke) is starting >> >> - For help or more information please see: >> >> http://incubator.apache.org/activemq/ >> >> - Database driver recognized: [jconnect__tm__for_jdbc__tm_] >> >> - Attempting to acquire the exclusive lock to become the Master broker >> >> - Failed to acquire lock: com.sybase.jdbc3.jdbc.SybSQLException: FOR >> >> UPDATE >> >> can not be used in a SELECT which is not part of the declaration of a >> >> cursor >> >> or which is not a stored procedure. >> >> com.sybase.jdbc3.jdbc.SybSQLException: FOR UPDATE can not be used in >> a >> >> SELECT which is not part of the declaration of a cursor or which is >> not a >> >> stored procedure. >> >> at com.sybase.jdbc3.tds.Tds.a(Unknown Source) >> >> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) >> >> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown >> Source) >> >> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown >> Source) >> >> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown >> Source) >> >> at com.sybase.jdbc3.jdbc.SybStatement.executeLoop(Unknown >> Source) >> >> at com.sybase.jdbc3.jdbc.SybStatement.execute(Unknown Source) >> >> at com.sybase.jdbc3.jdbc.SybPreparedStatement.execute(Unknown >> >> Source) >> >> at >> >> >> org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) >> >> at >> >> >> org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) >> >> at >> >> >> org.apache.activemq.store.jdbc.DefaultDatabaseLocker.start(DefaultDatabaseLocker.java:59) >> >> >> >> How can I handle this? >> >> -- >> >> View this message in context: >> >> http://www.nabble.com/error-when-start-broker-tf2844348.html#a7942260 >> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Regards, >> > Hiram >> > >> > Blog: http://hiramchirino.com >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/error-when-start-broker-tf2844348.html#a7983092 >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > -- View this message in context: http://www.nabble.com/error-when-start-broker-tf2844348.html#a8001705 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: error when start broker
every DB is slightly different we just need to figure out how to do it with sybase. On 12/19/06, rain.xk <[EMAIL PROTECTED]> wrote: I have not used a pessimistic lock on database record in sybase ASE 12.5. :( Is this the sybase's defect? Hiram Chirino wrote: > > How do you do a pessimistic lock on database record in sybase ASE 12.5?? > > On 12/19/06, rain.xk <[EMAIL PROTECTED]> wrote: >> >> Hi, >> My database is sybaseASE12.5,and I use the activemq4.1.0. >> The following is the series of messages when I start broker: >> >> - ActiveMQ 4.1.0-incubator JMS Message Broker (xuke) is starting >> - For help or more information please see: >> http://incubator.apache.org/activemq/ >> - Database driver recognized: [jconnect__tm__for_jdbc__tm_] >> - Attempting to acquire the exclusive lock to become the Master broker >> - Failed to acquire lock: com.sybase.jdbc3.jdbc.SybSQLException: FOR >> UPDATE >> can not be used in a SELECT which is not part of the declaration of a >> cursor >> or which is not a stored procedure. >> com.sybase.jdbc3.jdbc.SybSQLException: FOR UPDATE can not be used in a >> SELECT which is not part of the declaration of a cursor or which is not a >> stored procedure. >> at com.sybase.jdbc3.tds.Tds.a(Unknown Source) >> at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) >> at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) >> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) >> at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) >> at com.sybase.jdbc3.jdbc.SybStatement.executeLoop(Unknown Source) >> at com.sybase.jdbc3.jdbc.SybStatement.execute(Unknown Source) >> at com.sybase.jdbc3.jdbc.SybPreparedStatement.execute(Unknown >> Source) >> at >> org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) >> at >> org.apache.commons.dbcp.DelegatingPreparedStatement.execute(DelegatingPreparedStatement.java:117) >> at >> org.apache.activemq.store.jdbc.DefaultDatabaseLocker.start(DefaultDatabaseLocker.java:59) >> >> How can I handle this? >> -- >> View this message in context: >> http://www.nabble.com/error-when-start-broker-tf2844348.html#a7942260 >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. >> >> > > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > -- View this message in context: http://www.nabble.com/error-when-start-broker-tf2844348.html#a7983092 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- Regards, Hiram Blog: http://hiramchirino.com
Re: Maximum number of topics per broker
On 12/13/06, toolpusher2006 <[EMAIL PROTECTED]> wrote: Hello, What is the maximum number of topics that can be configured on a single broker? The only limit is RAM in the broker process We are planning to run around a thousand separate durable topics and I was wondering if I can do this on one broker. Sure. Just watch your RAM usage in JMX to see how the RAM usage is affected as you ramp up clients, destinations and subscriptions etc -- James --- http://radio.weblogs.com/0112098/
Maximum number of topics per broker
Hello, What is the maximum number of topics that can be configured on a single broker? We are planning to run around a thousand separate durable topics and I was wondering if I can do this on one broker. If not what are our options? Thanks in advance. -Hari Koduru -- View this message in context: http://www.nabble.com/Maximum-number-of-topics-per-broker-tf2816378.html#a7860425 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Re: Broker
Solved!!! garima015 wrote: > > I am new to ActiveMQJMS.I have requirement where Requestor and Replier are > residing on different JMS.If the broker is started is there any way from > which i can find out which broker is running to get the connection from > ActiveMQConnectionFactory. > I need it to be as java code. > Any help will be really appreciated > -- View this message in context: http://www.nabble.com/Broker-tf2781151.html#a7760355 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
Broker
I am new to ActiveMQJMS.I have requirement where Requestor and Replier are residing on different JMS.If the broker is started is there any way from which i can find out which broker is running to get the connection from ActiveMQConnectionFactory. I need it to be as java code. Any help will be really appreciated -- View this message in context: http://www.nabble.com/Broker-tf2781151.html#a7759151 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Commented: (AMQ-1020) Slow consumer terminally blocks both client and broker
[ https://issues.apache.org/activemq/browse/AMQ-1020?page=comments#action_37631 ] paul normington commented on AMQ-1020: -- I have run into this same issue I think. We have a scenario with a DurableSubscriber that has retrieved some messages and then disconnects. The publisher continuous publishing at 1000 messages per second. After 6 messages are sent, the publisher hangs, and the broker quiesces. I have seen this behavior with 4.0.1 and 4.1.0 I took a stack trace which showed the server was stuck in UsageManager.waitForSpace(). I can delay the hanging problem by configuring more memory in the MemoryManager. I have tried setting timeToLives and pendingMessageLimitStrategies but I still get the hanging. If I use a non durable subscriber the problem goes away, but this is not an ideal solution for us. > Slow consumer terminally blocks both client and broker > -- > > Key: AMQ-1020 > URL: https://issues.apache.org/activemq/browse/AMQ-1020 > Project: ActiveMQ > Issue Type: Bug > Components: Broker >Affects Versions: 4.0.2 > Environment: Broker: Windows XP, Sun JDK1.5 Client: activemq-dotnet > (Trunk) >Reporter: Rob Lugt > > I have a multi-threaded client (client1) which is acting as both a publisher > (Topic1) and subscriber (Topic2) using a single session. There is another > client process (client2) which publishes on Topic2. > I have witnessed the following repeatable scenario where both clients get > stuck, which can only be rectified by restarting the broker! :- > Client1 publishes messages to Topic1 (rate = about 30 msgs/sec). > Client2 publishes bursts of messages to Topic2 (rate = 500 msgs/sec) > Client1 is a slow subscriber on Topic2 > After running in this scenario for a couple of seconds, Client1 and Client2 > become stuck. Looking at a stack trace for Client1 I can see that it's > read_loop is stuck waiting for input, and it's publisher thread is stuck > waiting for an acknowledgement to the synchronous message send (the > acknowledgement never arrives because the broker won't sent any more > messages). > Client2 is also stuck waiting for an acknowledgement to a synchronous send. > My perception is that it appears the broker is throttling the connection > because the consumer is running slowly, but for some reason it gets into a > state where all message flow stops (even though the consumer is automatically > acknowledging messages, albeit slowly). Furthermore, if I kill Client1 the > broker doesn't recover (using a JMX console the connection remains visible). > The broker uses a vanilla configuration (i.e. no policies are set for the > topics in quedtion). > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Broker state and racing conditions
While analyzing http://issues.apache.org/activemq/browse/AMQ-724 issue it seems that broker state is spread across several objects and modification of this state is not synchronized. On connection add/remove modification is made in many objects (you can see it in AbstractConnection), so on heavy load it can leave broker in inconsistent state. Bug mentioned above exactly shows the problem. And the fix is only dealing with consequences, not with the cause. This bug never occures when synchronization is made in AbstractConnection on add/remove operations. So it seems that current architecture is more towards performance than roubustness. Any thoughts? -- View this message in context: http://www.nabble.com/Broker-state-and-racing-conditions-tf2759642.html#a7694274 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Reopened: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=all ] Danielius Jurna reopened AMQ-724: - I wonder how this bug has slipped through unit tests. I'm adding patch for org.apache.activemq.state.SessionState > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: SessionState.patch, StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-724) Stomp client is not removed from the broker on client disconnect
[ https://issues.apache.org/activemq/browse/AMQ-724?page=all ] Danielius Jurna updated AMQ-724: Attachment: SessionState.patch This patch is against 4.0 branch. This bug is also in 4.1 branch > Stomp client is not removed from the broker on client disconnect > > > Key: AMQ-724 > URL: https://issues.apache.org/activemq/browse/AMQ-724 > Project: ActiveMQ > Issue Type: Bug > Components: Transport >Affects Versions: 4.0 > Environment: Linux, Java 1.5.0_06 >Reporter: Danielius Jurna > Assigned To: james strachan > Fix For: 4.0.2, 4.1.0 > > Attachments: SessionState.patch, StompSubscriptionRemoveTest.java > > > If Stomp client crashes (or disconnects unexpectedly) when there are > unconsumed messages in the broker, the subscriptions are not removed from the > broker and some phantom consumer is still consuming messages. If you connect > other client, it receives only half messages (other half messages goes to > that phantom consumer still left afrter client disconnect). There are no > error logs in activemq logs. We are using stomp client, whith client > acknowledge mode, so on broker restart, all messages are delivered properly. > You can also see in jmx console, that subscription still exists whithout any > connection left. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-841) NullPointerException when using MasterConnector and specifying the broker name with space in it.
[
https://issues.apache.org/activemq/browse/AMQ-841?page=comments#action_37532 ]
Marlon Santos commented on AMQ-841:
---
It also happens with other broker configurations and present in the windows xp
os..
> NullPointerException when using MasterConnector and specifying the broker
> name with space in it.
>
>
> Key: AMQ-841
> URL: https://issues.apache.org/activemq/browse/AMQ-841
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0.1
> Environment: Linux, jdk1.5.0_06
>Reporter: Richard Wafer
>Priority: Minor
>
> I've got a hard time trying to figure out why I got a null pointer trying to
> use the Master/slave configuration for ActiveMQ.
> Finnally by looking at the code I've saw the following:
> In BrokerService.java
> public void initializeMasterConnector(URI remoteURI) throws Exception {
> ...
> URI localURI = getVmConnectorURI();
> ...
> }
> public URI getVmConnectorURI() {
> if (vmConnectorURI == null) {
> try {
> vmConnectorURI = new URI("vm://" + getBrokerName());
> }
> catch (URISyntaxException e) {
> }
> }
> return vmConnectorURI;
> }
> My problem is that I've specified a broker name with space in it "Slave
> Broker". So I the new URI() here throw a URISyntaxException that was badly
> absorb. And this leads to a null pointer at line:159 of TransportFactory.java.
>String scheme = location.getScheme(); when location is null du to the
> previous exception.
> The link between the error and the cause was not clear at the first sigth.
> A precondition on the setBrokerName could do the job.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-841) NullPointerException when using MasterConnector and specifying the broker name with space in it.
[
https://issues.apache.org/activemq/browse/AMQ-841?page=comments#action_37531 ]
Marlon Santos commented on AMQ-841:
---
Hi,
i had seen that the problem was when the URISyntaxException was catched,
there was no actual value given to the vmConnectorURI so it stays null. I can
create a patch for this but i dont know which is the best approach, because of
some issues.
a) shutdown the broker gracefully and display a warn sign that the broker is
shutting down because of invalid brokername
b) trim the starting and ending space, and change spaces in - between the
brokername.
> NullPointerException when using MasterConnector and specifying the broker
> name with space in it.
>
>
> Key: AMQ-841
> URL: https://issues.apache.org/activemq/browse/AMQ-841
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
>Affects Versions: 4.0.1
> Environment: Linux, jdk1.5.0_06
>Reporter: Richard Wafer
>Priority: Minor
>
> I've got a hard time trying to figure out why I got a null pointer trying to
> use the Master/slave configuration for ActiveMQ.
> Finnally by looking at the code I've saw the following:
> In BrokerService.java
> public void initializeMasterConnector(URI remoteURI) throws Exception {
> ...
> URI localURI = getVmConnectorURI();
> ...
> }
> public URI getVmConnectorURI() {
> if (vmConnectorURI == null) {
> try {
> vmConnectorURI = new URI("vm://" + getBrokerName());
> }
> catch (URISyntaxException e) {
> }
> }
> return vmConnectorURI;
> }
> My problem is that I've specified a broker name with space in it "Slave
> Broker". So I the new URI() here throw a URISyntaxException that was badly
> absorb. And this leads to a null pointer at line:159 of TransportFactory.java.
>String scheme = location.getScheme(); when location is null du to the
> previous exception.
> The link between the error and the cause was not clear at the first sigth.
> A precondition on the setBrokerName could do the job.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
