[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
by Justin Holmes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ]
Justin Holmes commented on DROOLS-4137:
---------------------------------------
Good to know about XLS decision tables.
I will get back to the example my team put together today with this new understanding and see where get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more.
Thanks again for your help. I hope you are well, Mario.
> KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4137
> URL: https://issues.jboss.org/browse/DROOLS-4137
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.22.0.Final
> Reporter: Justin Holmes
> Assignee: Mario Fusco
> Priority: Major
>
> I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up.
> See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information.
> Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix.
> We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
by Justin Holmes (Jira)
[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ]
Justin Holmes edited comment on DROOLS-4137 at 6/6/19 11:41 AM:
----------------------------------------------------------------
Good to know about XLS decision tables.
I will get back to the example my team put together today with this new understanding and see where we get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more.
Thanks again for your help. I hope you are well, Mario.
was (Author: jholmessr):
Good to know about XLS decision tables.
I will get back to the example my team put together today with this new understanding and see where get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more.
Thanks again for your help. I hope you are well, Mario.
> KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build
> ---------------------------------------------------------------------------------------------
>
> Key: DROOLS-4137
> URL: https://issues.jboss.org/browse/DROOLS-4137
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.22.0.Final
> Reporter: Justin Holmes
> Assignee: Mario Fusco
> Priority: Major
>
> I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up.
> See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information.
> Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix.
> We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months
[JBoss JIRA] (ELY-1826) Cannot connect to management interface with Java Security Manager enabled
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELY-1826?page=com.atlassian.jira.plugin.s... ]
Farah Juma updated ELY-1826:
----------------------------
Fix Version/s: 1.6.3.CR1
> Cannot connect to management interface with Java Security Manager enabled
> -------------------------------------------------------------------------
>
> Key: ELY-1826
> URL: https://issues.jboss.org/browse/ELY-1826
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Security Manager
> Affects Versions: 1.6.2.Final
> Reporter: Ilia Vassilev
> Assignee: Ilia Vassilev
> Priority: Major
> Fix For: 1.6.3.CR1
>
>
> When JBoss EAP is configured to authenticate management interfaces with LDAPS and RBAC enabled authentication works unless the security manager is enabled. When security manager is enabled the exception [1] occurs in console and exception [2] is logged in server.log
> [1]
> {code}
> "Failed to connect to the controller: Unable to authenticate against controller at ... Authentication failed: all available authentication mechanisms failed: PLAIN: javax.security.sasl.SaslException: PLAIN: Server rejected authentication"
> {code}
> [2]
> {code}
> 2019-05-15 09:30:45,434 DEBUG [org.wildfly.security] (management task-3) Could not create [class javax.naming.ldap.InitialLdapContext]. Failed to connect to LDAP server.: javax.naming.CommunicationException: myldap.mydomain:636 [Root exception is java.lang.ClassNotFoundException: org/wildfly/security/auth/realm/ldap/ThreadLocalSSLSocketFactory]
> at com.sun.jndi.ldap.Connection.<init>(Connection.java:238)
> at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137)
> at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1609)
> at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)
> at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
> at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
> at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
> at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)
> at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116)
> at org.jboss.as.naming.InitialContext.init(InitialContext.java:101)
> at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> ...
> at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245)
> at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217)
> at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.ClassNotFoundException: org/wildfly/security/auth/realm/ldap/ThreadLocalSSLSocketFactory
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at com.sun.jndi.ldap.VersionHelper12.loadClass(VersionHelper12.java:72)
> at com.sun.jndi.ldap.Connection.createSocket(Connection.java:293)
> at com.sun.jndi.ldap.Connection.<init>(Connection.java:215)
> ... 42 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 11 months