Re: Openejb and port 1099
Kevan, Thanks again! The information you provided saved me a lot of time.. I found that ManagementContext [1] is using ConnectorPort set to 1099. Should we wrap this in a GBean to be able configure this port? [1] https://svn.apache.org/repos/asf/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/broker/jmx/ManagementContext.java Thanks Anita --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Apr 13, 2007, at 11:59 AM, Anita Kulshreshtha wrote: > > > David B, > >The activemq-core jar is being used by openejb-activemq. I > > looked at > > BrokerServer, but nothing jumped at me.. Any help will be greatly > > appreciated. > > Anita, it's the ActiveMQ GBean that's being started. It's being > created during the start of the OpenEJB module, but it's just a > dependency. OpenEJB isn't doing anything directly... > > FYI, here's a stack trace: > > Thread [main] (Suspended (breakpoint at line 382 in > ManagementContext)) > ManagementContext.createConnector(MBeanServer) line: 382 > ManagementContext.findMBeanServer() line: 301 > ManagementContext.getMBeanServer() line: 154 > ManagementContext.start() line: 78 > BrokerService.start() line: 391 > BrokerServiceGBeanImpl.doStart() line: 95 > GBeanInstance.createInstance() line: 986 > GBeanInstanceState.attemptFullStart() line: 267 > GBeanInstanceState.start() line: 102 > GBeanInstance.start() line: 529 > GBeanDependency.attemptFullStart() line: 111 > GBeanDependency.addTarget(AbstractName) line: 146 > ... > > Not sure if (or how) the ManagementContext behavior can be altered... > > Can I assume you'll look into this? :-) > > --kevan > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[jira] Updated: (GERONIMO-3019) Remove JAXB dependencies from Axis2 JAXWS
[ https://issues.apache.org/jira/browse/GERONIMO-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lasantha Ranaweera updated GERONIMO-3019: - Attachment: G3019-2.patch It is unnecessary to keep generating JAXB files for the test cases. Also some of the dependencies are not necessary too. Thanks, Lasantha > Remove JAXB dependencies from Axis2 JAXWS > - > > Key: GERONIMO-3019 > URL: https://issues.apache.org/jira/browse/GERONIMO-3019 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: webservices > Environment: Linux >Reporter: Lasantha Ranaweera > Attachments: G3019-2.patch, GERONIMO-3019.patch > > > As Axis2 moves with XBeans it is unnecessary to keep dependencies with JAXB > related stuff. Also JAXB related code generation has been removed from the > test cases too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3081) javax.annotation.security annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMO-3081: Attachment: GERONIMO-3081-2.patch Patch #2 with the cleanup as recommended by David Jencks > javax.annotation.security annotation support > > > Key: GERONIMO-3081 > URL: https://issues.apache.org/jira/browse/GERONIMO-3081 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Tim McConnell > Assigned To: Tim McConnell > Attachments: GERONIMO-3081-2.patch, GERONIMO-3081.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Geronimo Board Report for 1Q 2007
Here is a link to our Wiki with the report: http://cwiki.apache.org/ GMOxPMGT/apache-geronimo-board-report-2007-04-april.html For posterity the text is included below: Apache Geronimo Board Report for 1Q 2007 The Apache Geronimo Project has been mostly focusing on achieving Java EE 5 functionality for its 2.0 release. We have been refining our release procedures and as a result have been fairly consistent at releasing monthly Milestones to make our work in progress available to users. Version 1.2 is nearing its readiness to release but has been delayed due to external dependencies that have not been fulfilled. Collaboration with several other projects in Apache is going on which includes Axis 2, OpenJPA, OpenEJB, CXF and Yoko. Releases * Geronimo 2.0-M2 and 2.0-M3 were released in January and February respectively. Continuing the "Drive to 5" and hope to have a developer release by May. * Geronimo Javamail New release of the javamail jars were released. The new versions are geronimo-javamail_1.3.1_mail-1.1, geronimo- javamail_1.3.1_provider-1.1, and geronimo-javamail_1.3.1_spec-1.3. Devtools Xbean Website Migrated the authoring of the website to Confluence. GMOxSITE space can be updated by Geronimo committers only and uses autoexport plugin to create the HTML version that is served from minotaur. Some content on the website such as plugin repo lists, schemas, images are still maintained via the original svn repo. JUGs and Conferences * Apache Geronimo v2 - a Java EE 5 application server by Jacek Laskowski at Studencki Festiwal Informatyczny (SFI) - Krakow, Poland March 8-10, 2007 * More, faster, easier with Java EE 5 and Apache Geronimo v2 by Jacek Laskowski at Software Development GigaCon 2007 - Warszawa, Poland, March 22-23, 2007 Policy Changes * TCK Access The PMC approved a policy allowing read access to our TCK framework for any Apache committer that has signed the NDA for access to the Sun TCK. There is a 72-hour waiting period for non-Geronimo committers so the PMC membership can comment. Non-committers are granted read-only access (and can earn karma) while Geronimo committers are granted Read / Write access. Subprojects * DayTrader Currently working on development to provide an EJB 3.0 version of this benchmark * DevTools * XBean Community New Committers: * Jarek Gawor * Rakesh Midha * Donald Woods PMC Additions: * Prasad Kashyap * Dain Sundstrom
[jira] Closed: (GERONIMO-3095) Eclipse plugin conflict with Websphere Community Edition
[ https://issues.apache.org/jira/browse/GERONIMO-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods closed GERONIMO-3095. -- Resolution: Invalid This is a known limitation that has been there since day one for WASCE and we will not be fixing it in the 1.1 or 2.0 releases. The WASCE version extends the Geronimo plugin and we change names and graphics to match our offering. Please discuss WASCE related topics on our Forum at - http://www-128.ibm.com/developerworks/forums/dw_forum.jsp?forum=541&cat=51 > Eclipse plugin conflict with Websphere Community Edition > > > Key: GERONIMO-3095 > URL: https://issues.apache.org/jira/browse/GERONIMO-3095 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: eclipse-plugin >Affects Versions: 1.1.1 > Environment: Windows XP, Eclipse 3.2.2 >Reporter: Bruno Melloni >Priority: Minor > > Discovered it trying to compare Geronimo with Websphere Community Edition > (Geronimo with supposedly improved management screens and labeled as > Websphere). > Steps: > - Open Eclipse 3.2.2 > - Go to Servers view > - Install new server support - for Geronimo and for Websphere Community > Edition. > - Both "appear to install". > - If attempt to install both without Eclipse restart after each, the first > one *does not* show in the list of servers nor in the list of server plugins > available for download (From a fresh Eclipse install, I used Geronimo as the > first server and Websphere CE as the second - no sign of Geronimo afterwards > in the list of servers or available server plugin downloads). > - If restart after each install, only the first one installed shows in the > Server list afterwards, the second one shows in list of server plugins > available for download, but the install fails with "Error occurred installing > server: Could not download and install update feature." (From another fresh > Eclipse install I again used Geronimo as the first server and Websphere CE as > the second one - in this case Websphere CE does not show in the list of > servers). > I suspect that the problem is caused by IBM failing to clearly differentiate > its plugin from the Apache-distributed Geronimo plugin thus confusing > Eclipse, but it can still give the impression that Geronimo is at fault and > might be worth investigating and maybe requiring IBM (and future > Geronimo-based plugins from other vendors) to do a better job. > Workaround: > - Use two separate installs of Eclipse, one with Geronimo and one with > Websphere. Very annoying, but functional. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2964) Cannot specify the Tomcat work directory for a web application
[ https://issues.apache.org/jira/browse/GERONIMO-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Donald Woods updated GERONIMO-2964: --- Affects Version/s: 2.0-M5 > Cannot specify the Tomcat work directory for a web application > -- > > Key: GERONIMO-2964 > URL: https://issues.apache.org/jira/browse/GERONIMO-2964 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: Tomcat >Affects Versions: 1.2, 2.0-M5 >Reporter: Aman Nanner >Priority: Minor > Fix For: 1.2 > > Attachments: tomcat-config-workdir.patch, tomcat-workdir.patch > > > In Tomcat, a work directory can be specified for a web application in a > WEB-INF/context.xml file. The GeronimoStandardContext does not permit the > user to specify a work directory, and so the work directory defaults to > var/catalina/work/. > I've submitted a patch file that modifies the geronimo-tomcat-1.2 schema to > permit the user to optionally specify a work directory. This work directory > is then propagated into the TomcatContext. I've tested this and it seems to > work well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Openejb and port 1099
On Apr 13, 2007, at 11:59 AM, Anita Kulshreshtha wrote: David B, The activemq-core jar is being used by openejb-activemq. I looked at BrokerServer, but nothing jumped at me.. Any help will be greatly appreciated. Anita, it's the ActiveMQ GBean that's being started. It's being created during the start of the OpenEJB module, but it's just a dependency. OpenEJB isn't doing anything directly... FYI, here's a stack trace: Thread [main] (Suspended (breakpoint at line 382 in ManagementContext)) ManagementContext.createConnector(MBeanServer) line: 382 ManagementContext.findMBeanServer() line: 301 ManagementContext.getMBeanServer() line: 154 ManagementContext.start() line: 78 BrokerService.start() line: 391 BrokerServiceGBeanImpl.doStart() line: 95 GBeanInstance.createInstance() line: 986 GBeanInstanceState.attemptFullStart() line: 267 GBeanInstanceState.start() line: 102 GBeanInstance.start() line: 529 GBeanDependency.attemptFullStart() line: 111 GBeanDependency.addTarget(AbstractName) line: 146 ... Not sure if (or how) the ManagementContext behavior can be altered... Can I assume you'll look into this? :-) --kevan
[jira] Commented: (GERONIMO-3081) javax.annotation.security annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488705 ] Tim McConnell commented on GERONIMO-3081: - Good suggestions David, I'll make them today. Thanks much > javax.annotation.security annotation support > > > Key: GERONIMO-3081 > URL: https://issues.apache.org/jira/browse/GERONIMO-3081 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Tim McConnell > Assigned To: Tim McConnell > Attachments: GERONIMO-3081.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
corba :: builder Build Failure
Trying to build Geronimo from scratch. Fails on building CORBA Builder
module, with following trace, any ideas:
---
[INFO] Building Geronimo :: CORBA :: Builder
[INFO]task-segment: [install]
[INFO]
-
---
[INFO] [enforcer:enforce {execution: default}]
[INFO] snapshot org.apache.geronimo.modules:geronimo-corba:2.0-SNAPSHOT:checkin
g for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-corba:2.0-SNAPSHOT:checkin
g for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-corba:2.0-SNAPSHOT:checkin
g for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-timer:2.0-SNAPSHOT:checkin
g for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-timer:2.0-SNAPSHOT:checkin
g for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.modules:geronimo-timer:2.0-SNAPSHOT:checkin
g for updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.0-SNAPSHO
T: checking for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.0-SNAPSHO
T: checking for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-openejb-builder:2.0-SNAPSHO
T: checking for updates from apache.snapshots
Downloading:
http://tomcat.apache.org/dev/dist/m2-repository/axis/axis-jaxrpc/1.
4/axis-jaxrpc-1.4.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//axis/axis-j
axrpc/1.4/axis-jaxrpc-1.4.pom
Downloading:
http://repo1.maven.org/maven2/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.
pom
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 4.844 seconds
Time to generate code: 0.547 seconds
error: error reading
C:\.m2\org\apache\openejb\container\3.0-incubating-SNAPSHOT
\container-3.0-incubating-SNAPSHOT.pom; error in opening zip file
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
1 error
BUILD FAILED
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] XmlBeans compile failed:
xml ErrorLoading schema file
C:\geronimo-dev\server\modules\geronimo-corba-buil
der\src\main\schema\corba-css-config-2.1.xsd
xml ErrorLoading schema file
C:\geronimo-dev\server\modules\geronimo-corba-build
er\src\main\schema\corba-tss-config-2.1.xsd
xml ErrorLoading config file
C:\geronimo-dev\server\modules\geronimo-corba-build
er\src\main\schema\xmlconfig.xml
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 30 seconds
[INFO] Finished at: Fri Apr 13 11:07:58 CDT 2007
[INFO] Final Memory: 30M/56M
[INFO]
Re: Openejb and port 1099
David B, The activemq-core jar is being used by openejb-activemq. I looked at BrokerServer, but nothing jumped at me.. Any help will be greatly appreciated. Thanks Anita --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Apr 13, 2007, at 8:37 AM, Anita Kulshreshtha wrote: > > >I am trying to find why port 1099 appears to be hardcoded. This > > message is generated by running two instances of G: > > 1. instance1 uses 1099 for rmi NamingPort > > 2. instance2 uses 1108 > >Both server start fine and have functioning console. JMXService > is > > running correctly. > > > > message from instance2: > > > > .. > > Module 4/30 > org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/ > > car > > started in .531s > > Module 5/30 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car > > 08:03:16,703 WARN [ManagementContext] Failed to start jmx > > connector: Cannot > > bind to URL [rmi://localhost:1099/jmxrmi]: > > javax.naming.NameAlreadyBoundExcepti > > on: jmxrmi [Root exception is java.rmi.AlreadyBoundException: > jmxrmi] > > started in 13.579s > > .. > > > > Could someone please point me to the source of this message? > > Hi Anita, > It's ActiveMQ -- activemq-4.1.1/activemq-core/src/main/java/org/ > apache/activemq/broker/jmx/ManagementContext.java > > --kevan > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Openejb and port 1099
Thanks Kevan! Anita --- Kevan Miller <[EMAIL PROTECTED]> wrote: > > On Apr 13, 2007, at 8:37 AM, Anita Kulshreshtha wrote: > > >I am trying to find why port 1099 appears to be hardcoded. This > > message is generated by running two instances of G: > > 1. instance1 uses 1099 for rmi NamingPort > > 2. instance2 uses 1108 > >Both server start fine and have functioning console. JMXService > is > > running correctly. > > > > message from instance2: > > > > .. > > Module 4/30 > org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/ > > car > > started in .531s > > Module 5/30 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car > > 08:03:16,703 WARN [ManagementContext] Failed to start jmx > > connector: Cannot > > bind to URL [rmi://localhost:1099/jmxrmi]: > > javax.naming.NameAlreadyBoundExcepti > > on: jmxrmi [Root exception is java.rmi.AlreadyBoundException: > jmxrmi] > > started in 13.579s > > .. > > > > Could someone please point me to the source of this message? > > Hi Anita, > It's ActiveMQ -- activemq-4.1.1/activemq-core/src/main/java/org/ > apache/activemq/broker/jmx/ManagementContext.java > > --kevan > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Openejb and port 1099
On Apr 13, 2007, at 8:37 AM, Anita Kulshreshtha wrote: I am trying to find why port 1099 appears to be hardcoded. This message is generated by running two instances of G: 1. instance1 uses 1099 for rmi NamingPort 2. instance2 uses 1108 Both server start fine and have functioning console. JMXService is running correctly. message from instance2: .. Module 4/30 org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/ car started in .531s Module 5/30 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car 08:03:16,703 WARN [ManagementContext] Failed to start jmx connector: Cannot bind to URL [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundExcepti on: jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi] started in 13.579s .. Could someone please point me to the source of this message? Hi Anita, It's ActiveMQ -- activemq-4.1.1/activemq-core/src/main/java/org/ apache/activemq/broker/jmx/ManagementContext.java --kevan
[jira] Commented: (GERONIMO-3081) javax.annotation.security annotation support
[ https://issues.apache.org/jira/browse/GERONIMO-3081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488690 ] David Jencks commented on GERONIMO-3081: Applied in rev 528505. However, I wonder if you would consider whether it would be cleaner to have an additional interface for the getServlets[] and addServlet method. In fact I think passing WebAppType in directly might be reasonable since this is only for servlets. > javax.annotation.security annotation support > > > Key: GERONIMO-3081 > URL: https://issues.apache.org/jira/browse/GERONIMO-3081 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Tim McConnell > Assigned To: Tim McConnell > Attachments: GERONIMO-3081.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3007) JSP MBE should not create temporary files when scanning for TLD files
[ https://issues.apache.org/jira/browse/GERONIMO-3007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-3007. -- Resolution: Fixed Fix Version/s: 2.0-M5 Applied in rev 528503, thanks! > JSP MBE should not create temporary files when scanning for TLD files > - > > Key: GERONIMO-3007 > URL: https://issues.apache.org/jira/browse/GERONIMO-3007 > Project: Geronimo > Issue Type: Sub-task > Security Level: public(Regular issues) >Reporter: Tim McConnell > Assigned To: Tim McConnell > Fix For: 2.0-M5 > > Attachments: GERONIMO-3007.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-2864) JAX-RPC app client error
[ https://issues.apache.org/jira/browse/GERONIMO-2864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-2864. --- Resolution: Fixed Closing as this was fixed a while back. > JAX-RPC app client error > > > Key: GERONIMO-2864 > URL: https://issues.apache.org/jira/browse/GERONIMO-2864 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: webservices >Reporter: Jarek Gawor > Attachments: GERONIMO-2864.patch > > > JAX-RPC app client can fail with ClassNotFoundException wsdl4j class. The > attached patch adds wsdl4j.jar dependency to the app client. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3075) LocalAttributeManager parse error during startup.
[ https://issues.apache.org/jira/browse/GERONIMO-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488668 ] Don Hill commented on GERONIMO-3075: This issue is also happening in 1.2 beta so i would assume that it has been around for a while, in my case I am using a usr for the data source as jdbc:mysql://localhost:3306/db?useUnicode=true&characterEncoding=utf8&connectionCollation=utf8_bin What is happening is that when this element is read from the config.xml the & is unencoded to & so in the writeXml method a parse error happens when trying to create an element from this string value jdbc:mysql://localhost:3306/db?useUnicode=true&characterEncoding=utf8&connectionCollation=utf8_bin Patch to follow. > LocalAttributeManager parse error during startup. > - > > Key: GERONIMO-3075 > URL: https://issues.apache.org/jira/browse/GERONIMO-3075 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: startup/shutdown >Affects Versions: 2.0-M4 > Environment: Linux 2.6.17-11-386 (ubuntu) > java version "1.5.0_08" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) > Java HotSpot(TM) Client VM (build 1.5.0_08-b03, mixed mode, sharing) >Reporter: Bill Brown >Priority: Minor > > Greetings: > I'm getting this parse error sprinkeled several times during startup while > tailing the geronimo.log file with the unofficial 2.0M4 build. I do not know > what negative effect it has on the running system. > 20:32:52,340 ERROR [LocalAttributeManager] Error occurred during execution of > attributeChanged TimerTask > java.lang.RuntimeException: Failed to write attribute value fragment: The > reference to entity "password" must end with the ';' delimiter. > at > org.apache.geronimo.system.configuration.GBeanOverride.writeXml(GBeanOverride.java:542) > at > org.apache.geronimo.system.configuration.ConfigurationOverride.writeXml(ConfigurationOverride.java:155) > at > org.apache.geronimo.system.configuration.ServerOverride.writeXml(ServerOverride.java:108) > at > org.apache.geronimo.system.configuration.LocalAttributeManager.saveXmlToFile(LocalAttributeManager.java:416) > at > org.apache.geronimo.system.configuration.LocalAttributeManager.save(LocalAttributeManager.java:382) > at > org.apache.geronimo.system.configuration.LocalAttributeManager$2.run(LocalAttributeManager.java:600) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > Caused by: org.xml.sax.SAXParseException: The reference to entity "password" > must end with the ';' delimiter. > at > com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264) > at > com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) > at > org.apache.geronimo.system.configuration.GBeanOverride.writeXml(GBeanOverride.java:529) > ... 7 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
axis2 test failure
--- T E S T S --- Running org.apache.geronimo.axis2.Axis2HandlerResolverTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.859 sec Running org.apache.geronimo.axis2.Axis2WebServiceContainerTest java.lang.ExceptionInInitializerError at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:555) at org.apache.axis2.deployment.DescriptionBuilder.buildOM (DescriptionBuilder.java:94) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig (AxisConfigBuilder.java:76) at org.apache.axis2.context.ConfigurationContextFactory.createDefaultConfig urationContext(ConfigurationContextFactory.java:270) at org.apache.geronimo.axis2.Axis2WebServiceContainer. (Axis2WebServiceContainer.java:109) at org.apache.geronimo.axis2.pojo.POJOWebServiceContainer. (POJOWebServiceContainer.java:61) at org.apache.geronimo.axis2.Axis2WebServiceContainerTest.invokeWithWSDL (Axis2WebServiceContainerTest.java:144) at org.apache.geronimo.axis2.Axis2WebServiceContainerTest.testInvokeWithWSD L(Axis2WebServiceContainerTest.java:49) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.junit.JUnitTestSet.execute (JUnitTestSet.java:210) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSe t(AbstractDirectoryTestSuite.java:135) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute (AbstractDirectoryTestSuite.java:122) at org.apache.maven.surefire.Surefire.run(Surefire.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess (SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main (SurefireBooter.java:747) Caused by: java.lang.IllegalStateException: No valid ObjectCreator found. at org.apache.axiom.om.util.StAXUtils$Pool. (StAXUtils.java:42) at org.apache.axiom.om.util.StAXUtils. (StAXUtils.java:66) ... 34 more Tests run: 3, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.314 sec <<< FAILURE! Results : Tests run: 8, Failures: 0, Errors: 2, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. [INFO] -sachin
Openejb and port 1099
I am trying to find why port 1099 appears to be hardcoded. This message is generated by running two instances of G: 1. instance1 uses 1099 for rmi NamingPort 2. instance2 uses 1108 Both server start fine and have functioning console. JMXService is running correctly. message from instance2: .. Module 4/30 org.apache.geronimo.configs/j2ee-security/2.0-SNAPSHOT/car started in .531s Module 5/30 org.apache.geronimo.configs/openejb/2.0-SNAPSHOT/car 08:03:16,703 WARN [ManagementContext] Failed to start jmx connector: Cannot bind to URL [rmi://localhost:1099/jmxrmi]: javax.naming.NameAlreadyBoundExcepti on: jmxrmi [Root exception is java.rmi.AlreadyBoundException: jmxrmi] started in 13.579s .. Could someone please point me to the source of this message? Thanks Anita __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
