[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13867017#comment-13867017 ] Jarek Gawor commented on GERONIMO-6451: --- I fixed the comma. The new snaphost is published at: http://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-jpa_2.1_spec/1.0-SNAPSHOT/. API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0-src.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, jpa2.1-src.patch.txt Updated JPA 2.1 jar for Java EE 7. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-6507: - Assignee: Jarek Gawor Various code samples not visible Key: GERONIMO-6507 URL: https://issues.apache.org/jira/browse/GERONIMO-6507 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0.0 Reporter: Peter Lynch Assignee: Jarek Gawor Priority: Minor As per related defect GERONIMO-6506, there are a number of documentation pages that do not display all code samples. Here is a list: ||Page title||URL|| |Replacing default Realm in Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| |Database (SQL) Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| |Configuring Virtual Host in Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| |Monitoring thread pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| |Creating deployment plans for EJB applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| |Creating deployment plans for enterprise applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| |Creating deployment plans for Java EE application clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| |Creating deployment plans for Java Persistence API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| |Developing container managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| |Developing bean managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| |Developing persistence for JSF applications with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| |Deploying and running JPA application client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| |Developing Web services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13813984#comment-13813984 ] Jarek Gawor commented on GERONIMO-6507: --- Most of them should be fixed now but I just checked and I think I missed a couple in the first round. Remaining updates should be publishing a few hours. Various code samples not visible Key: GERONIMO-6507 URL: https://issues.apache.org/jira/browse/GERONIMO-6507 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0.0 Reporter: Peter Lynch Assignee: Jarek Gawor Priority: Minor As per related defect GERONIMO-6506, there are a number of documentation pages that do not display all code samples. Here is a list: ||Page title||URL|| |Replacing default Realm in Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| |Database (SQL) Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| |Configuring Virtual Host in Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| |Monitoring thread pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| |Creating deployment plans for EJB applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| |Creating deployment plans for enterprise applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| |Creating deployment plans for Java EE application clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| |Creating deployment plans for Java Persistence API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| |Developing container managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| |Developing bean managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| |Developing persistence for JSF applications with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| |Deploying and running JPA application client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| |Developing Web services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (GERONIMO-6507) Various code samples not visible
[ https://issues.apache.org/jira/browse/GERONIMO-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6507. --- Resolution: Fixed Should be all fixed now. Various code samples not visible Key: GERONIMO-6507 URL: https://issues.apache.org/jira/browse/GERONIMO-6507 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0.0 Reporter: Peter Lynch Assignee: Jarek Gawor Priority: Minor As per related defect GERONIMO-6506, there are a number of documentation pages that do not display all code samples. Here is a list: ||Page title||URL|| |Replacing default Realm in Geronimo|[http://geronimo.apache.org/GMOxDOC30/replacing-default-realm-in-geronimo.html]| |Database (SQL) Realm|[http://geronimo.apache.org/GMOxDOC30/database-sql-realm.html]| |LDAP Realm|[http://geronimo.apache.org/GMOxDOC30/ldap-realm.html]| |Configuring Virtual Host in Jetty|[http://geronimo.apache.org/GMOxDOC30/configuring-virtual-host-in-jetty.html]| |Monitoring thread pools|[http://geronimo.apache.org/GMOxDOC30/monitoring-thread-pools.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| |Creating deployment plans for EJB applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-ejb-applications.html]| |Creating deployment plans for enterprise applications|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-enterprise-applications.html]| |Creating deployment plans for Java EE application clients|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-ee-application-clients.html]| |Creating deployment plans for Java Persistence API|[http://geronimo.apache.org/GMOxDOC30/creating-deployment-plans-for-java-persistence-api.html]| |Developing container managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-container-managed-persistence-with-jpa.html]| |Developing bean managed persistence with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-bean-managed-persistence-with-jpa.html]| |Developing persistence for JSF applications with JPA|[http://geronimo.apache.org/GMOxDOC30/developing-persistence-for-jsf-applications-with-jpa.html]| |Deploying and running JPA application client|[http://geronimo.apache.org/GMOxDOC30/deploying-and-running-jpa-application-client.html]| |Developing Web services|[http://geronimo.apache.org/GMOxDOC30/developing-web-services.html]| |Extensible Administration Console|[http://geronimo.apache.org/GMOxDOC30/extensible-administration-console.html]| -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (XBEAN-255) Remove doPrivldged blocks
Jarek Gawor created XBEAN-255: - Summary: Remove doPrivldged blocks Key: XBEAN-255 URL: https://issues.apache.org/jira/browse/XBEAN-255 Project: XBean Issue Type: Improvement Components: classloader, reflect Reporter: Jarek Gawor Assignee: Jarek Gawor Certain xbean components have a few doPrivleged() calls. Since these components have not been designed or tested to run with a security manager, these doPrivleged() are unnecessary and in the worst case they can actually cause problems. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (GERONIMO-6506) Code samples not visible in Developing a Simple JavaServer Faces application tutorial
[ https://issues.apache.org/jira/browse/GERONIMO-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6506. --- Resolution: Fixed Assignee: Jarek Gawor Should be fixed now. Thanks! Code samples not visible in Developing a Simple JavaServer Faces application tutorial --- Key: GERONIMO-6506 URL: https://issues.apache.org/jira/browse/GERONIMO-6506 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: documentation Affects Versions: 3.0.0 Environment: Windows 7 Home Premium Service Pack 1 Mozilla Firefox 24.0 Internet Explorer 9.0.8112.16421 Reporter: Peter Lynch Assignee: Jarek Gawor Priority: Minor When viewing the Developing a Simple JavaServer Faces application tutorial (http://geronimo.apache.org/GMOxDOC30/developing-a-simple-javaserver-faces-application.html) in either of the above browsers, several code samples are not displayed: * login.jsp, welcome.jsp and 3 code snippets from login.jsp, all in the section Define and implement View (V) in application * index.jsp in the section Define and implement the View navigation by Controller (C) I notice that when I view this page, I receive what seem to be javascript errors, stating SyntaxHighlighter Can't find brush for: actionscript. This message is displayed 6 times, perhaps corresponding to the 6 code samples above. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802946#comment-13802946 ] Jarek Gawor commented on GERONIMO-6451: --- It has not been released yet and therefore it's not available on Maven central. However, you can pick up a snaphost from the following location: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-jpa_2.1_spec/1.0-SNAPSHOT/ API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, jpa2.1-src.patch.txt Updated JPA 2.1 jar for Java EE 7. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (GERONIMO-6505) CloseReason.CloseCodes enum's getCode method always returns 1111
[ https://issues.apache.org/jira/browse/GERONIMO-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6505. --- Resolution: Fixed Thanks for the patch. Committed it in revision 1531446. CloseReason.CloseCodes enum's getCode method always returns Key: GERONIMO-6505 URL: https://issues.apache.org/jira/browse/GERONIMO-6505 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Reporter: Andy McCright Assignee: Andy McCright Priority: Minor Attachments: patch-websockets-CloseReason.txt The initial implementation of the websockets API has a mistake in the implementation of the CloseCodes enum (in javax.websocket.CloseReason). When calling the getCode() method, instead of returning the proper code for the specified CloseReason (i.e. NORMAL_CLOSURE should return 1000, GOING_AWAY should return 1001, etc.), it always returns . -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (GERONIMO-6484) Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
[
https://issues.apache.org/jira/browse/GERONIMO-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713902#comment-13713902
]
Jarek Gawor commented on GERONIMO-6484:
---
Btw, a snapshot should be published soon as
https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-activation_1.1_spec/1.2-SNAPSHOT/
Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
-
Key: GERONIMO-6484
URL: https://issues.apache.org/jira/browse/GERONIMO-6484
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: specs
Reporter: Bert Jacobs
Assignee: Jarek Gawor
I'm using Karaf 2.3.2.
The endorsed directory contains the ServiceMix
org.apache.servicemix.specs.jaxb-api-2.2-2.2.0 bundle which in turn includes
a shaded version of geronimo-activation_1.1_spec version 1.0.2.
My code uses a FileDataSource, requests the content type and receives this:
{noformat}
Caused by: java.lang.NullPointerException
at
javax.activation.MimetypesFileTypeMap.init(MimetypesFileTypeMap.java:62)[:2.2.0]
at
javax.activation.FileTypeMap.getDefaultFileTypeMap(FileTypeMap.java:53)[:2.2.0]
at
javax.activation.FileDataSource.getContentType(FileDataSource.java:69)[:2.2.0]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6484) Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
[
https://issues.apache.org/jira/browse/GERONIMO-6484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-6484.
---
Resolution: Fixed
Assignee: Jarek Gawor
Committed the fix in revision 1504952.
Activation 1.1 spec: NullPointerException in MimetypesFileTypeMap
-
Key: GERONIMO-6484
URL: https://issues.apache.org/jira/browse/GERONIMO-6484
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: specs
Reporter: Bert Jacobs
Assignee: Jarek Gawor
I'm using Karaf 2.3.2.
The endorsed directory contains the ServiceMix
org.apache.servicemix.specs.jaxb-api-2.2-2.2.0 bundle which in turn includes
a shaded version of geronimo-activation_1.1_spec version 1.0.2.
My code uses a FileDataSource, requests the content type and receives this:
{noformat}
Caused by: java.lang.NullPointerException
at
javax.activation.MimetypesFileTypeMap.init(MimetypesFileTypeMap.java:62)[:2.2.0]
at
javax.activation.FileTypeMap.getDefaultFileTypeMap(FileTypeMap.java:53)[:2.2.0]
at
javax.activation.FileDataSource.getContentType(FileDataSource.java:69)[:2.2.0]
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6453. --- Resolution: Fixed Committed your patch in revision 1505072. Thanks again! API jar for JSR 340 - Servlet 3.1 - Key: GERONIMO-6453 URL: https://issues.apache.org/jira/browse/GERONIMO-6453 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Assignee: Andy McCright Attachments: getVirtualServerName-patch.txt, patch.txt Update jar file for Java EE 7. -- 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] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13710220#comment-13710220 ] Jarek Gawor commented on GERONIMO-6481: --- I committed your patch with minor changes in revision 1503881. I updated the sshd and mina dependencies to match what Karaf wanted. Please double check things and thanks for the patch! Karaf shell ssh bundle for IBM JDK SR10 host key issue -- Key: GERONIMO-6481 URL: https://issues.apache.org/jira/browse/GERONIMO-6481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0.0, 3.0.1 Reporter: xiezhi Assignee: Andy McCright Attachments: 6481-patch-2.txt, 6481-patch.txt When you launch Geronimo Shell Terminal in eclipse, you will meet the errorError connecting localhost:8101 : SSH client error: verify: false. Please refer karaf jira KARAF-1513 for the root cause. https://issues.apache.org/jira/browse/KARAF-1513 -- 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] (GERONIMO-6482) Ensure loading of JVM ext classloader classes from Geronimo bundles
[
https://issues.apache.org/jira/browse/GERONIMO-6482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707005#comment-13707005
]
Jarek Gawor commented on GERONIMO-6482:
---
I realized that Karaf sets this property in the etc/config.properties file so I
moved your change to that file as well in Geronimo to make things consistent.
The end result is pretty much the same anyway. Changes committed in revision
1502585 in 3.0 branch. Please double check if things are still working ok and
if so close the bug.
Thanks for the patch!
Ensure loading of JVM ext classloader classes from Geronimo bundles
---
Key: GERONIMO-6482
URL: https://issues.apache.org/jira/browse/GERONIMO-6482
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: osgi
Affects Versions: 3.0.1
Reporter: Andy McCright
Assignee: Andy McCright
Priority: Minor
Attachments: sys-prop-patch.txt
IBM has changed the classloader used to load com.sun.* (specifically
com.sun.script.javascript) classes in JDK 7. In JDK 6, these classes were
loaded by the JVM's boot classloader - in JDK 7, they are loaded via the
JVM's ext classloader (a child classloader of the boot loader). This change
has the effect of breaking servlet code like this:
ScriptEngineManager manager = new ScriptEngineManager();
ScriptEngine engine = manager.getEngineByName(JavaScript);
if(engine == null) {
throw new RuntimeException(Oh no, unable to find a script engine
found for JavaScript);
}
When running Geronimo 3.0.1 on JDK 6, this code works (engine is non-null, no
exception is thrown). When I switch to JDK7, I see:
ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory:
Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
java.lang.RuntimeException: Oh no, unable to find a script engine found for
JavaScript
at org.apache.jsp.HelloWorld_jsp._jspService(HelloWorld_jsp.java:96)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:731)
at
org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:48)
at
org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at
org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:267)
at
org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:397)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1121)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:614)
at java.lang.Thread.run(Thread.java:769)
The reason this fails is that the bundle's classloader's parent loader is the
JVM's boot classloader, not the ext loader - so it cannot load the com.sun.*
classes that it needs (and that it could in JDK6).
One solution to this is to add the following line to
geronimo_home/etc/system.properties:
osgi.parentClassloader=ext
This forces the bundle's to search the ext loader (in addition to the boot
loader) on
[jira] [Commented] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13707023#comment-13707023 ] Jarek Gawor commented on GERONIMO-6481: --- A few comments: 1) The latest released version of Karaf 2.2.x is 2.2.11. It would be preferable to upgrade to the latest 2.2.x version unless of course this a huge hassle. 2) The eclipse project files are not under source control for the Geronimo server project. The only project that I'm aware of that has them under source control is the Geronimo Eclipse Plugin project. So, I don't think you need to worry about this. 3) Make sure to double check that any shared third party dependencies between Karaf and Geronimo are (more or less) on the same level. However, there are a few old dependencies that we might keep as it (for example aries blueprint). Karaf shell ssh bundle for IBM JDK SR10 host key issue -- Key: GERONIMO-6481 URL: https://issues.apache.org/jira/browse/GERONIMO-6481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0.0, 3.0.1 Reporter: xiezhi Assignee: Andy McCright Attachments: 6481-patch.txt When you launch Geronimo Shell Terminal in eclipse, you will meet the errorError connecting localhost:8101 : SSH client error: verify: false. Please refer karaf jira KARAF-1513 for the root cause. https://issues.apache.org/jira/browse/KARAF-1513 -- 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] (GERONIMO-6481) Karaf shell ssh bundle for IBM JDK SR10 host key issue
[ https://issues.apache.org/jira/browse/GERONIMO-6481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13703351#comment-13703351 ] Jarek Gawor commented on GERONIMO-6481: --- Hopefully, since this looks like it is fixed in Karaf 2.2.8 we can just upgrade Geronimo to use Karaf 2.2.8 or so? Karaf shell ssh bundle for IBM JDK SR10 host key issue -- Key: GERONIMO-6481 URL: https://issues.apache.org/jira/browse/GERONIMO-6481 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0.0, 3.0.1 Reporter: xiezhi When you launch Geronimo Shell Terminal in eclipse, you will meet the errorError connecting localhost:8101 : SSH client error: verify: false. Please refer karaf jira KARAF-1513 for the root cause. https://issues.apache.org/jira/browse/KARAF-1513 -- 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] (GERONIMO-6477) Misconfigured RMI classloader
Jarek Gawor created GERONIMO-6477: - Summary: Misconfigured RMI classloader Key: GERONIMO-6477 URL: https://issues.apache.org/jira/browse/GERONIMO-6477 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: core Affects Versions: 3.0-beta-1, 3.0.0, 3.0-M1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker to send a serialized object via JMX that could compromise the system. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6477) Misconfigured RMI classloader
[ https://issues.apache.org/jira/browse/GERONIMO-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6477. --- Resolution: Fixed CVE-2013-1777 was assigned for this issue. The original issue was discovered by Pierre Ernst of IBM Canada Ltd. Misconfigured RMI classloader - Key: GERONIMO-6477 URL: https://issues.apache.org/jira/browse/GERONIMO-6477 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker to send a serialized object via JMX that could compromise the system. -- 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] (GERONIMO-6477) Misconfigured RMI classloader
[ https://issues.apache.org/jira/browse/GERONIMO-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696905#comment-13696905 ] Jarek Gawor commented on GERONIMO-6477: --- Remote exploits can be prevented by hiding the naming (1099) and JMX () ports behind a firewall or binding the ports to a local network interface. Fix for this issue was committed in revision 1458113. Misconfigured RMI classloader - Key: GERONIMO-6477 URL: https://issues.apache.org/jira/browse/GERONIMO-6477 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: core Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 A misconfigured RMI classloader in Apache Geronimo 3.0 may enable an attacker to send a serialized object via JMX that could compromise the system. -- 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] (GERONIMO-6472) SpnegoLoginModule problems
Jarek Gawor created GERONIMO-6472: - Summary: SpnegoLoginModule problems Key: GERONIMO-6472 URL: https://issues.apache.org/jira/browse/GERONIMO-6472 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: security Affects Versions: 2.1.8 Reporter: Jarek Gawor Assignee: Jarek Gawor A few different problems were discovered with the SpnegoLoginModule: 1) The searchFilter to lookup the user information uses cn attribute for matching. The cn (common name) might be different that the actual account name, and so the user lookup might fail. 2) NPE when memberOf attribute is not there 3) ArrayOutOfBoundsException when parsing group names -- 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] (GERONIMO-6472) SpnegoLoginModule problems
[ https://issues.apache.org/jira/browse/GERONIMO-6472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689922#comment-13689922 ] Jarek Gawor commented on GERONIMO-6472: --- Committed fixes to 3.0 branch (revision 1495244), 2.2 branch (revision 1495259) and 2.1 branch (revision 1495258). SpnegoLoginModule problems -- Key: GERONIMO-6472 URL: https://issues.apache.org/jira/browse/GERONIMO-6472 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: security Affects Versions: 2.1.8 Reporter: Jarek Gawor Assignee: Jarek Gawor A few different problems were discovered with the SpnegoLoginModule: 1) The searchFilter to lookup the user information uses cn attribute for matching. The cn (common name) might be different that the actual account name, and so the user lookup might fail. 2) NPE when memberOf attribute is not there 3) ArrayOutOfBoundsException when parsing group names -- 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] (GERONIMO-6462) API jar for JSR 356 - WebSockets 1.0
[ https://issues.apache.org/jira/browse/GERONIMO-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13680934#comment-13680934 ] Jarek Gawor commented on GERONIMO-6462: --- Committed your patch in revision 1492048. Thanks! Snapshot published at: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-websockets_1.0_spec/1.0-SNAPSHOT/ API jar for JSR 356 - WebSockets 1.0 Key: GERONIMO-6462 URL: https://issues.apache.org/jira/browse/GERONIMO-6462 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Assignee: Andy McCright Attachments: websockets-patch.txt New jar file for Java EE 7. -- 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] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679547#comment-13679547 ] Jarek Gawor commented on GERONIMO-6453: --- I had a little bit of problems applying your patch but eventually managed to resolve the issues. Your patch was applied in revision 1491469. The servlet 3.1 API require Java 7 to compile. Currently, the entire spec project is setup to be compiled with Java 6 so that's something we still need to figure out. API jar for JSR 340 - Servlet 3.1 - Key: GERONIMO-6453 URL: https://issues.apache.org/jira/browse/GERONIMO-6453 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: patch.txt Update jar file for Java EE 7. -- 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] (GERONIMO-6453) API jar for JSR 340 - Servlet 3.1
[ https://issues.apache.org/jira/browse/GERONIMO-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679667#comment-13679667 ] Jarek Gawor commented on GERONIMO-6453: --- Btw, for now I manually published a snapshot of the spec jar: https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/specs/geronimo-servlet_3.1_spec/1.0-SNAPSHOT/ API jar for JSR 340 - Servlet 3.1 - Key: GERONIMO-6453 URL: https://issues.apache.org/jira/browse/GERONIMO-6453 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Assignee: Andy McCright Attachments: patch.txt Update jar file for Java EE 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6451. --- Resolution: Fixed Resolving as most of the API is defined now. Please open another bug / task for fixing any potential problems discovered by TCK testing. API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, jpa2.1-src.patch.txt Updated JPA 2.1 jar for Java EE 7. -- 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] (GERONIMO-6034) testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest)
[ https://issues.apache.org/jira/browse/GERONIMO-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13664288#comment-13664288 ] Jarek Gawor commented on GERONIMO-6034: --- Looks like the problem here is that our porting code - specifically BeansImpl.isProxy() hasn't been updated to deal with changing package names of dynamic proxies. Here are the package names I see for a few different maintenance releases of Oracle Java 6: jdk6_43: class com.sun.proxy.$Proxy0 jdk6_39: class sun.proxy.$Proxy0 jdk6_23: class $Proxy0 Anyway, I updated the code in revision 1485297 and the tests appears to be passing now. testSerializeSFSB(org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest) - Key: GERONIMO-6034 URL: https://issues.apache.org/jira/browse/GERONIMO-6034 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: David Blevins -- 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] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13661000#comment-13661000 ] Jarek Gawor commented on GERONIMO-6451: --- Committed your patch in revision 1483970. Thanks! Are you planning to validate this against TCK (signature tests)? API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar, jpa2.1-src.patch.txt Updated JPA 2.1 jar for Java EE 7. -- 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] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659650#comment-13659650 ] Jarek Gawor commented on GERONIMO-6451: --- In revision 1483415 I setup a new geronimo-jpa_2.1_spec project (copied from 2.0) - see https://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jpa_2.1_spec/ (svn location). Can you please submit your 2.1 updates as a patch against this code? API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar Updated JPA 2.1 jar for Java EE 7. -- 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] (GERONIMO-6451) API jar for JSR 338 - JPA 2.1
[ https://issues.apache.org/jira/browse/GERONIMO-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13659765#comment-13659765 ] Jarek Gawor commented on GERONIMO-6451: --- Committed some JPA 2.1 updates in revision 1483469. API jar for JSR 338 - JPA 2.1 - Key: GERONIMO-6451 URL: https://issues.apache.org/jira/browse/GERONIMO-6451 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Reporter: Kevin Sutter Attachments: geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0.jar, geronimo-jpa_2.1_spec-1.0-src.jar Updated JPA 2.1 jar for Java EE 7. -- 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] (GERONIMODEVTOOLS-810) Server status not updated as server hostname is changed in server configuration
Jarek Gawor created GERONIMODEVTOOLS-810: Summary: Server status not updated as server hostname is changed in server configuration Key: GERONIMODEVTOOLS-810 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's are the steps to demonstrate the issue: 1) Stat a local server - serer status should be [Started] 2) Edit server configuration and change hostname to specify a server on a remote host. The remote server should be stopped. The server status should eventually be updated to [Stopped] but it does not change. That's happening because GEP cached a connection to the local server and won't release it until the local server is stopped somehow. Once the cached connection is released the server status will reflect the right status of the remote server. -- 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] (GERONIMODEVTOOLS-810) Server status not updated as server hostname is changed in server configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13647688#comment-13647688 ] Jarek Gawor commented on GERONIMODEVTOOLS-810: -- Fixes committed (with other minor connection management improvements) in revision 1478439. Server status not updated as server hostname is changed in server configuration Key: GERONIMODEVTOOLS-810 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's are the steps to demonstrate the issue: 1) Stat a local server - serer status should be [Started] 2) Edit server configuration and change hostname to specify a server on a remote host. The remote server should be stopped. The server status should eventually be updated to [Stopped] but it does not change. That's happening because GEP cached a connection to the local server and won't release it until the local server is stopped somehow. Once the cached connection is released the server status will reflect the right status of the remote server. -- 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] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635160#comment-13635160 ] Jarek Gawor commented on GERONIMO-6446: --- Ok, I changed the logic in revision 1469316. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6446. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as I think the key issues with building with Java 7 have been addressed. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Ensure that 3.0 branch builds with Java 7. -- 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] [Reopened] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reopened GERONIMO-6319: --- A performance problem was discovered when fragment bundles are being OBR resolved. Instead of resolving just the discovered fragment bundles, the current code resolves the application content and the fragment bundles. Basically, the application content is being resolved twice. Discover and provision fragment bundles during OSGi application resolution -- Key: GERONIMO-6319 URL: https://issues.apache.org/jira/browse/GERONIMO-6319 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for discovering and provisioning fragment bundles during OSGi application resolution. The application resolver will look for one fragment per application bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6319. --- Resolution: Fixed Performance improvement committed in revision 1469337. Discover and provision fragment bundles during OSGi application resolution -- Key: GERONIMO-6319 URL: https://issues.apache.org/jira/browse/GERONIMO-6319 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for discovering and provisioning fragment bundles during OSGi application resolution. The application resolver will look for one fragment per application bundle. -- 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] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633235#comment-13633235 ] Jarek Gawor commented on GERONIMO-6446: --- In revision 1468573 I committed additional changes that hopefully should make this error go away on Apple Java 7. Please verify. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6443. --- Resolution: Fixed Resolving as the work-around seems to be working ok. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- 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] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-809. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as the new port checking seems to be working as expected. In-use port detection does not work sometimes - Key: GERONIMODEVTOOLS-809 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Before starting a server, GEP checks if the http and naming ports are free. This check does not work sometimes on some platforms (e.g. Windows). That's because on Windows it is possible to bind to 0.0.0.0 (any/all network interfaces) and 127.0.0.1 with the same port at the same time. -- 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] [Closed] (XBEAN-242) Potential file descriptor leak in BundleResourceFinder
[ https://issues.apache.org/jira/browse/XBEAN-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor closed XBEAN-242. - Resolution: Fixed Fix Version/s: 3.13 Fixed. Potential file descriptor leak in BundleResourceFinder -- Key: XBEAN-242 URL: https://issues.apache.org/jira/browse/XBEAN-242 Project: XBean Issue Type: Bug Components: bundleutils Affects Versions: 3.12 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.13 BundleResourceFinder opens ZipInputStream but never explicitly closes it. That can potentially lead to file descriptor leaks. -- 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] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-795. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as it works as expected. Synchronizing port configuration Key: GERONIMODEVTOOLS-795 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Currently, GEP keep its own port configuration, separate from the server's configuration. The port information between GEP server is not synchronized in any way. And sometimes as the port information between the server GEP becomes out of synch, it creates problems for users when starting or deploying modules to the server from GEP. It would be nice to update the GEP to keep the port information in synch with the server. That is, if the server configuration is changed, that change is reflected in GEP. And if the change in made in GEP, the server configuration is updated as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6417) Launch listener
[ https://issues.apache.org/jira/browse/GERONIMO-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6417. --- Resolution: Fixed Fix Version/s: 3.0.1 Launch listener --- Key: GERONIMO-6417 URL: https://issues.apache.org/jira/browse/GERONIMO-6417 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for launch listeners. This is so that one can register a listener to receive events about launcher starting and stopping the runtime in order to perform custom action based on those events. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6445) Support configuration imports
[ https://issues.apache.org/jira/browse/GERONIMO-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6445. --- Resolution: Fixed Fix Version/s: 3.0.1 Support configuration imports -- Key: GERONIMO-6445 URL: https://issues.apache.org/jira/browse/GERONIMO-6445 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for configuration imports for config.properties and system.properties files. That will make it simpler to have separate configuration files for command line tools and server without duplicating the configuration information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5166) Enable car-maven-plugin to use Equinox
[ https://issues.apache.org/jira/browse/GERONIMO-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5166. --- Resolution: Fixed Fix Version/s: 3.0.0 Resolving as this is done and we are / were building with Equinox for a while. Enable car-maven-plugin to use Equinox -- Key: GERONIMO-5166 URL: https://issues.apache.org/jira/browse/GERONIMO-5166 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1, 3.0.0 Ability for car-maven-plugin to switch between Felix or Equinox as the OSGi framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5231) Override JVM libraries with newer versions
[ https://issues.apache.org/jira/browse/GERONIMO-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5231. --- Resolution: Fixed Fix Version/s: (was: 3.0.1) 3.0.0 This was done/enabled a while ago. Forgot to close it. Override JVM libraries with newer versions -- Key: GERONIMO-5231 URL: https://issues.apache.org/jira/browse/GERONIMO-5231 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.0 In some cases, Java EE 6 requires newer library versions then what is provided by Java SE 6. For example, EE 6 requires annotations 1.1 api but SE 6 provides annotation 1.0 api. So it is necessary that during a build we override the JVM provided libraries with newer versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6434) in-place deployment for OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6434. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as in-place deployment of OSGi applications seems to be working now. in-place deployment for OSGi applications - Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6397) Improve resolver-based error messages for OSGi application
[ https://issues.apache.org/jira/browse/GERONIMO-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6397. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. Improve resolver-based error messages for OSGi application -- Key: GERONIMO-6397 URL: https://issues.apache.org/jira/browse/GERONIMO-6397 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Improve ResolverErrorAnalyzer for OSGi applications. Specifically in cases where a import package cannot be satisfied provide details if the given package is exported by any bundles or if there are bundles that export that package with different version, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6319. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. Discover and provision fragment bundles during OSGi application resolution -- Key: GERONIMO-6319 URL: https://issues.apache.org/jira/browse/GERONIMO-6319 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for discovering and provisioning fragment bundles during OSGi application resolution. The application resolver will look for one fragment per application bundle. -- 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] (GERONIMODEVTOOLS-235) Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-235. -- Resolution: Fixed Fix Version/s: (was: 2.2.2) 3.0.1 WIth GERONIMODEVTOOLS-795 GEP will tell the server what ports to use. Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file Key: GERONIMODEVTOOLS-235 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Fix For: 3.0.1 -- 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] (GERONIMODEVTOOLS-695) Synchronize dependency version with Geronimo 3.0 M2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-695. -- Resolution: Fixed This is/was already done. Synchronize dependency version with Geronimo 3.0 M2 --- Key: GERONIMODEVTOOLS-695 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 3.0-M2 -- 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] (GERONIMODEVTOOLS-714) Synchronize the server configuration between GEP and server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-714. -- Resolution: Duplicate This is duplicate of GERONIMODEVTOOLS-795. Synchronize the server configuration between GEP and server --- Key: GERONIMODEVTOOLS-714 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.1, 2.1.7, 3.0 Reporter: Han Hong Fang Currently GEP has server configuration such as administrator id, administrator password, HTTP port value and RMI Naming port value. These are set with default values when server is created. Although the values can be modified during server creation or after server creation, this can be improved by reading such values from server configuration files when runtime is located on local machine. -- 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] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-762. -- Resolution: Fixed Resolving as the latest deployable and p2 zip are now automatically published after each change at https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/devtools/assembly/ GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build_new.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- 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] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-706. -- Resolution: Fixed Fix Version/s: 3.0.1 This feature is implemented now. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Fix For: 3.0.1 Attachments: enableKarafShell_706_m0.patch, enableKarafShell_706_m1.patch, enableKarafShell_706.patch, karafSSHTerminal_improvement.jpg, karafSSHTerminal.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- 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] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630901#comment-13630901 ] Jarek Gawor commented on GERONIMO-6446: --- Looks like this is a known issue in the jspc plugin - see https://jira.codehaus.org/browse/MJSPC-53. There is a work-around but there is no fixed version of the plugin. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- 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] (GERONIMO-6448) Configuration already exists error when redeploying OSGi application
Jarek Gawor created GERONIMO-6448: - Summary: Configuration already exists error when redeploying OSGi application Key: GERONIMO-6448 URL: https://issues.apache.org/jira/browse/GERONIMO-6448 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Environment: Windows 7 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's how to replicate the problem on Windows using GEP: 1. Publish OSGi application which has dependency problems. 2. Start server and get publish errors. 3. Right click this application in Servers view and remove it. 4. Right click server and add the application again. Then this error happens. Following is the error generated: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba org.apache.geronimo.common.DeploymentException: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba -- 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] (GERONIMO-6448) Configuration already exists error when redeploying OSGi application
[ https://issues.apache.org/jira/browse/GERONIMO-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13629325#comment-13629325 ] Jarek Gawor commented on GERONIMO-6448: --- Looks like there is a bug Aries' BundleManifest.fromBundle(File) function. It doesn't close the input stream if the file argument is a directory. In revision 1467077 I committed a fix (on Geronimo side) for this issue - it ensures we always close the input stream. Configuration already exists error when redeploying OSGi application -- Key: GERONIMO-6448 URL: https://issues.apache.org/jira/browse/GERONIMO-6448 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Environment: Windows 7 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's how to replicate the problem on Windows using GEP: 1. Publish OSGi application which has dependency problems. 2. Start server and get publish errors. 3. Right click this application in Servers view and remove it. 4. Right click server and add the application again. Then this error happens. Following is the error generated: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba org.apache.geronimo.common.DeploymentException: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: application/test.eba/1.0.0-qualifier/eba -- 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] (GERONIMO-6446) Build with Java 7
Jarek Gawor created GERONIMO-6446: - Summary: Build with Java 7 Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- 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] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13628135#comment-13628135 ] Jarek Gawor commented on GERONIMO-6446: --- Committed initial changes in revision 1466631. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6138. --- Resolution: Fixed I'm resolving this issue as TranQL 1.8 has been released and things in Geronimo are looking good. JDBC 4 API is not supported Key: GERONIMO-6138 URL: https://issues.apache.org/jira/browse/GERONIMO-6138 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0-M1, 3.0.0 Reporter: Arnaud MERGEY Assignee: Jarek Gawor Fix For: 3.0.1 Attachments: geronimo.patch, tranql.patch I try to deploy an application that uses some JDBC 4 API like java.sql.ResultSet.isClosed() This calls fails with following error java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo 3, and it seems not. -- 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] [Assigned] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-6138: - Assignee: Jarek Gawor JDBC 4 API is not supported Key: GERONIMO-6138 URL: https://issues.apache.org/jira/browse/GERONIMO-6138 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0-M1, 3.0.0 Reporter: Arnaud MERGEY Assignee: Jarek Gawor Fix For: 3.0.1 Attachments: geronimo.patch, tranql.patch I try to deploy an application that uses some JDBC 4 API like java.sql.ResultSet.isClosed() This calls fails with following error java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo 3, and it seems not. -- 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] (GERONIMO-6138) JDBC 4 API is not supported
[ https://issues.apache.org/jira/browse/GERONIMO-6138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624057#comment-13624057 ] Jarek Gawor commented on GERONIMO-6138: --- In revision 1465128 I updated the 3.0 branch to use tranql 1.8 rc. Please try it out. JDBC 4 API is not supported Key: GERONIMO-6138 URL: https://issues.apache.org/jira/browse/GERONIMO-6138 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0-M1, 3.0.0 Reporter: Arnaud MERGEY Assignee: Jarek Gawor Fix For: 3.0.1 Attachments: geronimo.patch, tranql.patch I try to deploy an application that uses some JDBC 4 API like java.sql.ResultSet.isClosed() This calls fails with following error java.lang.AbstractMethodError: org.tranql.connector.jdbc.ResultSetHandle.isClosed()Z According to JEE 6 specifications, JDBC 4 API should be supported in Geronimo 3, and it seems not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6444) Server riskactionsreadserv1 failed to start.
[ https://issues.apache.org/jira/browse/GERONIMO-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6444. --- Resolution: Invalid Looks like you are using WAS CE. Please contact IBM for WAS CE support. Server riskactionsreadserv1 failed to start. Key: GERONIMO-6444 URL: https://issues.apache.org/jira/browse/GERONIMO-6444 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: geronimo-maven-plugin Affects Versions: 1.1.1 Reporter: sridharraj kanakasai Priority: Blocker Attachments: config.xml, geronimo-web.xml Starting server... Server Build: V1.1.0.0-200806130552 JVM in use:IBM Corporation Java 1.6.0 2013-04-03 14:20:40,460 INFO [Log4jService] -- 2013-04-03 14:20:40,460 INFO [Log4jService] Started Logging Service 2013-04-03 14:20:40,645 INFO [Daemon] Basic Kernel and System Configuration Started 2013-04-03 14:20:40,645 INFO [Daemon] Server Information: 2013-04-03 14:20:40,645 INFO [Daemon] IBM WebSphere Application Server Community Edition V1.1.0.0 2013-04-03 14:20:40,645 INFO [Daemon] Copyright (C) 2005-2008 IBM Corporation. All Rights Reserved. 2013-04-03 14:20:40,645 INFO [Daemon] Build = 1.1.0.0-200806130552 2013-04-03 14:20:40,645 INFO [Daemon] Based on Apache Geronimo V1.1 2013-04-03 14:20:40,645 INFO [Daemon] Environment Information: 2013-04-03 14:20:40,645 INFO [Daemon] System property [os.name] = Windows 7 2013-04-03 14:20:40,646 INFO [Daemon] System property [os.version] = 6.1 build 7601 Service Pack 1 2013-04-03 14:20:40,646 INFO [Daemon] System property [sun.os.patch.level] = null 2013-04-03 14:20:40,646 INFO [Daemon] System property [os.arch] = x86 2013-04-03 14:20:40,646 INFO [Daemon] System property [locale] = en_US 2013-04-03 14:20:40,646 INFO [Daemon] System property [unicode.encoding] = UnicodeLittle 2013-04-03 14:20:40,646 INFO [Daemon] System property [file.encoding] = UTF-8 2013-04-03 14:20:40,646 INFO [Daemon] System property [java.vm.vendor] = IBM Corporation 2013-04-03 14:20:40,646 INFO [Daemon] System property [java.vm.version] = 2.4 2013-04-03 14:20:40,646 INFO [Daemon] System property [java.vm.info] = JRE 1.6.0 IBM J9 2.4 Windows 7 x86-32 jvmwi3260sr10-20111207_96808 (JIT enabled, AOT enabled) J9VM - 20111207_096808 JIT - r9_2007_21307ifx1 GC - 20110519_AA 2013-04-03 14:20:40,647 INFO [Daemon] System property [java.home] = C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre 2013-04-03 14:20:40,647 INFO [Daemon] System property [java.library.path] = C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre\bin;C:\WINDOWS\SysWOW64;C:\WINDOWS;C:\Perl64\site\bin;C:\Perl64\bin;C:\PERL51001\Perl\site\bin;C:\PERL51001\Perl\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft Application Virtualization Client;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\java\jre6\bin\;C:\Program Files(x86)\Perforce;C:\Program Files\TortoiseSVN\bin;C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre\bin;C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\bin;C:\ppde-helix-0.3.2\apache-maven-2.2.1\bin;%GROOVY_HOME%\bin;C:\Program Files\Common Files\Hitachi ID\;%TOMCAT_HOME%\bin;C:\ppde-helix-0.3.2\apache-maven-2.2.1\bin;C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre\bin;C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\bin;C:\ppde-helix-0.3.2\jetty-6.1.5\bin;. 2013-04-03 14:20:40,647 INFO [Daemon] System property [java.endorsed.dirs] = C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre\lib\endorsed;C:\RiskActionReadServWorkSpace_NEW\ce\riskactionsreadserv1\lib\endorsed 2013-04-03 14:20:40,647 INFO [Daemon] System property [java.ext.dirs] = C:\ppde-helix-0.3.2\java6-ibm-sr10ifx1-2011-12-08-windows\jre\lib\ext;C:\RiskActionReadServWorkSpace_NEW\ce\riskactionsreadserv1\lib\ext 2013-04-03 14:20:40,647 INFO [Daemon] System property [sun.boot.class.path] =
[jira] [Created] (GERONIMO-6445) Support configuration imports
Jarek Gawor created GERONIMO-6445: - Summary: Support configuration imports Key: GERONIMO-6445 URL: https://issues.apache.org/jira/browse/GERONIMO-6445 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for configuration imports for config.properties and system.properties files. That will make it simpler to have separate configuration files for command line tools and server without duplicating the configuration information. -- 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] (GERONIMO-6445) Support configuration imports
[ https://issues.apache.org/jira/browse/GERONIMO-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623275#comment-13623275 ] Jarek Gawor commented on GERONIMO-6445: --- Added support for imports in revision 1464814. I also added command-system.properties file (similar to command-config.properties) for command line tools to use. Support configuration imports -- Key: GERONIMO-6445 URL: https://issues.apache.org/jira/browse/GERONIMO-6445 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for configuration imports for config.properties and system.properties files. That will make it simpler to have separate configuration files for command line tools and server without duplicating the configuration information. -- 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] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
Jarek Gawor created GERONIMO-6443: - Summary: Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful. -- 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] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-6443: -- Description: During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). was: During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- 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] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620166#comment-13620166 ] Jarek Gawor commented on GERONIMO-6443: --- With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. But forcing bundle resolution again seems to work ok. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- 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] [Comment Edited] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620166#comment-13620166 ] Jarek Gawor edited comment on GERONIMO-6443 at 4/2/13 7:36 PM: --- With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. This timeout can be increased by setting osgi.usesTimeout property (it's 30 seconds by default). However, setting it to something larger then 30 seconds or making it unlimited doesn't really help as Equinox just keeps looking for a better solution. However, forcing bundle resolution again (after the first try) seems to work ok. was (Author: ga...@mcs.anl.gov): With Equinox debugging turned on we see the output like the following: ... Combination is not better that current best: 13=13 [0,0,1,1,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Combination is not better that current best: 14=13 Uses constraint check has timedout. Using the best solution found so far. Best combination found: [1,0,0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0,0] Found conflicting constraint: Import-Package: com.ctc.wstx.api; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] Found conflicting constraint: Import-Package: com.ctc.wstx.msv; version=3.2.0 in bundle [org.apache.geronimo.bundles.woodstox_3.2.9.1] ... It looks like Equinox times out trying to resolve the package uses conflicts. But forcing bundle resolution again seems to work ok. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- 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] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13620172#comment-13620172 ] Jarek Gawor commented on GERONIMO-6443: --- Committed changed in revision 1463715 to perform bundle resolution twice to work-around this problem. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- 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] (GERONIMO-6442) Improve deployment performance of OSGi applications
Jarek Gawor created GERONIMO-6442: - Summary: Improve deployment performance of OSGi applications Key: GERONIMO-6442 URL: https://issues.apache.org/jira/browse/GERONIMO-6442 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor When OSGi application (eba) is deployed, the archive is first extracted into a temporary directory. Then (during installation) the contents of the temporary directory is copied (and unpacked) into the final destination directory under the repository/ directory. For OSGi applications unpacking the archive into the temporary directory is not needed and therefore can be avoided. -- 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] (GERONIMO-6442) Improve deployment performance of OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13616937#comment-13616937 ] Jarek Gawor commented on GERONIMO-6442: --- Committed improvements in revision 1462372. Improve deployment performance of OSGi applications --- Key: GERONIMO-6442 URL: https://issues.apache.org/jira/browse/GERONIMO-6442 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor When OSGi application (eba) is deployed, the archive is first extracted into a temporary directory. Then (during installation) the contents of the temporary directory is copied (and unpacked) into the final destination directory under the repository/ directory. For OSGi applications unpacking the archive into the temporary directory is not needed and therefore can be avoided. -- 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] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes
Jarek Gawor created GERONIMODEVTOOLS-809: Summary: In-use port detection does not work sometimes Key: GERONIMODEVTOOLS-809 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Before starting a server, GEP checks if the http and naming ports are free. This check does not work sometimes on some platforms (e.g. Windows). That's because on Windows it is possible to bind to 0.0.0.0 (any/all network interfaces) and 127.0.0.1 with the same port at the same time. -- 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] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13615717#comment-13615717 ] Jarek Gawor commented on GERONIMODEVTOOLS-809: -- Committed improvements in revision 1461837. Besides checking 0.0.0.0 (as done before), GEP will also now lookup and check the address of the server as configured in Eclipse (getServer().getHost()). In-use port detection does not work sometimes - Key: GERONIMODEVTOOLS-809 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Before starting a server, GEP checks if the http and naming ports are free. This check does not work sometimes on some platforms (e.g. Windows). That's because on Windows it is possible to bind to 0.0.0.0 (any/all network interfaces) and 127.0.0.1 with the same port at the same time. -- 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] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13612987#comment-13612987 ] Jarek Gawor commented on GERONIMODEVTOOLS-795: -- In revision 1460849 I committed additional changes. Now instead of updating the config-substitutions.properties file, GEP will pass the port offset, http port, etc. information (via system properties) to the server. That way, the port information specified in GEP will always be accurate and correct. Synchronizing port configuration Key: GERONIMODEVTOOLS-795 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Currently, GEP keep its own port configuration, separate from the server's configuration. The port information between GEP server is not synchronized in any way. And sometimes as the port information between the server GEP becomes out of synch, it creates problems for users when starting or deploying modules to the server from GEP. It would be nice to update the GEP to keep the port information in synch with the server. That is, if the server configuration is changed, that change is reflected in GEP. And if the change in made in GEP, the server configuration is updated as well. -- 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] [Assigned] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMODEVTOOLS-795: Assignee: Jarek Gawor Synchronizing port configuration Key: GERONIMODEVTOOLS-795 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Currently, GEP keep its own port configuration, separate from the server's configuration. The port information between GEP server is not synchronized in any way. And sometimes as the port information between the server GEP becomes out of synch, it creates problems for users when starting or deploying modules to the server from GEP. It would be nice to update the GEP to keep the port information in synch with the server. That is, if the server configuration is changed, that change is reflected in GEP. And if the change in made in GEP, the server configuration is updated as well. -- 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] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13611162#comment-13611162 ] Jarek Gawor commented on GERONIMODEVTOOLS-795: -- Committed initial changes in revision 1459957. I added support for setting PortOffset in GEP and changes made to port information will be now saved into the config-substitutions.properties file (if the server is local). However, currently, the config-substitutions.properties will be read when a new server is created. With these changes I also fixed a couple of problems in the server configuration editor: 1) I've improved undo functionality, 2) Fixed an issue where un-saved configuration properties could actually get used by GEP before they were actually saved or discarded, 3) Added basic validation to numeric fields, and 3) Increased published timeout to 4 hours. Synchronizing port configuration Key: GERONIMODEVTOOLS-795 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Currently, GEP keep its own port configuration, separate from the server's configuration. The port information between GEP server is not synchronized in any way. And sometimes as the port information between the server GEP becomes out of synch, it creates problems for users when starting or deploying modules to the server from GEP. It would be nice to update the GEP to keep the port information in synch with the server. That is, if the server configuration is changed, that change is reflected in GEP. And if the change in made in GEP, the server configuration is updated as well. -- 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] (GERONIMODEVTOOLS-808) Server restarts after project is removed
Jarek Gawor created GERONIMODEVTOOLS-808: Summary: Server restarts after project is removed Key: GERONIMODEVTOOLS-808 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Priority: Minor The server automatically starts if previously deployed project is removed from the workspace. -- 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] (GERONIMODEVTOOLS-808) Server restarts after project is removed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13607708#comment-13607708 ] Jarek Gawor commented on GERONIMODEVTOOLS-808: -- When a (deployed) project is deleted from the workspace, Eclipse forces a publish operation on the server. Since GEP is configured with a start server before publish option that causes Eclipse to automatically start the server in this particular case - in order to undeploy the project from the server. It is possible for GEP to disable the start server before publish option and manage on its own when and how the server gets started. However, this use-case is pretty rare (and considering the changes needed for this feature) I'm marking this as a low priority issue. Server restarts after project is removed Key: GERONIMODEVTOOLS-808 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-808 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Priority: Minor The server automatically starts if previously deployed project is removed from the workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6432) JAXWS API: javax.xml.ws.spi.FactoryFinder look at the wrong properties file to find the factory implementation
[ https://issues.apache.org/jira/browse/GERONIMO-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6432. --- Resolution: Fixed You're right. Thanks! Fixed in revision 1458320. JAXWS API: javax.xml.ws.spi.FactoryFinder look at the wrong properties file to find the factory implementation -- Key: GERONIMO-6432 URL: https://issues.apache.org/jira/browse/GERONIMO-6432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs, webservices Reporter: Loïc ALBERTIN Assignee: Jarek Gawor Hi, I think there is a copy/paste mistake in class javax.xml.ws.spi.FactoryFinder for jaxws api 2.1 and 2.2. In method static Object find(String factoryId, String fallbackClassName) you should look at java-home/lib/jaxws.properties for a Factory implementation but you look at java-home/lib/jaxrpc.properties instead. https://github.com/apache/geronimo-specs/blob/trunk/geronimo-jaxws_2.2_spec/src/main/java/javax/xml/ws/spi/FactoryFinder.java#L185 Regards, Loïc -- 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] [Assigned] (GERONIMO-6440) unlock keystore action appears to be broken when running server against Oracle JDK 1.7
[
https://issues.apache.org/jira/browse/GERONIMO-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor reassigned GERONIMO-6440:
-
Assignee: Jarek Gawor
unlock keystore action appears to be broken when running server against
Oracle JDK 1.7
--
Key: GERONIMO-6440
URL: https://issues.apache.org/jira/browse/GERONIMO-6440
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: JVM-compatibility
Affects Versions: 2.1.8, 2.2.1, 3.0-beta-1
Reporter: xiezhi
Assignee: Jarek Gawor
Priority: Blocker
Attachments: PropertyEditors.java.patch
To reproduce the issue, you can follow the steps below.
1.Start geronimo 3.0 server.
2.Use keytool command to create a keystore with a key. For example,
keytool -genkeypair -keystore test.jks -alias testkey -keyalg RSA -keysize
2048 -dname cn=test.apache.org,c=US -validity 365 -storepass welcome1
3.Copy the keystore to geronimo-home\var\security\keystores
4.use deploy encrypt to encrypt the password welcome,go the encrypt string:
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
add the string into config-substitution.properties like this:
test.jks =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
testkey =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
5. restart the server.
6. use deploy unlock-keystore command to unlock test.jks. For example,
deploy -u system -p manager unlock-keystore test.jks
The result is the unlock action seems to success. But you can find an ERROR
below in admin console. It will generate a incomplete j2ee-security module in
config.xml. When you restart the server, you will fail on it.
2013-02-27 11:41:06,564 WARN [FileKeystoreManager] keystoreType for new
keystore test.jks set to jks based on file extension.
2013-02-27 11:41:06,660 ERROR [LocalAttributeManager] Unable to format
attribute of type java.net.URI; no editor found
2013-02-27 11:41:06,660 WARN [BasicProxyManager] Could not load interface
org.apache.geronimo.security.keystore.FileKeystoreInsta
nce in provided ClassLoader for
org.apache.geronimo.framework/j2ee-security/3.0.0/car?ServiceModule=org.apache.geronimo.framework/
j2ee-security/3.0.0/car,j2eeType=Keystore,name=test.jks
--
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] (GERONIMO-6440) unlock keystore action appears to be broken when running server against Oracle JDK 1.7
[
https://issues.apache.org/jira/browse/GERONIMO-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13605906#comment-13605906
]
Jarek Gawor commented on GERONIMO-6440:
---
I applied slightly modified patch (to make it a bit more efficient) in revision
1458076. Please verify.
unlock keystore action appears to be broken when running server against
Oracle JDK 1.7
--
Key: GERONIMO-6440
URL: https://issues.apache.org/jira/browse/GERONIMO-6440
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: JVM-compatibility
Affects Versions: 2.1.8, 2.2.1, 3.0-beta-1
Reporter: xiezhi
Assignee: Jarek Gawor
Priority: Blocker
Attachments: PropertyEditors.java.patch
To reproduce the issue, you can follow the steps below.
1.Start geronimo 3.0 server.
2.Use keytool command to create a keystore with a key. For example,
keytool -genkeypair -keystore test.jks -alias testkey -keyalg RSA -keysize
2048 -dname cn=test.apache.org,c=US -validity 365 -storepass welcome1
3.Copy the keystore to geronimo-home\var\security\keystores
4.use deploy encrypt to encrypt the password welcome,go the encrypt string:
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
add the string into config-substitution.properties like this:
test.jks =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
testkey =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
5. restart the server.
6. use deploy unlock-keystore command to unlock test.jks. For example,
deploy -u system -p manager unlock-keystore test.jks
The result is the unlock action seems to success. But you can find an ERROR
below in admin console. It will generate a incomplete j2ee-security module in
config.xml. When you restart the server, you will fail on it.
2013-02-27 11:41:06,564 WARN [FileKeystoreManager] keystoreType for new
keystore test.jks set to jks based on file extension.
2013-02-27 11:41:06,660 ERROR [LocalAttributeManager] Unable to format
attribute of type java.net.URI; no editor found
2013-02-27 11:41:06,660 WARN [BasicProxyManager] Could not load interface
org.apache.geronimo.security.keystore.FileKeystoreInsta
nce in provided ClassLoader for
org.apache.geronimo.framework/j2ee-security/3.0.0/car?ServiceModule=org.apache.geronimo.framework/
j2ee-security/3.0.0/car,j2eeType=Keystore,name=test.jks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6440) unlock keystore action appears to be broken when running server against Oracle JDK 1.7
[
https://issues.apache.org/jira/browse/GERONIMO-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-6440.
---
Resolution: Fixed
Fix Version/s: 3.0.1
unlock keystore action appears to be broken when running server against
Oracle JDK 1.7
--
Key: GERONIMO-6440
URL: https://issues.apache.org/jira/browse/GERONIMO-6440
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: JVM-compatibility
Affects Versions: 2.1.8, 2.2.1, 3.0-beta-1
Reporter: xiezhi
Assignee: Jarek Gawor
Priority: Blocker
Fix For: 3.0.1
Attachments: PropertyEditors.java.patch
To reproduce the issue, you can follow the steps below.
1.Start geronimo 3.0 server.
2.Use keytool command to create a keystore with a key. For example,
keytool -genkeypair -keystore test.jks -alias testkey -keyalg RSA -keysize
2048 -dname cn=test.apache.org,c=US -validity 365 -storepass welcome1
3.Copy the keystore to geronimo-home\var\security\keystores
4.use deploy encrypt to encrypt the password welcome,go the encrypt string:
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
add the string into config-substitution.properties like this:
test.jks =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
testkey =
{Simple}rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHB1cgACW0Ks8xf4BghU4AIAAHhwEKvo5tkjHVqHlsBtDNRytadwdAADQUVT
5. restart the server.
6. use deploy unlock-keystore command to unlock test.jks. For example,
deploy -u system -p manager unlock-keystore test.jks
The result is the unlock action seems to success. But you can find an ERROR
below in admin console. It will generate a incomplete j2ee-security module in
config.xml. When you restart the server, you will fail on it.
2013-02-27 11:41:06,564 WARN [FileKeystoreManager] keystoreType for new
keystore test.jks set to jks based on file extension.
2013-02-27 11:41:06,660 ERROR [LocalAttributeManager] Unable to format
attribute of type java.net.URI; no editor found
2013-02-27 11:41:06,660 WARN [BasicProxyManager] Could not load interface
org.apache.geronimo.security.keystore.FileKeystoreInsta
nce in provided ClassLoader for
org.apache.geronimo.framework/j2ee-security/3.0.0/car?ServiceModule=org.apache.geronimo.framework/
j2ee-security/3.0.0/car,j2eeType=Keystore,name=test.jks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6432) JAXWS API: javax.xml.ws.spi.FactoryFinder look at the wrong properties file to find the factory implementation
[ https://issues.apache.org/jira/browse/GERONIMO-6432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6432. --- Resolution: Fixed Assignee: Jarek Gawor Fix committed in revision 1458087. Thanks! JAXWS API: javax.xml.ws.spi.FactoryFinder look at the wrong properties file to find the factory implementation -- Key: GERONIMO-6432 URL: https://issues.apache.org/jira/browse/GERONIMO-6432 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs, webservices Reporter: Loïc ALBERTIN Assignee: Jarek Gawor Hi, I think there is a copy/paste mistake in class javax.xml.ws.spi.FactoryFinder for jaxws api 2.1 and 2.2. In method static Object find(String factoryId, String fallbackClassName) you should look at java-home/lib/jaxws.properties for a Factory implementation but you look at java-home/lib/jaxrpc.properties instead. https://github.com/apache/geronimo-specs/blob/trunk/geronimo-jaxws_2.2_spec/src/main/java/javax/xml/ws/spi/FactoryFinder.java#L185 Regards, Loïc -- 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] [Closed] (XBEAN-241) finder doesn't handle #
[ https://issues.apache.org/jira/browse/XBEAN-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor closed XBEAN-241. - Resolution: Fixed Fix Version/s: 3.13 Assignee: Jarek Gawor (was: Mark Struberg) finder doesn't handle # --- Key: XBEAN-241 URL: https://issues.apache.org/jira/browse/XBEAN-241 Project: XBean Issue Type: Bug Components: finder Reporter: Romain Manni-Bucau Assignee: Jarek Gawor Priority: Blocker Fix For: 3.13 Attachments: XBEAN-test.patch current trunk (i didn't check previous versions) doesn't handle '#' for Jars. In org.apache.xbean.finder.archive.JarArchive#JarArchive replacing line 53 (jar = new JarFile(u.getFile().replace(%20, )); // no more an url) by jar = new JarFile(FileArchive.decode(u.getFile())); is enough to fix it (i can do a patch but since that's trivial to do i thought it was not mandatory, if you need it please ask) -- 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] (XBEAN-242) Potential file descriptor leak in BundleResourceFinder
Jarek Gawor created XBEAN-242: - Summary: Potential file descriptor leak in BundleResourceFinder Key: XBEAN-242 URL: https://issues.apache.org/jira/browse/XBEAN-242 Project: XBean Issue Type: Bug Components: bundleutils Affects Versions: 3.12 Reporter: Jarek Gawor Assignee: Jarek Gawor BundleResourceFinder opens ZipInputStream but never explicitly closes it. That can potentially lead to file descriptor leaks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6435) Invalid method interface: MessageEndpoint
[ https://issues.apache.org/jira/browse/GERONIMO-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6435. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Jarek Gawor I updated the Geronimo server code (j2ee-server module specifically) to set the additional EJB 3.1 method interfaces (Timer and MessageEndpoint) via JACC API extensibility mechanism. Changes committed in revision 1448884. Invalid method interface: MessageEndpoint Key: GERONIMO-6435 URL: https://issues.apache.org/jira/browse/GERONIMO-6435 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: javaee6 Affects Versions: 3.0-beta-1 Environment: EJB Reporter: Hiroko Takamiya Assignee: Jarek Gawor Priority: Minor Labels: newbie Fix For: 3.0.1 Our customer is getting following error (Invalid method interface: MessageEndpoint) when running their EJB 3.1 beans. --Error message- [12/18/12 15:13:08:638 CET] 0030 SecurityColla 3 Authorization failed accessing EJBjava.lang.IllegalArgumentException: Invalid method interface: MessageEndpoint at javax.security.jacc.EJBMethodPermission$MethodSpec.checkMethodInterface( EJBMethodPermission.java:303) at javax.security.jacc.EJBMethodPermission$MethodSpec.init(EJBMethodPermi ssion.java:183) -- Fortunately, interface list is extensible by adding property org.apache. security.jacc.EJBMethodPermission.methodInterfaces to JVM. And this solution works, although it is quite dirty. Looking at EJB 3.1 spec below, MessageEndpoint is newly added interface. http://download.oracle.com/otndocs/jcp/ejb-3.1-mrel-full-oth-JSpec/ I have looked at apache geronimo download page but no luck finding the interface in the latest downloads. --- details on what I looked for -- http://geronimo.apache.org/downloads.html ..and clicked on the latest release available Apache Geronimo v3.0.0 - Released July 13, 2012 (http://geronimo.apache.org/apache-geronimo-v300-release.html) ..and downloaded Certified Java EE 6 Full Profile Releases ...and looked into following class geronimo-tomcat7-javaee6-3.0.0\repository\org\apache\ geronimo\specs\geronimo-jacc_1.4_spec\1.0\javax\security\ jacc\EJBMethodPermission.class --- Please kindly look at adding this one interface to the file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6439) There are some spelling mistakes in CommandUnlockKeystore.java's DeploymentException message
[ https://issues.apache.org/jira/browse/GERONIMO-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6439. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Jarek Gawor Committed the patch in revision 1448011. Thanks for the patch! There are some spelling mistakes in CommandUnlockKeystore.java's DeploymentException message Key: GERONIMO-6439 URL: https://issues.apache.org/jira/browse/GERONIMO-6439 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 3.0-beta-1 Reporter: xiezhi Assignee: Jarek Gawor Priority: Minor Fix For: 3.0.1 Attachments: CommandUnlockKeystore.java.patch Found some spelling mistakes in DeploymentException message. Then checked the source. In http://svn.apache.org/repos/asf/geronimo/server/trunk/framework/modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/cli/CommandUnlockKeystore.java Line 126 throw new DeploymentException(No alias with the name + aliasName + exists in the kyeStoreTruststore password properties file:: + System.getProperty(KEYSTORE_TRUSTSTORE_PASSWORD_FILE, DEFAULT_KEYSTORE_TRUSTSTORE_PASSWORD_FILE)); Line 172 throw new DeploymentException(No keyStorePassword attribute named + keyStoreName + exists in the kyeStoreTruststore password properties file:: + System.getProperty(KEYSTORE_TRUSTSTORE_PASSWORD_FILE, DEFAULT_KEYSTORE_TRUSTSTORE_PASSWORD_FILE)); I think the kyeStoreTruststore should be corrected to keyStoreTruststore -- 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] (GERONIMO-6434) in-place deployment for OSGi applications
Jarek Gawor created GERONIMO-6434: - Summary: in-place deployment for OSGi applications Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- 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] (GERONIMODEVTOOLS-807) Handle updates to static and class resources at the same time
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-807. -- Resolution: Fixed Fix Version/s: 3.0.1 Handle updates to static and class resources at the same time - Key: GERONIMODEVTOOLS-807 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-807 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 When working with OSGi application and making changes to both static and class resources at the same time will cause the bundle to be automatically restarted. A bundle restart might be an expensive operation. However, in some cases it might be possible to just update the static resources on the server and perform hot code replace on the class files without restarting a bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
[ https://issues.apache.org/jira/browse/GERONIMO-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6427. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. Transport scheme NOT recognized: [tcp] -- Key: GERONIMO-6427 URL: https://issues.apache.org/jira/browse/GERONIMO-6427 Project: Geronimo Issue Type: Bug Components: console Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 I ran into the following exception: 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656) at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099) at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511) at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458) This happens if all the activemq modules are configured with load=false in config.xml and somebody tries to display all web applications using the admin console. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6393) javax.validation.Validator lookup improvement
[ https://issues.apache.org/jira/browse/GERONIMO-6393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6393. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. javax.validation.Validator lookup improvement - Key: GERONIMO-6393 URL: https://issues.apache.org/jira/browse/GERONIMO-6393 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: general Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Each time the same application looks up javax.validation.Validator object in JNDI a completely new instance of the object is returned (as required per spec). However, with Apache Bean Validation implementation that means that expensive annotation scanning is done on each Validator.validate() call. Apache Bean Validation implementation maintains an annotation cache with each ValidatorContext. However, each ValidatorFactory.getValidator() call creates a new instance of ValidatorContext and that's why the cache is not reused and annotation scanning is done on each call. In Geronimo we can ensure that the same ValidatorContext is used for the given application and therefore, ensure that cache is reused and annotation scanning is only done one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6385) Adjust default thread pool at runtime
[ https://issues.apache.org/jira/browse/GERONIMO-6385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6385. --- Resolution: Fixed Fix Version/s: 3.0.1 Forgot to close. Adjust default thread pool at runtime - Key: GERONIMO-6385 URL: https://issues.apache.org/jira/browse/GERONIMO-6385 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: core Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Right now the default thread pool size can only be adjusted while the server is not running. However, sometimes it might be desirable to adjust the thread pool size at runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6374) Clear cache after unclean shutdown
[ https://issues.apache.org/jira/browse/GERONIMO-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6374. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: viola.lu Clear cache after unclean shutdown -- Key: GERONIMO-6374 URL: https://issues.apache.org/jira/browse/GERONIMO-6374 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: viola.lu Fix For: 3.0.1 Clear caches on server start up after the server was forcibly killed. This is in case the cache got corrupted when the server was killed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6370) Update static files without bundle restart
[ https://issues.apache.org/jira/browse/GERONIMO-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6370. --- Resolution: Fixed Closing as work for this issue is done. Update static files without bundle restart -- Key: GERONIMO-6370 URL: https://issues.apache.org/jira/browse/GERONIMO-6370 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: viola.lu Assignee: viola.lu Fix For: 3.0.1 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-796 have to extract bundles when install EBA and install it via reference: file -- 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] (GERONIMO-6434) in-place deployment for OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571526#comment-13571526 ] Jarek Gawor commented on GERONIMO-6434: --- I re-factored the code a bit to support in-place deployment for OSGi applications. Changes committed in revision 1442682. in-place deployment for OSGi applications - Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- 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] (GERONIMO-6406) Import some fixed from axis2 to geronimo 3.0 for ssl issue
[ https://issues.apache.org/jira/browse/GERONIMO-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13568928#comment-13568928 ] Jarek Gawor commented on GERONIMO-6406: --- In revision 1441563 I added an ability to disable hostname verification. This might be needed in some circumstances - e.g. during testing. To disable hostname verification one can set the following system property: org.apache.commons.httpclient.protocol.SSLProtocolSocketFactory.hostnameVerifier=allow_all Import some fixed from axis2 to geronimo 3.0 for ssl issue -- Key: GERONIMO-6406 URL: https://issues.apache.org/jira/browse/GERONIMO-6406 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient, webservices Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 Reporter: xiezhi Assignee: Jarek Gawor Priority: Critical Fix For: 3.0.1 Attachments: commons-httpclient-3.1_1.jar, SSL_Fix.patch SSL Certificate Validation issue -- 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] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566603#comment-13566603 ] Jarek Gawor commented on GERONIMO-6319: --- In revision 1440511 I committed a fix to avoid the resources have not been resolved error while resolving fragment bundles. Discover and provision fragment bundles during OSGi application resolution -- Key: GERONIMO-6319 URL: https://issues.apache.org/jira/browse/GERONIMO-6319 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Add support for discovering and provisioning fragment bundles during OSGi application resolution. The application resolver will look for one fragment per application bundle. -- 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] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
Jarek Gawor created GERONIMO-6427: - Summary: Transport scheme NOT recognized: [tcp] Key: GERONIMO-6427 URL: https://issues.apache.org/jira/browse/GERONIMO-6427 Project: Geronimo Issue Type: Bug Components: console Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor I ran into the following exception: 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656) at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099) at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511) at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458) This happens if all the activemq modules are configured with load=false in config.xml and somebody tries to display all web applications using the admin console. -- 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] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
[ https://issues.apache.org/jira/browse/GERONIMO-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547235#comment-13547235 ] Jarek Gawor commented on GERONIMO-6427: --- This is caused by the portlet that displays a list of web or ear applications. The portlet tries to temporarily load the disabled module to see if it is a web module and to populate the context path and display name information. The portlet then unloads the given module. The load operation followed a quick unload operation causes this error (because some things in this case are handled asynchronously). We could try synchronizing the code better so that unload only happens if load was fully completed but I don't think that's really needed for the portlet. The load operation is expensive (it installs bundles, loads gbeans, etc.) so maybe a better option is not to load the disabled modules. The side effect is that the context path and display name fields in the portlet would not be populated and also the war portlet would not show war modules that are embedded in the ear modules (for modules are of course not loaded). Transport scheme NOT recognized: [tcp] -- Key: GERONIMO-6427 URL: https://issues.apache.org/jira/browse/GERONIMO-6427 Project: Geronimo Issue Type: Bug Components: console Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor I ran into the following exception: 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656) at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099) at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511) at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458) This happens if all the activemq modules are configured with load=false in config.xml and somebody tries to display all web applications using the admin console. -- 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] (GERONIMO-6427) Transport scheme NOT recognized: [tcp]
[ https://issues.apache.org/jira/browse/GERONIMO-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547244#comment-13547244 ] Jarek Gawor commented on GERONIMO-6427: --- In revision 1430511 I modified the portelet not to load and unload disabled modules. Transport scheme NOT recognized: [tcp] -- Key: GERONIMO-6427 URL: https://issues.apache.org/jira/browse/GERONIMO-6427 Project: Geronimo Issue Type: Bug Components: console Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor I ran into the following exception: 2013-01-03 19:25:20,497 ERROR [BrokerService] Failed to start ActiveMQ JMS Message Broker. Reason: java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] java.io.IOException: Transport Connector could not be registered in JMX: Transport scheme NOT recognized: [tcp] at org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:27) at org.apache.activemq.broker.BrokerService.registerConnectorMBean(BrokerService.java:1656) at org.apache.activemq.broker.BrokerService.startTransportConnector(BrokerService.java:2099) at org.apache.activemq.broker.BrokerService.startAllConnectors(BrokerService.java:2049) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:511) at org.apache.activemq.broker.BrokerService.autoStart(BrokerService.java:458) This happens if all the activemq modules are configured with load=false in config.xml and somebody tries to display all web applications using the admin console. -- 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] (GERONIMO-6406) Import some fixed from axis2 to geronimo 3.0 for ssl issue
[ https://issues.apache.org/jira/browse/GERONIMO-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13529322#comment-13529322 ] Jarek Gawor commented on GERONIMO-6406: --- Committed the patch for http-commons bundle in revision 1420389. Thanks for the patch! Import some fixed from axis2 to geronimo 3.0 for ssl issue -- Key: GERONIMO-6406 URL: https://issues.apache.org/jira/browse/GERONIMO-6406 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient, webservices Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 Reporter: xiezhi Priority: Critical Attachments: commons-httpclient-3.1_1.jar, SSL_Fix.patch SSL Certificate Validation issue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6406) Import some fixed from axis2 to geronimo 3.0 for ssl issue
[ https://issues.apache.org/jira/browse/GERONIMO-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6406. --- Resolution: Fixed Fix Version/s: 3.0.1 Assignee: Jarek Gawor Updated branches/3.0 to use the latest commons-httpclient bundle in revision 1420420. Import some fixed from axis2 to geronimo 3.0 for ssl issue -- Key: GERONIMO-6406 URL: https://issues.apache.org/jira/browse/GERONIMO-6406 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient, webservices Affects Versions: 3.0-M1, 3.0.0, 3.0-beta-1 Reporter: xiezhi Assignee: Jarek Gawor Priority: Critical Fix For: 3.0.1 Attachments: commons-httpclient-3.1_1.jar, SSL_Fix.patch SSL Certificate Validation issue -- 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
