[JBoss JIRA] (WFLY-4843) Wildfly 9 missing commons-configuration module
by Brett Meyer (JIRA)
Brett Meyer created WFLY-4843:
---------------------------------
Summary: Wildfly 9 missing commons-configuration module
Key: WFLY-4843
URL: https://issues.jboss.org/browse/WFLY-4843
Project: WildFly
Issue Type: Bug
Affects Versions: 9.0.0.CR2
Reporter: Brett Meyer
Assignee: Jason Greene
Definitely not a big deal to provide the commons-configuration jar on our own. But, was there any reason for the module's removal in WF 9, while most other commons-* modules remain?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4842) A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
by Alex Lashchuk (JIRA)
Alex Lashchuk created WFLY-4842:
-----------------------------------
Summary: A resource packaged in a RAR file fails to call a native library packaged in the same RAR.
Key: WFLY-4842
URL: https://issues.jboss.org/browse/WFLY-4842
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 9.0.0.CR2, 8.2.0.Final
Environment: Windows 7, 64-bit
Reporter: Alex Lashchuk
Assignee: David Lloyd
JSR322, section 20.2.0.2, specifies that native libraries, packaged at an arbitrary location in a resource adapter's RAR file, will be made available to resource adapter's managed code. In fact, section 20.2.0.1 requires that the platform-specific libraries be packaged with the resource adapter module instead of being placed on java.library.path. However, attempting to access a native library included in a RAR from resource adapter code on WildFly results in an UnsatisfiedLinkError.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4841) Injection of a JCA connection factory exposed from a RAR into a CDI bean fails due to class loading issues.
by Alex Lashchuk (JIRA)
Alex Lashchuk created WFLY-4841:
-----------------------------------
Summary: Injection of a JCA connection factory exposed from a RAR into a CDI bean fails due to class loading issues.
Key: WFLY-4841
URL: https://issues.jboss.org/browse/WFLY-4841
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 9.0.0.CR2, 8.2.0.Final
Environment: Windows 7, 64-bit
Reporter: Alex Lashchuk
Assignee: David Lloyd
Attempting to inject a connection factory from a RAR into an enterprise application by interface results in a NoClassDefFoundError while looking for the interface class definition. This is likely in violation of JSR342 section EE.8.3.2.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4827) Network Connection leak on client abort connection
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4827?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4827:
--------------------------------------
ah, sorry, I left off:
git checkout 1.1.x
To checkout the 1.1 branch.
I am not sure about that error though, it looks like a network connection error with maven central.
> Network Connection leak on client abort connection
> --------------------------------------------------
>
> Key: WFLY-4827
> URL: https://issues.jboss.org/browse/WFLY-4827
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Sockets
> Affects Versions: 8.2.0.Final
> Environment: On Windows Server 2012, JDK 1.8.0_45, Wildfly 8.2.0.Final in standalone mode.
> Reporter: Andrea Bertolini
> Assignee: Stuart Douglas
>
> We have a classic client-server application, all written in Java. Each client is installed on a forklift which can move all around a large area. This area is under wi-fi coverage.
> Sometimes the clients can have a bad connection quality and the client-server communication is interrupted; in such a case it takes too many seconds to be restored.
> To fix this situation, we add a timeout client-side. After 5 seconds it aborts the call and tries again a second time.
> To achieve this call we use apache httpcomponents library (version 4.4). We use the abort method of httppost to interrupt this call.
> Server-side, we have a group of web-servlets which listen to the incoming calls, manage requests and send a response.
> It appears that sometimes a communication remains stuck in reading or writing from/to the stream. When the client aborts the communication, an exception is thrown on the server caused by the channel being closed.
> It happens that a large number of connections remains stuck in connection status 'established' (only server-side) even if the real connection is actually closed (client doesn't have that connection active anymore).
> When the number of established connections grows up to 200, server stops responding on port 8080, so it cannot accept more connections and it seems to freeze.
> We tried to add tcp-keep-alive=true and no-request-timeout=120000 on http-listener in undertow subsystem, but sometimes it removes idle connections after any incoming requests are received for 2 minutes, some other times it keep connections as established and doesn't close them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4827) Network Connection leak on client abort connection
by Andrea Bertolini (JIRA)
[ https://issues.jboss.org/browse/WFLY-4827?page=com.atlassian.jira.plugin.... ]
Andrea Bertolini commented on WFLY-4827:
----------------------------------------
With correct url i can download the new branch...
But using mvn install i get this error.
[INFO] Scanning for projects...
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jboss-p...
Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/jboss/jboss-p... (31 KB at 22.7 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Undertow
[INFO] Undertow Parser Generator
[INFO] Undertow Core
[INFO] Undertow Servlet
[INFO] Undertow WebSockets JSR356 implementations
[INFO] Undertow Examples
[INFO] Undertow HTTP2 test suite
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Undertow 1.3.0.Beta3-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: http://repository.jboss.org/nexus/content/groups/public/org/apache/maven/...
Downloading: https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-enfor...
giu 29, 2015 5:37:11 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:11 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
giu 29, 2015 5:37:32 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:32 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
giu 29, 2015 5:37:53 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: I/O exception (java.net.SocketException) caught when processing request to {s}->https://repo.maven.apache.org:443: Connection reset
giu 29, 2015 5:37:53 PM org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec execute
INFORMAZIONI: Retrying request to {s}->https://repo.maven.apache.org:443
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Undertow ........................................... FAILURE [01:26 min]
[INFO] Undertow Parser Generator .......................... SKIPPED
[INFO] Undertow Core ...................................... SKIPPED
[INFO] Undertow Servlet ................................... SKIPPED
[INFO] Undertow WebSockets JSR356 implementations ......... SKIPPED
[INFO] Undertow Examples .................................. SKIPPED
[INFO] Undertow HTTP2 test suite .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:28 min
[INFO] Finished at: 2015-06-29T17:38:15+02:00
[INFO] Final Memory: 13M/150M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4: Could not trans
fer artifact org.apache.maven.plugins:maven-enforcer-plugin:pom:1.4 from/to central (https://repo.maven.apache.org/maven2): Connection reset -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
But did I download 1.3.0 version??
[INFO] Building Undertow 1.3.0.Beta3-SNAPSHOT
> Network Connection leak on client abort connection
> --------------------------------------------------
>
> Key: WFLY-4827
> URL: https://issues.jboss.org/browse/WFLY-4827
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Sockets
> Affects Versions: 8.2.0.Final
> Environment: On Windows Server 2012, JDK 1.8.0_45, Wildfly 8.2.0.Final in standalone mode.
> Reporter: Andrea Bertolini
> Assignee: Stuart Douglas
>
> We have a classic client-server application, all written in Java. Each client is installed on a forklift which can move all around a large area. This area is under wi-fi coverage.
> Sometimes the clients can have a bad connection quality and the client-server communication is interrupted; in such a case it takes too many seconds to be restored.
> To fix this situation, we add a timeout client-side. After 5 seconds it aborts the call and tries again a second time.
> To achieve this call we use apache httpcomponents library (version 4.4). We use the abort method of httppost to interrupt this call.
> Server-side, we have a group of web-servlets which listen to the incoming calls, manage requests and send a response.
> It appears that sometimes a communication remains stuck in reading or writing from/to the stream. When the client aborts the communication, an exception is thrown on the server caused by the channel being closed.
> It happens that a large number of connections remains stuck in connection status 'established' (only server-side) even if the real connection is actually closed (client doesn't have that connection active anymore).
> When the number of established connections grows up to 200, server stops responding on port 8080, so it cannot accept more connections and it seems to freeze.
> We tried to add tcp-keep-alive=true and no-request-timeout=120000 on http-listener in undertow subsystem, but sometimes it removes idle connections after any incoming requests are received for 2 minutes, some other times it keep connections as established and doesn't close them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4827) Network Connection leak on client abort connection
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-4827?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-4827:
--------------------------------------
Oops, I gave the writeable address.
https://github.com/undertow-io/undertow.git
is the correct one
> Network Connection leak on client abort connection
> --------------------------------------------------
>
> Key: WFLY-4827
> URL: https://issues.jboss.org/browse/WFLY-4827
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Sockets
> Affects Versions: 8.2.0.Final
> Environment: On Windows Server 2012, JDK 1.8.0_45, Wildfly 8.2.0.Final in standalone mode.
> Reporter: Andrea Bertolini
> Assignee: Stuart Douglas
>
> We have a classic client-server application, all written in Java. Each client is installed on a forklift which can move all around a large area. This area is under wi-fi coverage.
> Sometimes the clients can have a bad connection quality and the client-server communication is interrupted; in such a case it takes too many seconds to be restored.
> To fix this situation, we add a timeout client-side. After 5 seconds it aborts the call and tries again a second time.
> To achieve this call we use apache httpcomponents library (version 4.4). We use the abort method of httppost to interrupt this call.
> Server-side, we have a group of web-servlets which listen to the incoming calls, manage requests and send a response.
> It appears that sometimes a communication remains stuck in reading or writing from/to the stream. When the client aborts the communication, an exception is thrown on the server caused by the channel being closed.
> It happens that a large number of connections remains stuck in connection status 'established' (only server-side) even if the real connection is actually closed (client doesn't have that connection active anymore).
> When the number of established connections grows up to 200, server stops responding on port 8080, so it cannot accept more connections and it seems to freeze.
> We tried to add tcp-keep-alive=true and no-request-timeout=120000 on http-listener in undertow subsystem, but sometimes it removes idle connections after any incoming requests are received for 2 minutes, some other times it keep connections as established and doesn't close them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-799) Errai QuickStart modifies source tree
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-799?page=com.atlassian.jira.plugin.s... ]
Eduardo Martins reassigned WFLY-799:
------------------------------------
Assignee: Eduardo Martins
> Errai QuickStart modifies source tree
> -------------------------------------
>
> Key: WFLY-799
> URL: https://issues.jboss.org/browse/WFLY-799
> Project: WildFly
> Issue Type: Bug
> Reporter: Ondrej Zizka
> Assignee: Eduardo Martins
> Labels: quickstarts
>
> In current Quickstarts master, the Errai QS, after built, adds these files:
> {code}
> # On branch master
> # Untracked files:
> # helloworld-errai/src/main/gwt-unitCache/
> # helloworld-errai/src/main/webapp/HelloWorldApp/
> # helloworld-errai/src/main/webapp/WEB-INF/deploy/
> {code}
> The build should be configured so they end up in `target/`, or at least we should ignore these files in `.gitignore`.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-1366) @DataSourceDefinition incorrectly requires other properties than name and class-name
by Eduardo Martins (JIRA)
[ https://issues.jboss.org/browse/WFLY-1366?page=com.atlassian.jira.plugin.... ]
Eduardo Martins reassigned WFLY-1366:
-------------------------------------
Assignee: Eduardo Martins
> @DataSourceDefinition incorrectly requires other properties than name and class-name
> ------------------------------------------------------------------------------------
>
> Key: WFLY-1366
> URL: https://issues.jboss.org/browse/WFLY-1366
> Project: WildFly
> Issue Type: Feature Request
> Components: EE
> Affects Versions: 8.0.0.Alpha1
> Reporter: arjan tijms
> Assignee: Eduardo Martins
> Labels: spec, validation
>
> When using the <data-source> element in e.g. web.xml or application.xml JBoss EAP 6.0.1/JBoss AS 7.1.3 does not accept a configuration without properties other than {{name}} and {{class-name}}. For instance:
> {code:xml}
> <data-source>
> <name>java:app/myDS</name>
> <class-name>com.example.MyDS</class-name>
> </data-source>
> {code}
> With such configuration, the following exception is thrown:
> {noformat}
> Caused by: org.jboss.jca.common.api.validator.ValidateException: IJ010069: Missing required element xa-datasource-property in org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl
> at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.validate(XADataSourceImpl.java:385)
> at org.jboss.jca.common.metadata.ds.v10.XADataSourceImpl.<init>(XADataSourceImpl.java:116)
> at org.jboss.jca.common.metadata.ds.v11.XADataSourceImpl.<init>(XADataSourceImpl.java:76)
> at org.jboss.as.connector.subsystems.datasources.ModifiableXaDataSource.getUnModifiableInstance(ModifiableXaDataSource.java:373)
> at org.jboss.as.connector.subsystems.datasources.XaDataSourceService.getDeployer(XaDataSourceService.java:70)
> at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:116)
> {noformat}
> At the point where the exception is thrown, the code checks if there are any properties at all:
> {code}
> if (this.xaDataSourceProperty.isEmpty())
> throw new ValidateException(
> bundle.requiredElementMissing(
> Tag.XA_DATASOURCE_PROPERTY.getLocalName(),
> this.getClass().getCanonicalName()));
> {code}
> I don't understand why this check is there. If I'm not mistaken the spec (e.g. JSR 250 section 2.13 and JSR 316 section EE.5.17) does not seem to mandate properties to be present and the corresponding annotation only requires {{name}} and {{className}} to be specified.
> A workaround is to subclass the data source class and provide a dummy property, e.g.
> {code:xml}
> <data-source>
> <name>java:app/myDS</name>
> <class-name>com.example.MySubDS</class-name>
> <property>
> <name>dummy</name>
> <value>dummy</value>
> </property>
> </data-source>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (WFLY-4827) Network Connection leak on client abort connection
by Andrea Bertolini (JIRA)
[ https://issues.jboss.org/browse/WFLY-4827?page=com.atlassian.jira.plugin.... ]
Andrea Bertolini commented on WFLY-4827:
----------------------------------------
Launching git as you specified and get this error.
Cloning into 'undertow'...
Warning: Permanently added the RSA host key for IP address '192.30.252.130' to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights and the repository exists.
> Network Connection leak on client abort connection
> --------------------------------------------------
>
> Key: WFLY-4827
> URL: https://issues.jboss.org/browse/WFLY-4827
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow), Web Sockets
> Affects Versions: 8.2.0.Final
> Environment: On Windows Server 2012, JDK 1.8.0_45, Wildfly 8.2.0.Final in standalone mode.
> Reporter: Andrea Bertolini
> Assignee: Stuart Douglas
>
> We have a classic client-server application, all written in Java. Each client is installed on a forklift which can move all around a large area. This area is under wi-fi coverage.
> Sometimes the clients can have a bad connection quality and the client-server communication is interrupted; in such a case it takes too many seconds to be restored.
> To fix this situation, we add a timeout client-side. After 5 seconds it aborts the call and tries again a second time.
> To achieve this call we use apache httpcomponents library (version 4.4). We use the abort method of httppost to interrupt this call.
> Server-side, we have a group of web-servlets which listen to the incoming calls, manage requests and send a response.
> It appears that sometimes a communication remains stuck in reading or writing from/to the stream. When the client aborts the communication, an exception is thrown on the server caused by the channel being closed.
> It happens that a large number of connections remains stuck in connection status 'established' (only server-side) even if the real connection is actually closed (client doesn't have that connection active anymore).
> When the number of established connections grows up to 200, server stops responding on port 8080, so it cannot accept more connections and it seems to freeze.
> We tried to add tcp-keep-alive=true and no-request-timeout=120000 on http-listener in undertow subsystem, but sometimes it removes idle connections after any incoming requests are received for 2 minutes, some other times it keep connections as established and doesn't close them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months