[JBoss JIRA] (ELY-1468) IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1468?page=com.atlassian.jira.plugin.s... ]
Martin Choma edited comment on ELY-1468 at 2/1/18 9:45 AM:
-----------------------------------------------------------
As a side effect of JBEAP-14187 fix this seems be fixed for IBM, however popped up for Oracle/OpenJDK
was (Author: mchoma):
As a side effect of JBEAP-14187 fiz this seems be fixed for IBM, however popped up for Oracle/OpenJDK
> IBM java, 403 instead of 401 sent, when kerberos mechanism is not supported
> ---------------------------------------------------------------------------
>
> Key: ELY-1468
> URL: https://issues.jboss.org/browse/ELY-1468
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Mechanisms
> Affects Versions: 1.2.0.Beta10
> Reporter: Martin Choma
> Priority: Minor
>
> When more mechanismTypes is provided but the Kerberos mechanism is not listed as the supported one then authentication should fail. And 401 should be returned, but 403 is on IBM java.
> This issue was hidden by ELY-1340.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9749) Drop old & legacy batch subsystem
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFLY-9749:
---------------------------------
Summary: Drop old & legacy batch subsystem
Key: WFLY-9749
URL: https://issues.jboss.org/browse/WFLY-9749
Project: WildFly
Issue Type: Task
Components: Batch
Reporter: Tomaz Cerar
Assignee: Cheng Fang
Priority: Critical
Batch subsystem was added in WildFly 8 to support EE7, but was replaced by "batch-jberet" in 9.
By this time noone should be using it anymore and we can drop it.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9727) WildFly Randomly Terminates after 5-10 minutes
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-9727?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-9727:
-----------------------------------
What is the exact version of JDK you are using?
> WildFly Randomly Terminates after 5-10 minutes
> ----------------------------------------------
>
> Key: WFLY-9727
> URL: https://issues.jboss.org/browse/WFLY-9727
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 10.0.0.Final
> Environment: Running WildFly 10.x from within Eclipse Oxygen (4.7.2) on 2015 MacBook Pro running OS X El Capitan (10.11.6)
> Reporter: Daniel Wiseman
> Assignee: Jason Greene
> Priority: Blocker
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> I've been experiencing an odd intermittent issue on my WildFly server that has been running on my local system. Every other day or so my server will shutdown, without warning, after running for five to ten minutes from launch. The WildFly server logs contain no errors but the Eclipse logs output these two stack identical stack traces every time:
> {{Exception in thread "Remoting "management-client" I/O-1" java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:354)
> at org.xnio.AbstractIoFuture.runAllNotifiers(AbstractIoFuture.java:233)
> at org.xnio.AbstractIoFuture.setCancelled(AbstractIoFuture.java:291)
> at org.xnio.FutureResult.setCancelled(FutureResult.java:98)
> at org.xnio.nio.WorkerThread$ConnectHandle.forceTermination(WorkerThread.java:339)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:492)
> Exception in thread "Remoting "management-client" I/O-1" java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
> at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
> at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:354)
> at org.xnio.AbstractIoFuture.runAllNotifiers(AbstractIoFuture.java:233)
> at org.xnio.AbstractIoFuture.setCancelled(AbstractIoFuture.java:291)
> at org.xnio.FutureResult.setCancelled(FutureResult.java:98)
> at org.xnio.nio.WorkerThread$ConnectHandle.forceTermination(WorkerThread.java:339)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:492)}}
> This issue will occur on every server start for an entire day and then the next day it won't happen at all. However, when it happens it makes debugging the software I write that runs of the server near impossible. Does anyone have any ideas what could be causing this issue? Let me know if you need more details, thanks!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3571) Improve CLI error handling in ListCommand
by Marek Kopecký (JIRA)
Marek Kopecký created WFCORE-3571:
-------------------------------------
Summary: Improve CLI error handling in ListCommand
Key: WFCORE-3571
URL: https://issues.jboss.org/browse/WFCORE-3571
Project: WildFly Core
Issue Type: Bug
Components: CLI
Reporter: Marek Kopecký
Assignee: Marek Kopecký
Priority: Minor
Improve CLI error handling in ListCommand class. If management operation doesn't return correct results, CLI should throw correct error message.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9748) Support new method-level "@Priority" annotation
by David Lloyd (JIRA)
David Lloyd created WFLY-9748:
---------------------------------
Summary: Support new method-level "@Priority" annotation
Key: WFLY-9748
URL: https://issues.jboss.org/browse/WFLY-9748
Project: WildFly
Issue Type: Enhancement
Components: CDI / Weld, EE, EJB
Reporter: David Lloyd
Priority: Critical
Fix For: 12.0.0.Alpha1
The {{@Priority}} annotation in Common Annotations 1.3 has gained a METHOD applicability level. We must ensure that our interceptor metadata processing picks up these annotations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months