Interoperability testing
by David M. Lloyd
Folks, we need some solution for interoperability testing between
WildFly versions. Something CI-based would be ideal - remember the old
jboss-test stuff that could test multiple versions of things? Something
like that but updated for modularity and/or in-container execution and
Maven support seems to be indicated.
We'd want to test interop between the current release and each previous
Final release. Anyone have any ideas or is willing to tackle such a beast?
--
- DML
10 years, 9 months
Favour jboss-persistence.xml if present
by Klein, Christopher
Hey guys,
I already filled out a feature request in JIRA (https://issues.jboss.org/browse/WFLY-2816).
We have the situation that our development environment (currently JBoss AS 7.1.1) differs from the production instance (WebSphere 8.5). Our persistence.xml has to be adjusted for production environment: different jta-data-source, different properties. The dirty solution for this problem would be to generate separate build artifacts for both environments. As you can imagine I don't like the idea of having two binaries just because of a few different settings. Other options (WildFly or WebSphere specific JPA properties; extending Hibernate persistence provider) do not work.
A much nicer solution would be: WildFly checks on deployment process for the existence of a jboss-persistence.xml. If it does, the jboss-persistence.xml is used for configuring the JPA subsystem. Otherwise it falls back to the standard persistence.xml. The jboss-persistence.xml would use the XML schema from persistence.xml.
I lookup into the WildFly sources and this change should be an easy patch which I would provide.
So here are my questsions:
1. Are you generally interested in accepting such a pull request or is it a feature you don't want?
2. Does another solution exists to my problem apart from generating different artifacts which makes this pull request needless?
Greetings from Wolfsburg/Germany,
Christopher
10 years, 9 months
Pull requests testing using IPv6
by Brian Stansberry
Just an FYI, the CI job that tests github pull requests has been
reconfigured to test using IPv6 addresses.
This is the way the PR testing was done for most of AS7. We've gotten
away from it for a while but now we're switching back to help catch
regressions or new tests that incorrectly assume IPv4.
The nightly build job still uses the IPv4 config, as do the
"master-ignore" jobs we often run before merging sets of patches. So we
have coverage both ways.
--
Brian Stansberry
Senior Principal Software Engineer
JBoss by Red Hat
10 years, 9 months
Decoding query name attribute in deployment/subsystem/jpa/hibernate-persistence-unit/query-cache nodes
by Thomas Segismont
Hi,
deployment/subsystem/jpa/hibernate-persistence-unit/query-cache nodes
expose an "encoded" query name attribute. Here's an example:
"rhq.ear/rhq-core-domain-ejb3.jar#rhqpu.rhq.ear_divide_rhq_minus_core_minus_domain_minus_ejb3.jar#rhqpu.rhq.ear_divide_rhq_minus_core_minus_domain_minus_ejb3.jar#rhqpu.SELECT_space_subject_newline_FROM_space_Subject_space_subject_newline_WHERE_space__left_paren__space_LOWER_left_paren__space_subject.name_space__right_paren__space_like_space__colon_name_space_ESCAPE_space__quote_\\_quote__space__space__right_paren__newline_ORDER_space_BY_space_subject.id_space_ASC_newline_"
I could write something to decode every occurrence of "_minus_",
"_space_" and so on, provided I can get the list of all the keywords in
use. But I wonder if there's already a library in the Hibernate
subsystem which does that.
By the way, these nodes exist in AS7 and EAP6, but I found no equivalent
in Wildfly management model. Did I miss the definition on the Wildscribe
site?
http://wildscribe.github.io/JBoss%20AS7/7.1.1/deployment/subsystem/jpa/hi...
Thanks,
Thomas
10 years, 10 months
Small Defect in cli xa-data-source command
by Marrrrck
Hello everyone,
I think I found a minor defect in the jboss-cli /xa-data-source operation
in Widlfly 8. Can anyone confirm this or correct me if I'm wrong?
Currently the jboss-cli doesn't let you set the jta true/false property on
an XA data source. You can set this property on a regular data source, but
not an XA one. Is this intentional or a defect?
If it is a defect, I think the problem might be in this file:
https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or...
You can see on line 419 that DATASOURCE_ATTRIBUTE includes the JTA
attribute definition:
static final SimpleAttributeDefinition[] DATASOURCE_ATTRIBUTE = new
SimpleAttributeDefinition[]{CONNECTION_URL,
> DRIVER_CLASS, Constants.DATASOURCE_CLASS, JNDI_NAME,
> DATASOURCE_DRIVER,
> NEW_CONNECTION_SQL, URL_DELIMITER,
> URL_SELECTOR_STRATEGY_CLASS_NAME, USE_JAVA_CONTEXT,
> *JTA*, org.jboss.as.connector.subsystems.common.pool.Constants.MAX_POOL_SIZE,
But on line 492, the XA_DATASOURCE_ATTRIBUTE doesn't have JTA
static final SimpleAttributeDefinition[] XA_DATASOURCE_ATTRIBUTE =
new SimpleAttributeDefinition[]{
> Constants.XA_DATASOURCE_CLASS, JNDI_NAME, DATASOURCE_DRIVER,
> NEW_CONNECTION_SQL, URL_DELIMITER,
> URL_SELECTOR_STRATEGY_CLASS_NAME, USE_JAVA_CONTEXT,
> org.jboss.as.connector.subsystems.common.pool.Constants.MAX_POOL_SIZE,
Would just adding "JTA," after USE_JAVA_CONTEXT on line 492 fix this, or is
there more that needs to be done? I'm happy to submit a pull request to
fix, but it is such a minor change that it might be easier for someone
already working in the code to do it.
Thanks for your help and my apologies if this is already been reported or
previously discussed.
Marc Zbyszynski
Verifi LLC
http://verificoncrete.com/
10 years, 10 months
localhost:8080 always has AS 7 running, even right after reboot
by tjc
How can I disable as 7 from starting automatically whenever I login to my pc
?
I need to use other app servers on this port.
I am using jboss-as-7.1.1.Final, standalone config, more or less out of the
box.
Right after booting and logging in, if I browse to localhost:8080 the as 7
server screen will be there and tell me it is running. (no other apps have
been started)
I want it to only start when I tell it to.
trying to stop it using the cli just gets me an error saying:
"The controller is not available at localhost:9999"
--
View this message in context: http://wildfly-development.1055759.n5.nabble.com/localhost-8080-always-ha...
Sent from the WildFly Development mailing list archive at Nabble.com.
10 years, 10 months
WFLY-818 Slave host does not register to DC
by Claudio Miranda
Hi, do you have any solution for this ?
What do you think about this ?
1. HC starts with NO --cached-dc, it try to registers to DC, if it
doesn't register, HC fails to starts, as it is today.
2. HC starts with --cached-dc, it try to registers to DC,
a) if HC doesn't register to DC, HC uses the cached copy of
domain.xml. Try to registers to DC at interval times, if register is
successful see 3.a
b) if HC registers to DC, it works as is today copy domain.xml from DC
and replaces local backup.
3. HC starts with NO --cached-dc, HC register to DC, everything works
as is today. If HC disconnects from DC (unknown reason), HC keeps
trying to registers at interval times.
a) HC re-connects to DC, and detects domain.xml changed between DC and
HC. HC emits a warning and asks to restart the HC and their servers.
regards
--
Claudio Miranda
claudio(a)claudius.com.br
http://www.claudius.com.br
10 years, 10 months
How to map a client certificate to a management user?
by Thomas Segismont
Hi,
I have setup client certificate authentication on AS7.1.1 with this
Management realm definition:
<security-realm name="ManagementRealm">
<server-identities>
<ssl>
<keystore path="server.jks"
relative-to="jboss.server.config.dir" password="abcdef"/>
</ssl>
</server-identities>
<authentication>
<truststore path="server.jks"
relative-to="jboss.server.config.dir" password="abcdef" />
<properties path="mgmt-users.properties" relative
to="jboss.server.config.dir"/>
</authentication>
</security-realm>
When I try to browse the admin console in Firefox, it asks me to confirm
I want to authenticate with the client cert (good) and then I can only
see the error page:
===
Your JBoss Application Server 7 is running.
However you have not yet added any users to be able to access the admin
console.
===
How can I map a client certificate to a management user?
Thanks for your help,
Thomas
10 years, 10 months
Re: [wildfly-dev] "It's The Final Countdown!"
by Jason Greene
Hmm I guess we shouldn’t use that keyboard riff when you walk up to give your next JUDCon talk :)
4.3.1 sounds like a good thing to get in. Let’s plan on that.
On Jan 21, 2014, at 1:41 PM, Steve Ebersole <steven.ebersole(a)gmail.com> wrote:
> Damn it, you ruined my day putting that song in my head! ;)
>
> We should talk about using Hibernate ORM 4.3.1 here. One bug at least was hitting some WildFly users: https://hibernate.atlassian.net/browse/HHH-8884
>
> I am cutting 4.3.1 tomorrow...
>
>
> On Tue 21 Jan 2014 01:00:22 PM CST, Jason Greene wrote:
>>
>> No this isn’t the Europe song (Sorry to disappoint!).
>>
>> It is however the countdown to WildFly 8 Final release!
>>
>> The key things that remain are:
>>
>> 1) Final Components - We need PRs upgrading to “Final” for all outstanding
>> subcomponents[1]. If you own one of them, then please make this a high priority.
>> The sooner the better.
>>
>> 2) Identify Blockers - We need to identify all remaining blockers that have been
>> reported against CR1. I’m hoping everyone can look through the forms for likely
>> blockers and convert them to JIRAs. As a reminder a blocker is anything that is
>> mass user effecting and severe in nature. Examples include: hangs, crashes,
>> memory leaks, vulnerabilities, and data corruption.
>>
>> 3) JASPIC Acceptance - A few of you on this list have noted issues. We need to
>> ensure that the Final release has addressed the outstanding issues.
>>
>> Thanks!
>>
>> [1] Outstanding components.
>>
>> io.undertow 1.0.0.Beta30
>> io.undertow.jastow 1.0.0.CR1
>> org.glassfish.javax.el 3.0-b07
>> org.hibernate.search 4.5.0.Alpha2 *exception*
>> org.infinispan.protostream 1.0.0.CR1
>> org.jberet 1.0.0.CR1
>> org.jboss.ejb-client 2.0.0.Beta5
>> org.jboss.narayana 5.0.0.CR2
>> org.jboss.jsfunit 2.0.0.Beta1
>> org.jboss.logging.jboss-logging-tools 1.2.0.Beta1
>> org.jboss.metadata 8.0.0.CR1
>> org.jboss.mod_cluster 1.3.0.Alpha1
>> org.jboss.msc.jboss-msc 1.2.0.CR1
>> org.jboss.xnio.netty.netty-xnio-transport 0.1.1.CR2
>> org.jboss.remote-naming 2.0.0.Beta2
>> org.jboss.remoting 4.0.0.Beta3
>> org.jboss.remotingjmx.remoting-jmx 2.0.0.CR4
>> org.jboss.sasl 1.0.4.CR1
>> org.jboss.spec.javax.el.jboss-el-api_3.0_spec 1.0.0.Beta1
>> org.jboss.spec.javax.security.auth.message.jboss-jaspi-api_1.1_spec 1.0.0.Alpha1
>> org.jboss.spec.javax.security.jacc.jboss-jacc-api_1.5_spec 1.0.0.Beta1
>> org.jboss.spec.javax.servlet.jsp.jboss-jsp-api_2.3_spec 1.0.0.Beta1
>> org.jboss.spec.javax.servlet.jstl.jboss-jstl-api_1.2_spec 1.0.4.Beta1
>> org.jboss.xnio 3.2.0.Beta4
>> org.picketbox 4.0.20.Beta4
>> org.wildfly.security.manager 1.0.0.Beta3
>>
>>
>>
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
10 years, 10 months
