February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6297: ------------------------------ Parent: WFLY-3854 Issue Type: Sub-task (was: Task) > Identify problems introduced with new JDK9 versioning scheme > ------------------------------------------------------------ > > Key: WFLY-6297 > URL: https://issues.jboss.org/browse/WFLY-6297 > Project: WildFly > Issue Type: Sub-task > Affects Versions: 10.0.0.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6297) Identify problems introduced with new JDK9 versioning scheme

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6297?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-6297: ------------------------------ Fix Version/s: (was: 10.1.0.Final) > Identify problems introduced with new JDK9 versioning scheme > ------------------------------------------------------------ > > Key: WFLY-6297 > URL: https://issues.jboss.org/browse/WFLY-6297 > Project: WildFly > Issue Type: Sub-task > Affects Versions: 10.0.0.Final > Reporter: Richard Opalka > Assignee: Richard Opalka > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-429) LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-429?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-429: --------------------------------- Fix Version/s: 1.1.0.Beta5 > LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible. > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-429 > URL: https://issues.jboss.org/browse/ELY-429 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Class LdapSecurityRealm cannot be used from elytron subsystem since is has only package access, see [1]. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta4/src/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-429) LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-429?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-429: --------------------------------- Priority: Critical (was: Major) > LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible. > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-429 > URL: https://issues.jboss.org/browse/ELY-429 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta5 > > > Class LdapSecurityRealm cannot be used from elytron subsystem since is has only package access, see [1]. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta4/src/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-429) LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-429?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-429: --------------------------------- Summary: LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible. (was: Missing public modifier in LdapSecurityRealm) > LdapSecurityRealmBuilder.build() should be retunring an interface type and not the implementation type as the implementation is not visible. > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ELY-429 > URL: https://issues.jboss.org/browse/ELY-429 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Class LdapSecurityRealm cannot be used from elytron subsystem since is has only package access, see [1]. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta4/src/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-429) Missing public modifier in LdapSecurityRealm

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-429?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas commented on ELY-429: ---------------------------------- Running following CLI command: {code} /subsystem=elytron/ldap-realm=ldapRealm:add(dir-context={url="ldap://127.0.0.1:10389",principal="uid=admin,ou=system",credential="secret"},identity-mapping={rdn-identifier=uid,search-base-dn="ou=People,dc=jboss,dc=org",attribute-mapping=[from=cn]}) {code} results to: {code} { "outcome" => "failed", "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.BootstrapMethodError: java.lang.IllegalAccessError: tried to access class org.wildfly.security.auth.provider.ldap.LdapSecurityRealm from class org.wildfly.extension.elytron.LdapRealmDefinition$RealmAddHandler", "rolled-back" => true } {code} and following Excetion is logged to server log: {code} ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("ldap-realm" => "ldapRealm") ]): java.lang.BootstrapMethodError: java.lang.IllegalAccessError: tried to access class org.wildfly.security.auth.provider.ldap.LdapSecurityRealm from class org.wildfly.extension.elytron.LdapRealmDefinition$RealmAddHandler at org.wildfly.extension.elytron.LdapRealmDefinition$RealmAddHandler.performRuntime(LdapRealmDefinition.java:228) at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337) at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1344) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:208) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:130) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:152) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:148) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:92) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:148) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363) at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:472) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320) Caused by: java.lang.IllegalAccessError: tried to access class org.wildfly.security.auth.provider.ldap.LdapSecurityRealm from class org.wildfly.extension.elytron.LdapRealmDefinition$RealmAddHandler ... 23 more {code} In case when class LdapSecurityRealm becomes public then mentioned above CLI command finish successfully. > Missing public modifier in LdapSecurityRealm > -------------------------------------------- > > Key: ELY-429 > URL: https://issues.jboss.org/browse/ELY-429 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Class LdapSecurityRealm cannot be used from elytron subsystem since is has only package access, see [1]. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta4/src/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1068) java.lang.UnsupportedOperationException thrown by org.drools.core.reteoo.BaseLeftTuple.getBlocker(BaseLeftTuple.java:535)

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1068?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1068: ------------------------------------- Thanks a lot Bill, I reproduced the same problem with the far easier test case I'm pasting below. I'm investigating this issue and I'll keep you updated. {code} @Test public void testNotWithBreakingBranch() throws Exception { // DROOLS-1068 String drl = "rule R when\n" + " Integer()\n" + " if (true) break[branch]\n" + " not Integer()\n" + "then\n" + " System.out.println(\"main\");\n" + "then[branch]\n" + " System.out.println(\"branch\");\n" + "end\n"; KieSession ksession = new KieHelper().addContent( drl, ResourceType.DRL ) .build() .newKieSession(); FactHandle fh = ksession.insert(1); ksession.fireAllRules(); ksession.delete(fh); ksession.fireAllRules(); } {code} > java.lang.UnsupportedOperationException thrown by org.drools.core.reteoo.BaseLeftTuple.getBlocker(BaseLeftTuple.java:535) > ------------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-1068 > URL: https://issues.jboss.org/browse/DROOLS-1068 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.3.0.Final > Reporter: Bill Tuminaro > Assignee: Mario Fusco > Attachments: droolsReproducer.jar, droolsReproducer.jar, Person.java, UnsupportedOperationTest.drl, UnsupportedOperationTest.java > > > We have encountered this issue when we insert a fact matching a certain rule, delete the fact then call fire all rules. > A reproducer is attached. > -BillT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-429) Missing public modifier in LdapSecurityRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-429?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse commented on ELY-429: -------------------------------------- Do you have an error message? This security realm is instantiated by it's builder which is in the same package. > Missing public modifier in LdapSecurityRealm > -------------------------------------------- > > Key: ELY-429 > URL: https://issues.jboss.org/browse/ELY-429 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta4 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > Class LdapSecurityRealm cannot be used from elytron subsystem since is has only package access, see [1]. > [1] https://github.com/wildfly-security/wildfly-elytron/blob/1.1.0.Beta4/src/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1416) PostgreSQL Non-XA DS - relation does not exist

by Anton Saburov (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1416?page=com.atlassian.jira.plugi... ] Anton Saburov updated WFCORE-1416: ---------------------------------- Labels: datasource postgresql (was: ) > PostgreSQL Non-XA DS - relation does not exist > ---------------------------------------------- > > Key: WFCORE-1416 > URL: https://issues.jboss.org/browse/WFCORE-1416 > Project: WildFly Core > Issue Type: Bug > Environment: WildFly 10.0.0.Final, PostgreSQL 9.4, PostgreSQL JDBC Driver 9.3 and 9.4 > Reporter: Anton Saburov > Labels: datasource, postgresql > > I tried to check the same in WildFly 8.2.1 and 9.0.2 - everything is working > WildFly 10 - I get error. > Registered PostgreSQL JDBC driver as a module: > module add --name=org.postgresql --resources=postgresql-9.3-1102-jdbc41.jar --resource-delimiter=, --dependencies=javax.api,javax.transaction.api > Registered PostgreSQL JDBC driver: > /subsystem=datasources/jdbc-driver=postgresql:add(driver-name=postgresql, driver-module-name=org.postgresql, driver-class-name=org.postgresql.Driver, driver-datasource-class-name=org.postgresql.ds.PGSimpleDataSource, driver-xa-datasource-class-name=org.postgresql.xa.PGXADataSource) > Created Non-XA Datasource - MyDS and XA Datasource MyXADS > When I try to use Non-XA DS - I got error: relation "<table>" does not exist > When I try to use XA DS - all is OK. > I checked list of schema by SQL script: "select distinct table_schema from information_schema.tables" > For Non-XA I see only this: > - information_schema > - pg_default > For XA I see this: > - information_schema > - pg_default > - public > Maybe I have to make some additional options for DS ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5857) HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but start is not called in Node1 again after Node1 is selected Master again

by Serg Jakean19019 (JIRA)

[ https://issues.jboss.org/browse/WFLY-5857?page=com.atlassian.jira.plugin.... ] Serg Jakean19019 commented on WFLY-5857: ---------------------------------------- thanks i have meant that examples in Git contained some good docu about installation, start, but no docu that describes methods of new services, classes "how do they work". it is important if implemented services are very new concept and don't have similar models-descriptions in past. > HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but start is not called in Node1 again after Node1 is selected Master again > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-5857 > URL: https://issues.jboss.org/browse/WFLY-5857 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 9.0.1.Final > Environment: Wildfly-9.0.1.Final. Full HA Configuration. Cluster Full Ha > Reporter: Serg Jakean19019 > Assignee: Paul Ferraro > > HASingleton Stop is called in Node1 (Master) during down of Node2 in cluster, but Start is not called in Node1 again after Node1 is selected Master again. > If Node2 ist started again, than Start is called in Node1 again. > This Solution worked in 8.2.0.Final and was taken from GitHub > Part of Log after Stop in Singletone: > 2015-12-16 10:25:39,832 WARN [org.wildfly.clustering.server] (remote-thread--p8-t5) WFLYCLSV0007: Just reached required quorum of 1 for jboss.quickstart.ha.singleton.default service. If this cluster loses another member, no node will be chosen to provide this service. > 2015-12-16 10:25:39,832 INFO [org.wildfly.clustering.server] (remote-thread--p8-t5) WFLYCLSV0003: DevNode1 elected as the singleton provider of the jboss.quickstart.ha.singleton.default service > 2015-12-16 10:25:40,410 WARN [org.hornetq.core.client] (Thread-514 (HornetQ-client-global-threads-816000930)) HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED] > 2015-12-16 10:25:40,424 WARN [org.hornetq.core.client] (Thread-515 (HornetQ-client-global-threads-816000930)) HQ212037: Connection failure has been detected: HQ119015: The connection was disconnected because of server shutdown [code=DISCONNECTED] > 2015-12-16 10:25:40,442 INFO [org.hornetq.core.server] (Thread-16 (HornetQ-server-HornetQServerImpl::serverUUID=5f62a17c-a33d-11e5-b968-cda4b2119720-1601129088)) HQ221029: stopped bridge sf.my-cluster.b27b8fc6-a33e-11e5-84b8-b7bbc6dfe24c > 2015-12-16 10:25:40,495 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel server: [Node1|2] (1) [DevNode1] > 2015-12-16 10:25:40,496 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel ejb: [Node1|2] (1) [DevNode1] > 2015-12-16 10:25:40,497 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-5,ee,DevNode1) ISPN000094: Received new cluster view for channel hibernate: [DevNode1|2] (1) [DevNode1] > 2015-12-16 10:25:57,010 WARNING [org.jgroups.protocols.UDP] (INT-1,hq-cluster,DevNode1) JGRP000012: discarded message from different cluster ee (our cluster is hq-cluster). Sender was DevNode1 (received 38 identical messages from DevNode1 in the last 63946 ms) > 2015-12-16 10:26:30,810 WARNING [org.jgroups.protocols.UDP] (Incoming-13,ee,DevNode1) JGRP000012: discarded message from different cluster hq-cluster (our cluster is ee). Sender was DevNode1 (received 80 identical messages from DevNode1 in the last 60008 ms) > This issue also in: > https://developer.jboss.org/thread/266831 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016