September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3724) Batch jobs don't receive partition-specific parameters

by Cheng Fang (JIRA)

[ https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin.... ] Cheng Fang edited comment on WFLY-3724 at 9/2/14 5:39 PM: ---------------------------------------------------------- See batch spec group discussion thread: https://java.net/projects/jbatch/lists/public/archive/2014-08/message/2 https://java.net/projects/jbatch/lists/public/archive/2014-09/message/0 was (Author: cfang): See batch spec group discussion thread: https://java.net/projects/jbatch/lists/public/archive/2014-08/message/2 > Batch jobs don't receive partition-specific parameters > ------------------------------------------------------ > > Key: WFLY-3724 > URL: https://issues.jboss.org/browse/WFLY-3724 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Batch > Affects Versions: 8.1.0.Final > Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly 8.1.0 Final > Reporter: Ari Silvan > Assignee: Enrique González Martínez > > When defining a batch job chunk step to run as partitions, ItemReader doesn't receive the partition-specific parameters specified by an implementation of the PartitionPlan interface. Parameters are null. See steps to reproduce for further details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-4) Add the ability to override the specific version of Maven artifacts

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-4?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFBUILD-4: -------------------------------------- Another thing to note is that there is a requirement to support multiple different versions of artifacts, as some feature packs may need a different version to what is supplied by core, and as such will create a module with a different slot name. If we just use the maven version of a dependency this is no longer possible. In general the same file *must* result in the same server being provisioned, no matter what front end to the provisioning library is in use. > Add the ability to override the specific version of Maven artifacts > ------------------------------------------------------------------- > > Key: WFBUILD-4 > URL: https://issues.jboss.org/browse/WFBUILD-4 > Project: WildFly Build Tools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha3 > > > e.g. it should be possible to assemble a server with a newer version of Weld or Resteasy that what was provided in the feature pack. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-111) ClassLoaderLogContextSelector should optionally include parent CL for context scanning

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-111?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-111: --------------------------------- Summary: ClassLoaderLogContextSelector should optionally include parent CL for context scanning (was: ClassLoaderLogContextSelector - include parent CL for context scanning) > ClassLoaderLogContextSelector should optionally include parent CL for context scanning > -------------------------------------------------------------------------------------- > > Key: LOGMGR-111 > URL: https://issues.jboss.org/browse/LOGMGR-111 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.5.2.Final > Reporter: Dominik Pospisil > Assignee: James Perkins > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3803) Missing -jandex.jar libs with build using feature-pack

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3803?page=com.atlassian.jira.plugin.... ] Stuart Douglas reassigned WFLY-3803: ------------------------------------ Assignee: Stuart Douglas (was: Tomaz Cerar) > Missing -jandex.jar libs with build using feature-pack > ------------------------------------------------------ > > Key: WFLY-3803 > URL: https://issues.jboss.org/browse/WFLY-3803 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Alessio Soldano > Assignee: Stuart Douglas > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > After the recent changes to have feature-packs, the build is not creating {noformat}-jandex.jar{noformat} libs anymore. We used to have two of them in the org.apache.cxf.impl module. Those are strictly required for WS-* functionalities. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-4) Add the ability to override the specific version of Maven artifacts

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-4?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFBUILD-4: -------------------------------------- Provisioning should not be taking information from maven, all the information to provision a server should be specified in the server provisioning file. All overrides have to be explicitly specified, otherwise if maven somehow brings in a transient dependency that happens to be also used by a feature pack then this will be un-intentionally overridden. > Add the ability to override the specific version of Maven artifacts > ------------------------------------------------------------------- > > Key: WFBUILD-4 > URL: https://issues.jboss.org/browse/WFBUILD-4 > Project: WildFly Build Tools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha3 > > > e.g. it should be possible to assemble a server with a newer version of Weld or Resteasy that what was provided in the feature pack. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2384) 2 RAs with the same ResourceAdapter classes do not work (they overlap in JCA internals)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2384?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2384: ----------------------------------------------- Jesper Pedersen <jpederse(a)redhat.com> changed the Status of [bug 1023380|https://bugzilla.redhat.com/show_bug.cgi?id=1023380] from NEW to CLOSED > 2 RAs with the same ResourceAdapter classes do not work (they overlap in JCA internals) > --------------------------------------------------------------------------------------- > > Key: WFLY-2384 > URL: https://issues.jboss.org/browse/WFLY-2384 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Ivo Studensky > Assignee: Jesper Pedersen > > SimpleResourceAdapterRepository implementation breaks the possibility to deploy 2 separate resource adapters with the same resource adapter class to WildFly server. > More details in the linked IJ jira. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1181) Recovery is not run for XA datasource which does not define password under <security>

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1181?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1181: ------------------------------------------------ Jesper Pedersen <jpederse(a)redhat.com> changed the Status of [bug 1107991|https://bugzilla.redhat.com/show_bug.cgi?id=1107991] from NEW to CLOSED > Recovery is not run for XA datasource which does not define password under <security> > ------------------------------------------------------------------------------------- > > Key: JBJCA-1181 > URL: https://issues.jboss.org/browse/JBJCA-1181 > Project: IronJacamar > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Deployer > Affects Versions: 1.0.26.Final, 1.1.6.Final, 1.2.0.Beta2 > Reporter: Ondřej Chaloupka > Assignee: Jesper Pedersen > Fix For: 1.0.27.Final, 1.2.0.Beta4 > > Attachments: server.log > > > If you do not define password for xa datsource then recovery does not run despite the fact that there is no need of password for connection to database. > When you define just: > {code} > <security> > <user-name>crashrec</user-name> > </security> > {code} > and database is set to not require password - e.g. for postgres > vim /var/lib/pgsql/data/pg_hba.conf > you define connection with 'trust' > host all all 127.0.0.1/32 trust > Then you will experience WARNING message during recovery and recovery itself on the xa datasource is not run > {code} > 10:12:58,137 WARN [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000904: No security domain defined for crash recovery: java:jboss/xa-datasources/CrashRecoveryDS > 10:12:58,138 WARN [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000905: Subject for crash recovery was null: java:jboss/xa-datasources/CrashRecoveryDS > {code} > Whole configuration of xa-datasource used: > {code} > <xa-datasource jndi-name="java:jboss/xa-datasources/CrashRecoveryDS" pool-name="CrashRecoveryDS" enabled="true" use-java-context="true"> > <xa-datasource-property name="DatabaseName">crashrec</xa-datasource-property> > <xa-datasource-property name="PortNumber">5432</xa-datasource-property> > <xa-datasource-property name="ServerName">127.0.0.1</xa-datasource-property> > <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class> > <driver>postgres</driver> > <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> > <xa-pool> > <min-pool-size>5</min-pool-size> > <max-pool-size>50</max-pool-size> > </xa-pool> > <security> > <user-name>crashrec</user-name> > </security> > <recovery> >  > </recovery> > <validation> > <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker"/> > <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter"/> > </validation> > <timeout> > <blocking-timeout-millis>30000</blocking-timeout-millis> > <idle-timeout-minutes>15</idle-timeout-minutes> > </timeout> > <statement> > <prepared-statement-cache-size>75</prepared-statement-cache-size> > </statement> > </xa-datasource> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3729) config-properties should be "read-write" by CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3729?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3729: ----------------------------------------------- Jesper Pedersen <jpederse(a)redhat.com> changed the Status of [bug 1129496|https://bugzilla.redhat.com/show_bug.cgi?id=1129496] from NEW to CLOSED > config-properties should be "read-write" by CLI > ----------------------------------------------- > > Key: WFLY-3729 > URL: https://issues.jboss.org/browse/WFLY-3729 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JCA > Environment: EAP 6.1.0 > RHEL 6.5 > Reporter: Jooho Lee > Assignee: Jesper Pedersen > Labels: eap6, jboss > > Using CLI, it is possible to control websphere message server but config-properties can not be modified or created because its access-type is read-only. > For example, > {code:title=CLI Command|borderStyle=solid} > /profile=MMPS-dev-03-profile/subsystem=resource-adapters/resource-adapter=wmq.jmsra.rar/admin-objects=FDSLPublishQueue/config-properties=baseQueueName:write-attribute(name=value,value=test) > { > "outcome" => "failed", > "failure-description" => "JBAS014639: Attribute value is not writable", > "rolled-back" => true > } > {code} > This is because the fact that baseQueueName(config-properties)' access-type is read-only but I don't see any reasons why this attritbute couldn't be writable. > Is there any reasons the attribute has to be read-only? otherwise, it should be read-write. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-81) {crypt} passwords in Apache DS longer than 8 characters are not compatible with Elytron

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-81: ----------------------------------- Summary: {crypt} passwords in Apache DS longer than 8 characters are not compatible with Elytron Key: ELY-81 URL: https://issues.jboss.org/browse/ELY-81 Project: WildFly Elytron Issue Type: Bug Security Level: Public (Everyone can see) Components: Password Types, Realms Reporter: Darran Lofthouse Fix For: 1.0.0.Beta1 I have left this out of the pull request for LDAP as this is going to require some in-depth investigation of the two implementations and how they are both interpreting passwords longer than 8 characters. It may be there is a subtle variation in the two implementations or it may just be one has a bug. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-81) Expose address of DC as runtime attributes on the HC

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-81?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFCORE-81: ---------------------------------------- It belongs somewhere in /host=hc-1 itself. Not in the core-service=host-environment child as that resource is about the environmental info the HC picked up at initial boot, i.e. stuff that comes in from the command line. The most relevant place is the domain-controller attribute on the /host=hc-1 resource: {code} [domain@localhost:9999 host=slave-a] :read-resource { "outcome" => "success", "result" => { "directory-grouping" => "by-server", "domain-controller" => {"remote" => { "port" => expression "${jboss.domain.master.port:9999}", "host" => expression "${jboss.domain.master.address}", "username" => undefined, "admin-only-policy" => undefined, "security-realm" => "ManagementRealm" }}, {code} That would need something like "resolved-scheme", "resolved-host" and "resolved-port" fields added. The "resolved-scheme" comes in because of WFCORE-75 which is currently being worked on. We can no longer assume the protocol scheme is "remote". My thinking is we only expose this for the slave HC's; i.e. it's part of that domain-controller => remote structure that only exists on a slave. We don't add something to the domain-controller => local structure that exists on the master, because it would be redundant, and once WFCORE-75 is done, vague. The way to learn about how to communicate with any HC that you're already connected to is via the existing /host=*/core-service=management/management-interface=* resources. As for what class to use to expose this... that's a tough question. Looking at this, it's quite complex. Possible places are org.jboss.as.host.controller.MasterDomainControllerClient or org.jboss.as.domain.controllerLocalHostControllerInfo. The way that domain-controller attribute is handled would need to change though. Currently its contents are set once via RemoteDomainControllerAddHandler (for the slave aka remote case) and LocalDomainControllerAddHandler (for the master aka local case) and thereafter reading that attribute is a simple, using the default read handler. But now HostResourceDefinition L250 would need to register a custom read handler instead of null, one that can read the add in the dynamically determined "resolved-scheme", "resolved-host" and "resolved-port" fields. So, not a simple task. > Expose address of DC as runtime attributes on the HC > ---------------------------------------------------- > > Key: WFCORE-81 > URL: https://issues.jboss.org/browse/WFCORE-81 > Project: WildFly Core > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Heiko Rupp > Labels: rhq > > Currently there is no way to learn about the http management port of the DC from a slave's host.xml or runtime. > 17:02:31] <pilhuhn> I am reading host.xml to find the DC, so that I can contact its http port for e.g. querying the /socket-binding-group if the one on the host is undefined > [17:02:41] <+bstansberry> I don't want it in the config, but I'm ok with adding it as a runtime attribute > [17:04:13] <pilhuhn> bstansberry fine with me when I can query the HC for the http port of the DC > [17:04:46] <+bstansberry> pilhuhn: the native API port should be a runtime attribute as well > [17:04:51] <+bstansberry> yes please > [17:05:04] <+bstansberry> what i mean by that is we should expose it as a runtime attribute > 17:05:49] <+bstansberry> the config bit is an instruction to the HC, but we are going to add alternatives, e.g. a multicast address > [17:06:55] <+bstansberry> so using the config will not be a reliable source; runtime can be -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014