November 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-1728) Allow testsuite parallelism to be controlled from build.xml alone

by Richard Achmatowicz (JIRA)

[ https://issues.jboss.org/browse/JGRP-1728?page=com.atlassian.jira.plugin.... ] Richard Achmatowicz commented on JGRP-1728: ------------------------------------------- I've made some changes to the files in conf/testng as well as build.xml so that parallel execution of test cases can be controlled solely from the build.xml properties parallel.methods and parallel.tests: To make use of parallelism: {noformat} parallel.tests=tests parallel.methods=methods {noformat} To supress parallelism: {noformat} parallel.tests=false parallel.methods=false {noformat} > Allow testsuite parallelism to be controlled from build.xml alone > ----------------------------------------------------------------- > > Key: JGRP-1728 > URL: https://issues.jboss.org/browse/JGRP-1728 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.5 > Reporter: Richard Achmatowicz > Assignee: Bela Ban > Priority: Minor > Fix For: 3.5 > > > Directives controlling parallel execution of the JGroups testsuite can be specified at two levels: as parameters to the testng ant task (in build.xml), or as attributes of the suite element in the suite definition files (found in the conf/testng directory). > At present, parallelism directives in the various suite definition files (functional.xml, udp.xml, tcp.xml, etc.) take precedence over any directives specified in testng ant tasks. In fact, the directives passed to runtest in build.xml are (incorrectly) not passed through to the testng ant task, so that parallelism is controlled solely from the suite definition files. > Making use of parallel execution of test cases when running in the QA lab leads to a higher proportion of test failures, leading to a proliferation of JIRA/bugzilla issues. Therefore it is important that we be able to turn on (turn off) parallel execution of test cases through some simple specification of system properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2422) Simplify the remote-outbound connections

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-2422?page=com.atlassian.jira.plugin.... ] Cheng Fang commented on WFLY-2422: ---------------------------------- Sure, I will take a look. > Simplify the remote-outbound connections > ---------------------------------------- > > Key: WFLY-2422 > URL: https://issues.jboss.org/browse/WFLY-2422 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EJB, Remoting > Affects Versions: 8.0.0.Beta1 > Reporter: Wolf-Dieter Fink > Assignee: Cheng Fang > > At the moment the application need to reference each outbound connection with a remote-ejb-receiver element in the jboss-ejb-client.xml. > But from an application perspective it is not relevant whether the server environment provide one or many receivers or whether the ejb-receiver is a cluster. > It should be possible to add many outbound-socket-binding-ref elements and related properties to the remote-outbound-connection element of the server configuration. > In this case it is possible to keep the application deployment independent from the server environment. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-1728) Allow testsuite parallelism to be controlled from build.xml alone

by Richard Achmatowicz (JIRA)

Richard Achmatowicz created JGRP-1728: ----------------------------------------- Summary: Allow testsuite parallelism to be controlled from build.xml alone Key: JGRP-1728 URL: https://issues.jboss.org/browse/JGRP-1728 Project: JGroups Issue Type: Bug Affects Versions: 3.5 Reporter: Richard Achmatowicz Assignee: Bela Ban Priority: Minor Fix For: 3.5 Directives controlling parallel execution of the JGroups testsuite can be specified at two levels: as parameters to the testng ant task (in build.xml), or as attributes of the suite element in the suite definition files (found in the conf/testng directory). At present, parallelism directives in the various suite definition files (functional.xml, udp.xml, tcp.xml, etc.) take precedence over any directives specified in testng ant tasks. In fact, the directives passed to runtest in build.xml are (incorrectly) not passed through to the testng ant task, so that parallelism is controlled solely from the suite definition files. Making use of parallel execution of test cases when running in the QA lab leads to a higher proportion of test failures, leading to a proliferation of JIRA/bugzilla issues. Therefore it is important that we be able to turn on (turn off) parallel execution of test cases through some simple specification of system properties. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2437) Update slf4j-api to 1.7.5

by Jorge Solorzano (JIRA)

Jorge Solorzano created WFLY-2437: ------------------------------------- Summary: Update slf4j-api to 1.7.5 Key: WFLY-2437 URL: https://issues.jboss.org/browse/WFLY-2437 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Affects Versions: 8.0.0.Beta1 Reporter: Jorge Solorzano Assignee: James Perkins The logger factories in most SLF4J modules namely in jcl-over-slf4j, log4j-over-slf4j, slf4j-jcl, slf4j-jdk14, slf4j-log4j12, and slf4j-simple now use a ConcurrentHashMap instead of a regular HashMap to cache logger instances. This change significantly improves logger retrieval times at the cost of some memory overhead. Acording to SLF4J developers: Given the significance of these performance improvements, users are highly encouraged to migrate to SLF4J version 1.7.5 or later. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2410) composite operation containing a host op does not get rolled out to all hosts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2410?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2410: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1015098|https://bugzilla.redhat.com/show_bug.cgi?id=1015098] from POST to MODIFIED > composite operation containing a host op does not get rolled out to all hosts > ----------------------------------------------------------------------------- > > Key: WFLY-2410 > URL: https://issues.jboss.org/browse/WFLY-2410 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.Beta1 > Reporter: Emanuel Muckenhuber > Assignee: Emanuel Muckenhuber > Fix For: 8.0.0.CR1 > > > If a composite operation contains an operation targeting the domain as well as a single host, it will only get rolled out to the host specified rather than to the complete domain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2428) MDBs should use the full identifier of the resource adapter

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2428?page=com.atlassian.jira.plugin.... ] Jesper Pedersen reassigned WFLY-2428: ------------------------------------- Assignee: Stefano Maestri (was: Jesper Pedersen) > MDBs should use the full identifier of the resource adapter > ----------------------------------------------------------- > > Key: WFLY-2428 > URL: https://issues.jboss.org/browse/WFLY-2428 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB > Affects Versions: 8.0.0.CR1 > Reporter: Jesper Pedersen > Assignee: Stefano Maestri > Fix For: 8.0.0.CR1 > > > The .rar suffix shouldn't be stripped anymore, as the resource adapters are registered under their full name. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) @Resource injection of Datasource on clustered SFSB fails with serialization error

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Jesper Pedersen moved WFLY-30 to JBJCA-1112: -------------------------------------------- Project: IronJacamar (was: WildFly) Key: JBJCA-1112 (was: WFLY-30) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: Deployer JDBC (was: JCA) Security: (was: Public) Fix Version/s: 1.0.22.Final 1.1.2.Final (was: 8.0.0.CR1) > @Resource injection of Datasource on clustered SFSB fails with serialization error > ---------------------------------------------------------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: Deployer, JDBC > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.22.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1112) DataSource marked as Serializable

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1112?page=com.atlassian.jira.plugin... ] Jesper Pedersen updated JBJCA-1112: ----------------------------------- Summary: DataSource marked as Serializable (was: @Resource injection of Datasource on clustered SFSB fails with serialization error) Affects Version/s: 1.1.1.Final 1.0.21.Final > DataSource marked as Serializable > --------------------------------- > > Key: JBJCA-1112 > URL: https://issues.jboss.org/browse/JBJCA-1112 > Project: IronJacamar > Issue Type: Bug > Components: Deployer, JDBC > Affects Versions: 1.0.21.Final, 1.1.1.Final > Reporter: Paul Ferraro > Assignee: Jesper Pedersen > Priority: Critical > Fix For: 1.0.22.Final, 1.1.2.Final > > > See JBPAPP6-1762 for details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1111) Throwable instantiation on TxConnectionListener.TransactionSynchronization

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1111?page=com.atlassian.jira.plugin... ] Jesper Pedersen closed JBJCA-1111. ---------------------------------- Resolution: Rejected http://www.ironjacamar.org/doc/userguide/1.1/en-US/html/ch14.html#ithinki... > Throwable instantiation on TxConnectionListener.TransactionSynchronization > -------------------------------------------------------------------------- > > Key: JBJCA-1111 > URL: https://issues.jboss.org/browse/JBJCA-1111 > Project: IronJacamar > Issue Type: Task > Reporter: Luis Barreiro > Assignee: Jesper Pedersen > > In org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.TransactionSynchronization there is a Throwable that is always instantiated during the creation of the object, but in most cases it's never thrown. > There is a performance penalty associated with filling the stack trace of every exception, even if it's not thrown. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1924) An EJB on a WildFly server can't call another bean on a second server with remoting and SSL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1924?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1924: ----------------------------------------------- Brian Stansberry <brian.stansberry(a)redhat.com> changed the Status of [bug 1025319|https://bugzilla.redhat.com/show_bug.cgi?id=1025319] from POST to MODIFIED > An EJB on a WildFly server can't call another bean on a second server with remoting and SSL > ------------------------------------------------------------------------------------------- > > Key: WFLY-1924 > URL: https://issues.jboss.org/browse/WFLY-1924 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB, Remoting, Security > Affects Versions: 8.0.0.Alpha4 > Environment: WildFly 8.0.0.Beta1-SNAPSHOT from Do 22. Aug 2013, 07:48 UTC > on Linux with Java 1.7.0_25-b15 > Reporter: Bernd Koecke > Assignee: jaikiran pai > Fix For: 8.0.0.Beta1 > > > I configured two WildFly server, one is the service provider (server), the other one the consumer (client). An EJB on the consumer server tries to call an EJB on the provider server and the remoting connection is secured by SSL. But it doesn't work. I can see the negotiation of the cipher suites and then the communication stops. I get a > {{javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?}} > on the provider side. A JavaSE client can call the service provider, but only when SSL_SARTTLS is not set. My current setup is: > subsystem undertow, default-server: > {code:xml} > <https-listener name="defaults" socket-binding="https" security-realm="HttpsRealm"/> > {code} > subsystem ejb3: > {code:xml} > <remote connector-ref="https-remoting-connector" thread-pool-name="default"/> > {code} > Output on the service provider side when the communication stops: > {noformat} > [stdout] (default I/O-3) Using SSLEngineImpl. > [stdout] (default I/O-3) Ignoring unavailable cipher suite: ... > *** 13 lines more *** > [stdout] (default I/O-3) Allow unsafe renegotiation: false > [stdout] (default I/O-3) Allow legacy hello messages: true > [stdout] (default I/O-3) Is initial handshake: true > [stdout] (default I/O-3) Is secure renegotiation: false > [stdout] (default I/O-3) default I/O-3, fatal error: 80: problem unwrapping net record > [stdout] (default I/O-3) javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? > [stdout] (default I/O-3) default I/O-3, SEND TLSv1 ALERT: fatal, description = internal_error > [stdout] (default I/O-3) default I/O-3, WRITE: TLSv1 Alert, length = 2 > [stdout] (default I/O-3) default I/O-3, called closeOutbound() > [stdout] (default I/O-3) default I/O-3, closeOutboundInternal() > [stdout] (default I/O-3) [Raw write]: length = 7 > [stdout] (default I/O-3) 0000: 15 03 01 00 02 02 50 ......P > {noformat} > WildFly consumer config > subsystem remoting, outbound connections: > {code:xml} > <remote-outbound-connection name="provider-one-connection" outbound-socket-binding-ref="provider-ejb" security-realm="ProviderOneRealm" protocol="https-remoting"> > <properties> > <property name="SASL_POLICY_NOANONYMOUS" value="false"/> > </properties> > </remote-outbound-connection> > {code} > The realms contain the key- and truststores and all passwords are configured. > The reason for the communication problem comes from the following code. > The service consumer (or client) WildFly has a remote-outbound-connection in the remoting subsystem config which results in an {{org.jboss.as.remoting.RemoteOutboundConnectionService}}. There is a {{connect()}} method which contains the lines: > {code:java} > OptionMap.Builder builder = OptionMap.builder(); > builder.addAll(this.connectionCreationOptions); > builder.set(SASL_POLICY_NOANONYMOUS, Boolean.FALSE); > builder.set(SASL_POLICY_NOPLAINTEXT, Boolean.FALSE); > builder.set(Options.SASL_DISALLOWED_MECHANISMS, Sequence.of(JBOSS_LOCAL_USER)); > builder.set(Options.SSL_ENABLED, true); > builder.set(Options.SSL_STARTTLS, true); > return endpoint.connect(uri, builder.getMap(), callbackHandler, sslContext); > {code} > My configuration comes from {{this.connectionOptions}} and is overwritten by the defaults. The service consumer will open the connection with {{SSL_STARTTLS==true}}. > The service provider (or server) WildFly uses an https-listener from the undertow subsystem. Which generates an {{org.wildfly.extension.undertow.HttpsListenerService}}. Method {{startListening(XnioWorker worker,...)}} has the following code: > {code:java} > protected void startListening(XnioWorker worker, InetSocketAddress socketAddress, ChannelListener<AcceptingChannel<StreamConnection>> acceptListener) throws IOException { > SSLContext sslContext = securityRealm.getValue().getSSLContext(); > Builder builder = OptionMap.builder().addAll(SERVER_OPTIONS); > builder.set(UndertowOptions.MAX_ENTITY_SIZE, maxUploadSize); > if (securityRealm.getValue().getSupportedAuthenticationMechanisms().contains(AuthMechanism.CLIENT_CERT)) { > builder.set(SSL_CLIENT_AUTH_MODE, REQUESTED); > } > builder.set(Options.USE_DIRECT_BUFFERS,true); > OptionMap combined = builder.getMap(); > XnioSsl xnioSsl = new JsseXnioSsl(worker.getXnio(), combined, sslContext); > sslServer = xnioSsl.createSslConnectionServer(worker, socketAddress, (ChannelListener) acceptListener, combined); > sslServer.resumeAccepts(); > UndertowLogger.ROOT_LOGGER.listenerStarted("HTTPS", getName(), socketAddress); > } > {code} > The OptionMap {{combined}} is used for the {{JsseXnioSsl}} and I can't see a way how to add my own configuration options. The result is that {{SSL_STARTTLS}} is undefined and in {{JsseXnioSsl}} has a method {{connectSsl}} which calls {{openSslConnection}}. There is an event handler build which calls: > {code:java} > new JsseSslStreamConnection(connection, JsseSslUtils.createSSLEngine(sslContext, optionMap, destination), socketBufferPool, applicationBufferPool, optionMap.get(Options.SSL_STARTTLS, false)); > {code} > This sets the flag {{startTls}} of the constructor to false and the member variable {{tls}} in {{org.xnio.ssl.JsseSslStreamConnection}} to true. And when I understand it right, will then the consumer start unencrypted and will only switch to TLS when it is told todo so. But the service provider expectes, because of {{tls==true}}, an encrypted connection right from the beginning. And this generates the above error message/exception. I can reproduce this by using a JavaSE client to call the service provider. This works well when I don't set {{SSL_STARTTLS}} on the client side. But when I set it to {{true}} I get the same behavior like when the client is another WildFly instance. > [~ctomc] said that on the consumer side in the {{connect()}} method the {{builder.addAll(...)}} should be moved to the end after setting the defaults. Thats the reason for this issue. > With this solution I can switch off {{SSL_STARTTLS}} on the consumer(client) side. > Another additional possibility could be to make the provider (server) side configurable that the hard coded options can be overwritten. But I don't know if this fits in the original design. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2013