[JBoss JIRA] (WFLY-2907) Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2907?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-2907:
-----------------------------------
Can you verify if this is still problem in WildFly 8.1.0.CR1?
> Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error
> --------------------------------------------------------------------------
>
> Key: WFLY-2907
> URL: https://issues.jboss.org/browse/WFLY-2907
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: Trinidad 2
> Reporter: deepak vohra
>
> A Trinidad 2 UI page generates following exception. Application runs fine on JBoss AS 8.
> {noformat}
> java.lang.NullPointerException
> at com.sun.el.ValueExpressionLiteral.getValue(ValueExpressionLiteral.java:79) [javax.el-3.0-b07.jar:3.0-b07]
> at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperty(UIXComponentELTag.java:109) [trinidad-api-2.0.1.jar:2.0.1]
> at org.apache.myfaces.trinidadinternal.taglib.core.nav.CoreCommandLinkTag.setProperties(CoreCommandLinkTag.java:251) [trinidad-impl-2.0.1.jar:2.0.1]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:96) [trinidad-api-2.0.1.jar:2.0.1]
> at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:230) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.createChild(UIComponentClassicTagBase.java:504) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:742) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1309) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:67) [trinidad-api-2.0.1.jar:2.0.1]
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fcommandLink_005f0(index_jsp.java:252)
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fform_005f0(index_jsp.java:208)
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fdocument_005f0(index_jsp.java:161)
> at org.apache.jsp.index_jsp._jspx_meth_f_005fview_005f0(index_jsp.java:118)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:80)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> ... 54 more
> {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
10 years, 5 months
[JBoss JIRA] (WFLY-2907) Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2907?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-2907:
------------------------------
Description:
A Trinidad 2 UI page generates following exception. Application runs fine on JBoss AS 8.
{noformat}
java.lang.NullPointerException
at com.sun.el.ValueExpressionLiteral.getValue(ValueExpressionLiteral.java:79) [javax.el-3.0-b07.jar:3.0-b07]
at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperty(UIXComponentELTag.java:109) [trinidad-api-2.0.1.jar:2.0.1]
at org.apache.myfaces.trinidadinternal.taglib.core.nav.CoreCommandLinkTag.setProperties(CoreCommandLinkTag.java:251) [trinidad-impl-2.0.1.jar:2.0.1]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:96) [trinidad-api-2.0.1.jar:2.0.1]
at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:230) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.createChild(UIComponentClassicTagBase.java:504) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:742) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1309) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:67) [trinidad-api-2.0.1.jar:2.0.1]
at org.apache.jsp.index_jsp._jspx_meth_tr_005fcommandLink_005f0(index_jsp.java:252)
at org.apache.jsp.index_jsp._jspx_meth_tr_005fform_005f0(index_jsp.java:208)
at org.apache.jsp.index_jsp._jspx_meth_tr_005fdocument_005f0(index_jsp.java:161)
at org.apache.jsp.index_jsp._jspx_meth_f_005fview_005f0(index_jsp.java:118)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:80)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
... 54 more
{noformat}
was:
A Trinidad 2 UI page generates following exception. Application runs fine on JBoss AS 8.
java.lang.NullPointerException
at com.sun.el.ValueExpressionLiteral.getValue(ValueExpressionLiteral.java:79) [javax.el-3.0-b07.jar:3.0-b07]
at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperty(UIXComponentELTag.java:109) [trinidad-api-2.0.1.jar:2.0.1]
at org.apache.myfaces.trinidadinternal.taglib.core.nav.CoreCommandLinkTag.setProperties(CoreCommandLinkTag.java:251) [trinidad-impl-2.0.1.jar:2.0.1]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:96) [trinidad-api-2.0.1.jar:2.0.1]
at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:230) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.createChild(UIComponentClassicTagBase.java:504) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:742) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1309) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:67) [trinidad-api-2.0.1.jar:2.0.1]
at org.apache.jsp.index_jsp._jspx_meth_tr_005fcommandLink_005f0(index_jsp.java:252)
at org.apache.jsp.index_jsp._jspx_meth_tr_005fform_005f0(index_jsp.java:208)
at org.apache.jsp.index_jsp._jspx_meth_tr_005fdocument_005f0(index_jsp.java:161)
at org.apache.jsp.index_jsp._jspx_meth_f_005fview_005f0(index_jsp.java:118)
at org.apache.jsp.index_jsp._jspService(index_jsp.java:80)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
... 54 more
> Trinidad applications runs fine on JBoss AS 7, but on AS 8 generates error
> --------------------------------------------------------------------------
>
> Key: WFLY-2907
> URL: https://issues.jboss.org/browse/WFLY-2907
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Environment: Trinidad 2
> Reporter: deepak vohra
>
> A Trinidad 2 UI page generates following exception. Application runs fine on JBoss AS 8.
> {noformat}
> java.lang.NullPointerException
> at com.sun.el.ValueExpressionLiteral.getValue(ValueExpressionLiteral.java:79) [javax.el-3.0-b07.jar:3.0-b07]
> at org.apache.jasper.el.JspValueExpression.getValue(JspValueExpression.java:101) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperty(UIXComponentELTag.java:109) [trinidad-api-2.0.1.jar:2.0.1]
> at org.apache.myfaces.trinidadinternal.taglib.core.nav.CoreCommandLinkTag.setProperties(CoreCommandLinkTag.java:251) [trinidad-impl-2.0.1.jar:2.0.1]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.setProperties(UIXComponentELTag.java:96) [trinidad-api-2.0.1.jar:2.0.1]
> at javax.faces.webapp.UIComponentELTag.createComponent(UIComponentELTag.java:230) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.createChild(UIComponentClassicTagBase.java:504) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.findComponent(UIComponentClassicTagBase.java:742) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at javax.faces.webapp.UIComponentClassicTagBase.doStartTag(UIComponentClassicTagBase.java:1309) [jboss-jsf-api_2.2_spec-2.2.4.jar:2.2.4]
> at org.apache.myfaces.trinidad.webapp.UIXComponentELTag.doStartTag(UIXComponentELTag.java:67) [trinidad-api-2.0.1.jar:2.0.1]
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fcommandLink_005f0(index_jsp.java:252)
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fform_005f0(index_jsp.java:208)
> at org.apache.jsp.index_jsp._jspx_meth_tr_005fdocument_005f0(index_jsp.java:161)
> at org.apache.jsp.index_jsp._jspx_meth_f_005fview_005f0(index_jsp.java:118)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:80)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) [jboss-servlet-api_3.1_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:366) [jastow-1.0.0.CR1.jar:1.0.0.CR1]
> ... 54 more
> {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
10 years, 5 months
[JBoss JIRA] (WFLY-2493) EL cannot access public methods/fields of non-public classes
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2493?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-2493:
------------------------------
Affects Version/s: JBoss AS7 7.2.0.Final
> EL cannot access public methods/fields of non-public classes
> ------------------------------------------------------------
>
> Key: WFLY-2493
> URL: https://issues.jboss.org/browse/WFLY-2493
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: JBoss AS7 7.2.0.Final
> Environment: JBoss AS 7.2.0.Final
> Reporter: Jonáš Trantina
> Attachments: elresolver_stack, reproducer.zip
>
>
> When trying to access public method/field of non-public class that implements public interface via EL I get
> {noformat}
> java.lang.IllegalAccessException: Class javax.el.BeanELResolver can not access a member of class X with modifiers "private"
> {noformat}
> E.g. accessing Collections.unmodifiableList(..).size() via EL will throw the exception, because #unmodifiableList returns non-public implementation of List interface.
> This is apparently caused by JDK-4071957 [1], but since that is opened for over 16 years, it should be probably worth it to implement a workaround.
> Workaround for this issue is setting setAccessible(true) on the method before invoking it, thus suppress Java access checking.
> I have attached a simple reproducer app as well as a stack trace of the exception.
> [1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4071957
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-2937) Lack of Native Mgmt Makes Maven Plugin Unusable OTB
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-2937?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-2937:
-----------------------------------
wildfly-maven-plugin works just fine without native mgmt port open...
> Lack of Native Mgmt Makes Maven Plugin Unusable OTB
> ---------------------------------------------------
>
> Key: WFLY-2937
> URL: https://issues.jboss.org/browse/WFLY-2937
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 8.0.0.Final
> Reporter: Bill Burke
>
> jboss-as-maven-plugin and wildfly-maven-plugin use the native-management interface. Starting in Wildfly 8.0.0.Final, this management interface has been turned off and you have to manually add it in order to use the plugin. Any reason it can't be turned back on in the distro? Other than port reduction? At least until there is a maven plugin solution?
> This may not seem like a big deal, but it is seriously annoying for users. Especially those unknowledgable enough to figure out why their jboss-maven-plugin no longer works.
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-3068) could fail more gracefully when wrong Java version used
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3068?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3068:
------------------------------
Component/s: Class Loading
> could fail more gracefully when wrong Java version used
> -------------------------------------------------------
>
> Key: WFLY-3068
> URL: https://issues.jboss.org/browse/WFLY-3068
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Class Loading, Server
> Affects Versions: 8.0.0.Final
> Environment: Java version < 7
> Reporter: dpocock
> Priority: Minor
>
> If I try to start Wildfly with Java 6 (which is no longer support of course) it just fails with a stack:
> 09:51:00,536 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
> 09:51:00,543 WARN [org.jboss.modules] (main) Failed to define class org.jboss.as.jmx.PluggableMBeanServerBuilder in Module "org.jboss.as.jmx:main" from local module loader @36b60b93 (finder: local module finder @69b1fbf4 ()): java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.6.0_26]
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) [rt.jar:1.6.0_26]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615) [rt.jar:1.6.0_26]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:548) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373) [jboss-modules.jar:1.3.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118) [jboss-modules.jar:1.3.0.Final]
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213) [rt.jar:1.6.0_26]
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174) [rt.jar:1.6.0_26]
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302) [rt.jar:1.6.0_26]
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504) [rt.jar:1.6.0_26]
> at org.jboss.modules.Main.main(Main.java:449) [jboss-modules.jar:1.3.0.Final]
> Exception in thread "main" java.lang.UnsupportedClassVersionError: org/jboss/as/jmx/PluggableMBeanServerBuilder : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
> at org.jboss.modules.Module.loadModuleClass(Module.java:548)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:189)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:443)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:431)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:373)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:118)
> at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFactory.java:423)
> at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServerFactory.java:465)
> at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanServerFactory.java:511)
> at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory.java:298)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:213)
> at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFactory.java:174)
> at sun.management.ManagementFactory.createPlatformMBeanServer(ManagementFactory.java:302)
> at java.lang.management.ManagementFactory.getPlatformMBeanServer(ManagementFactory.java:504)
> at org.jboss.modules.Main.main(Main.java:449)
> It would be more friendly if it checked the Java version in the main() function and stopped gracefully. The stack trace is not hard to understand but may not be obvious to everybody.
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-3267) Confusing error message when tag file's attribute type is unknown
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3267?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3267:
------------------------------
Component/s: Web (Undertow)
(was: Web (JBoss Web))
> Confusing error message when tag file's attribute type is unknown
> -----------------------------------------------------------------
>
> Key: WFLY-3267
> URL: https://issues.jboss.org/browse/WFLY-3267
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Paul B
> Assignee: Remy Maucherat
> Priority: Trivial
>
> I have a JSP tag file that requires a "size" attribute:
> {code}
> <%@ attribute name="size" required="true" type="Long" %>
> {code}
> Because the type accidentally wasn't a FQN (it should have been a {{java.lang.Long}}), this error was generated:
> {code}
> JBWEB004193: Unknown attribute type (size) for attribute Number
> {code}
> The message doesn't make any sense. "size" isn't the attribute type and the attribute is not "Number". A possible fix:
> {code}
> JBWEB004193: Unknown type (Number) was declared for attribute (size)
> {code}
> PS: It's really important to talk about the "declaration" here because the tag file isn't mentioned at all in the exception. The Jasper compiler only reports the enclosing JSP, which makes it look like the problem is with the usage not the tag file itself.
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-3267) Confusing error message when tag file's attribute type is unknown
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3267?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3267:
-----------------------------------
You get any different result if you try running on WildFly 8.1.0.CR1?
> Confusing error message when tag file's attribute type is unknown
> -----------------------------------------------------------------
>
> Key: WFLY-3267
> URL: https://issues.jboss.org/browse/WFLY-3267
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: Paul B
> Assignee: Remy Maucherat
> Priority: Trivial
>
> I have a JSP tag file that requires a "size" attribute:
> {code}
> <%@ attribute name="size" required="true" type="Long" %>
> {code}
> Because the type accidentally wasn't a FQN (it should have been a {{java.lang.Long}}), this error was generated:
> {code}
> JBWEB004193: Unknown attribute type (size) for attribute Number
> {code}
> The message doesn't make any sense. "size" isn't the attribute type and the attribute is not "Number". A possible fix:
> {code}
> JBWEB004193: Unknown type (Number) was declared for attribute (size)
> {code}
> PS: It's really important to talk about the "declaration" here because the tag file isn't mentioned at all in the exception. The Jasper compiler only reports the enclosing JSP, which makes it look like the problem is with the usage not the tag file itself.
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-3267) Confusing error message when tag file's attribute type is unknown
by Paul B (JIRA)
Paul B created WFLY-3267:
----------------------------
Summary: Confusing error message when tag file's attribute type is unknown
Key: WFLY-3267
URL: https://issues.jboss.org/browse/WFLY-3267
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (JBoss Web)
Affects Versions: 8.0.0.Final
Reporter: Paul B
Assignee: Remy Maucherat
Priority: Trivial
I have a JSP tag file that requires a "size" attribute:
{code}
<%@ attribute name="size" required="true" type="Long" %>
{code}
Because the type accidentally wasn't a FQN (it should have been a {{java.lang.Long}}), this error was generated:
{code}
JBWEB004193: Unknown attribute type (size) for attribute Number
{code}
The message doesn't make any sense. "size" isn't the attribute type and the attribute is not "Number". A possible fix:
{code}
JBWEB004193: Unknown type (Number) was declared for attribute (size)
{code}
PS: It's really important to talk about the "declaration" here because the tag file isn't mentioned at all in the exception. The Jasper compiler only reports the enclosing JSP, which makes it look like the problem is with the usage not the tag file itself.
--
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
10 years, 5 months
[JBoss JIRA] (WFLY-3104) datasource created with console cannot be enabled
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3104?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-3104:
------------------------------
Affects Version/s: 8.0.0.Final
> datasource created with console cannot be enabled
> -------------------------------------------------
>
> Key: WFLY-3104
> URL: https://issues.jboss.org/browse/WFLY-3104
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Final
> Environment: Wildfly 8.0.0 Final
> Reporter: Gabriele Garuglieri
>
> Consider the following cli file:
> {noformat}
> /subsystem=datasources/data-source=fai-bfsa:add( \
> driver-name=PostgresJDBCDriver, \
> driver-class="org.postgresql.Driver", \
> jndi-name=java:jboss/jdbc/fai-bfsa, \
> connection-url=jdbc:postgresql://tpg0001:5432/xfgb01, \
> max-pool-size=20, \
> min-pool-size=10, \
> new-connection-sql="select 1", \
> check-valid-connection-sql="select 1", \
> user-name=uuuuu, \
> password=uuuuu, \
> background-validation=false, \
> validate-on-match=false, \
> enabled=false, \
> jta=true, \
> use-ccm=true, \
> share-prepared-statements=false, \
> )
> {noformat}
> This is reflected into standalone-full.xml as:
> {code:xml}
> <datasource jta="true" jndi-name="java:jboss/jdbc/fai-bfsa" pool-name="fai-bfsa" enabled="false" use-ccm="true">
> <connection-url>jdbc:postgresql://tpg0001:5432/xfgb01</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>PostgresJDBCDriver</driver>
> <new-connection-sql>select 1</new-connection-sql>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>20</max-pool-size>
> </pool>
> <security>
> <user-name>uuuuu</user-name>
> <password>uuuuu</password>
> </security>
> <validation>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <validate-on-match>false</validate-on-match>
> <background-validation>false</background-validation>
> </validation>
> <statement>
> <share-prepared-statements>false</share-prepared-statements>
> </statement>
> </datasource>
> {code}
> I can now enable and disable that datasource both via cli or console without problem.
> If i create the same datasource via console, with the very same attributes, producing the very same standalone-full.xml (i have diffed them), i cannot enable it nether via cli nor console because i get the following error:
> {noformat}
> 14:33:00,230 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-3) Error during the deployment of java:jboss/jdbc/fai-bfsa: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.getTransactionIntegration(AbstractDataSourceService.java:409)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.createMcf(AbstractDataSourceService.java:461)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:430)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:283)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:310)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:124)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 14:33:00,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.data-source.java:jboss/jdbc/fai-bfsa: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/jdbc/fai-bfsa: JBAS010433: Error during the deployment of fai-bfsa
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:131)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:126)
> ... 5 more
> 14:33:00,242 INFO [org.jboss.as.controller] (XNIO-4 task-2) JBAS014774: Servicestatus report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.data-source.reference-factory.fai-bfsa (missing) dependents:[service jboss.naming.context.java.jboss.jdbc.fai-bfsa]
> service jboss.data-source-config.fai-bfsa (missing) dependents: [service jboss.data-source.java:jboss/jdbc/fai-bfsa]
> JBAS014777: Services which failed to start: service jboss.data-source.java:jboss/jdbc/fai-bfsa
> {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
10 years, 5 months
[JBoss JIRA] (WFLY-3104) datasource created with console cannot be enabled
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3104?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-3104:
---------------------------------
Assignee: Stefano Maestri
> datasource created with console cannot be enabled
> -------------------------------------------------
>
> Key: WFLY-3104
> URL: https://issues.jboss.org/browse/WFLY-3104
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.0.Final
> Environment: Wildfly 8.0.0 Final
> Reporter: Gabriele Garuglieri
> Assignee: Stefano Maestri
>
> Consider the following cli file:
> {noformat}
> /subsystem=datasources/data-source=fai-bfsa:add( \
> driver-name=PostgresJDBCDriver, \
> driver-class="org.postgresql.Driver", \
> jndi-name=java:jboss/jdbc/fai-bfsa, \
> connection-url=jdbc:postgresql://tpg0001:5432/xfgb01, \
> max-pool-size=20, \
> min-pool-size=10, \
> new-connection-sql="select 1", \
> check-valid-connection-sql="select 1", \
> user-name=uuuuu, \
> password=uuuuu, \
> background-validation=false, \
> validate-on-match=false, \
> enabled=false, \
> jta=true, \
> use-ccm=true, \
> share-prepared-statements=false, \
> )
> {noformat}
> This is reflected into standalone-full.xml as:
> {code:xml}
> <datasource jta="true" jndi-name="java:jboss/jdbc/fai-bfsa" pool-name="fai-bfsa" enabled="false" use-ccm="true">
> <connection-url>jdbc:postgresql://tpg0001:5432/xfgb01</connection-url>
> <driver-class>org.postgresql.Driver</driver-class>
> <driver>PostgresJDBCDriver</driver>
> <new-connection-sql>select 1</new-connection-sql>
> <pool>
> <min-pool-size>10</min-pool-size>
> <max-pool-size>20</max-pool-size>
> </pool>
> <security>
> <user-name>uuuuu</user-name>
> <password>uuuuu</password>
> </security>
> <validation>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <validate-on-match>false</validate-on-match>
> <background-validation>false</background-validation>
> </validation>
> <statement>
> <share-prepared-statements>false</share-prepared-statements>
> </statement>
> </datasource>
> {code}
> I can now enable and disable that datasource both via cli or console without problem.
> If i create the same datasource via console, with the very same attributes, producing the very same standalone-full.xml (i have diffed them), i cannot enable it nether via cli nor console because i get the following error:
> {noformat}
> 14:33:00,230 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-3) Error during the deployment of java:jboss/jdbc/fai-bfsa: java.lang.IllegalStateException
> at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.getTransactionIntegration(AbstractDataSourceService.java:409)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.createMcf(AbstractDataSourceService.java:461)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:430)
> at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:283)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:310)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:124)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> 14:33:00,236 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.data-source.java:jboss/jdbc/fai-bfsa: org.jboss.msc.service.StartException in service jboss.data-source.java:jboss/jdbc/fai-bfsa: JBAS010433: Error during the deployment of fai-bfsa
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:131)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
> Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS010432: Unable to start the ds because it generated more than one cf
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:126)
> ... 5 more
> 14:33:00,242 INFO [org.jboss.as.controller] (XNIO-4 task-2) JBAS014774: Servicestatus report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.data-source.reference-factory.fai-bfsa (missing) dependents:[service jboss.naming.context.java.jboss.jdbc.fai-bfsa]
> service jboss.data-source-config.fai-bfsa (missing) dependents: [service jboss.data-source.java:jboss/jdbc/fai-bfsa]
> JBAS014777: Services which failed to start: service jboss.data-source.java:jboss/jdbc/fai-bfsa
> {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
10 years, 5 months