[jira] Commented: (SM-847) Old version of xml-apis in distribution
[ https://issues.apache.org/activemq/browse/SM-847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38539 ] Guillaume Nodet commented on SM-847: Is this is a problem for JDK 1.4 compat ? If yes, it should also be fixed in 3.1.1 imo. Old version of xml-apis in distribution --- Key: SM-847 URL: https://issues.apache.org/activemq/browse/SM-847 Project: ServiceMix Issue Type: Bug Components: servicemix-assembly Affects Versions: 3.1 Reporter: Juergen Mayrbaeurl Fix For: 3.2 In the ServiceMix 3.1 distribution (lib folder) a very old version (1.0b2) of xml-apis is included. Replace it with version 1.3.03 or higher -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-846) Call to default constructor of JBIContainer changes log4j log level
[ https://issues.apache.org/activemq/browse/SM-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38541 ] Guillaume Nodet commented on SM-846: Philip, Is the IdGenerator the only issue ? I still don't understand why / how servicemix could change the log4j level ... What's the way to reproduce the problem ? Call to default constructor of JBIContainer changes log4j log level --- Key: SM-846 URL: https://issues.apache.org/activemq/browse/SM-846 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0 Environment: Windows XP Professional, java version 1.5.0_09, JUnit 4.1 Reporter: Philipp Rossmanith Priority: Minor A call to the default constructor of org.apache.servicemix.jbi.container.JBIContainer sets the log4j log level to ERROR. See http://www.nabble.com/Default-constructor-for-JBIContainer-changes-log-level--tf3235243s12049.html Can be observed in org.apache.servicemix.jbi.security.SecuredBrokerTest, line 63: jbi = new JBIContainer(); JBIContainer doesn't seem to use org.apache.log4j, but makes calls to org.apache.commons.logging.Log and org.apache.commons.logging.LogFactory: private static final Log log = LogFactory.getLog(JBIContainer.class); ... as well as to java.util.logging.Logger: public Logger getLogger(String suffix, String resourceBundleName) throws MissingResourceException, JBIException commons-logging is configured in ServiceMix. Which in turns, starts log4j if included in the classpath. It seems that org.apache.servicemix.id.IdGenerator calls the java.util.logging package. This is the only call afaik and it should be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-847) Old version of xml-apis in distribution
[ https://issues.apache.org/activemq/browse/SM-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-847. Resolution: Fixed Fix Version/s: 3.1.1 Assignee: Guillaume Nodet URL: http://svn.apache.org/viewvc?view=revrev=508539 URL: http://svn.apache.org/viewvc?view=revrev=508540 Old version of xml-apis in distribution --- Key: SM-847 URL: https://issues.apache.org/activemq/browse/SM-847 Project: ServiceMix Issue Type: Bug Components: servicemix-assembly Affects Versions: 3.1 Reporter: Juergen Mayrbaeurl Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 In the ServiceMix 3.1 distribution (lib folder) a very old version (1.0b2) of xml-apis is included. Replace it with version 1.3.03 or higher -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-850) Error starting ServiceMix on AIX
[ https://issues.apache.org/activemq/browse/SM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen updated SM-850: --- Attachment: SM-850.patch Error starting ServiceMix on AIX Key: SM-850 URL: https://issues.apache.org/activemq/browse/SM-850 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Gert Vanthienen Fix For: 3.1.1 Attachments: SM-850.patch After adding support for OS/400 to ServiceMix's startup script, the script no longer worked correctly for AIX. See also: http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SM-850) Error starting ServiceMix on AIX
[ https://issues.apache.org/activemq/browse/SM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38543 ] Gert Vanthienen commented on SM-850: The current script doesn't work correctly on AIX because: - the JVM on AIX was not correctly identified as an IBM JVM - the option -Xverify:none was not set for AIX, while it is required This patch file contains a fix for the startup script to solve both problems. Error starting ServiceMix on AIX Key: SM-850 URL: https://issues.apache.org/activemq/browse/SM-850 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Gert Vanthienen Fix For: 3.1.1 Attachments: SM-850.patch After adding support for OS/400 to ServiceMix's startup script, the script no longer worked correctly for AIX. See also: http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SM-848) ServiceMix 3.x with Java 1.4.x
[ https://issues.apache.org/activemq/browse/SM-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated SM-848: --- Fix Version/s: (was: 3.2) 3.1.1 ServiceMix 3.x with Java 1.4.x -- Key: SM-848 URL: https://issues.apache.org/activemq/browse/SM-848 Project: ServiceMix Issue Type: Improvement Affects Versions: 3.1 Environment: Java Runtime Environment 1.4.x Reporter: Juergen Mayrbaeurl Fix For: 3.1.1 Since ServiceMix 3.1 can only be used with Java 5 or higher, rework it to make it Java 1.4.x compatible -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-846) Call to default constructor of JBIContainer changes log4j log level
[ https://issues.apache.org/activemq/browse/SM-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-846. Resolution: Fixed Fix Version/s: 3.2 3.1.1 Assignee: Guillaume Nodet URL: http://svn.apache.org/viewvc?view=revrev=508541 URL: http://svn.apache.org/viewvc?view=revrev=508544 Call to default constructor of JBIContainer changes log4j log level --- Key: SM-846 URL: https://issues.apache.org/activemq/browse/SM-846 Project: ServiceMix Issue Type: Bug Affects Versions: 3.0 Environment: Windows XP Professional, java version 1.5.0_09, JUnit 4.1 Reporter: Philipp Rossmanith Assigned To: Guillaume Nodet Priority: Minor Fix For: 3.1.1, 3.2 A call to the default constructor of org.apache.servicemix.jbi.container.JBIContainer sets the log4j log level to ERROR. See http://www.nabble.com/Default-constructor-for-JBIContainer-changes-log-level--tf3235243s12049.html Can be observed in org.apache.servicemix.jbi.security.SecuredBrokerTest, line 63: jbi = new JBIContainer(); JBIContainer doesn't seem to use org.apache.log4j, but makes calls to org.apache.commons.logging.Log and org.apache.commons.logging.LogFactory: private static final Log log = LogFactory.getLog(JBIContainer.class); ... as well as to java.util.logging.Logger: public Logger getLogger(String suffix, String resourceBundleName) throws MissingResourceException, JBIException commons-logging is configured in ServiceMix. Which in turns, starts log4j if included in the classpath. It seems that org.apache.servicemix.id.IdGenerator calls the java.util.logging package. This is the only call afaik and it should be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SM-850) Error starting ServiceMix on AIX
[ https://issues.apache.org/activemq/browse/SM-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved SM-850. Resolution: Fixed Fix Version/s: 3.2 Assignee: Guillaume Nodet Thanks a lot Gert to have taken care of that :-) URL: http://svn.apache.org/viewvc?view=revrev=508547 URL: http://svn.apache.org/viewvc?view=revrev=508550 Error starting ServiceMix on AIX Key: SM-850 URL: https://issues.apache.org/activemq/browse/SM-850 Project: ServiceMix Issue Type: Bug Components: servicemix-core Affects Versions: 3.1 Reporter: Gert Vanthienen Assigned To: Guillaume Nodet Fix For: 3.1.1, 3.2 Attachments: SM-850.patch After adding support for OS/400 to ServiceMix's startup script, the script no longer worked correctly for AIX. See also: http://www.nabble.com/Can%27t-start-on-aix-tf3056948s12049.html#a8985397 (sorry, mail-archives.apache.org seems to be down for the moment) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Useing shared libraries from service units
Hi Juergen and all ! Starting this thread on dev list ... Not sure exactly what the best way would be, but I see several ways: * enhance the classpath / feature to reference SL somehow * use the jbi descriptor somehow, as done for components I haven't thought about it a lot yet. So any idea is welcome ... -- Cheers, Guillaume Nodet Architect, LogicBlaze (http://www.logicblaze.com/) Blog: http://gnodet.blogspot.com/
