[JBoss JIRA] (WFLY-4025) Log Viewer [Download] does not work
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-4025?page=com.atlassian.jira.plugin.... ]
James Perkins commented on WFLY-4025:
-------------------------------------
I'll leave this open for now as a reminder, but it's just not implemented yet is all.
> Log Viewer [Download] does not work
> -----------------------------------
>
> Key: WFLY-4025
> URL: https://issues.jboss.org/browse/WFLY-4025
> Project: WildFly
> Issue Type: Bug
> Components: Logging, Web Console
> Affects Versions: 8.1.0.Final
> Reporter: Robert Smith
> Assignee: James Perkins
>
> We are running a domain mode configuration using Wildfly 8.1.0.Final 'Kenny'. The Log Viewer allows us to [View] logs but the download button does nothing. No error is reported in the server.log when pressing the button and the log file is not downloaded.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3262) WebServiceRef injection without explicit wsdl file fails during Servlet initialization
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-3262?page=com.atlassian.jira.plugin.... ]
R Searls resolved WFLY-3262.
----------------------------
Resolution: Won't Fix
This is not a bug. A new jira has been filed to address this scenario. Please see comments in this jira
> WebServiceRef injection without explicit wsdl file fails during Servlet initialization
> --------------------------------------------------------------------------------------
>
> Key: WFLY-3262
> URL: https://issues.jboss.org/browse/WFLY-3262
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.CR1
> Reporter: Matus Abaffy
> Assignee: R Searls
> Fix For: 9.0.0.CR1
>
>
> Reproducer test available at https://github.com/bafco/wildfly/commits/wsServletInjection
> I have the following servlet
> {code}
> @WebServlet(/*..., */ loadOnStartup = 1)
> public class ServletLoadOnStartup extends HttpServlet {
> @WebServiceRef(value = EndpointService.class)
> private EndpointInterface endpoint1;
> //...
> {code}
> (It is located in the package org.jboss.as.test.integration.ws.serviceref. There you can find more info about the other classes.)
> And i get the following exception:
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ws-servlet-test.war
> ...
> Caused by: java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./ws-servlet-test" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ws-servlet-test: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
> Caused by: java.lang.RuntimeException: JBAS011875: Resource lookup for injection failed: env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1
> Caused by: javax.naming.NamingException: JBAS011878: Failed to lookup env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1 [Root exception is org.jboss.wsf.spi.WSFException: Cannot create service]
> Caused by: org.jboss.wsf.spi.WSFException: Cannot create service
> Caused by: java.lang.reflect.InvocationTargetException
> Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl'.: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl
> Caused by: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl"}}
> {code}
> If I change loadOnStartup parameter to -1, everything works fine, i.e. servlet gets instantiated and WS is injected correctly. Therefore, I suppose this is a bug.
> Another workaround exists - adding wsdl file to the deployment archive and using the 'wsdlLocation' parameter in @WebServiceRef (as can be seen in ServiceRefSevletTestCase).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3262) WebServiceRef injection without explicit wsdl file fails during Servlet initialization
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-3262?page=com.atlassian.jira.plugin.... ]
R Searls commented on WFLY-3262:
--------------------------------
There is no way to uniquely identify this situation in order to provide a more detailed error message.
> WebServiceRef injection without explicit wsdl file fails during Servlet initialization
> --------------------------------------------------------------------------------------
>
> Key: WFLY-3262
> URL: https://issues.jboss.org/browse/WFLY-3262
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.CR1
> Reporter: Matus Abaffy
> Assignee: R Searls
> Fix For: 9.0.0.CR1
>
>
> Reproducer test available at https://github.com/bafco/wildfly/commits/wsServletInjection
> I have the following servlet
> {code}
> @WebServlet(/*..., */ loadOnStartup = 1)
> public class ServletLoadOnStartup extends HttpServlet {
> @WebServiceRef(value = EndpointService.class)
> private EndpointInterface endpoint1;
> //...
> {code}
> (It is located in the package org.jboss.as.test.integration.ws.serviceref. There you can find more info about the other classes.)
> And i get the following exception:
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ws-servlet-test.war
> ...
> Caused by: java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./ws-servlet-test" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ws-servlet-test: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
> Caused by: java.lang.RuntimeException: JBAS011875: Resource lookup for injection failed: env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1
> Caused by: javax.naming.NamingException: JBAS011878: Failed to lookup env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1 [Root exception is org.jboss.wsf.spi.WSFException: Cannot create service]
> Caused by: org.jboss.wsf.spi.WSFException: Cannot create service
> Caused by: java.lang.reflect.InvocationTargetException
> Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl'.: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl
> Caused by: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl"}}
> {code}
> If I change loadOnStartup parameter to -1, everything works fine, i.e. servlet gets instantiated and WS is injected correctly. Therefore, I suppose this is a bug.
> Another workaround exists - adding wsdl file to the deployment archive and using the 'wsdlLocation' parameter in @WebServiceRef (as can be seen in ServiceRefSevletTestCase).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFCORE-206) Exporting a value for LAUNCH_JBOSS_IN_BACKGROUND doesn't exit the script
by James Perkins (JIRA)
James Perkins created WFCORE-206:
------------------------------------
Summary: Exporting a value for LAUNCH_JBOSS_IN_BACKGROUND doesn't exit the script
Key: WFCORE-206
URL: https://issues.jboss.org/browse/WFCORE-206
Project: WildFly Core
Issue Type: Bug
Components: Scripts
Reporter: James Perkins
Assignee: James Perkins
There should be the ability to launch a server in a new process by setting the {{LAUNCH_JBOSS_IN_BACKGROUND}} environment variable. At least in standalone a new process is launched, but the script waits to exit until the launched process exits.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (DROOLS-632) java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems
by Roman Stumm (JIRA)
[ https://issues.jboss.org/browse/DROOLS-632?page=com.atlassian.jira.plugin... ]
Roman Stumm commented on DROOLS-632:
------------------------------------
We had the same problem after upgrading from jetty 9.1.0.v20131115 to jetty 9.2.3.v20140905.
The reason is that the jetty WebAppClassLoader hides classes (e.g. the eclipse compiler and all classes in package "org.eclipse.jdt."). This can be changed, see org.eclipse.jetty.webapp.WebAppContext.getDefaultServerClasses() and setServerClasses().
see https://bugs.eclipse.org/bugs/show_bug.cgi?id=414885
> java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult.getProblems
> --------------------------------------------------------------------------------------------
>
> Key: DROOLS-632
> URL: https://issues.jboss.org/browse/DROOLS-632
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.1.0.Final
> Environment: hadoop,console,mapreduce
> Reporter: Yongbo Wu
> Assignee: Mario Fusco
> Priority: Trivial
> Labels: hadoop,CompilationResult,NoSuchMethosError
>
> I create a Drools Project(with some example code) and it run well in eclipse.
> then I package it and run in console, alongwith all jars needed.
> Here comes the error:
> java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult
> .getProblems()[Lorg/eclipse/jdt/core/compiler/CategorizedProblem;
> at org.drools.compiler.commons.jci.compilers.EclipseJavaCompiler$3.accep
> tResult(EclipseJavaCompiler.java:379)
> at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:335)
> at org.drools.compiler.commons.jci.compilers.EclipseJavaCompiler.compile
> (EclipseJavaCompiler.java:409)
> at org.drools.compiler.commons.jci.compilers.AbstractJavaCompiler.compil
> e(AbstractJavaCompiler.java:49)
> at org.drools.compiler.rule.builder.dialect.java.JavaDialect.compileAll(
> JavaDialect.java:409)
> at org.drools.compiler.compiler.DialectCompiletimeRegistry.compileAll(Di
> alectCompiletimeRegistry.java:46)
> at org.drools.compiler.compiler.PackageRegistry.compileAll(PackageRegist
> ry.java:109)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAll(Know
> ledgeBuilderImpl.java:1202)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAllRules
> (KnowledgeBuilderImpl.java:846)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildR
> ules(CompositeKnowledgeBuilderImpl.java:279)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildP
> ackages(CompositeKnowledgeBuilderImpl.java:103)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(
> CompositeKnowledgeBuilderImpl.java:91)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledge
> Packages(AbstractKieModule.java:220)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(K
> ieContainerImpl.java:386)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieC
> ontainerImpl.java:346)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(K
> ieContainerImpl.java:498)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(K
> ieContainerImpl.java:469)
> at com.sohu.adrd.QLabel.DroolsTest.main(DroolsTest.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:186)
> java.lang.NoSuchMethodError: org.eclipse.jdt.internal.compiler.CompilationResult
> .getProblems()[Lorg/eclipse/jdt/core/compiler/CategorizedProblem;
> at org.drools.compiler.commons.jci.compilers.EclipseJavaCompiler$3.accep
> tResult(EclipseJavaCompiler.java:379)
> at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:335)
> at org.drools.compiler.commons.jci.compilers.EclipseJavaCompiler.compile
> (EclipseJavaCompiler.java:409)
> at org.drools.compiler.commons.jci.compilers.AbstractJavaCompiler.compil
> e(AbstractJavaCompiler.java:49)
> at org.drools.compiler.rule.builder.dialect.java.JavaDialect.compileAll(
> JavaDialect.java:409)
> at org.drools.compiler.compiler.DialectCompiletimeRegistry.compileAll(Di
> alectCompiletimeRegistry.java:46)
> at org.drools.compiler.compiler.PackageRegistry.compileAll(PackageRegist
> ry.java:109)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAll(Know
> ledgeBuilderImpl.java:1202)
> at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.compileAllRules
> (KnowledgeBuilderImpl.java:846)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildR
> ules(CompositeKnowledgeBuilderImpl.java:279)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.buildP
> ackages(CompositeKnowledgeBuilderImpl.java:103)
> at org.drools.compiler.builder.impl.CompositeKnowledgeBuilderImpl.build(
> CompositeKnowledgeBuilderImpl.java:91)
> at org.drools.compiler.kie.builder.impl.AbstractKieModule.buildKnowledge
> Packages(AbstractKieModule.java:220)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.createKieBase(K
> ieContainerImpl.java:386)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.getKieBase(KieC
> ontainerImpl.java:346)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(K
> ieContainerImpl.java:498)
> at org.drools.compiler.kie.builder.impl.KieContainerImpl.newKieSession(K
> ieContainerImpl.java:469)
> at com.sohu.adrd.QLabel.DroolsTest.main(DroolsTest.java:21)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.util.RunJar.main(RunJar.java:186)
> How could I get rid of this? Any suggestion is weclome!
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-3262) WebServiceRef injection without explicit wsdl file fails during Servlet initialization
by R Searls (JIRA)
[ https://issues.jboss.org/browse/WFLY-3262?page=com.atlassian.jira.plugin.... ]
R Searls commented on WFLY-3262:
--------------------------------
Created enhancement request https://issues.jboss.org/browse/WFLY-4026
> WebServiceRef injection without explicit wsdl file fails during Servlet initialization
> --------------------------------------------------------------------------------------
>
> Key: WFLY-3262
> URL: https://issues.jboss.org/browse/WFLY-3262
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.1.0.CR1
> Reporter: Matus Abaffy
> Assignee: R Searls
> Fix For: 9.0.0.CR1
>
>
> Reproducer test available at https://github.com/bafco/wildfly/commits/wsServletInjection
> I have the following servlet
> {code}
> @WebServlet(/*..., */ loadOnStartup = 1)
> public class ServletLoadOnStartup extends HttpServlet {
> @WebServiceRef(value = EndpointService.class)
> private EndpointInterface endpoint1;
> //...
> {code}
> (It is located in the package org.jboss.as.test.integration.ws.serviceref. There you can find more info about the other classes.)
> And i get the following exception:
> {code}
> org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: ws-servlet-test.war
> ...
> Caused by: java.lang.Exception: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./ws-servlet-test" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./ws-servlet-test: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: javax.servlet.ServletException: UT010013: Could not instantiate ServletLoadOnStartup
> Caused by: java.lang.IllegalStateException: JBAS011048: Failed to construct component instance
> Caused by: java.lang.RuntimeException: JBAS011875: Resource lookup for injection failed: env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1
> Caused by: javax.naming.NamingException: JBAS011878: Failed to lookup env/org.jboss.as.test.integration.ws.serviceref.ServletLoadOnStartup/endpoint1 [Root exception is org.jboss.wsf.spi.WSFException: Cannot create service]
> Caused by: org.jboss.wsf.spi.WSFException: Cannot create service
> Caused by: java.lang.reflect.InvocationTargetException
> Caused by: javax.xml.ws.WebServiceException: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: org.apache.cxf.service.factory.ServiceConstructionException: Failed to create service.
> Caused by: javax.wsdl.WSDLException: WSDLException: faultCode=PARSER_ERROR: Problem parsing 'http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl'.: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl
> Caused by: java.io.FileNotFoundException: http://localhost:8080/ws-servlet-test/EndpointService/EJB3Bean?wsdl"}}
> {code}
> If I change loadOnStartup parameter to -1, everything works fine, i.e. servlet gets instantiated and WS is injected correctly. Therefore, I suppose this is a bug.
> Another workaround exists - adding wsdl file to the deployment archive and using the 'wsdlLocation' parameter in @WebServiceRef (as can be seen in ServiceRefSevletTestCase).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-4027) RESTEasy ViolationReport is not processed by JAXB provider
by Harald Wellmann (JIRA)
Harald Wellmann created WFLY-4027:
-------------------------------------
Summary: RESTEasy ViolationReport is not processed by JAXB provider
Key: WFLY-4027
URL: https://issues.jboss.org/browse/WFLY-4027
Project: WildFly
Issue Type: Bug
Components: REST
Affects Versions: 9.0.0.Alpha1, 8.1.0.Final, 8.2.0.CR1
Reporter: Harald Wellmann
Assignee: Stuart Douglas
When used in combination with Bean Validation, RESTEasy should wrap validation errors in a {{ValidationReport}} which should be included in the REST response, marshalled to JSON or XML, depending on the content type.
This does not work currently in WildFly 8.1.0.Final.
The issue was reported in RESTEASY-1054. and is marked as fixed in RESTEasy 3.0.9.Final.
However, I can still reproduce the issue with a local build of WildFly 8.2.0.CR1-SNAPSHOT (from the 8.x branch) which includes RESTEasy 3.0.10.Final.
Going back to WildFly 8.1.0.Final, the issue no longer occurs when I add
{code}
<module name="javax.xml.bind.api"/>
{code}
to the {{module.xml}} descriptor of {{org.jboss.resteasy.resteasy-validator-provider-11}}.
The same fix works for 8.2.0.CR1-SNAPSHOT.
Looking at the module descriptor, it seems that 9.0.0.Alpha1 is also affected (but I did not test my sample on 9.0.0.Alpha1).
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (WFLY-4026) add a configuration attribute to @WebContext to handle EJB3 loadOnStartup > -1 situations
by R Searls (JIRA)
R Searls created WFLY-4026:
------------------------------
Summary: add a configuration attribute to @WebContext to handle EJB3 loadOnStartup > -1 situations
Key: WFLY-4026
URL: https://issues.jboss.org/browse/WFLY-4026
Project: WildFly
Issue Type: Feature Request
Components: EJB
Affects Versions: 9.0.0.Alpha1
Reporter: R Searls
Assignee: David Lloyd
An app with a servlet that is loadOnStartup = 1 that references an EJB3 webservice not defined by a WSDL fails because the EJB3 servlet does not have the same loadOnStartup designator. There is an existing wildFly integration test that demonstrates this. (see org.jboss.as.test.integration.ws.serviceref.ServiceRefWithoutExplicitWsdlServletTestCase)
Also see the original bug filed against this behavior and the comments on the
cause, https://issues.jboss.org/browse/WFLY-3262.
A suggested solution is to add a configuration attribute to @WebContext.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months