[JBoss JIRA] (WFCORE-1985) :read-resource-description operation should consistently order resources by alphabet
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1985?page=com.atlassian.jira.plugi... ]
Jiri Ondrusek reassigned WFCORE-1985:
-------------------------------------
Assignee: Jiri Ondrusek (was: Ken Wills)
> :read-resource-description operation should consistently order resources by alphabet
> ------------------------------------------------------------------------------------
>
> Key: WFCORE-1985
> URL: https://issues.jboss.org/browse/WFCORE-1985
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Michal Jurc
> Assignee: Jiri Ondrusek
>
> While {{:read-resource-description}} returns an ordered list of resources with their descriptions for most resources, some resources do not return result consistent with this (resources ordered by alphabet).
> Affected resources:
> * {{/subsystem=iiop-openjdk:read-resource-description()}} returns unordered list of resources and their descriptions, while {{/subsystem=iiop-openjdk:read-resource()}} returns ordered list
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-2310) JDBC driver not deployed from exploded EAR, but works with packaged .ear
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-2310?page=com.atlassian.jira.plugin.... ]
David Lloyd reassigned WFLY-2310:
---------------------------------
Assignee: (was: David Lloyd)
> JDBC driver not deployed from exploded EAR, but works with packaged .ear
> ------------------------------------------------------------------------
>
> Key: WFLY-2310
> URL: https://issues.jboss.org/browse/WFLY-2310
> Project: WildFly
> Issue Type: Bug
> Components: EE, JCA
> Affects Versions: 8.0.0.Beta1
> Reporter: Paul Alesius
> Labels: deployer,, exploded
> Attachments: testear.zip
>
>
> The jdbc driver in an exploded EAR isn't picked up by wildfly, it causes problems when deploying from eclipse.
> It is picked up when deployed as a zipped .ear.
> Example jboss-as.xml in the ear with xa driver:
> <driver>testear-0.0.1-SNAPSHOT.ear_org.postgresql.Driver_9_2</driver>
> You should see a message when the ear is deployed showing that the JDBC is picked up byt he server. This appears only when the .ear is zipped.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-3588) Undertow subsystem should support arbitrary options
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-3588?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-3588:
-----------------------------------
We've been moving away from dynamic options in the model towards static properties that can be verified in the model, documented, etc. Do we still want this?
> Undertow subsystem should support arbitrary options
> ---------------------------------------------------
>
> Key: WFLY-3588
> URL: https://issues.jboss.org/browse/WFLY-3588
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Tomaz Cerar
>
> At the moment all well known options are hard coded in the schema. We should also support dynamic options where the class name is specified. This will allow the use of user defined options.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-4522) Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
by Edvin Syse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4522?page=com.atlassian.jira.plugin.... ]
Edvin Syse commented on WFLY-4522:
----------------------------------
You're right, this will only be an option as long as we stay with Java 8. When we switch to Java 9 (or 10) I will just ask the vendor to realize it's 2018 and provide a better option :)
I don't even know exactly what they are being used for, and the more I think about this the more I agree that it probably shouldn't be added. I can continue to use my workaround until I'm upgrading to Java 9/10.
In fairness, I created this ticket in 2015, at which time it would have made more sense IMO.
> Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
> --------------------------------------------------------------------
>
> Key: WFLY-4522
> URL: https://issues.jboss.org/browse/WFLY-4522
> Project: WildFly
> Issue Type: Task
> Components: Class Loading, Web Services
> Affects Versions: 9.0.0.Beta2
> Reporter: Edvin Syse
> Assignee: David Lloyd
>
> The following paths are needed for xws-security:
> com/sun/org/apache/xml/internal/security
> com/sun/org/apache/xml/internal/security/exceptions
> com/sun/org/apache/xerces/internal/jaxp
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-4522) Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-4522?page=com.atlassian.jira.plugin.... ]
David Lloyd commented on WFLY-4522:
-----------------------------------
Starting in Java 9, these classes are (I believe) inaccessible hidden members of the {{java.xml.crypto}} module so I'm not sure that this solution is going to continue to work for you much longer. In addition I believe we have our own SAAJ implementation so that might be a factor. Since we're using CXF for most JAX-WS things, including providing our own API spec JAR (not the JDK's), I think you'll have to use CXF's implementation. The JDK classes will not interoperate with ours.
Unfortunately I don't know much about xws-security itself, but my brief googling seemed to imply that it's mostly configuration driven. Can I ask what classes you're accessing, and what you're using them for?
> Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
> --------------------------------------------------------------------
>
> Key: WFLY-4522
> URL: https://issues.jboss.org/browse/WFLY-4522
> Project: WildFly
> Issue Type: Task
> Components: Class Loading, Web Services
> Affects Versions: 9.0.0.Beta2
> Reporter: Edvin Syse
> Assignee: David Lloyd
>
> The following paths are needed for xws-security:
> com/sun/org/apache/xml/internal/security
> com/sun/org/apache/xml/internal/security/exceptions
> com/sun/org/apache/xerces/internal/jaxp
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-4522) Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
by Edvin Syse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4522?page=com.atlassian.jira.plugin.... ]
Edvin Syse commented on WFLY-4522:
----------------------------------
I'm forced to use the xws-security API for certain (old) web services using JAX-WS with authentication. The API classes are supplied by the owner of the API, so it's not an option for me to use CXF. As the API is still supported in the JDK, I feel they should still be supported by JBoss as well :)
> Add 'com/sun/org/apache/xml/internal/security'++ to 'sun.jdk' module
> --------------------------------------------------------------------
>
> Key: WFLY-4522
> URL: https://issues.jboss.org/browse/WFLY-4522
> Project: WildFly
> Issue Type: Task
> Components: Class Loading, Web Services
> Affects Versions: 9.0.0.Beta2
> Reporter: Edvin Syse
> Assignee: David Lloyd
>
> The following paths are needed for xws-security:
> com/sun/org/apache/xml/internal/security
> com/sun/org/apache/xml/internal/security/exceptions
> com/sun/org/apache/xerces/internal/jaxp
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9849) Hibernate session related leak on module undeployment
by Joni Syri (JIRA)
[ https://issues.jboss.org/browse/WFLY-9849?page=com.atlassian.jira.plugin.... ]
Joni Syri updated WFLY-9849:
----------------------------
Affects Version/s: 12.0.0.Final
> Hibernate session related leak on module undeployment
> -----------------------------------------------------
>
> Key: WFLY-9849
> URL: https://issues.jboss.org/browse/WFLY-9849
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Environment: * Ubuntu 16.04.3 LTS
> * OpenJDK 1.8.0_151
> * Wildfly 11.0.0.Final
> Seems to occur at least on CentOS 7/OpenJDK 1.8.0_151 also.
> Reporter: Joni Syri
> Assignee: Jason Greene
>
> In some cases it seems that removing deployment from the Wildfly, doesn't free up {{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus some other Hibernate related classes). This can be seen by taking memory dump with VisualVM and looking up {{SessionFactoryImpl}} instances.
> This leads to cumulative memory leak in cases, where application is repeatedly deployed/undeployed (or updated).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9849) Hibernate session related leak on module undeployment
by Joni Syri (JIRA)
[ https://issues.jboss.org/browse/WFLY-9849?page=com.atlassian.jira.plugin.... ]
Joni Syri updated WFLY-9849:
----------------------------
Description:
In some cases it seems that removing deployment from the Wildfly, doesn't free up {{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus some other Hibernate related classes). This can be seen by taking memory dump with VisualVM and looking up {{SessionFactoryImpl}} instances.
This leads to cumulative memory leak in cases, where application is repeatedly deployed/undeployed (or updated).
updated: Seems to occur on 12.0.0.Final also
was:
In some cases it seems that removing deployment from the Wildfly, doesn't free up {{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus some other Hibernate related classes). This can be seen by taking memory dump with VisualVM and looking up {{SessionFactoryImpl}} instances.
This leads to cumulative memory leak in cases, where application is repeatedly deployed/undeployed (or updated).
> Hibernate session related leak on module undeployment
> -----------------------------------------------------
>
> Key: WFLY-9849
> URL: https://issues.jboss.org/browse/WFLY-9849
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 11.0.0.Final, 12.0.0.Final
> Environment: * Ubuntu 16.04.3 LTS
> * OpenJDK 1.8.0_151
> * Wildfly 11.0.0.Final
> Seems to occur at least on CentOS 7/OpenJDK 1.8.0_151 also.
> Reporter: Joni Syri
> Assignee: Jason Greene
>
> In some cases it seems that removing deployment from the Wildfly, doesn't free up {{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus some other Hibernate related classes). This can be seen by taking memory dump with VisualVM and looking up {{SessionFactoryImpl}} instances.
> This leads to cumulative memory leak in cases, where application is repeatedly deployed/undeployed (or updated).
> updated: Seems to occur on 12.0.0.Final also
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months