[jira] Assigned: (AMQ-594) SimpleNetworkTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-594?page=all ] Adrian Co reassigned AMQ-594: - Assignee: Rob Davies (was: Adrian Co) Assigning to Rob for technical review. :) SimpleNetworkTest hangs --- Key: AMQ-594 URL: https://issues.apache.org/activemq/browse/AMQ-594 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 4.0 RC2 Reporter: Darwin Flores Assigned To: Rob Davies Fix For: 4.2.0 Attachments: DemandForwardingBridgePatch.patch The SimpleNetworkTest appears to be hanging in Linux platform -- 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-594) SimpleNetworkTest hangs
[ https://issues.apache.org/activemq/browse/AMQ-594?page=all ] Adrian Co updated AMQ-594: -- Attachment: DemandForwardingBridgePatch.patch Seems that the test is hanging because the remote broker is trying to send a ShutdownInfo to the local broker after the fact that the local broker has been stopped. I've attached a patch that would not use failover when the forwarding bridge is sending a shutdown info. I'm not sure though if this is a good approach. SimpleNetworkTest hangs --- Key: AMQ-594 URL: https://issues.apache.org/activemq/browse/AMQ-594 Project: ActiveMQ Issue Type: Bug Components: Test Cases Affects Versions: 4.0 RC2 Reporter: Darwin Flores Assigned To: Adrian Co Fix For: 4.2.0 Attachments: DemandForwardingBridgePatch.patch The SimpleNetworkTest appears to be hanging in Linux platform -- 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-1062) Closing consumer does not free server memory, server heap overflows
[ https://issues.apache.org/activemq/browse/AMQ-1062?page=all ] Rob Davies reassigned AMQ-1062: --- Assignee: Rob Davies Closing consumer does not free server memory, server heap overflows --- Key: AMQ-1062 URL: https://issues.apache.org/activemq/browse/AMQ-1062 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.2.0 Environment: Windows XP Professional, Java HotSpot(TM) Client VM version 1.5.0_09-b01 Reporter: [EMAIL PROTECTED] Assigned To: Rob Davies Priority: Critical Fix For: 4.2.0 I am using the store durable pending cursor. Create a producer for a topic and let it run continuously for the remainder of the test. Create a durable consumer and kill it immediately. (So now messages are piling up for the consumer, but memory usage is low thanks to the store cursor.) Wait a few minutes. Now, start the same durable consumer again. Memory usage will increase considerably at this point (I get it around 20%). Now, stop the consumer. Memory usage DOES NOT go down. Now, reconnect the same durable consumer. It is possible to get a heap overrun that nukes the server! This is a problem when there are many consumers, and the general use case is that many of them are not active at the same time. I am classifying this as critical bug due to the heap overflow whenI try to reconnect, but it would be great if the memory usage went down as soon as disconnect. I image there may also be problems like this with queues, but did not test. 2006-11-19 17:24:20,015 [/127.0.0.1:3278] DEBUG PrefetchSubscription - Prefetch limit. 2006-11-19 17:24:21,281 [/127.0.0.1:3278] DEBUG Service - Error occured while processing sync command: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space -- 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-493) Improve queue and durable subscription recovery performance.
[ https://issues.apache.org/activemq/browse/AMQ-493?page=all ] Rob Davies reassigned AMQ-493: -- Assignee: Rob Davies Improve queue and durable subscription recovery performance. Key: AMQ-493 URL: https://issues.apache.org/activemq/browse/AMQ-493 Project: ActiveMQ Issue Type: Improvement Components: Broker Affects Versions: 4.0 Reporter: Hiram Chirino Assigned To: Rob Davies Fix For: 4.2.0 The performance of recovering persistent messages for a queue or a durable consumer is not spectacular in our current implementation for several reasons: (1) Producers are paused while recovery is occuring. (2) All messages for the destination are unmarshalled and sometimes even kept in a list when they are recovered (causes scaleability issues) We should provide more of a lazy loading strategy where messages are only loaded based on consumer demand. -- 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-914) OutOfMemoryError
[ https://issues.apache.org/activemq/browse/AMQ-914?page=all ] Rob Davies resolved AMQ-914. Fix Version/s: 4.2.0 Resolution: Fixed Use optional Store cursor to page messages into the broker from the persistent store SVN revision 478967. OutOfMemoryError Key: AMQ-914 URL: https://issues.apache.org/activemq/browse/AMQ-914 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.0.1 Reporter: Daniel Aioanei Assigned To: Rob Davies Fix For: 4.2.0 Attachments: activemq.xml, jmxconsole.png I was doing some testing with a single MDP listening to a queue which had about 247300 messages, with a postgres backend. ActiveMQ server was started using the default activemq startup script (on Linux). In this configuration the cpu normally stays mostly idle and I described this behaviour in another bug report. Another issue came to surface when I tried to profile the client application with EclipseColorer to see why a single MDP can't hog my machine. But when I tried so, 4 OutOfMemoryError messages were logged by ActiveMQ server. Note that I was *not* profiling the server, but the client which is a totally different process. -- 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-1061) Memory usage jumps 100% with durable subscription and stays there
[ https://issues.apache.org/activemq/browse/AMQ-1061?page=all ] Rob Davies resolved AMQ-1061. - Resolution: Fixed SVN revision 478967. Memory usage jumps 100% with durable subscription and stays there --- Key: AMQ-1061 URL: https://issues.apache.org/activemq/browse/AMQ-1061 Project: ActiveMQ Issue Type: Bug Affects Versions: 4.2.0 Environment: Windows XP Professional, JVM 1.5.0_09 Reporter: [EMAIL PROTECTED] Assigned To: Rob Davies Priority: Critical Fix For: 4.2.0 Using the store pending cursor, activemq.xml configured to use 200M of RAM and Kaha store. JVM started with options -Xms512M -Xmx512M -Xmn100M. Messages are 10KB in size, prefetch is default. I am seeing the memory usage immediately jump up really high (100) as soon as a durable consumer is activated when a large number of messages are waiting for that consumer. The producer hangs under this situation. If the consumer is killed before memory usage drops to normal, memory usage does not drop (i.e., the server locks forever). Sometimes, it is possible to exhaust the Java heap and actually crash the server. Here is the kind of things I'm seeing in the DEBUG log: 2006-11-19 13:51:53,046 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 10, to: 9 2006-11-19 13:51:53,046 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 9, to: 8 2006-11-19 13:51:53,046 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 8, to: 7 2006-11-19 13:51:53,046 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 7, to: 6 2006-11-19 13:51:53,046 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 6, to: 5 2006-11-19 13:51:53,062 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 5, to: 4 2006-11-19 13:51:53,062 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 4, to: 3 2006-11-19 13:51:53,062 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 3, to: 2 2006-11-19 13:51:53,062 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 2, to: 1 2006-11-19 13:51:53,062 [ata File Writer] DEBUG UsageManager - Memory usage change. from: 1, to: 0 2006-11-19 13:51:53,468 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 58, to: 59 2006-11-19 13:51:53,593 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 59, to: 60 2006-11-19 13:51:53,812 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 60, to: 61 2006-11-19 13:51:53,843 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 61, to: 62 2006-11-19 13:51:53,890 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 62, to: 63 2006-11-19 13:51:54,015 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 63, to: 64 2006-11-19 13:51:54,015 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 64, to: 65 2006-11-19 13:51:54,046 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 65, to: 66 2006-11-19 13:51:54,062 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 66, to: 67 2006-11-19 13:51:54,109 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 67, to: 68 2006-11-19 13:51:54,109 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 68, to: 69 2006-11-19 13:51:54,109 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 69, to: 70 2006-11-19 13:51:54,125 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 70, to: 71 2006-11-19 13:51:54,171 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 71, to: 72 2006-11-19 13:51:54,171 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 72, to: 73 2006-11-19 13:51:54,171 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 73, to: 74 2006-11-19 13:51:54,187 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 74, to: 75 2006-11-19 13:51:54,234 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 75, to: 76 2006-11-19 13:51:54,234 [/127.0.0.1:1999] DEBUG UsageManager - Memory usage change. from: 76, to: 77 2006-11-19 13:51:54,265
[jira] Resolved: (AMQ-1062) Closing consumer does not free server memory, server heap overflows
[ https://issues.apache.org/activemq/browse/AMQ-1062?page=all ] Rob Davies resolved AMQ-1062. - Resolution: Fixed SVN revision 478967. Closing consumer does not free server memory, server heap overflows --- Key: AMQ-1062 URL: https://issues.apache.org/activemq/browse/AMQ-1062 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 4.2.0 Environment: Windows XP Professional, Java HotSpot(TM) Client VM version 1.5.0_09-b01 Reporter: [EMAIL PROTECTED] Assigned To: Rob Davies Priority: Critical Fix For: 4.2.0 I am using the store durable pending cursor. Create a producer for a topic and let it run continuously for the remainder of the test. Create a durable consumer and kill it immediately. (So now messages are piling up for the consumer, but memory usage is low thanks to the store cursor.) Wait a few minutes. Now, start the same durable consumer again. Memory usage will increase considerably at this point (I get it around 20%). Now, stop the consumer. Memory usage DOES NOT go down. Now, reconnect the same durable consumer. It is possible to get a heap overrun that nukes the server! This is a problem when there are many consumers, and the general use case is that many of them are not active at the same time. I am classifying this as critical bug due to the heap overflow whenI try to reconnect, but it would be great if the memory usage went down as soon as disconnect. I image there may also be problems like this with queues, but did not test. 2006-11-19 17:24:20,015 [/127.0.0.1:3278] DEBUG PrefetchSubscription - Prefetch limit. 2006-11-19 17:24:21,281 [/127.0.0.1:3278] DEBUG Service - Error occured while processing sync command: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space -- 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: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37542 ] Guillaume Nodet commented on SM-745: I agree with the common shared class. Another thing which is specific to ActiveMQ, is the fact that queues are created dynamically. The jms / jca flows uses lots of different destinations ... and ActiveMQ does not need them to be created through an admin console. Allow usage of other JMS providers than ActiveMQ Key: SM-745 URL: https://issues.apache.org/activemq/browse/SM-745 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0.1 Reporter: Christian Schneider Fix For: 3.1 Attachments: jmsflow.patch, jmsflow.patch, jmsflow2.patch, jmsflow3.patch JMSFlow and JCA flow are too tightly bound to ActiveMQ. Instead of ActiveMQ specific classes jms Interfaces should be used where possible. I have attached a patch that replaces ActiveMQConnection and ActiveMQConnectionFactory by the jms equivalents. There is one possible issue with my patch. The getConnectionFactory now returns a ConnectionFactory instead of a ActiveMQConnectionFactory. I don´t know if any other part of the sources depends on the specific class. My patch is of course only the first step. The next could be having a specific subclass JMSFlowActiveMQ that does all stuff that is ActiveMQ specific. I will deliver a second patch for this. -- 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: (SM-756) The jms/jca consumer endpoint should be able to rollback transactions when an exchange with an ERROR status comes back
The jms/jca consumer endpoint should be able to rollback transactions when an exchange with an ERROR status comes back -- Key: SM-756 URL: https://issues.apache.org/activemq/browse/SM-756 Project: ServiceMix Issue Type: Improvement Components: servicemix-jms Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- 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: (SM-756) The jms/jca consumer endpoint should be able to rollback transactions when an exchange with an ERROR status comes back
[ https://issues.apache.org/activemq/browse/SM-756?page=all ] Guillaume Nodet resolved SM-756. Resolution: Fixed Author: gnodet Date: Fri Nov 24 00:23:58 2006 New Revision: 478801 URL: http://svn.apache.org/viewvc?view=revrev=478801 Log: SM-756: The jms/jca consumer endpoint should be able to rollback transactions when an exchange with an ERROR status comes back Modified: incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms/src/main/java/org/apache/servicemix/jms/JmsEndpoint.java incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms/src/main/java/org/apache/servicemix/jms/jca/JcaConsumerProcessor.java The jms/jca consumer endpoint should be able to rollback transactions when an exchange with an ERROR status comes back -- Key: SM-756 URL: https://issues.apache.org/activemq/browse/SM-756 Project: ServiceMix Issue Type: Improvement Components: servicemix-jms Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- 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: (SM-752) [patch] Content-Enricher Implementation
[ https://issues.apache.org/activemq/browse/SM-752?page=all ] Guillaume Nodet resolved SM-752. Fix Version/s: 3.1 Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Fri Nov 24 01:24:35 2006 New Revision: 478813 URL: http://svn.apache.org/viewvc?view=revrev=478813 Log: SM-752: Content-Enricher EIP pattern Patch submitted by Kristian Koehler, thx :) Added: incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/main/java/org/apache/servicemix/eip/patterns/ContentEnricher.java (with props) incubator/servicemix/trunk/deployables/serviceengines/servicemix-eip/src/test/java/org/apache/servicemix/eip/ContentEnricherTest.java (with props) [patch] Content-Enricher Implementation --- Key: SM-752 URL: https://issues.apache.org/activemq/browse/SM-752 Project: ServiceMix Issue Type: Improvement Components: servicemix-eip Affects Versions: incubation Reporter: Kristian Koehler Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: asf-licenced-patch.txt, patch.txt, site-patch.txt Hi this is a patch implementing the 'Content-Enricher' Pattern (http://www.enterpriseintegrationpatterns.com/DataEnricher.html). see also: http://www.nabble.com/-patch--Content-Enricher-for-ServiceMix-tf2677905s12049.html Kristian -- 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: (SM-751) Flow tracing with correlation id
[ https://issues.apache.org/activemq/browse/SM-751?page=all ] Guillaume Nodet resolved SM-751. Fix Version/s: 3.1 Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Fri Nov 24 01:42:46 2006 New Revision: 478816 URL: http://svn.apache.org/viewvc?view=revrev=478816 Log: SM-751: Flow tracing with correlation id. Patch provided by Gianfranco Boccalon Modified: incubator/servicemix/trunk/common/servicemix-common/src/main/java/org/apache/servicemix/common/AsyncBaseLifeCycle.java incubator/servicemix/trunk/core/servicemix-core/src/main/java/org/apache/servicemix/JbiConstants.java Author: gnodet Date: Fri Nov 24 01:46:45 2006 New Revision: 478818 URL: http://svn.apache.org/viewvc?view=revrev=478818 Log: SM-751: Flow tracing with correlation id. Patch provided by Gianfranco Boccalon Modified: incubator/servicemix/trunk/common/servicemix-components/src/main/java/org/apache/servicemix/components/drools/DroolsComponent.java Flow tracing with correlation id Key: SM-751 URL: https://issues.apache.org/activemq/browse/SM-751 Project: ServiceMix Issue Type: Improvement Reporter: Gianfranco Boccalon Assigned To: Guillaume Nodet Fix For: 3.1 Attachments: patch.zip, servicemix-components.zip Add the possibility to trace the flow of the messages inside a Service Assembly. For example, if we have a Service Assembly composed of three components, two binding components (call them BC1 and BC2) and a service engine (SE) organized in this sequence BC1-SE-BC2, we need to recognize that the output messages produced by the SE component are related to some messages provided by BC1. To do this, we need to add a process correlation id to the message exchanges and to modify the used components, to propagate this correlation id in all Message Exchanges sent. Enclosed there is the modified code for the following components: - HTTP binding component: here I added the code to generate the correlation Id and set it in the Message Exchange - Splitter - Router (the lightweight component) -- 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: (SM-745) Allow usage of other JMS providers than ActiveMQ
[ https://issues.apache.org/activemq/browse/SM-745?page=comments#action_37548 ] Christian Schneider commented on SM-745: Dynamic creation of queues is also possible in Tibco EMS so we should have no problem with this. I only wonder how security is achieved with dynamic queues. As far as I know everyone can listen and write to a dynamic queue. Can you tell me how the security in servicemix works. I have seen the authorization map is used to authorize users. But I have not yet understood how the authentication works. I know that you can use username/password to access the JMS server but how is this user token transported to the destination? Do I have to do anything special for Tibco EMS to achieve good authentication? Allow usage of other JMS providers than ActiveMQ Key: SM-745 URL: https://issues.apache.org/activemq/browse/SM-745 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.0.1 Reporter: Christian Schneider Fix For: 3.1 Attachments: jmsflow.patch, jmsflow.patch, jmsflow2.patch, jmsflow3.patch JMSFlow and JCA flow are too tightly bound to ActiveMQ. Instead of ActiveMQ specific classes jms Interfaces should be used where possible. I have attached a patch that replaces ActiveMQConnection and ActiveMQConnectionFactory by the jms equivalents. There is one possible issue with my patch. The getConnectionFactory now returns a ConnectionFactory instead of a ActiveMQConnectionFactory. I don´t know if any other part of the sources depends on the specific class. My patch is of course only the first step. The next could be having a specific subclass JMSFlowActiveMQ that does all stuff that is ActiveMQ specific. I will deliver a second patch for this. -- 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: (SM-757) Pipeline throws NPE when configured in synchronous mode and an exchange in ERROR status is received
Pipeline throws NPE when configured in synchronous mode and an exchange in ERROR status is received --- Key: SM-757 URL: https://issues.apache.org/activemq/browse/SM-757 Project: ServiceMix Issue Type: Bug Components: servicemix-eip Affects Versions: 3.0.1 Reporter: Guillaume Nodet Assigned To: Guillaume Nodet Fix For: 3.1 -- 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: (SM-758) JBoss Deployer 3.0 Snapshot classloading issues
JBoss Deployer 3.0 Snapshot classloading issues
---
Key: SM-758
URL: https://issues.apache.org/activemq/browse/SM-758
Project: ServiceMix
Issue Type: Bug
Components: tooling
Affects Versions: 3.0.1, 3.0
Environment: JBoss 4.02 , any System (tested on Windows XP)
Reporter: Alexis Kinsella
Fix For: 3.0.1, 3.0
Message From Forum:
Hello, I have noticed some problems related to classloading with jboss-deployer.
Due to the JBoss classloading mechanism (cf: UCL and loader-repositories), if
you install the sar, you can't anymore deploy any web application with spring
jar even if you use the default isolated Tomcat classloader mechanisms. To
resolve definitively the problem, the best bugfix is to create a
loader-repository for the servicemix jbi deployer sar and its JBI components
by affecting this newly defined loader-repository to it.
The loader-repository has to be defined in the jboss-service.xml from
servicemix-jboss-deployer and set the default java2ClassDelegation to true:
server
loader-repository
org.jboss:loader-repository=servicemix
loader-repository-configjava2ParentDelegation=true/loader-repository-config
/loader-repository
...
(Jboss wiki: http://www.jboss.org/wiki/Wiki.jsp?page=ClassLoadingConfiguration
and related pages)
java2ParentDelegation=true = to inherit from jboss server classloader et jboss
profile classloader and base service classloaders.
After it you have to modify the JBIDeployer to affect this loader-repository to
loader JBIComponents!
Examples can be found in EARDeployer.java (affect loader to DeployementInfo).
After thos modifications, servicemix jbi service is now really safely isolated,
and the global service loader-repository, is not pollued by servicemix jars
(like spring).
The reason of that problem is the Tomcat-service and so Webapps classloaders in
jboss inherit from the jboss profile classloader which is related to the
default laoder-repository in jboss. So, there is a problem if servicemix jbi
service or jbi components jar are deployed in the same loader-repository,
because, for example spring jar will be in the scope of the webapp
classloaders, but has not been loader directly by those classloader, the direct
consequency is that spring verify if some classes have been loader by the same
classloader and crash if it is not the case! (cf: example of namespace
handlers, when loading applicationContexts).
Sorry, for my bad explanations in english, if you want better explanations, I
can explain it in french eventually.
The main thing is that it is very impotant to isolate correctly servicemix
related classloaders in jboss, to avoid strange classloader issues in other
J2EE app deployed in JBoss by using correctly Jboss classloading mechanisms.
I have tested a working patch, and all works like a charm. If you prefer to
have a directly a patch(maybe some dirty code, due to some jboss and
servmicemix underknowledges), I can send it.
--
Bug Fixes:
1 - In POM.xml from jboss-deployer, add this to avoid many problems with class
no found exceptions when deploying -sm.xml files in JBoss :
!-- Added as dependency, needed by lw components, example: filebindings --
dependency
groupIdorg.apache.servicemix/groupId
artifactIdservicemix-components/artifactId
version3.0-incubating/version
/dependency
2 - In Jboss-service.xml, add loader-repository like this:
?xml version=1.0 encoding=UTF-8?
!-- The J2EE application client deployer service --
server
loader-repository
org.servicemix:loader-repository=JBIContainer
loader-repository-configjava2ParentDelegation=false/loader-repository-config
/loader-repository
mbean code=org.servicemix.jboss.deployment.JBIDeployer
name=org.servicemix:service=Deployer
depends
optional-attribute-name=JBIContainerorg.servicemix:service=JBIService/depends
/mbean
mbean code=org.servicemix.jboss.deployment.JBIService
name=org.servicemix:service=JBIService
dependsjboss:service=TransactionManager/depends
attribute name=TransactionManagerjava:/TransactionManager/attribute
/mbean
/server
In trunk there is a fault in actual jboss-service.xml : there is a token --
that should not be here!
3 - In JBIDeployer.java you should correct source like this:
/**
* Describe codeinit/code method here.
*
* @param di
*a codeDeploymentInfo/code value
* @exception DeploymentException
*if an error occurs
* @jmx.managed-operation
*/
public void init(DeploymentInfo di) throws DeploymentException {
try
{
log.info(Init ServiceMix JBI Component: +
[jira] Closed: (GERONIMO-2363) Console: create new pool using wizard, cannot use show plan button for any XA database, even derby
[ http://issues.apache.org/jira/browse/GERONIMO-2363?page=all ] Vamsavardhana Reddy closed GERONIMO-2363. - Fix Version/s: 1.2 2.0 Resolution: Fixed This must have been fixed in rev 478240 (trunk) and rev 478243 (branches\1.2) for javascript validation of input fields in edit Database pools. Console: create new pool using wizard, cannot use show plan button for any XA database, even derby Key: GERONIMO-2363 URL: http://issues.apache.org/jira/browse/GERONIMO-2363 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, databases Affects Versions: 1.1.1, 1.2 Reporter: Ted Kirby Fix For: 1.2, 2.0 Attachments: dbwizard_edit.jsp.patch From admin console, click Database Pools, Create new pool using the wizard, choose an XA database type. If you select any driver jars, or none and click show plan, you don't get a plan (all blank), but you do get this traceback in the log/ on the console: 13:48:53,552 ERROR [DatabasePoolPortlet] Unable to save connection pool java.lang.IllegalArgumentException: Invalid id: at org.apache.geronimo.kernel.repository.Artifact.create(Artifact.java:49) at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.save(DatabasePoolPortlet.java:899) at org.apache.geronimo.console.databasemanager.wizard.DatabasePoolPortlet.processAction(DatabasePoolPortlet.java:340) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) at org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:163) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at org.apache.pluto.portalImpl.Servlet.doPost(Servlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:52) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:342) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:31) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:419) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:667) at
[jira] Assigned: (AMQ-920) Two TCP connection requirement for bidirectional message flow ...
[ https://issues.apache.org/activemq/browse/AMQ-920?page=all ] Rob Davies reassigned AMQ-920: -- Assignee: Rob Davies Two TCP connection requirement for bidirectional message flow ... - Key: AMQ-920 URL: https://issues.apache.org/activemq/browse/AMQ-920 Project: ActiveMQ Issue Type: Improvement Components: Connector Reporter: Sridhar Komandur Assigned To: Rob Davies We noticed the following during our testing When a broker A establishes connection to broker B, the message flow is unidirectional from A to B. This is a an issue for us: For example, consider brokers associated with business critical services X and Y. There are many secondary services that either monitor/feed off of the messages coming from them. A FOO service would like to process messages going from X to Y. So in FOO's broker configuration we add X's name. However, messages are not going to flow from X to FOO, till X initiates a connection to FOO. It may not be desirable/possible to change business critical brokers' configuration for usage scenarios like this. TCP is bidirectional and asymmetry at connection establishment should not be translated to the higher level network connector. Is there a fundamental need/justification for this design that I may not be aware of ? Otherwise I would like to explore other design options. Thanks Regards - Sridhar Komandur -- 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-979) Allow NetworkConnections to bi-directional
[ https://issues.apache.org/activemq/browse/AMQ-979?page=all ] Rob Davies resolved AMQ-979. Resolution: Duplicate this is a duplicate of: https://issues.apache.org/activemq/browse/AMQ-920 Allow NetworkConnections to bi-directional -- Key: AMQ-979 URL: https://issues.apache.org/activemq/browse/AMQ-979 Project: ActiveMQ Issue Type: New Feature Components: Broker Reporter: Rob Davies Assigned To: Rob Davies Fix For: 4.2.0 Network connections are generally one way - with messages only flowing out from the broker that made the network connection. In order to support WAN hub/spoke - where the central broker is behind a firewall, and can only receive inbound connections, it is necessary to enable optional b-idirectional network connections. This issue was raised on the activemq-dev list: http://www.nabble.com/Having-some-trouble-making-a-simple-network...-tf2449661.html -- 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: (GERONIMO-2566) Creating new listeners for ActiveMQ from JMS Server portlet fails
[ http://issues.apache.org/jira/browse/GERONIMO-2566?page=all ] Vamsavardhana Reddy updated GERONIMO-2566: -- Fix Version/s: 2.0 Assignee: Vamsavardhana Reddy Creating new listeners for ActiveMQ from JMS Server portlet fails - Key: GERONIMO-2566 URL: http://issues.apache.org/jira/browse/GERONIMO-2566 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Environment: sun java 1.5 Reporter: Paul McMahan Assigned To: Vamsavardhana Reddy Fix For: 1.2, 2.0 From the JMS Server portlet click Add new tcp listener. Provide name, host, and port. Click 'save'. The following stacktrace appears in the command window: 16:13:32,703 ERROR [JMSConnectorPortlet] Unable to process portlet action java.lang.NoClassDefFoundError: org/apache/activemq/broker/BrokerService at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2365) at java.lang.Class.getDeclaredMethods(Class.java:1763) at net.sf.cglib.core.ReflectUtils.addAllMethods(ReflectUtils.java:348) at net.sf.cglib.proxy.Enhancer.getMethods(Enhancer.java:426) at net.sf.cglib.proxy.Enhancer.generateClass(Enhancer.java:456) at net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorS trategy.java:25) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerato r.java:216) at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377) at net.sf.cglib.proxy.Enhancer.createClass(Enhancer.java:317) at org.apache.geronimo.kernel.basic.BasicProxyManager$ManagedProxyFactor y.init(BasicProxyManager.java:202) at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxyFactory (BasicProxyManager.java:78) at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicP roxyManager.java:116) at org.apache.geronimo.console.util.KernelManagementHelper.getObject(Ker nelManagementHelper.java:368) at org.apache.geronimo.console.util.PortletManager.getJMSBroker(PortletM anager.java:274) at org.apache.geronimo.console.util.PortletManager.createJMSConnector(Po rtletManager.java:278) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.pro cessAction(JMSConnectorPortlet.java:80) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229 ) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvoke rImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvoke rImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletCon tainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processP ortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSu bjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica torBase.java:524) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve. invoke(GeronimoStandardContext.java:326) at
[jira] Closed: (GERONIMO-2566) Creating new listeners for ActiveMQ from JMS Server portlet fails
[ http://issues.apache.org/jira/browse/GERONIMO-2566?page=all ] Vamsavardhana Reddy closed GERONIMO-2566. - Resolution: Fixed ClassNotFoundException is due to the classLoader in which the proxy is loaded. Once this is fixed, further investigation revealed problems in ActiveMQManagerGBean and TransportConnectorGBeanImpl. Fixed in rev 478875 (trunk) and rev 478878 (branches\1.2). Creating new listeners for ActiveMQ from JMS Server portlet fails - Key: GERONIMO-2566 URL: http://issues.apache.org/jira/browse/GERONIMO-2566 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 1.2 Environment: sun java 1.5 Reporter: Paul McMahan Assigned To: Vamsavardhana Reddy Fix For: 1.2, 2.0 From the JMS Server portlet click Add new tcp listener. Provide name, host, and port. Click 'save'. The following stacktrace appears in the command window: 16:13:32,703 ERROR [JMSConnectorPortlet] Unable to process portlet action java.lang.NoClassDefFoundError: org/apache/activemq/broker/BrokerService at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2365) at java.lang.Class.getDeclaredMethods(Class.java:1763) at net.sf.cglib.core.ReflectUtils.addAllMethods(ReflectUtils.java:348) at net.sf.cglib.proxy.Enhancer.getMethods(Enhancer.java:426) at net.sf.cglib.proxy.Enhancer.generateClass(Enhancer.java:456) at net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorS trategy.java:25) at net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerato r.java:216) at net.sf.cglib.proxy.Enhancer.createHelper(Enhancer.java:377) at net.sf.cglib.proxy.Enhancer.createClass(Enhancer.java:317) at org.apache.geronimo.kernel.basic.BasicProxyManager$ManagedProxyFactor y.init(BasicProxyManager.java:202) at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxyFactory (BasicProxyManager.java:78) at org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicP roxyManager.java:116) at org.apache.geronimo.console.util.KernelManagementHelper.getObject(Ker nelManagementHelper.java:368) at org.apache.geronimo.console.util.PortletManager.getJMSBroker(PortletM anager.java:274) at org.apache.geronimo.console.util.PortletManager.createJMSConnector(Po rtletManager.java:278) at org.apache.geronimo.console.jmsmanager.server.JMSConnectorPortlet.pro cessAction(JMSConnectorPortlet.java:80) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229 ) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:574) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:499) at org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvoke rImpl.java:120) at org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvoke rImpl.java:68) at org.apache.pluto.PortletContainerImpl.processPortletAction(PortletCon tainerImpl.java:164) at org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processP ortletAction(PortletContainerWrapperImpl.java:82) at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:178) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSu bjectValve.java:56) at
[jira] Created: (GERONIMO-2595) Hardcoded MX4J logger in org.apache.geronimo.kernel.log.GeronimoLogging class
Hardcoded MX4J logger in org.apache.geronimo.kernel.log.GeronimoLogging class
-
Key: GERONIMO-2595
URL: http://issues.apache.org/jira/browse/GERONIMO-2595
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Logging
Affects Versions: 1.2
Reporter: Nellya Udovichenko
Description: MX4J logger class (mx4j.log.CommonsLogger) is hardcoded in
org.apache.geronimo.kernel.log.GeronimoLogging:
...
Class clazz = Class.forName(mx4j.log.Log);
Class paramClazz = Class.forName(mx4j.log.Logger);
Method method = clazz.getDeclaredMethod(redirectTo, new Class[]
{paramClazz});
paramClazz = Class.forName(mx4j.log.CommonsLogger);
method.invoke(null, new Object[] {paramClazz.newInstance()});
...
So you can't have another logger class instead of default one.
If you use JDK with mx4j.jar in bootclasspath (Apache Harmony, for example),
mx4j can't access commons-logging.jar
that is only available in classpath, so Geronimo doesn't start and
NoClassDefFoundError exception occurs.
And there's no way to replace mx4j.log.CommonsLogger with another logger.
Looks like there're two ways to resolve this problem:
1. Comment the code above and use the existing mechanism in mx4j to set the
property 'mx4j.log.prototype' from the command line.
2. Add the property to xml file (pom.xml?), and use 'mx4j.log.CommonsLogger' as
default value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
