-
1. Re: wildfly alpha2 becomes unresponsive accessing via browser
lafr Jun 23, 2013 6:16 AM (in response to alberto_souza)What do you try to access through the browser? Pages of your own web application you have deployed?
What you get? "source code" of your web pages like jsp or faces pages or do you have static html pages or what?
What do you access via curl?
Try to access the console under http://server:9990/console and see if this works.
-
2. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 23, 2013 12:30 PM (in response to lafr)Hi Frank, same result when i try to access the management console. It is my own web application that i am trying to deploy. The pages are jsps. In fact, the app is deployed and apparently running. I can access the same urls via curl that i was trying to access via browser. Seems to be a very specific problem...
-
3. Re: wildfly alpha2 becomes unresponsive accessing via browser
ctomc Jun 23, 2013 12:42 PM (in response to alberto_souza)What kind of browser are you using?
also is there any kind of firewall installed on your machine (or machine you have WildFly installed on)
-
4. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 23, 2013 12:45 PM (in response to ctomc)I've tested with chrome and firefox... There is not any firewall... It's just my computer . The response is sent but, i don't know exactly how to explain, seems that the socket was not closed... The browser never stops to loading.
-
5. Re: wildfly alpha2 becomes unresponsive accessing via browser
swd847 Jun 23, 2013 5:56 PM (in response to alberto_souza)Is there any chance you could attach a wireshark capture file containing the data that is being sent over the wire?
This sounds like a fixed length response that has less than the specified number of bytes written, although that is just a guess.
-
7. Re: wildfly alpha2 becomes unresponsive accessing via browser
swd847 Jun 24, 2013 7:22 PM (in response to alberto_souza)I'm not sure what is going on here, looking at the wireshark dumps everything should be fine. Do you have a reproducer application you can share?
-
8. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 25, 2013 7:52 AM (in response to swd847)Here is a war exported => https://dl.dropboxusercontent.com/u/19243610/vraptor-example-cdi-0.0.1-SNAPSHOT.war
It is using the ExampleDS that is already configured in wildfly.
-
9. Re: wildfly alpha2 becomes unresponsive accessing via browser
swd847 Jun 25, 2013 7:27 PM (in response to alberto_souza)I can't deploy your example. I get a deployment exception:
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014227: EJB ProdutoDAO of type app.repositories.ProdutoDAO must have public default constructor
-
10. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 25, 2013 8:14 PM (in response to swd847)Sorry... To run this project, you have to enable a javaagent that instruments all classes and add the nonargs constructor...
Here => https://dl.dropboxusercontent.com/u/19243610/cdiagent.jar
-
11. Re: wildfly alpha2 becomes unresponsive accessing via browser
swd847 Jun 25, 2013 8:19 PM (in response to alberto_souza)Now I get:
{code}
10:19:09,339 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-9) MSC000001: Failed to start service jboss.deployment.unit."vraptor-example-cdi-0.0.1-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."vraptor-example-cdi-0.0.1-SNAPSHOT.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1898) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_10-ea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_10-ea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_10-ea]
Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
java.lang.ArrayIndexOutOfBoundsException: 1
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedCallableImpl.getAnnotatedParameters(AnnotatedCallableImpl.java:85)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedCallableImpl.<init>(AnnotatedCallableImpl.java:46)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedConstructorImpl.<init>(AnnotatedConstructorImpl.java:43)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedTypeImpl.<init>(AnnotatedTypeImpl.java:83)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedTypeBuilder.create(AnnotatedTypeBuilder.java:845)
at br.com.caelum.vraptor.ioc.cdi.extensions.ModifyComponentExtension.processAnnotatedType(ModifyComponentExtension.java:22)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:274)
at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:261)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:240)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:171)
at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:130)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:94)
at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:146)
at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:172)
at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:231)
at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:481)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:99)
at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:146)
at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:172)
at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:231)
at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:481)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875) [jboss-msc-1.2.0.Beta1.jar:1.2.0.Beta1]
... 3 more
10:19:09,350 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "vraptor-example-cdi-0.0.1-SNAPSHOT.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"vraptor-example-cdi-0.0.1-SNAPSHOT.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"vraptor-example-cdi-0.0.1-SNAPSHOT.war\".WeldStartService: Failed to start service
Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
Exception 0 :
java.lang.ArrayIndexOutOfBoundsException: 1
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedCallableImpl.getAnnotatedParameters(AnnotatedCallableImpl.java:85)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedCallableImpl.<init>(AnnotatedCallableImpl.java:46)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedConstructorImpl.<init>(AnnotatedConstructorImpl.java:43)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedTypeImpl.<init>(AnnotatedTypeImpl.java:83)
at org.apache.deltaspike.core.util.metadata.builder.AnnotatedTypeBuilder.create(AnnotatedTypeBuilder.java:845)
at br.com.caelum.vraptor.ioc.cdi.extensions.ModifyComponentExtension.processAnnotatedType(ModifyComponentExtension.java:22)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:93)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:274)
at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:261)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:240)
at org.jboss.weld.event.ObserverNotifier.notifyObserver(ObserverNotifier.java:171)
at org.jboss.weld.event.ObserverNotifier.notifyObservers(ObserverNotifier.java:130)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:109)
at org.jboss.weld.bootstrap.events.ProcessAnnotatedTypeImpl.fire(ProcessAnnotatedTypeImpl.java:94)
at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:146)
at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:172)
at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:231)
at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:481)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:63)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
"}}
{code}
-
12. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 25, 2013 8:33 PM (in response to alberto_souza)huuummm...
Could you, please, try these one => https://dl.dropboxusercontent.com/u/19243610/vraptor-example-cdi.war
It is synchronizing...
Sorry about the last war .
-
13. Re: wildfly alpha2 becomes unresponsive accessing via browser
swd847 Jun 26, 2013 8:19 PM (in response to alberto_souza)Can you try removing the <buffer-caches> entry from the undertow subsystem and try again? I'm not sure if it is related but I managed to introduce a fairly major resource caching bug into Alpha2 right before the release (which has since been fixed upstream).
-
14. Re: wildfly alpha2 becomes unresponsive accessing via browser
alberto_souza Jun 26, 2013 9:58 PM (in response to swd847)Hi Stuart, unfortunately the problem remains. I do not have any ideas to help you .