[JBoss JIRA] (ELY-1406) Elytron, IBM SPNEGO misconfiguration handling difference
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-1406?page=com.atlassian.jira.plugin.s... ]
Jan Kalina updated ELY-1406:
----------------------------
Description:
Fallback on unavailable KDC is on IBM JDK too slow, because server is waiting for the KDC around 30 seconds on every HTTP request.
Should be possible to configure IBM JDK to not contact KDC, or at least to cache failed state of GSSCredential obtaining for defined time period.
was:
IBM jdk creates kerberos ticket on server side - in other words validates server kerberos configuration.
This is different to how Oracle/OpenJDK works, where this behaviour can be switch on with obtain-kerberos-ticket attribute [1].
Main question here is, could be this default IBM java behaviour switched off? .
Because this can make troubles when KDC is temporary down - with IBM java it won't be possible to fallback to another authentication.
Basically, this is separate tracking issue for this comment [2]
[1] https://issues.jboss.org/browse/JBEAP-10246?focusedCommentId=13392098&pag...
[2] https://issues.jboss.org/browse/JBEAP-10653?focusedCommentId=13407417&pag...
> Elytron, IBM SPNEGO misconfiguration handling difference
> --------------------------------------------------------
>
> Key: ELY-1406
> URL: https://issues.jboss.org/browse/ELY-1406
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Credentials
> Affects Versions: 1.2.0.Beta6
> Reporter: Jan Kalina
> Assignee: Jan Kalina
> Priority: Critical
>
> Fallback on unavailable KDC is on IBM JDK too slow, because server is waiting for the KDC around 30 seconds on every HTTP request.
> Should be possible to configure IBM JDK to not contact KDC, or at least to cache failed state of GSSCredential obtaining for defined time period.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-8013) Out of memory exception after a number of remote deploys
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/WFLY-8013?page=com.atlassian.jira.plugin.... ]
jaikiran pai commented on WFLY-8013:
------------------------------------
Given that WildFly 11.0.0.CR1 has been released a while back and the Final release is being worked upon, could you give this a try against the 11.0.0.CR1 or even the latest nightly WildFly build https://ci.wildfly.org/viewType.html?buildTypeId=WF_Nightly and see if it's still an issue in that version?
> Out of memory exception after a number of remote deploys
> --------------------------------------------------------
>
> Key: WFLY-8013
> URL: https://issues.jboss.org/browse/WFLY-8013
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Final
> Environment: Server: Ubuntu 16.04.1 LTS x64
> bq.
> bq. Startup arguments:
> bq.
> bq.
> bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0
> Reporter: Tiago Matias
> Assignee: Jason Greene
>
> Using the wildfly-maven-plugin for remotely deploying a WAR file do Wildfly and, after a few deploys (between 5 and 10) An outofmemory error emerges, requiring a full server restart.
> *Full error log of maven.*
> {quote}
> [INFO] Authenticating against security realm: ManagementRealm
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 47.630 s
> [INFO] Finished at: 2017-02-02T15:38:04+00:00
> [INFO] Final Memory: 22M/290M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:deploy (default) on project MyProject: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back
> . Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backoffice.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"
> backoffice.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"backoffice.war\"
> [ERROR] Caused by: java.lang.OutOfMemoryError: Metaspace"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"MyProject.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/una
> vailable dependencies" => undefined}}}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-8013) Out of memory exception after a number of remote deploys
by Miroslav Zaťko (JIRA)
[ https://issues.jboss.org/browse/WFLY-8013?page=com.atlassian.jira.plugin.... ]
Miroslav Zaťko commented on WFLY-8013:
--------------------------------------
Same here with 10.1.0-Final after few(4 or 5) deployments... I would say it has nothing to do with wildfly-maven-plugin, it is just a bug in maven class unloading itself... WFLY-6173, WFLY-6347, WFCORE-2077, ... are related probably...
> Out of memory exception after a number of remote deploys
> --------------------------------------------------------
>
> Key: WFLY-8013
> URL: https://issues.jboss.org/browse/WFLY-8013
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.1.0.Final
> Environment: Server: Ubuntu 16.04.1 LTS x64
> bq.
> bq. Startup arguments:
> bq.
> bq.
> bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0
> Reporter: Tiago Matias
> Assignee: Jason Greene
>
> Using the wildfly-maven-plugin for remotely deploying a WAR file do Wildfly and, after a few deploys (between 5 and 10) An outofmemory error emerges, requiring a full server restart.
> *Full error log of maven.*
> {quote}
> [INFO] Authenticating against security realm: ManagementRealm
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 47.630 s
> [INFO] Finished at: 2017-02-02T15:38:04+00:00
> [INFO] Final Memory: 22M/290M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:deploy (default) on project MyProject: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back
> . Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backoffice.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"
> backoffice.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"backoffice.war\"
> [ERROR] Caused by: java.lang.OutOfMemoryError: Metaspace"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"MyProject.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/una
> vailable dependencies" => undefined}}}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1765) Move FEEL type annotation to API
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1765?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-1765:
---------------------------------------
Matteo, FEEL should be "self-contained", so either we keep the annotations in the -feel module, or we create a -feel-api module.
I don't think moving it to the kie-dmn-api module would be desirable, as there is a move to re-use feel in other standards (namely BPMN and CMMN) and so it would be best if we keep the FEEL engine self-contained.
> Move FEEL type annotation to API
> --------------------------------
>
> Key: DROOLS-1765
> URL: https://issues.jboss.org/browse/DROOLS-1765
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1763) Dependent rule not firing
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1763?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-1763:
-------------------------------------
Assignee: Mario Fusco (was: Edson Tirelli)
> Dependent rule not firing
> -------------------------
>
> Key: DROOLS-1763
> URL: https://issues.jboss.org/browse/DROOLS-1763
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.0.0.Beta7, 7.3.0.Final
> Environment: Linux all versions.
> JDK 1.8.0 Update 144
> Reporter: David Wade
> Assignee: Mario Fusco
> Attachments: 7.0.0.Beta6.txt, 7.3.0.Final.txt
>
>
> We have been using Drools since 2.x.
> Currently we use 7.0.0.Beta6 which works.
> We can't upgrade because since 7.0.0.Beta7 rules dependent on the consequence of another rule are not firing for some reason. This happens for us on 7.0.0.Beta7 through to 7.3.0.Final.
> Consider the following two rules. When run on 7.0.0.Beta6 both rules fire. From Beta7 through to 7.3.0.Final, only the SQ rule fire, despite the RC rule passing its conditions
> {code}
> rule "H2"
> salience -300
> when
> segment:SegmentWithTax(
> containsTax("SQ")
> , notContainsTax("H2", "RC")
> )
> then
> segment.addPercentageTaxEntry(taxCodeMap,"SQ","RC_13_PERCENT");
> end
> rule "SQ"
> when
> segment:SegmentWithTax(
> !containsTax("SQ")
> )
> then
> modify(segment) {
> addTaxEntry(taxCodeMap,"SQ_TRANSFER_TRANSIT_LESS_THAN_FOUR_HOURS")
> }
> end
> {code}
> Will attach Drools trace logging output * 2. One for [^7.0.0.Beta6.txt] , one for [^7.3.0.Final.txt] .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months
[JBoss JIRA] (WFLY-9447) NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9447?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved JBEAP-13518 to WFLY-9447:
----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9447 (was: JBEAP-13518)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.CR2)
> NPE in ejb client and clean shutdown ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9447
> URL: https://issues.jboss.org/browse/WFLY-9447
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.CR1
> Reporter: Radoslav Husar
> Assignee: Flavia Rainone
>
> {noformat}
> ESC[0m13:59:55,004 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0211: Suspending server with 15000 ms timeout.
> ESC[0mESC[0m13:59:55,006 INFO [org.jboss.as.ejb3] (management-handler-thread - 1) WFLYEJB0493: EJB subsystem suspension complete
> ESC[0mESC[0m13:59:55,008 INFO [org.jboss.as.server] (Management Triggered Shutdown) WFLYSRV0241: Shutting down in response to management operation 'shutdown'
> ESC[0mESC[0m13:59:55,027 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: Host default-host stopping
> ESC[0mESC[0m13:59:55,028 INFO [org.jboss.modcluster] (ServerService Thread Pool -- 72) MODCLUSTER000002: Initiating mod_cluster shutdown
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,039 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000080: Disconnecting JGroups channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,040 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000082: Stopping the RpcDispatcher for channel ejb
> ESC[0mESC[0m13:59:55,042 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000029: Passivating all entries to disk
> ESC[0mESC[0m13:59:55,046 INFO [org.infinispan.eviction.impl.PassivationManagerImpl] (ServerService Thread Pool -- 74) ISPN000030: Passivated 2 entries in 3 milliseconds
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
> ESC[0mESC[0m13:59:55,055 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0003: Stopped twocluster-terminus.jar cache from ejb container
> ESC[0m13:59:55,057 DEBUG [org.jboss.ejb.client.invocation] (pool-1-thread-1) Calling invoke(module = /twocluster-forwarder-tx/ForwardingStatefulSBImpl, strong affinity = Cluster "ejb-forwarder", weak affinity = Node "clusterA-node0"):
> ESC[0m13:59:55,059 INFO [org.jboss.as.test.clustering.twoclusters.bean.forwarding.AbstractForwardingStatefulSBImpl] (default task-124) getSerialAndIncrement() called on forwarding node clusterA-node0
> ESC[0mESC[31m13:59:55,062 ERROR [org.jboss.ejb.client.invocation] (default task-8) EJBCLIENT000509: Unexpected exception processing EJB request: java.lang.NullPointerException
> at org.jboss.as.ejb3.deployment.DeploymentRepository.getStartedModules(DeploymentRepository.java:202)
> at org.jboss.as.ejb3.remote.AssociationImpl.findEJB(AssociationImpl.java:382)
> at org.jboss.as.ejb3.remote.AssociationImpl.receiveInvocationRequest(AssociationImpl.java:115)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleInvocationRequest(EJBServerChannel.java:450)
> at org.jboss.ejb.protocol.remote.EJBServerChannel$ReceiverImpl.handleMessage(EJBServerChannel.java:188)
> at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:926)
> 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)
> {noformat}
> Appears in https://github.com/jbossas/jboss-eap7/pull/2446
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 9 months