[JBoss JIRA] (WFLY-3538) Application does not deploy because DefaultDataSource is missing
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3538?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-3538:
-----------------------------------
better version of undefining attribute would be
{code}
/subsystem=ee/service=default-bindings:undefine-attribute(name=datasource)
{code}
but both should do the work
> Application does not deploy because DefaultDataSource is missing
> ----------------------------------------------------------------
>
> Key: WFLY-3538
> URL: https://issues.jboss.org/browse/WFLY-3538
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Environment: Debian linux 7.5, openjdk 7u55-2.4.7-1~deb7u1, Wildfly 8.1.0.Final
> Reporter: Peter Van Biesen
> Assignee: Chao Wang
>
> On our servers, the ExampleDs is removed from the config. In 7.2.0, this poses no problem, but in the 8.1.0.Final, when we deploy an application, the default datasource needs to be available, even if the application does not use a datasource. The error :
> {code}
> failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jolokia.jolokia.DefaultDataSource is missing [jboss.naming.context.java.jboss.datasources.ExampleDS]"]}
> {code}
> The example above is for the deployment of the jolokia war.
> To reproduce :
> * remove ExampleDS
> * deploy any application
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBJCA-1227) Use Message Patterns for Debug Logging
by Philippe Marschall (JIRA)
Philippe Marschall created JBJCA-1227:
-----------------------------------------
Summary: Use Message Patterns for Debug Logging
Key: JBJCA-1227
URL: https://issues.jboss.org/browse/JBJCA-1227
Project: IronJacamar
Issue Type: Patch
Reporter: Philippe Marschall
Assignee: Jesper Pedersen
There are several places where IronJacamar uses string concatenation for debug messages resulting in unnecessary allocation when debug logging is not on.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3255) IllegalArgumentException occurs while accessing the handler information via JMX MBean?
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3255?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3255:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1087146|https://bugzilla.redhat.com/show_bug.cgi?id=1087146] from POST to MODIFIED
> IllegalArgumentException occurs while accessing the handler information via JMX MBean?
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-3255
> URL: https://issues.jboss.org/browse/WFLY-3255
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 8.1.0.CR1
> Reporter: Jay Kumar SenSharma
> Assignee: James Perkins
> Labels: dmr
> Fix For: 9.0.0.Alpha1
>
> Attachments: WFLY-3255_TestCase.zip
>
>
> - While trying to get the "handler" information via JMX code the following kind of exception is encountered:
> {code}
> 12:09:24,853 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /LoggerJMX/index.jsp: org.apache.jasper.JasperException: java.lang.IllegalArgumentException
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:410) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:259) [jastow-1.0.0.Final.jar:1.0.0.Final]
> 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 io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getChild(ModelValue.java:112)
> at org.jboss.dmr.ModelNode.get(ModelNode.java:856)
> at org.jboss.as.jmx.model.TypeConverters$ComplexTypeConverter.fromModelNode(TypeConverters.java:538)
> at org.jboss.as.jmx.model.TypeConverters$ListTypeConverter.fromModelNode(TypeConverters.java:444)
> at org.jboss.as.jmx.model.TypeConverters.fromModelNode(TypeConverters.java:114)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:245)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:200)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getAttribute(ModelControllerMBeanServerPlugin.java:96)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:384)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:73)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.Final.jar:1.0.0.Final]
> 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.Final.jar:1.0.0.Final]
> ... 28 more
> {code}
> - The Handler is configured as following:
> {code}
> <logger category="org.jboss.as.config">
> <handlers>
> <handler name="CONSOLE"/>
> </handlers>
> <level name="DEBUG"/>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3538) Application does not deploy because DefaultDataSource is missing
by Dirk Rademann (JIRA)
[ https://issues.jboss.org/browse/WFLY-3538?page=com.atlassian.jira.plugin.... ]
Dirk Rademann commented on WFLY-3538:
-------------------------------------
I had the same problem after I deleted the {{ExampleDS}} cause I thought I wouldn't need it. Your CLI commands fixed that. Thank you, [~soul2zimate].
> Application does not deploy because DefaultDataSource is missing
> ----------------------------------------------------------------
>
> Key: WFLY-3538
> URL: https://issues.jboss.org/browse/WFLY-3538
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 8.1.0.Final
> Environment: Debian linux 7.5, openjdk 7u55-2.4.7-1~deb7u1, Wildfly 8.1.0.Final
> Reporter: Peter Van Biesen
> Assignee: Chao Wang
>
> On our servers, the ExampleDs is removed from the config. In 7.2.0, this poses no problem, but in the 8.1.0.Final, when we deploy an application, the default datasource needs to be available, even if the application does not use a datasource. The error :
> {code}
> failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jolokia.jolokia.DefaultDataSource is missing [jboss.naming.context.java.jboss.datasources.ExampleDS]"]}
> {code}
> The example above is for the deployment of the jolokia war.
> To reproduce :
> * remove ExampleDS
> * deploy any application
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3968) access log doesn't support %{r, xxx}
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/WFLY-3968?page=com.atlassian.jira.plugin.... ]
Vsevolod Golovanov commented on WFLY-3968:
------------------------------------------
The workaround works, thanks.
> access log doesn't support %{r,xxx}
> -----------------------------------
>
> Key: WFLY-3968
> URL: https://issues.jboss.org/browse/WFLY-3968
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 9.0.0.Alpha1
> Environment: Wildfly 8.1.0.Final
> Reporter: Vsevolod Golovanov
> Assignee: Stuart Douglas
>
> AccessLogHandler's javadoc mentions:
> {quote}
> {{%\{r,xxx\}}} xxx is an attribute in the ServletRequest
> {quote}
> But adding the following to access log pattern
> {code}
> %{r,javax.servlet.error.status_code}
> {code}
> results in a server log message:
> {code}
> 19:55:55,432 ERROR [undertow] (MSC service thread 1-6) UT005017: Unknown variable %{r,javax.servlet.error.status_code}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3255) IllegalArgumentException occurs while accessing the handler information via JMX MBean?
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3255?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3255:
-----------------------------------------------
James Perkins <jperkins(a)redhat.com> changed the Status of [bug 1087146|https://bugzilla.redhat.com/show_bug.cgi?id=1087146] from ASSIGNED to POST
> IllegalArgumentException occurs while accessing the handler information via JMX MBean?
> ---------------------------------------------------------------------------------------
>
> Key: WFLY-3255
> URL: https://issues.jboss.org/browse/WFLY-3255
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 8.1.0.CR1
> Reporter: Jay Kumar SenSharma
> Assignee: James Perkins
> Labels: dmr
> Fix For: 9.0.0.Alpha1
>
> Attachments: WFLY-3255_TestCase.zip
>
>
> - While trying to get the "handler" information via JMX code the following kind of exception is encountered:
> {code}
> 12:09:24,853 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /LoggerJMX/index.jsp: org.apache.jasper.JasperException: java.lang.IllegalArgumentException
> at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:410) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:326) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:259) [jastow-1.0.0.Final.jar:1.0.0.Final]
> 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 io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:113) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:56) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:45) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:61) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:58) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:70) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.security.handlers.SecurityInitialHandler.handleRequest(SecurityInitialHandler.java:76) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:25) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:240) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:227) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:73) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:146) [undertow-servlet-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:168) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:727) [undertow-core-1.0.5.Final.jar:1.0.5.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> Caused by: java.lang.IllegalArgumentException
> at org.jboss.dmr.ModelValue.getChild(ModelValue.java:112)
> at org.jboss.dmr.ModelNode.get(ModelNode.java:856)
> at org.jboss.as.jmx.model.TypeConverters$ComplexTypeConverter.fromModelNode(TypeConverters.java:538)
> at org.jboss.as.jmx.model.TypeConverters$ListTypeConverter.fromModelNode(TypeConverters.java:444)
> at org.jboss.as.jmx.model.TypeConverters.fromModelNode(TypeConverters.java:114)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:245)
> at org.jboss.as.jmx.model.ModelControllerMBeanHelper.getAttribute(ModelControllerMBeanHelper.java:200)
> at org.jboss.as.jmx.model.ModelControllerMBeanServerPlugin.getAttribute(ModelControllerMBeanServerPlugin.java:96)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.getAttribute(PluggableMBeanServerImpl.java:384)
> at org.apache.jsp.index_jsp._jspService(index_jsp.java:73)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:69) [jastow-1.0.0.Final.jar:1.0.0.Final]
> 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.Final.jar:1.0.0.Final]
> ... 28 more
> {code}
> - The Handler is configured as following:
> {code}
> <logger category="org.jboss.as.config">
> <handlers>
> <handler name="CONSOLE"/>
> </handlers>
> <level name="DEBUG"/>
> </logger>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (WFLY-3968) access log doesn't support %{r, xxx}
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-3968?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-3968:
--------------------------------------
This is actually a wildfly issues, the servlet support is provided via the service loader pattern, and the wrong class loader was used to initialise the access log handler.
You should be able to work around this by adding an dependency that imports services on the io.undertow.servlet module in the io.undertow.core module.
> access log doesn't support %{r,xxx}
> -----------------------------------
>
> Key: WFLY-3968
> URL: https://issues.jboss.org/browse/WFLY-3968
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.1.0.Final, 9.0.0.Alpha1
> Environment: Wildfly 8.1.0.Final
> Reporter: Vsevolod Golovanov
> Assignee: Stuart Douglas
>
> AccessLogHandler's javadoc mentions:
> {quote}
> {{%\{r,xxx\}}} xxx is an attribute in the ServletRequest
> {quote}
> But adding the following to access log pattern
> {code}
> %{r,javax.servlet.error.status_code}
> {code}
> results in a server log message:
> {code}
> 19:55:55,432 ERROR [undertow] (MSC service thread 1-6) UT005017: Unknown variable %{r,javax.servlet.error.status_code}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years