[JBoss JIRA] (DROOLS-123) Missing library com.google.gwt.http.client.URL
by Michael Anstis (JIRA)
[ https://issues.jboss.org/browse/DROOLS-123?page=com.atlassian.jira.plugin... ]
Michael Anstis resolved DROOLS-123.
-----------------------------------
Resolution: Out of Date
> Missing library com.google.gwt.http.client.URL
> ----------------------------------------------
>
> Key: DROOLS-123
> URL: https://issues.jboss.org/browse/DROOLS-123
> Project: Drools
> Issue Type: Bug
> Affects Versions: 6.0.0.Beta2
> Environment: Ubuntu 12.04 64 bits
> Java SE 1.6_u43
> JBoss 7.1.1.Final
> Reporter: Miguel Angel Júlvez
> Assignee: Michael Anstis
>
> 16:14:54,589 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/guvnor-6.0.0.Beta2-jboss-as7.0].[ErraiServlet]] (http--127.0.0.1-8080-6) Servlet.service() para servlet ErraiServlet lanzó excepción: java.lang.ClassNotFoundException: com.google.gwt.http.client.URL from [Module "deployment.guvnor-6.0.0.Beta2-jboss-as7.0.war:main" from Service Module Loader]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4113) 8.2.0.Final build hangs
by Romain Pelisse (JIRA)
[ https://issues.jboss.org/browse/WFLY-4113?page=com.atlassian.jira.plugin.... ]
Romain Pelisse commented on WFLY-4113:
--------------------------------------
I've rebuilt and tested jboss-remoting-4..0.7, and modify wfly 8.2 build to use it, and indeed, it fixes the issue.
Maybe this only make it worth having 4.0.7 release ? After all, being able to build wildfly appears worth the trouble.
> 8.2.0.Final build hangs
> -----------------------
>
> Key: WFLY-4113
> URL: https://issues.jboss.org/browse/WFLY-4113
> Project: WildFly
> Issue Type: Feature Request
> Components: Test Suite
> Affects Versions: 8.2.0.Final
> Reporter: Peter Major
> Assignee: David Lloyd
> Attachments: jstack.txt
>
>
> When trying to build 8.2.0.Final locally, my build just hangs indefinitely while executing a unit test in the controller module:
> {noformat}
> Running org.jboss.as.controller.ModelControllerClientTestCase
> {noformat}
> Running jstack against the build suggests that there is a deadlock between
> {noformat}
> - waiting to lock <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeMessages(RemoteConnectionChannel.java:560)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:542)
> at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:359)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:423)
> - locked <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
> at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:232)
> {noformat}
> and
> {noformat}
> - waiting to lock <0x00000007b8d8e6f8> (a java.util.ArrayDeque)
> at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:122)
> at org.jboss.remoting3.remote.OutboundMessage$1.accept(OutboundMessage.java:154)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:122)
> at org.xnio.streams.BufferPipeOutputStream.send(BufferPipeOutputStream.java:115)
> at org.xnio.streams.BufferPipeOutputStream.flush(BufferPipeOutputStream.java:139)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.xnio.streams.BufferPipeOutputStream.close(BufferPipeOutputStream.java:157)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at org.jboss.remoting3.remote.OutboundMessage.close(OutboundMessage.java:283)
> - locked <0x00000007bc3f96c8> (a org.xnio.streams.BufferPipeOutputStream)
> at java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> {noformat}
> Preferably locks should be obtained in the same order across the different code paths to prevent deadlocks.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4030) wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml, faces-config.x ml and persistence.xml
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/WFLY-4030?page=com.atlassian.jira.plugin.... ]
Rafael Benevides resolved WFLY-4030.
------------------------------------
Resolution: Rejected
This should be fixed at the Quickstarts
> wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml, faces-config.x ml and persistence.xml
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4030
> URL: https://issues.jboss.org/browse/WFLY-4030
> Project: WildFly
> Issue Type: Bug
> Reporter: Arun Gupta
> Assignee: Sebastian Łaskawiec
> Priority: Minor
> Labels: archetypes, maven, wildfly
>
> mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final
> The app has the following files:
> ./src/main/webapp/WEB-INF/beans.xml
> ./src/main/webapp/WEB-INF/faces-config.xml
> beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4031) Wildfly Quickstarts using old namespaces for beans.xml, faces-config.xml and persistence.xml
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/WFLY-4031?page=com.atlassian.jira.plugin.... ]
Rafael Benevides updated WFLY-4031:
-----------------------------------
Summary: Wildfly Quickstarts using old namespaces for beans.xml, faces-config.xml and persistence.xml (was: Wildfly Quickstarts using old namespaces for beans.xml and faces-config.xml)
> Wildfly Quickstarts using old namespaces for beans.xml, faces-config.xml and persistence.xml
> --------------------------------------------------------------------------------------------
>
> Key: WFLY-4031
> URL: https://issues.jboss.org/browse/WFLY-4031
> Project: WildFly
> Issue Type: Bug
> Reporter: Rafael Benevides
> Assignee: Sebastian Łaskawiec
> Priority: Minor
> Labels: quickstarts,
>
> All Wildfly quickstarts have the wrong XML namespaces for the following files.
> ./src/main/webapp/WEB-INF/beans.xml
> ./src/main/webapp/WEB-INF/faces-config.xml
> beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces.
> This affects the wildfly archetypes as well
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (WFLY-4030) wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml, faces-config.x ml and persistence.xml
by Rafael Benevides (JIRA)
[ https://issues.jboss.org/browse/WFLY-4030?page=com.atlassian.jira.plugin.... ]
Rafael Benevides updated WFLY-4030:
-----------------------------------
Summary: wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml, faces-config.x ml and persistence.xml (was: wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml and faces-config.xml)
> wildfly-javaee7-webapp-blank-archetype using old namespaces for beans.xml, faces-config.x ml and persistence.xml
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4030
> URL: https://issues.jboss.org/browse/WFLY-4030
> Project: WildFly
> Issue Type: Bug
> Reporter: Arun Gupta
> Assignee: Sebastian Łaskawiec
> Priority: Minor
> Labels: archetypes, maven, wildfly
>
> mvn archetype:generate -DgroupId=test -DartifactId=test -DarchetypeGroupId=org.wildfly.archetype -DarchetypeArtifactId=wildfly-javaee7-webapp-blank-archetype -DarchetypeVersion=8.1.0.Final
> The app has the following files:
> ./src/main/webapp/WEB-INF/beans.xml
> ./src/main/webapp/WEB-INF/faces-config.xml
> beans.xml and faces-config.xml are using java.sun.com-style namespaces instead of xmlns.jcp.org-style namespaces.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years