[JBoss JIRA] (WFLY-3004) properties are not resolved for arguments of commands handled on the client-side
by Alexey Loubyansky (JIRA)
[ https://issues.jboss.org/browse/WFLY-3004?page=com.atlassian.jira.plugin.... ]
Alexey Loubyansky updated WFLY-3004:
------------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/6019
> properties are not resolved for arguments of commands handled on the client-side
> --------------------------------------------------------------------------------
>
> Key: WFLY-3004
> URL: https://issues.jboss.org/browse/WFLY-3004
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CLI
> Affects Versions: 8.0.0.Final
> Environment: windows 7 and centos 6.4
> Reporter: Gabriele Garuglieri
> Assignee: Alexey Loubyansky
> Fix For: 8.0.1.Final
>
>
> When using cli for batch files using --file and --properties arguments, any property is resolved but for those defined in the connect command line.
> The properties file contains (among the others):
> server.bind.addr = xxxxx
> server.management.port = 9990
> Having:
> connect ${server.bind.addr}
> in the batch file gets
> ERROR [org.jboss.as.cli.CommandContext] Failed to resolve host '${server.bind.addr}': Failed to create URI: Illegal character in authority at index 16: http-remoting://${server.bind.addr}:9990
> Having:
> connect ${server.bind.addr}:${server.management.port}
> gets:
> ERROR [org.jboss.as.cli.CommandContext] The port must be a valid non-negative integer: '${server.bind.addr}:${server.management.
> If i use literal values for the connect command, any other property in the batch is correctly resolved (but that's exactly what i was trying to avoid)
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-3170) system properties are trim()'d and loose whitespace
by Tom Fonteyne (JIRA)
Tom Fonteyne created WFLY-3170:
----------------------------------
Summary: system properties are trim()'d and loose whitespace
Key: WFLY-3170
URL: https://issues.jboss.org/browse/WFLY-3170
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Domain Management
Affects Versions: 8.0.1.Final
Reporter: Tom Fonteyne
Assignee: Brian Stansberry
When a system property was defined as:
/system-property=foo:add(value=" spaces ");
it gets written with the correct spaces around it to the configuration file.
When the configuration is read the value gets trimmed and the prefix/suffix of spaces is lost.
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-2881) org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-2881?page=com.atlassian.jira.plugin.... ]
Eduardo Martins resolved WFLY-2881.
-----------------------------------
Fix Version/s: 8.0.1.Final
Resolution: Done
> org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase#testCalendarBasedTimeout
> --------------------------------------------------------------------------------------
>
> Key: WFLY-2881
> URL: https://issues.jboss.org/browse/WFLY-2881
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB
> Affects Versions: 8.0.0.Final
> Reporter: Frank Langelage
> Assignee: Eduardo Martins
> Fix For: 8.0.1.Final
>
> Attachments: org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.txt, TEST-org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.xml
>
>
> Running build with smoke tests on current github sources I get failure in this test case.
> HOUR_OF_DAY is not 0 as expected but 1.
> I changed the Assert in the test case to print out firstTimeout.toString() instead of only timeZoneDisplayName.
> See attached files for more.
--
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
12 years, 1 month
[JBoss JIRA] (JBWEB-293) NPE if method getClassLoader() returns null to represent the bootstrap class loader
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/JBWEB-293?page=com.atlassian.jira.plugin.... ]
Chao Wang resolved JBWEB-293.
-----------------------------
Resolution: Done
> NPE if method getClassLoader() returns null to represent the bootstrap class loader
> -----------------------------------------------------------------------------------
>
> Key: JBWEB-293
> URL: https://issues.jboss.org/browse/JBWEB-293
> Project: JBoss Web
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: JBossWeb-2.1.14.GA
> Reporter: Chao Wang
> Assignee: Chao Wang
> Attachments: JBWEB-293.patch
>
>
> from the scenario in [JBPAPP-11027|https://issues.jboss.org/browse/JBPAPP-11027] , and java code in java/javax/el/BeanELResolver.java :
> {code:title=BeanELResolver.java|borderStyle=solid}
> Iterator<Class<?>> iter = cache.keySet().iterator();
> while (iter.hasNext()) {
> Class<?> key = iter.next();
> BeanProperties bp = cache.get(key);
> if(bp.getType().getClassLoader().equals(classloader)){
> iter.remove();
> }
> }
> {code}
> Here, when key is "class java.lang.Class" and bp's type is "class java.lang.Class", method getClassLoader() returns null to represent the bootstrap class loader, then NPE as described is threw during stopping service jboss.web
> {noformat}
> cache content:
> class org.jboss.on.embedded.bean.ResourceListItem=javax.el.BeanELResolver$BeanProperties@36d4423d,
> class org.jboss.on.embedded.ui.NavigationAction_$$_javassist_seam_9=javax.el.BeanELResolver$BeanProperties@2948ceea,
> class org.jboss.on.embedded.ui.ResourceAction_$$_javassist_seam_12=javax.el.BeanELResolver$BeanProperties@6b0879d2,
> class org.jboss.on.embedded.ui.nav.SubCategoryTreeNode=javax.el.BeanELResolver$BeanProperties@797600e3,
> class org.jboss.on.embedded.ui.nav.PlatformResourceTreeNode=javax.el.BeanELResolver$BeanProperties@32347561,
> class java.lang.Class=javax.el.BeanELResolver$BeanProperties@12064d07,
> class org.jboss.on.embedded.ui.nav.SingletonResourceTypeTreeNode=javax.el.BeanELResolver$BeanProperties@5bab0fcf,
> class org.jboss.on.embedded.ui.nav.ResourceTreeNode=javax.el.BeanELResolver$BeanProperties@3b9b0e0d,
> class org.jboss.on.embedded.ui.nav.NonSingletonResourceTypeTreeNode=javax.el.BeanELResolver$BeanProperties@40b7960d,
> class org.rhq.core.domain.measurement.MeasurementDefinition=javax.el.BeanELResolver$BeanProperties@54dc50ac,
> class org.rhq.core.domain.resource.Resource=javax.el.BeanELResolver$BeanProperties@4c3477ba,
> class org.rhq.core.domain.measurement.MeasurementDataTrait=javax.el.BeanELResolver$BeanProperties@8a07b6c,
> class org.jboss.seam.security.Identity=javax.el.BeanELResolver$BeanProperties@6006f3e0,
> class org.jboss.on.embedded.bean.MeasurementDisplay=javax.el.BeanELResolver$BeanProperties@68752860}
> {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
12 years, 1 month
[JBoss JIRA] (WFLY-3169) Add JMX notifications for management resources
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-3169:
---------------------------------
Summary: Add JMX notifications for management resources
Key: WFLY-3169
URL: https://issues.jboss.org/browse/WFLY-3169
Project: WildFly
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: JMX
Reporter: Jeff Mesnil
Assignee: Kabir Khan
Based on WFLY-266, the JMX subsystem could provide standard JMX notifications for resource registered/unregistered and changes of attributes values.
--
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
12 years, 1 month
[JBoss JIRA] (WFLY-3168) Wrong Mojarra version on Linux
by Thorsten Richter (JIRA)
[ https://issues.jboss.org/browse/WFLY-3168?page=com.atlassian.jira.plugin.... ]
Thorsten Richter updated WFLY-3168:
-----------------------------------
Description:
We had a bug on Linux that the @ViewScoped annotation didn't work for AJAX requests. We found out, that the Mojarra version is causing the problem. On our Windows development machines everything worked fine, but on the Linux production server @ViewScoped didn't work.
So we searched for the root cause and found out, that the Mojarra version was different on Linux.
The Linux package of Wildfly contains an older version of Mojarra (2.1.7) within the modules/com/sun/jsf-impl folder that needs to be deleted.
The Windows package of Wildfly doesn't even contain a com folder within modules.
So maybe the whole com folder on Linux is wrong?
was:
We had a bug on Linux that the @ViewScoped annotation didn't work for AJAX requests. We found out, that the Mojarra version is causing the problem. On our Windows development machines everything worked fine, but on the Linux production server @ViewScoped didn't work.
So we searched for the root cause and found out, that the Mojarra version was different on Linux.
The Linux package contains an older version of Mojarra (2.1.7) within the modules/com/sun/jsf-impl folder that needs to be deleted.
The Windows package doesn't even contain a com folder within modules.
So maybe the whole com folder on Linux is wrong?
> Wrong Mojarra version on Linux
> ------------------------------
>
> Key: WFLY-3168
> URL: https://issues.jboss.org/browse/WFLY-3168
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.Final
> Environment: Linux
> Reporter: Thorsten Richter
> Assignee: Farah Juma
> Labels: jsf, linux, mojarra, viewscoped
>
> We had a bug on Linux that the @ViewScoped annotation didn't work for AJAX requests. We found out, that the Mojarra version is causing the problem. On our Windows development machines everything worked fine, but on the Linux production server @ViewScoped didn't work.
> So we searched for the root cause and found out, that the Mojarra version was different on Linux.
> The Linux package of Wildfly contains an older version of Mojarra (2.1.7) within the modules/com/sun/jsf-impl folder that needs to be deleted.
> The Windows package of Wildfly doesn't even contain a com folder within modules.
> So maybe the whole com folder on Linux is wrong?
--
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
12 years, 1 month