[jira] [Commented] (AMQ-4383) ActiveMQ dependency not present in central maven repository ??
[ https://issues.apache.org/jira/browse/AMQ-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608789#comment-13608789 ] Bhanu commented on AMQ-4383: Upgrading to Maven3 solved the issue. With Maven 1, the dependencies were not searched from repo.fusesource.com automatically. Thanks for the help guys. ActiveMQ dependency not present in central maven repository ?? -- Key: AMQ-4383 URL: https://issues.apache.org/jira/browse/AMQ-4383 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.8.0 Environment: Linux Reporter: Bhanu We're facing issues while trying to upgrade to ActiveMQ v5.8. The maven build is failing with the following error:- dependency groupIdorg.apache.activemq/groupId artifactIdactivemq-all/artifactId version5.8.0/version exclusions mvn package -Dmaven.test.skip=true [INFO] Scanning for projects... [INFO] [INFO] Building common [INFO]task-segment: [package] [INFO] [INFO] [resources:resources] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /prod/desflow-qa/dflowdev/test/desflow/common/src/main/resources Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.pom Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar Downloading: http://maven/deshaw/org/apache/qpid/proton-jms/0.3.0-fuse-2/proton-jms-0.3.0-fuse-2.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.qpid:proton-jms:jar:0.3.0-fuse-2 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.qpid -DartifactId=proton-jms -Dversion=0.3.0-fuse-2 -Dpackaging=jar -Dfile=/path/to/file Is something broken here ? Thanks, Bhanu -- 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] [Commented] (AMQ-4381) Broker throwing exception Failed to create directory 'activemq-data/amqProdBroker/tmp_storage'
[ https://issues.apache.org/jira/browse/AMQ-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608793#comment-13608793 ] Bhanu commented on AMQ-4381: Yep, permissions were all fine. Yep it was on a network drive. Another interesting thing was broker did not die after throwing this. Broker throwing exception Failed to create directory 'activemq-data/amqProdBroker/tmp_storage' Key: AMQ-4381 URL: https://issues.apache.org/jira/browse/AMQ-4381 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.6.0 Environment: Linux Reporter: Bhanu We saw the below reported exception with broker today. The interesting thing was the directory activemq-data/amqProdBroker/tmp_storage was already present and accessible by broker. Can anyone shed a little light on this weird broker behavior? Async error occurred: java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: Failed to create direc tory 'activemq-data/amqProdBroker/tmp_storage' | org.apache.activemq.broker.TransportConnection.Service | ActiveMQ Transport: tcp:///10.77.27.214:37710 java.lang.RuntimeException: java.lang.RuntimeException: java.io.IOException: Failed to create directory 'activemq-data/amqProdBroker/tmp_storage' at org.apache.activemq.broker.region.cursors.FilePendingMessageCursor.tryAddMessageLast(FilePendingMessageCursor.java:239) at org.apache.activemq.broker.region.TopicSubscription.add(TopicSubscription.java:136) at org.apache.activemq.broker.region.policy.SimpleDispatchPolicy.dispatch(SimpleDispatchPolicy.java:48) at org.apache.activemq.broker.region.Topic.dispatch(Topic.java:669) at org.apache.activemq.broker.region.Topic.doMessageSend(Topic.java:481) at org.apache.activemq.broker.region.Topic.send(Topic.java:417) at org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.java:407) at org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java:503) at org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegionBroker.java:305) at org.apache.activemq.advisory.AdvisoryBroker.fireAdvisory(AdvisoryBroker.java:533) at org.apache.activemq.advisory.AdvisoryBroker.fireAdvisory(AdvisoryBroker.java:464) at org.apache.activemq.advisory.AdvisoryBroker.fireAdvisory(AdvisoryBroker.java:459) at org.apache.activemq.advisory.AdvisoryBroker.addDestinationInfo(AdvisoryBroker.java:182) at org.apache.activemq.broker.BrokerFilter.addDestinationInfo(BrokerFilter.java:217) at org.apache.activemq.broker.BrokerFilter.addDestinationInfo(BrokerFilter.java:217) at org.apache.activemq.broker.BrokerFilter.addDestinationInfo(BrokerFilter.java:217) at org.apache.activemq.broker.MutableBrokerFilter.addDestinationInfo(MutableBrokerFilter.java:223) at org.apache.activemq.broker.util.LoggingBrokerPlugin.addDestinationInfo(LoggingBrokerPlugin.java:476) at org.apache.activemq.broker.MutableBrokerFilter.addDestinationInfo(MutableBrokerFilter.java:223) at org.apache.activemq.broker.TransportConnection.processAddDestination(TransportConnection.java:477) at org.apache.activemq.command.DestinationInfo.visit(DestinationInfo.java:122) at org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292) at org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:150) at org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:45) at org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:229) at org.apache.activemq.transport.stomp.StompTransportFilter.sendToActiveMQ(StompTransportFilter.java:87) at org.apache.activemq.transport.stomp.ProtocolConverter.sendToActiveMQ(ProtocolConverter.java:126) at org.apache.activemq.transport.stomp.ProtocolConverter.createTempDestination(ProtocolConverter.java:742) at org.apache.activemq.transport.stomp.LegacyFrameTranslator.convertDestination(LegacyFrameTranslator.java:189) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompSubscribe(ProtocolConverter.java:448) at org.apache.activemq.transport.stomp.ProtocolConverter.onStompCommand(ProtocolConverter.java:176) at org.apache.activemq.transport.stomp.StompTransportFilter.onCommand(StompTransportFilter.java:76) at org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83) at
[jira] [Deleted] (AMQ-4395) comment hi test
[ https://issues.apache.org/jira/browse/AMQ-4395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish deleted AMQ-4395: -- comment hi test --- Key: AMQ-4395 URL: https://issues.apache.org/jira/browse/AMQ-4395 Project: ActiveMQ Issue Type: Bug Reporter: Niraj Gupta test -- 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] [Deleted] (AMQ-4396) comment hi test
[ https://issues.apache.org/jira/browse/AMQ-4396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish deleted AMQ-4396: -- comment hi test --- Key: AMQ-4396 URL: https://issues.apache.org/jira/browse/AMQ-4396 Project: ActiveMQ Issue Type: Bug Reporter: Niraj Gupta test -- 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] [Created] (AMQ-4397) XSS vulnerability in scheduled.jsp
Dejan Bosanac created AMQ-4397:
--
Summary: XSS vulnerability in scheduled.jsp
Key: AMQ-4397
URL: https://issues.apache.org/jira/browse/AMQ-4397
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.9.0
If string like {{* * * * *scriptalert(1)/script}} is entered into cron of a
message, JS code will be executed on the scheduled.jsp page.
--
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] [Created] (AMQ-4398) XSS vulnerability in demo web application
Dejan Bosanac created AMQ-4398: -- Summary: XSS vulnerability in demo web application Key: AMQ-4398 URL: https://issues.apache.org/jira/browse/AMQ-4398 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.8.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.9.0 Portfolio publisher servlet doesn't sanitize input. For example he following url in Firefox http://localhost:8161/demo/portfolioPublish?count=1refresh=%27%3E%3Cscript%3Ealert%28%27XSS%27%29;%3C/script%3Estocks=IBMWstocks=BEASstocks=MSFTstocks=SUNW will trigger JS code. -- 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] (AMQ-4397) XSS vulnerability in scheduled.jsp
[
https://issues.apache.org/jira/browse/AMQ-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-4397.
Resolution: Fixed
Fixed with svn revision 1459265
XSS vulnerability in scheduled.jsp
--
Key: AMQ-4397
URL: https://issues.apache.org/jira/browse/AMQ-4397
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.9.0
If string like {{* * * * *scriptalert(1)/script}} is entered into cron of
a message, JS code will be executed on the scheduled.jsp page.
--
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] (AMQ-4398) XSS vulnerability in demo web application
[ https://issues.apache.org/jira/browse/AMQ-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-4398. Resolution: Fixed fixed with svn revision 1459301 XSS vulnerability in demo web application -- Key: AMQ-4398 URL: https://issues.apache.org/jira/browse/AMQ-4398 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.8.0 Reporter: Dejan Bosanac Assignee: Dejan Bosanac Fix For: 5.9.0 Portfolio publisher servlet doesn't sanitize input. For example he following url in Firefox http://localhost:8161/demo/portfolioPublish?count=1refresh=%27%3E%3Cscript%3Ealert%28%27XSS%27%29;%3C/script%3Estocks=IBMWstocks=BEASstocks=MSFTstocks=SUNW will trigger JS code. -- 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] [Commented] (AMQ-4394) Can't get module activemq-all with Ivy: org.apache.qpid#proton-jms;0.3.0-fuse-2: not found
[
https://issues.apache.org/jira/browse/AMQ-4394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608956#comment-13608956
]
Timothy Bish commented on AMQ-4394:
---
You'll need to update your IVY configuration so that it can get those new deps
from here:
{noformat}
repositories
!-- for the proton dependency --
repository
idcom.fusesource.m2/id
urlhttp://repo.fusesource.com/nexus/content/groups/public//url
releasesenabledtrue/enabled/releases
snapshotsenabledfalse/enabled/snapshots
/repository
repository
idcom.fusesource.m2.snapshot/id
urlhttp://repo.fusesource.com/nexus/content/repositories/snapshots//url
releasesenabledfalse/enabled/releases
snapshotsenabledtrue/enabled/snapshots
/repository
/repositories
{noformat}
Can't get module activemq-all with Ivy:
org.apache.qpid#proton-jms;0.3.0-fuse-2: not found
--
Key: AMQ-4394
URL: https://issues.apache.org/jira/browse/AMQ-4394
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Apache Ivy 2.3.0
Java version: 1.6.0_39, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_39\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows
Reporter: Gary Gregory
If I try to get activemq-all 5.8.0 with:
{code:xml}
ivy:retrieve organisation=org.apache.activemq module=activemq-all
revision=5.8.0 pattern=${jmeter.lib}/[artifact]-[type].[ext]
inline=true /
{code}
I get:
{noformat}
[ivy:retrieve] ::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::
[ivy:retrieve] :: org.apache.qpid#proton-jms;0.3.0-fuse-2: not found
[ivy:retrieve] ::
{noformat}
This worked fine in 5.7.0.
--
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] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608957#comment-13608957 ] Timothy Bish commented on AMQ-4364: --- Seems doubtful given that you started with a clean KahaDB, you can always go back to default settings and test. Cannot delete queue via JMX or JConsole --- Key: AMQ-4364 URL: https://issues.apache.org/jira/browse/AMQ-4364 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130308.055714-20 Reporter: Lionel Cons When using the latest 5.9 snapshot, we noticed that queues cannot be deleted via JMX or JConsole. When invoking the removeQueue() method, we get a success status but the queue is not removed. This may have been present in older versions and not only this particular snapshot. -- 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] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13608990#comment-13608990 ] Lionel Cons commented on AMQ-4364: -- Via trial and error, it seems that the following line is causing us problems: jaasDualAuthenticationPlugin configuration=activemq-domain sslConfiguration=activemq-ssl-domain/ Without it, queue deletion works. With it, it does not. Do you see the same behavior? Cannot delete queue via JMX or JConsole --- Key: AMQ-4364 URL: https://issues.apache.org/jira/browse/AMQ-4364 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130308.055714-20 Reporter: Lionel Cons When using the latest 5.9 snapshot, we noticed that queues cannot be deleted via JMX or JConsole. When invoking the removeQueue() method, we get a success status but the queue is not removed. This may have been present in older versions and not only this particular snapshot. -- 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] [Commented] (AMQ-4364) Cannot delete queue via JMX or JConsole
[ https://issues.apache.org/jira/browse/AMQ-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13609001#comment-13609001 ] Timothy Bish commented on AMQ-4364: --- Can you throw together a unit test that reproduces it? Cannot delete queue via JMX or JConsole --- Key: AMQ-4364 URL: https://issues.apache.org/jira/browse/AMQ-4364 Project: ActiveMQ Issue Type: Bug Environment: activemq-5.9-20130308.055714-20 Reporter: Lionel Cons When using the latest 5.9 snapshot, we noticed that queues cannot be deleted via JMX or JConsole. When invoking the removeQueue() method, we get a success status but the queue is not removed. This may have been present in older versions and not only this particular snapshot. -- 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] [Commented] (AMQ-3779) Allow logging broker plugin to use a log per destination
[ https://issues.apache.org/jira/browse/AMQ-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13609203#comment-13609203 ] Bhanu commented on AMQ-3779: Hi Gary, I Was looking for exactly the same functionality for one of our new use cases. Was happy to found a request but seems like this has been long forgotten. Can this be taken up for the next version please? Thanks, Bhanu Allow logging broker plugin to use a log per destination Key: AMQ-3779 URL: https://issues.apache.org/jira/browse/AMQ-3779 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.5.1 Reporter: Gary Tully Priority: Minor Labels: logging, plugin Re: http://activemq.2283324.n4.nabble.com/How-to-log-all-incoming-msgs-of-Queue-quot-hello-quot-into-a-separate-logfile-td4487917.html Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned. A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.destination name for producer send events -- Query on composites? For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination. -- 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] [Updated] (AMQ-3779) Allow logging broker plugin to use a log per destination
[ https://issues.apache.org/jira/browse/AMQ-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary Tully updated AMQ-3779: Fix Version/s: 5.9.0 @Bhanu - maybe attempt a patch, we love contributions :-) In any event will try to get to it for the next release. Allow logging broker plugin to use a log per destination Key: AMQ-3779 URL: https://issues.apache.org/jira/browse/AMQ-3779 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 5.5.1 Reporter: Gary Tully Priority: Minor Labels: logging, plugin Fix For: 5.9.0 Re: http://activemq.2283324.n4.nabble.com/How-to-log-all-incoming-msgs-of-Queue-quot-hello-quot-into-a-separate-logfile-td4487917.html Would be nice to configure the http://activemq.apache.org/logging-interceptor.html to use a send message log per destination so that destination messages can be easily partitioned. A logPerDestination boolean attribute, that would cause the plugin to use a logger of the form: org.apache.activemq.broker.util.LoggingBrokerPlugin.destination name for producer send events -- Query on composites? For the simplest implementation, composites, they would have their unique log rather than parsing the composite and repeating the log message per destination. -- 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] [Created] (AMQ-4399) jdbcPersistenceAdapter takes a long time to shutdown, causing journal recovery
Jason Shepherd created AMQ-4399: --- Summary: jdbcPersistenceAdapter takes a long time to shutdown, causing journal recovery Key: AMQ-4399 URL: https://issues.apache.org/jira/browse/AMQ-4399 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.7.0 Environment: 5.7.0.fuse-71-047 MySQL with Journal Reporter: Jason Shepherd Attachments: activemq.xml Using the attached configuration, we have configured JDBC persistence with a journal. After sending 30,000 messages to a queue, using persistent messages, we see that shutdown of the broker timeouts out and the process is killed by the OS. After restarting the broker, a journal recovery takes place, which takes a long time to complete. We would like to avoid such a long restart time in this scenario. -- 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
