November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4139) JBatch module dependencies not configured for valid deployments

by Brent Douglas (JIRA)

Brent Douglas created WFLY-4139: ----------------------------------- Summary: JBatch module dependencies not configured for valid deployments Key: WFLY-4139 URL: https://issues.jboss.org/browse/WFLY-4139 Project: WildFly Issue Type: Bug Components: Batch Affects Versions: 9.0.0.Alpha1, 8.2.0.Final Environment: Fedora 19, JDK 8u25, wildfly-dist:9.0.0.Alpha1 Reporter: Brent Douglas Assignee: Jason Greene In BatchEnvironmentProcessor the JBatch subsystem only adds a dependency on wildfly's transaction manager and bean manager if some marker files are detected. (See here) https://github.com/wildfly/wildfly/blob/bfc41360196f5183a005101bf7ac2d7bf... If they are not detected an unhelpful exception is thrown when instantiating the JobOperator: {noformat} 01:18:25,442 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 248.119 sec <<< FAILURE! - in io.machinecode.chainlink.ee.wildfly.WildFlyTest testGlassfish(io.machinecode.chainlink.ee.wildfly.WildFlyTest) Time elapsed: 0.336 sec <<< ERROR! java.util.ServiceConfigurationError: javax.batch.operations.JobOperator: Provider org.jberet.operations.JobOperatorImpl could not be instantiated at org.wildfly.jberet.services.BatchEnvironmentService$WildFlyBatchEnvironment.getArtifactFactory(BatchEnvironmentService.java:123) at org.wildfly.jberet.DelegatingBatchEnvironment.getArtifactFactory(DelegatingBatchEnvironment.java:52) at org.jberet.operations.JobOperatorImpl.<init>(JobOperatorImpl.java:89) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at java.lang.Class.newInstance(Class.java:438) at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:380) at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404) at java.util.ServiceLoader$1.next(ServiceLoader.java:480) at javax.batch.runtime.BatchRuntime.getJobOperator(BatchRuntime.java:57) at io.machinecode.chainlink.ee.wildfly.WildFlyTest.testGlassfish(WildFlyTest.java:36) {noformat} There are valid reasons that these marker files may not be in the deployment, an example being that the deployment might only read metadata from jobs started by other deployments from the configured repository. This check also does not take into account jars in a war's lib dir (for example if you try and run a test using arquillian) or in an ear, which should be allowed. I think there should be two changes. Firstly, those dependencies should be added unconditionally as there are cases where these marker will not be present and they will still be required. Secondly, the exception thrown because the beanManager has not been configured should be thrown earlier in the lifecycle where it will generate a real error message (perhaps in BatchEnvironmentService#start before creating the WildFlyBatchEnvironment where it can first be detected): https://github.com/wildfly/wildfly/blob/bfc41360196f5183a005101bf7ac2d7bf... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-260) Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-260: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1161589|https://bugzilla.redhat.com/show_bug.cgi?id=1161589] from POST to MODIFIED > Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab > ------------------------------------------------------------------------------------------ > > Key: WFCORE-260 > URL: https://issues.jboss.org/browse/WFCORE-260 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-57) Deprecated resource is present in r-r-d of /subsystem=security/security-domain=*

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-57?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-57: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1070214|https://bugzilla.redhat.com/show_bug.cgi?id=1070214] from POST to MODIFIED > Deprecated resource is present in r-r-d of /subsystem=security/security-domain=* > -------------------------------------------------------------------------------- > > Key: WFCORE-57 > URL: https://issues.jboss.org/browse/WFCORE-57 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha4 > Reporter: Harald Pehl > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 1.0.0.Alpha9 > > > When executing > {code} > /subsystem=security/security-domain=*:read-resource-description(recursive-depth=2) > {code} > the acl subresource contains both the deprecated child-resource {{login-module}} and the new one called {{acl-module}}: > {code} > ... > "acl" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > "model-description" => {"classic" => { > "description" => "Access control list configuration. Configures a list of ACL modules to be used.", > ... > "operations" => undefined, > "children" => { > "acl-module" => { > "description" => "ACL module", > "model-description" => {"*" => { > "description" => "List of authentication modules", > ... > "operations" => undefined, > "children" => {} > }} > }, > "login-module" => { > "description" => "Login module", > "model-description" => {"*" => undefined} > } > } > }} > }, > ... > {code} > However the deprecated subresource {{login-modules}} should only appear if setting {{include-aliases=true}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4013) The value of the bound attribute in socket-binding-group messaging is always false

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4013?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4013: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1156360|https://bugzilla.redhat.com/show_bug.cgi?id=1156360] from NEW to MODIFIED > The value of the bound attribute in socket-binding-group messaging is always false > ---------------------------------------------------------------------------------- > > Key: WFLY-4013 > URL: https://issues.jboss.org/browse/WFLY-4013 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.3.1. > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > The value of bound attribute in messaging socket group is always false. > {noformat} > /socket-binding-group=standard-sockets/socket-binding=messaging:read-resource(include-runtime=true, recursive=true) > { > "outcome" => "success", > "result" => { > "bound" => false, > "bound-address" => undefined, > "bound-port" => undefined, > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "messaging", > "port" => 5445 > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4137) Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4137?page=com.atlassian.jira.plugin.... ] Tomas Hofman updated WFLY-4137: ------------------------------- Tester: Martin Swiech > Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-4137 > URL: https://issues.jboss.org/browse/WFLY-4137 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. > Description of problem: > There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. > How reproducible: > always > Additional info: > It's also wrong in EAP 6.2. > EAP 6.1 is OK. > There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4138) Upgrade JBossWS CXF from 5.0.0.Beta2 to 5.0.0.BetaX

by Tomas Hofman (JIRA)

Tomas Hofman created WFLY-4138: ---------------------------------- Summary: Upgrade JBossWS CXF from 5.0.0.Beta2 to 5.0.0.BetaX Key: WFLY-4138 URL: https://issues.jboss.org/browse/WFLY-4138 Project: WildFly Issue Type: Component Upgrade Components: Web Services Affects Versions: 9.0.0.Alpha1 Reporter: Tomas Hofman Assignee: Alessio Soldano JBossWS CXF needs upgrade because of WFLY-4137. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4137) Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)

by Tomas Hofman (JIRA)

[ https://issues.jboss.org/browse/WFLY-4137?page=com.atlassian.jira.plugin.... ] Tomas Hofman updated WFLY-4137: ------------------------------- Description: Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. Description of problem: There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. How reproducible: always Additional info: It's also wrong in EAP 6.2. EAP 6.1 is OK. There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly. was: Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. Description of problem: There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. How reproducible: always Additional info: It's also wrong in EAP 6.2. EAP 6.1 is OK. There is a patch attached in BZ-1167348 for JBoss CXF 4.3.3. The same fix should be also applied to JBoss CXF 5.0.0 which is used by Wildfly. > Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...) > ------------------------------------------------------------------------------------------------- > > Key: WFLY-4137 > URL: https://issues.jboss.org/browse/WFLY-4137 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 9.0.0.Alpha1 > Reporter: Tomas Hofman > Assignee: Tomas Hofman > > Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. > Description of problem: > There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. > How reproducible: > always > Additional info: > It's also wrong in EAP 6.2. > EAP 6.1 is OK. > There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4137) Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)

by Tomas Hofman (JIRA)

Tomas Hofman created WFLY-4137: ---------------------------------- Summary: Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...) Key: WFLY-4137 URL: https://issues.jboss.org/browse/WFLY-4137 Project: WildFly Issue Type: Bug Components: Web Services Affects Versions: 9.0.0.Alpha1 Reporter: Tomas Hofman Assignee: Tomas Hofman Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible. Description of problem: There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it. How reproducible: always Additional info: It's also wrong in EAP 6.2. EAP 6.1 is OK. There is a patch attached in BZ-1167348 for JBoss CXF 4.3.3. The same fix should be also applied to JBoss CXF 5.0.0 which is used by Wildfly. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-199) The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer commented on DROOLS-199: ----------------------------------------------- tried to update tycho version to 0.21.0 and build droolsjbpm-toold with maven 3.2.3 but it is still not compiling: https://gist.github.com/mbiarnes/f7341948b7a2602ecc71 > The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x > -------------------------------------------------------------- > > Key: DROOLS-199 > URL: https://issues.jboss.org/browse/DROOLS-199 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > Old description: > To reproduce: > - Install maven 3.1.0 > - Run mvn-all.sh clean install -Dfull > Note: Any changes to the pom must still allow them to run with 3.0.5 too. > 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list. > So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say). > 2) There might be other surprises... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-286) The SecurityRealmService should only perform a generic mapping to RealmUser if really required.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-286?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-286: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1168595|https://bugzilla.redhat.com/show_bug.cgi?id=1168595] from POST to MODIFIED > The SecurityRealmService should only perform a generic mapping to RealmUser if really required. > ----------------------------------------------------------------------------------------------- > > Key: WFCORE-286 > URL: https://issues.jboss.org/browse/WFCORE-286 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > > If there is a more accurate way to calculate the RealmUser then use it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

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 2014