[JBoss JIRA] (WFCORE-3092) OauthbearerMgmtSaslTestCase in wildfly-core contains wrong test value for token without signature
by Josef Cacek (JIRA)
Josef Cacek created WFCORE-3092:
-----------------------------------
Summary: OauthbearerMgmtSaslTestCase in wildfly-core contains wrong test value for token without signature
Key: WFCORE-3092
URL: https://issues.jboss.org/browse/WFCORE-3092
Project: WildFly Core
Issue Type: Bug
Components: Test Suite
Reporter: Josef Cacek
Assignee: Tomaz Cerar
The current value of {{OauthbearerMgmtSaslTestCase.TOKEN_WITHOUT_SIGNATURE}} constant is a token with a signature.
{code:java}
/**
* Token without signature part
*
* <pre>
* {
* "alg": "HS256",
* "typ": "JWT"
* }
* {
* "iss": "issuer.wildfly.org",
* "sub": "elytron(a)wildfly.org",
* "exp": 2051222399, // 20341231235959Z
* "aud": "jwt"
* }
* </pre>
*/
protected static final String TOKEN_WITHOUT_SIGNATURE = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJpc3N1ZXIud2lsZGZseS5vcmciLCJzdWIiOiJlbHl0cm9uQHdpbGRmbHkub3JnIiwiZXhwIjoyMDUxMjIyMzk5LCJhdWQiOiJqd3QifQ.jOcMdBLdI7HMuW_VsoGD_7LqeX6M14_wV5ebP2S4tOM";
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3092) OauthbearerMgmtSaslTestCase in wildfly-core contains wrong test value for token without signature
by Josef Cacek (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3092?page=com.atlassian.jira.plugi... ]
Josef Cacek reassigned WFCORE-3092:
-----------------------------------
Assignee: Josef Cacek (was: Tomaz Cerar)
> OauthbearerMgmtSaslTestCase in wildfly-core contains wrong test value for token without signature
> -------------------------------------------------------------------------------------------------
>
> Key: WFCORE-3092
> URL: https://issues.jboss.org/browse/WFCORE-3092
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Reporter: Josef Cacek
> Assignee: Josef Cacek
>
> The current value of {{OauthbearerMgmtSaslTestCase.TOKEN_WITHOUT_SIGNATURE}} constant is a token with a signature.
> {code:java}
> /**
> * Token without signature part
> *
> * <pre>
> * {
> * "alg": "HS256",
> * "typ": "JWT"
> * }
> * {
> * "iss": "issuer.wildfly.org",
> * "sub": "elytron(a)wildfly.org",
> * "exp": 2051222399, // 20341231235959Z
> * "aud": "jwt"
> * }
> * </pre>
> */
> protected static final String TOKEN_WITHOUT_SIGNATURE = "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJpc3N1ZXIud2lsZGZseS5vcmciLCJzdWIiOiJlbHl0cm9uQHdpbGRmbHkub3JnIiwiZXhwIjoyMDUxMjIyMzk5LCJhdWQiOiJqd3QifQ.jOcMdBLdI7HMuW_VsoGD_7LqeX6M14_wV5ebP2S4tOM";
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBJCA-1352) IBM MQ deadlock on shutdown
by Flavia Rainone (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1352?page=com.atlassian.jira.plugin... ]
Flavia Rainone updated JBJCA-1352:
----------------------------------
Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/632
> IBM MQ deadlock on shutdown
> ---------------------------
>
> Key: JBJCA-1352
> URL: https://issues.jboss.org/browse/JBJCA-1352
> Project: IronJacamar
> Issue Type: Bug
> Components: AS
> Affects Versions: WildFly/IronJacamar 1.4.2.Final
> Environment: JBoss EAP 7.0.4
> Reporter: Doug Grove
> Assignee: Flavia Rainone
>
> Sporadically, on shut down, IBM MQ and JBoss will deadlock. This does not occur on EAP 6.
> The Deadlocking threads are
> [1]
> ~~~
> ServerService Thread Pool -- 63" #183 prio=5 os_prio=0 tid=0x00000000021ef800 nid=0x50e2 waiting for monitor entry [0x00007fef8451a000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.removeListener(ConnectionEventHandler.java:93)
> - waiting to lock <0x000000009be01318> (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.SemaphoreConcurrentLinkedDequeManagedConnectionPool.doDestroy(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1376)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.flush(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:882)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.shutdown(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1065)
> at org.jboss.jca.core.connectionmanager.pool.AbstractPool.shutdown(AbstractPool.java:930)
> - locked < 0x000000008d09b340> (a org.jboss.jca.core.connectionmanager.pool.strategy.OnePool)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.shutdown(AbstractConnectionManager.java:285)
> - locked < 0x000000008d09b2e0> (a org.jboss.jca.core.connectionmanager.notx.NoTxConnectionManagerImpl)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService.unregisterAll(AbstractResourceAdapterDeploymentService.java:192)
> at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$3.run(AbstractResourceAdapterDeploymentService.java:346)
> 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)
> ~~~
> [2]
> ~~~
> "DefaultMessageListenerContainer-2" #162 prio=5 os_prio=0 tid=0x0000000001d7a800 nid=0x46bf waiting for monitor entry [0x00007fef70a7d000]
> java.lang.Thread.State: BLOCKED (on object monitor)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.shutdown(AbstractConnectionManager.java:281)
> - waiting to lock <0x000000008d09b2e0> (a org.jboss.jca.core.connectionmanager.notx.NoTxConnectionManagerImpl)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.returnManagedConnection(AbstractConnectionManager.java:724)
> at org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener.connectionClosed(NoTxConnectionListener.java:93)
> at com.ibm.mq.connector.outbound.ConnectionEventHandler.fireEvent(ConnectionEventHandler.java:135)
> - locked < 0x000000009be01318> (a com.ibm.mq.connector.outbound.ConnectionEventHandler)
> at com.ibm.mq.connector.outbound.ManagedConnectionImpl.fireConnectionClosed(ManagedConnectionImpl.java:784)
> at com.ibm.mq.connector.outbound.ConnectionWrapper.close(ConnectionWrapper.java:337)
> at org.springframework.jms.connection.ConnectionFactoryUtils.releaseConnection(ConnectionFactoryUtils.java:80)
> at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:358)
> at org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:255)
> at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1166)
> at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1158)
> at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:1055)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (HAWKULARQE-150) Redeploy archive on EAP - Should fail
by Hayk Hovsepyan (JIRA)
Hayk Hovsepyan created HAWKULARQE-150:
-----------------------------------------
Summary: Redeploy archive on EAP - Should fail
Key: HAWKULARQE-150
URL: https://issues.jboss.org/browse/HAWKULARQE-150
Project: Hawkular QE
Issue Type: Task
Reporter: Hayk Hovsepyan
Assignee: Hayk Hovsepyan
Priority: Critical
<mfoley> both apps are deployed in the same eap?
<bhirsch> yep
<mfoley> so you deployed 1 ... shows in the display
<bhirsch> And actions work. I can use cf to start, stop, and deploy
<mfoley> deploy a 2nd ... not showing the display
<bhirsch> correct
<mfoley> odd
<bhirsch> agreed
<mfoley> i suppose a 3rd would not display either
<bhirsch> haven't tried yet. I'm not really an MW guy, so all I had was ticket-monster and helloworld :-) Need a third .war
<mfoley> it's okay
<mfoley> seems like a bug to me ...
<mfoley> i appreciate the feedback
<bhirsch> np
<mfoley> you are a solutions architect?
<bhirsch> correct, SA in the Northeast
<mfoley> cool ...
<mfoley> general question ... what is your impression of the MW Provider?
<bhirsch> I have a customer that wanted a CF demo, with a focus on the MW provider area (they are a JBoss customer) So, here we are.
<mfoley> you can be direct .... it's okay
<bhirsch> So far so good
<mfoley> :)
<mfoley> excellent
<bhirsch> No complaints really. The deployment is a little involved, but very well documented
<mfoley> well ... only demo 1 deployment :)
<bhirsch> haha... yeah. I'm not very worried about that part. Just figured it was something you all would want to know
<mfoley> oh we do
<bhirsch> they'll probably be thrilled to see MW in CF at all
<mfoley> i hope so ... it would be validation of the new direction and strategy
<bhirsch> They use a lot of EAP, so this plus OpenShift (also an OSE customer) could help us beat VMware VRA out the door
<mfoley> :)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9069) EJBClientContext could not initialize class org.jboss.ejb.client.DeploymentNodeSelector when building with JDK-9
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-9069?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on WFLY-9069:
-------------------------------------
Is there a CR6 component upgrade issue?
> EJBClientContext could not initialize class org.jboss.ejb.client.DeploymentNodeSelector when building with JDK-9
> ----------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-9069
> URL: https://issues.jboss.org/browse/WFLY-9069
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Amos Feng
> Assignee: Tomaz Cerar
> Fix For: 11.0.0.Beta1
>
>
> {noformat}
> testRejectionsEAP620(org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase) Time elapsed: 2.786 sec <<< ERROR!
> java.lang.IncompatibleClassChangeError: Inconsistent constant pool data in classfile for class org/jboss/ejb/client/DeploymentNodeSelector. Method lambda$static$1([Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/String; at index 109 is CONSTANT_MethodRef and should be CONSTANT_InterfaceMethodRef
> at org.jboss.ejb.client.DeploymentNodeSelector.<clinit>(DeploymentNodeSelector.java:83)
> at org.jboss.ejb.client.EJBClientContext$Builder.<init>(EJBClientContext.java:538)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem50Parser.parseProfile(EJB3Subsystem50Parser.java:218)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem30Parser.parseProfiles(EJB3Subsystem30Parser.java:215)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem40Parser.parseRemote(EJB3Subsystem40Parser.java:116)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:135)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem13Parser.readElement(EJB3Subsystem13Parser.java:66)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem14Parser.readElement(EJB3Subsystem14Parser.java:58)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem20Parser.readElement(EJB3Subsystem20Parser.java:69)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem30Parser.readElement(EJB3Subsystem30Parser.java:77)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem50Parser.readElement(EJB3Subsystem50Parser.java:88)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:104)
> at org.jboss.as.ejb3.subsystem.EJB3Subsystem12Parser.readElement(EJB3Subsystem12Parser.java:71)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
> at org.jboss.as.subsystem.test.TestParser.readElement(TestParser.java:103)
> at org.jboss.as.subsystem.test.TestParser.readElement(TestParser.java:51)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate.parse(SubsystemTestDelegate.java:223)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.parse(SubsystemTestDelegate.java:611)
> at org.jboss.as.model.test.ModelTestBootOperationsBuilder.internalSetSubsystemXml(ModelTestBootOperationsBuilder.java:76)
> at org.jboss.as.model.test.ModelTestBootOperationsBuilder.setXmlResource(ModelTestBootOperationsBuilder.java:55)
> at org.jboss.as.subsystem.test.SubsystemTestDelegate$KernelServicesBuilderImpl.parseXmlResource(SubsystemTestDelegate.java:624)
> at org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase.testRejections(Ejb3TransformersTestCase.java:174)
> at org.jboss.as.ejb3.subsystem.Ejb3TransformersTestCase.testRejectionsEAP620(Ejb3TransformersTestCase.java:138)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months