[JBoss JIRA] (ELY-1357) GSSCredential CredentialSource (local-kerberos) into XML
by Jan Kalina (JIRA)
Jan Kalina created ELY-1357:
-------------------------------
Summary: GSSCredential CredentialSource (local-kerberos) into XML
Key: ELY-1357
URL: https://issues.jboss.org/browse/ELY-1357
Project: WildFly Elytron
Issue Type: Enhancement
Components: Credentials
Reporter: Jan Kalina
Assignee: Jan Kalina
Priority: Blocker
Fix For: 1.2.0.Beta2
Initially this should be minimal / no configuration to make a GSSCrdential available if the local user has a Kerberos ticket - at a later point we can review adding additional config such as client keytabs etc...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3257) The add-identity filesystem-realm operation in Elytron subsystem intermittently fails on NullPointerException
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3257?page=com.atlassian.jira.plugi... ]
Josef Cacek reassigned WFCORE-3257:
-----------------------------------
Component/s: (was: Domain Management)
Assignee: (was: Brian Stansberry)
> The add-identity filesystem-realm operation in Elytron subsystem intermittently fails on NullPointerException
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3257
> URL: https://issues.jboss.org/browse/WFCORE-3257
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Josef Cacek
>
> Elytron filesystem-realm has an {{add-identity}} operation. I've experienced in few occasions it failed with NullPointerException.
> I'm executing set of CLI operations as batch using:
> {code}
> run-batch --file=/path/to/script.cli -v
> {code}
> When I hit the issue I see following in the log:
> {noformat}
> 17:23:19,182 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add-identity") failed - address: ([
> ("subsystem" => "elytron"),
> ("filesystem-realm" => "SeccontextFsRealm")
> ]): java.lang.NullPointerException
> at org.wildfly.extension.elytron.ModifiableRealmDecorator$AddIdentityHandler.executeRuntimeStep(ModifiableRealmDecorator.java:128)
> at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:59)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:976)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:446)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
> at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
> at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
> at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
> at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
> at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
> 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)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> {noformat}
> I'm attaching also the CLI file which caused the problem.
> The code which executes the script in Java seems like:
> {code:java}
> CommandContext commandCtx = ... //initialize
> commandCtx.handle("run-batch --file=/path/to/script.cli -v");
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9310) Class loading hierarchie
by stefano canu (JIRA)
stefano canu created WFLY-9310:
----------------------------------
Summary: Class loading hierarchie
Key: WFLY-9310
URL: https://issues.jboss.org/browse/WFLY-9310
Project: WildFly
Issue Type: Bug
Components: Class Loading
Affects Versions: 10.1.0.Final
Environment: windows 7
oracle jdk hotspot 8
wildfly 10 final
Reporter: stefano canu
Assignee: David Lloyd
Priority: Blocker
Attachments: image-2017-09-07-12-57-48-779.png, image-2017-09-07-12-57-52-827.png, image-2017-09-07-12-57-59-849.png
Deployng an EAR application with hibernate 4.x jars in lib folders but is ignored and workning with AS module (hibernate 5.0.10) . i tried to do module exclusion by using jboss-deployment- structure but whitout any luck.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFCORE-3257) The add-identity filesystem-realm operation in Elytron subsystem intermittently fails on NullPointerException
by Josef Cacek (JIRA)
Josef Cacek created WFCORE-3257:
-----------------------------------
Summary: The add-identity filesystem-realm operation in Elytron subsystem intermittently fails on NullPointerException
Key: WFCORE-3257
URL: https://issues.jboss.org/browse/WFCORE-3257
Project: WildFly Core
Issue Type: Bug
Components: Domain Management, Security
Reporter: Josef Cacek
Assignee: Brian Stansberry
Elytron filesystem-realm has an {{add-identity}} operation. I've experienced in few occasions it failed with NullPointerException.
I'm executing set of CLI operations as batch using:
{code}
run-batch --file=/path/to/script.cli -v
{code}
When I hit the issue I see following in the log:
{noformat}
17:23:19,182 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add-identity") failed - address: ([
("subsystem" => "elytron"),
("filesystem-realm" => "SeccontextFsRealm")
]): java.lang.NullPointerException
at org.wildfly.extension.elytron.ModifiableRealmDecorator$AddIdentityHandler.executeRuntimeStep(ModifiableRealmDecorator.java:128)
at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:59)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:976)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:722)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:446)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418)
at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:263)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:229)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:287)
at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:244)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70)
at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160)
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)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
{noformat}
I'm attaching also the CLI file which caused the problem.
The code which executes the script in Java seems like:
{code:java}
CommandContext commandCtx = ... //initialize
commandCtx.handle("run-batch --file=/path/to/script.cli -v");
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBJCA-1354) Potential for deadlock on pool's flush
by Martin Simka (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1354?page=com.atlassian.jira.plugin... ]
Martin Simka commented on JBJCA-1354:
-------------------------------------
[~flavia.rainone] I think this can be resolved, fix is included in 1.4.6.
> Potential for deadlock on pool's flush
> --------------------------------------
>
> Key: JBJCA-1354
> URL: https://issues.jboss.org/browse/JBJCA-1354
> Project: IronJacamar
> Issue Type: Bug
> Reporter: Flavia Rainone
> Assignee: Flavia Rainone
>
> There is a potential for deadlock on all flushes in pools. The problem is that flush is synchronized and inside the flush the code can be delegated to listeners, that are external to IronJacamar.
> If those listeners use their own synchronization system , they could require synchronization locking in themselves. If there is another thread locking the listener and at some point invoking an operation that results in a pool flush, the system could enter a deadlock state.
> An example of stack trace:
> {noformat}
> Found one Java-level deadlock:
> =============================
> "JMSCCThreadPoolWorker-18":
> waiting to lock monitor 0x00007f1d2409ff48 (object 0x00000007853ad060, a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool),
> which is held by "JMSCCThreadPoolWorker-16"
> "JMSCCThreadPoolWorker-16":
> waiting to lock monitor 0x00007f1d1c15d138 (object 0x0000000785998598, a com.ibm.mq.connector.outbound.ConnectionEventHandler),
> which is held by "JMSCCThreadPoolWorker-17"
> "JMSCCThreadPoolWorker-17":
> waiting to lock monitor 0x00007f1d2409ff48 (object 0x00000007853ad060, a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool),
> which is held by "JMSCCThreadPoolWorker-16"
> Java stack information for the threads listed above:
> ===================================================
> "JMSCCThreadPoolWorker-18":
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.flush(AbstractPool.java:322)
> - waiting to lock <0x00000007853ad060> (a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool)
> at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:368)
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.fireEvent(ConnectionEventHandler.java:141)
> - locked <0x0000000788fe1fa0> (a com.ibm.mq.connector.outbound.ConnectionEventHandler)
> at com.ibm.mq.connector.outbound.ManagedConnectionImpl.onException(ManagedConnectionImpl.java:848)
> at com.ibm.msg.client.jms.internal.JmsProviderExceptionListener.run(JmsProviderExceptionListener.java:427)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:214)
> at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:105)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:229)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:303)
> at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1241)
> "JMSCCThreadPoolWorker-16":
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.removeListener(ConnectionEventHandler.java:93)
> - waiting to lock <0x0000000785998598> (a com.ibm.mq.connector.outbound.ConnectionEventHandler)
> at com.ibm.mq.connector.outbound.ManagedConnectionImpl.removeConnectionEventListener(ManagedConnectionImpl.java:434)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.doDestroy(SemaphoreArrayListManagedConnectionPool.java:891)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.flush(SemaphoreArrayListManagedConnectionPool.java:621)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.flush(AbstractPool.java:330)
> - locked <0x00000007853ad060> (a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool)
> at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:368)
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.fireEvent(ConnectionEventHandler.java:141)
> - locked <0x0000000788fe20b0> (a com.ibm.mq.connector.outbound.ConnectionEventHandler)
> at com.ibm.mq.connector.outbound.ManagedConnectionImpl.onException(ManagedConnectionImpl.java:848)
> at com.ibm.msg.client.jms.internal.JmsProviderExceptionListener.run(JmsProviderExceptionListener.java:427)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:214)
> at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:105)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:229)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:303)
> at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1241)
> "JMSCCThreadPoolWorker-17":
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.flush(AbstractPool.java:322)
> - waiting to lock <0x00000007853ad060> (a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool)
> at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:368)
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.fireEvent(ConnectionEventHandler.java:141)
> - locked <0x0000000785998598> (a com.ibm.mq.connector.outbound.ConnectionEventHandler)
> at com.ibm.mq.connector.outbound.ManagedConnectionImpl.onException(ManagedConnectionImpl.java:848)
> at com.ibm.msg.client.jms.internal.JmsProviderExceptionListener.run(JmsProviderExceptionListener.java:427)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.runTask(WorkQueueItem.java:214)
> at com.ibm.msg.client.commonservices.workqueue.SimpleWorkQueueItem.runItem(SimpleWorkQueueItem.java:105)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueItem.run(WorkQueueItem.java:229)
> at com.ibm.msg.client.commonservices.workqueue.WorkQueueManager.runWorkQueueItem(WorkQueueManager.java:303)
> at com.ibm.msg.client.commonservices.j2se.workqueue.WorkQueueManagerImplementation$ThreadPoolWorker.run(WorkQueueManagerImplementation.java:1241)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (WFLY-9309) Incorrect license for jboss-transaction-api_1.2_spec
by Martin Minar (JIRA)
Martin Minar created WFLY-9309:
----------------------------------
Summary: Incorrect license for jboss-transaction-api_1.2_spec
Key: WFLY-9309
URL: https://issues.jboss.org/browse/WFLY-9309
Project: WildFly
Issue Type: Bug
Components: Build System
Reporter: Martin Minar
Assignee: Martin Minar
Priority: Critical
Wrong licenses for jboss-transaction-api_1.2_spec in servlet-feature-pack-licenses.xml and full-feature-pack-licenses.xml - contains:
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.2_spec</artifactId>
<licenses>
<license>
<name>Apache License 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0</url>
<distribution>repo</distribution>
</license>
</licenses>
</dependency>
and artifact contains:
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.2_spec</artifactId>
<licenses>
<license>
<name>Common Development and Distribution License 1.1</name>
<url>https://javaee.github.io/glassfish/LICENSE</url>
<distribution>repo</distribution>
</license>
<license>
<name>GNU General Public License, Version 2 with the Classpath Exception</name>
<url>http://repository.jboss.org/licenses/gpl-2.0-ce.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
we need to fix inconsistency.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months