February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (HAWKULARQE-35) Manual Testcases - Create and Run

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-35?page=com.atlassian.jira.plu... ] Vojtech Prusa commented on HAWKULARQE-35: ----------------------------------------- https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/worki... > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-35 > URL: https://issues.jboss.org/browse/HAWKULARQE-35 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Vojtech Prusa > Priority: Critical > > Add new provider with SSL and check that provider is added successfully and inventory is loaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-35) Manual Testcases - Create and Run

by Vojtech Prusa (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-35?page=com.atlassian.jira.plu... ] Vojtech Prusa reassigned HAWKULARQE-35: --------------------------------------- Assignee: Vojtech Prusa (was: mfoley user) > Manual Testcases - Create and Run > --------------------------------- > > Key: HAWKULARQE-35 > URL: https://issues.jboss.org/browse/HAWKULARQE-35 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Vojtech Prusa > Priority: Critical > > Add new provider with SSL and check that provider is added successfully and inventory is loaded. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2333) Native management interface does not work with SSL/TLS based on Elytron SSL Context

by Ondrej Kotek (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2333?page=com.atlassian.jira.plugi... ] Ondrej Kotek moved JBEAP-9153 to WFCORE-2333: --------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2333 (was: JBEAP-9153) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Security (was: Security) Affects Version/s: 3.0.0.Beta2 (was: 7.1.0.DR12) > Native management interface does not work with SSL/TLS based on Elytron SSL Context > ----------------------------------------------------------------------------------- > > Key: WFCORE-2333 > URL: https://issues.jboss.org/browse/WFCORE-2333 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta2 > Reporter: Ondrej Kotek > Priority: Blocker > > Following [1,2] to set management {{native-interface}} backed by SSL Context from Elytron, {{jboss-cli}} connection results in: > {{Failed to connect to the controller: Unable to negotiate SSL connection with controller at localhost:9999}} > Are there any configuration steps that needs to be performed for this configuration to work? > [1] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... > [2] https://docs.jboss.org/author/display/WFLY/WildFly+Elytron+Security#WildF... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2332) ReloadRedirectTestCase stuck on HP-UX

by Petr Kremensky (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2332?page=com.atlassian.jira.plugi... ] Petr Kremensky moved JBEAP-9151 to WFCORE-2332: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2332 (was: JBEAP-9151) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Test Suite (was: Test Suite) Affects Version/s: 3.0.0.Beta4 (was: 7.1.0.DR12) > ReloadRedirectTestCase stuck on HP-UX > ------------------------------------- > > Key: WFCORE-2332 > URL: https://issues.jboss.org/browse/WFCORE-2332 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Affects Versions: 3.0.0.Beta4 > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > org.jboss.as.test.manualmode.management.cli.ReloadRedirectTestCase from Wildfly core manual mode module stuck on HP-UX > {{destroy()}} is unable to kill the process waiting for the user input (accept certificate dialogue). We could either destroy the process forcibly by updating CliProcessWrapper: > {code:java} > public void destroyProcess() { > cliProcess.destroy(); > } > {code} > to > {code:java} > public void destroyProcess() { > cliProcess.destroyForcibly(); > } > {code} > or add {{cliProc.ctrlCAndWaitForClose();}} into finally block just before destroying the process in test case. > ReloadRedirectTestCase#testReloadwithRedirect() > {code:java} > finally { > cliProc.ctrlCAndWaitForClose(); > cliProc.destroyProcess(); > } > {code} > see WFCORE-2216 for test log and thread dump > I'll send a PR for the second option. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8232) SecurityAuditingTestCase fails with Elytron profile in AS TS

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8232?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-8232: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > SecurityAuditingTestCase fails with Elytron profile in AS TS > ------------------------------------------------------------ > > Key: WFLY-8232 > URL: https://issues.jboss.org/browse/WFLY-8232 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Josef Cacek > Assignee: Jan Kalina > > The {{SecurityAuditingTestCase}} fails when executed with Elytron profile ({{-Delytron}}) in AS TS. > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityAuditingTestCase -Delytron > ... > Failed tests: > SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template:181->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7322) LDAP referrals does not work in Elytron ldap-realm

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7322?page=com.atlassian.jira.plugin.... ] Jan Kalina resolved WFLY-7322. ------------------------------ Resolution: Done > LDAP referrals does not work in Elytron ldap-realm > -------------------------------------------------- > > Key: WFLY-7322 > URL: https://issues.jboss.org/browse/WFLY-7322 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Ondrej Lukas > Assignee: Jan Kalina > Priority: Blocker > Fix For: 11.0.0.Alpha1 > > > LDAP referrals cannot be used in Elytron {{ldap-realm}}. Ldap Realm is currently not prepared to work with referrals at all: > * {{ldap-realm}} does not include any options which enable working with LDAP referrals (PicketBox use {{baseFilter}} option which can be configured to return also referral object) > * implementation of {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm}} does not include any logic which handles referrals > Referrals are important feature of LDAP. It has to be covered by Elytron => requested blocker flag. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-41) Hawkular Agent for EAP7.1

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-41?page=com.atlassian.jira.plu... ] Hayk Hovsepyan updated HAWKULARQE-41: ------------------------------------- Description: Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... was: Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... Bug should be fixed https://bugzilla.redhat.com/show_bug.cgi?id=1370499 > Hawkular Agent for EAP7.1 > ------------------------- > > Key: HAWKULARQE-41 > URL: https://issues.jboss.org/browse/HAWKULARQE-41 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: mfoley user > > Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-41) Hawkular Agent for EAP7.1

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-41?page=com.atlassian.jira.plu... ] Hayk Hovsepyan reassigned HAWKULARQE-41: ---------------------------------------- Assignee: Hayk Hovsepyan (was: mfoley user) > Hawkular Agent for EAP7.1 > ------------------------- > > Key: HAWKULARQE-41 > URL: https://issues.jboss.org/browse/HAWKULARQE-41 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > > Smoke test is required based on template https://polarion.engineering.redhat.com/polarion/#/project/JBossON4/testr... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8248) EJB deployments with Elytron SD collides in EJB3 SD service

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8248: --------------------------------- Summary: EJB deployments with Elytron SD collides in EJB3 SD service Key: WFLY-8248 URL: https://issues.jboss.org/browse/WFLY-8248 Project: WildFly Issue Type: Bug Components: EJB, Security Reporter: Josef Cacek Assignee: Jan Kalina Priority: Critical Attachments: enable-elytron.cli, read-props-grant.ear, read-props-limited.ear Every EJB deployment associated with an Elytron security domain builds *jboss.ejb3.security-domain* service: https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jbo... But it fails if there are more such deployments, because it mean second service with the same name: {code} 00:02:12,118 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."read-props-limited.ear"."ejb-moduleread-props-limited.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of subdeployment "ejb-moduleread-props-limited.jar" of deployment "read-props-limited.ear" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) 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) Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.ejb3.security-domain is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317) at org.jboss.as.ejb3.deployment.processors.EJBDefaultSecurityDomainProcessor.deploy(EJBDefaultSecurityDomainProcessor.java:111) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) ... 5 more {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8247) Unable to send large message if JDBC-persistance-store is used

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8247?page=com.atlassian.jira.plugin.... ] Jeff Mesnil commented on WFLY-8247: ----------------------------------- The way how Artemis appends data to file was changed in Artemis, so SQL command in EAP's journal-sql.properties must be updated: {code} -append-to-file=UPDATE %s SET DATA = CONCAT(DATA, ?) WHERE ID=? +append-to-file=SELECT DATA FROM %s WHERE ID=? FOR UPDATE {code} append-to-file.derby should be updated as well. > Unable to send large message if JDBC-persistance-store is used > -------------------------------------------------------------- > > Key: WFLY-8247 > URL: https://issues.jboss.org/browse/WFLY-8247 > Project: WildFly > Issue Type: Bug > Components: JMS > Environment: The issue was hit with Oracle 12c database > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > > If producer sends large message to EAP with JDBC-persistance store, the following error arises on the server. > {code} > 11:49:34,248 ERROR [org.apache.activemq.artemis.core.server] (default I/O-9) AMQ224016: Caught exception: ActiveMQInternalErrorException[errorType=INTERNAL_ERROR message=Invalid conversion requested] > at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.validateFile(LargeServerMessageImpl.java:376) > at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.createLargeMessage(JournalStorageManager.java:458) > at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.sendLarge(ServerSessionImpl.java:1189) > at org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:436) > at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:624) > at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:373) > at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:356) > at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:621) > at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278) > at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277) > at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:264) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292) > at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278) > at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962) > at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435) > at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1] > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1] > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1] > at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1] > Caused by: java.sql.SQLException: Invalid conversion requested > at oracle.jdbc.driver.T4CVarcharAccessor.StringToNUMBER(T4CVarcharAccessor.java:832) > at oracle.jdbc.driver.T4CVarcharAccessor.getNUMBER(T4CVarcharAccessor.java:239) > at oracle.jdbc.driver.T4CVarcharAccessor.getInt(T4CVarcharAccessor.java:527) > at oracle.jdbc.driver.GeneratedStatement.getInt(GeneratedStatement.java:217) > at oracle.jdbc.driver.GeneratedScrollableResultSet.getInt(GeneratedScrollableResultSet.java:573) > at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1490) > at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFileFactoryDriver.createFile(JDBCSequentialFileFactoryDriver.java:165) > at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFileFactoryDriver.openFile(JDBCSequentialFileFactoryDriver.java:102) > at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.open(JDBCSequentialFile.java:98) > at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.openFile(LargeServerMessageImpl.java:391) > at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.validateFile(LargeServerMessageImpl.java:370) > ... 21 more > Caused by: java.lang.NumberFormatException > at java.math.BigDecimal.<init>(BigDecimal.java:494) [rt.jar:1.8.0_111] > at java.math.BigDecimal.<init>(BigDecimal.java:383) [rt.jar:1.8.0_111] > at java.math.BigDecimal.<init>(BigDecimal.java:806) [rt.jar:1.8.0_111] > at oracle.jdbc.driver.T4CVarcharAccessor.StringToNUMBER(T4CVarcharAccessor.java:825) > ... 31 more > {code} > *Customer impact*: Clients are not able to send large messages. Sending/receiving large messages is common customer use case. This blocks RFE EAP7-591. > There is no workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2017