February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2618) Intermittent 'AssertionError: expected:<200> but was:<500>' in org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2618?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2618: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1034229|https://bugzilla.redhat.com/show_bug.cgi?id=1034229] from MODIFIED to ON_QA > Intermittent 'AssertionError: expected:<200> but was:<500>' in org.jboss.as.test.manualmode.ws.ReloadWSDLPublisherTestCase.testHelloStringAfterReload > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2618 > URL: https://issues.jboss.org/browse/WFLY-2618 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 8.0.0.CR1 > > > http://brontes.lab.eng.brq.redhat.com/project.html?projectId=WF&testNameI... > The issue is due to the fact that the jvm is reusing the same connection because it has a keep-alive set to true with a timeout of 5 s. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2333) Web deployment code assumes only a single ServletContainerInitializer is present in each jar

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2333?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2333: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1060740|https://bugzilla.redhat.com/show_bug.cgi?id=1060740] from MODIFIED to ON_QA > Web deployment code assumes only a single ServletContainerInitializer is present in each jar > -------------------------------------------------------------------------------------------- > > Key: WFLY-2333 > URL: https://issues.jboss.org/browse/WFLY-2333 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Beta1 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > Attachments: diycdemo.zip, hellomyfaces.zip > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2746) Workaround for auditlog syslog Facility not being configurable

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2746?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2746: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1052187|https://bugzilla.redhat.com/show_bug.cgi?id=1052187] from MODIFIED to ON_QA > Workaround for auditlog syslog Facility not being configurable > -------------------------------------------------------------- > > Key: WFLY-2746 > URL: https://issues.jboss.org/browse/WFLY-2746 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Domain Management > Affects Versions: 8.0.0.CR1 > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 8.0.0.Final > > > Use -Dorg.jboss.TEMP.audit.log.facility=5 where the number is the FACILITY as mentioned in section 6.2.1 of RFC-5424 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2760) Intermittent failure of ExternalContextBindingTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2760?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2760: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1054106|https://bugzilla.redhat.com/show_bug.cgi?id=1054106] from MODIFIED to ON_QA > Intermittent failure of ExternalContextBindingTestCase > ------------------------------------------------------- > > Key: WFLY-2760 > URL: https://issues.jboss.org/browse/WFLY-2760 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Jan Martiska > Assignee: Jan Martiska > Priority: Minor > > The server setup task sometimes fails to start the ApacheDS server instance because for some reason, BouncyCastle security provider doesn't get registered (it is added through a maven dependency rather than added to the JDK). This leads to a "connection refused" error during the test when it is trying to connect to the LDAP instance. > It worked for us if we just programatically forced registration of the BouncyCastleProvider before the initialization of ApacheDS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2868) Expose underlying cause during InitialContextFactory instantiation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2868?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2868: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1061609|https://bugzilla.redhat.com/show_bug.cgi?id=1061609] from MODIFIED to ON_QA > Expose underlying cause during InitialContextFactory instantiation > ------------------------------------------------------------------ > > Key: WFLY-2868 > URL: https://issues.jboss.org/browse/WFLY-2868 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > Priority: Critical > Fix For: 8.0.0.Final > > > Instantiation an InitialContext might fail with just the follow cause: > javax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "deployment.externalContextBindingTest.jar:main" from Service Module Loader > The underlying cause is no longer available. > https://bugzilla.redhat.com/show_bug.cgi?id=1061609 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2047) testConnection should account for deployment classloader

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2047?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2047: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1060997|https://bugzilla.redhat.com/show_bug.cgi?id=1060997] from MODIFIED to ON_QA > testConnection should account for deployment classloader > -------------------------------------------------------- > > Key: WFLY-2047 > URL: https://issues.jboss.org/browse/WFLY-2047 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Alpha4 > Environment: All > Reporter: Jay Kumar SenSharma > Assignee: Stefano Maestri > Fix For: 9.0.0.CR1 > > > If a DataSource is created as following: > ++++++++++++++++ > <datasource jndi-name="java:jboss/datasources/test_pool" pool-name="test_pool" enabled="true" use-java-context="true"> > <connection-url>jdbc:oracle:thin:@ldap://example.com:3060/test,cn=OracleA,dc=worldA</connection-url> > <driver>oracle</driver> > <pool> > <min-pool-size>1</min-pool-size> > <max-pool-size>15</max-pool-size> > </pool> > <security> > <user-name>Test</user-name> > <password>testPassword</password> > </security> > </datasource> > <drivers> > <driver name="oracle" module="com.oracle.jdbc6"> > <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> > </driver> > <driver name="h2" module="com.h2database.h2"> > <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> > </driver> > </drivers> > ++++++++++++++++ > Then while testing the DataSource the Wildfly throws the following Exception: > +++++++++++++++++++++ > 16:47:10,498 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (management-handler-thread - 3) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:282) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:240) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:781) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.getConnection(SemaphoreArrayListManagedConnectionPool.java:344) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getSimpleConnection(AbstractPool.java:397) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.getConnection(AbstractPool.java:365) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.internalTestConnection(AbstractPool.java:627) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.jca.core.connectionmanager.pool.strategy.OnePool.testConnection(OnePool.java:89) [ironjacamar-core-impl-1.0.17.Final.jar:1.0.17.Final] > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$TestConnectionInPool.invokeCommandOn(PoolOperations.java:143) [jboss-as-connector-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.connector.subsystems.common.pool.PoolOperations$1.execute(PoolOperations.java:82) [jboss-as-connector-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:440) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:322) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:229) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:224) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:194) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:115) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:139) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:108) [jboss-as-controller-7.3.0.Final-redhat-X-SNAPSHOT.jar:7.3.0.Final-redhat-X-SNAPSHOT] > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:296) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:518) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_21] > at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: java.sql.SQLRecoverableException: Io exception: JNDI Package failurejavax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.as.connector:main" from local module loader @571a75a2 (finder: local module finder @a210b5b (roots: /home/jsensharma/NotBackedUp/SVN_16_Jan/EAP6_Main/build_wildfly/jboss-as-7.3.0.Final-redhat-X-SNAPSHOT/modules,/home/jsensharma/NotBackedUp/SVN_16_Jan/EAP6_Main/build_wildfly/jboss-as-7.3.0.Final-redhat-X-SNAPSHOT/modules/system/layers/base)) > at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101) > at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112) > at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173) > at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229) > at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:458) > at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411) > at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:490) > at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202) > at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33) > at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:474) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:254) [ironjacamar-jdbc-1.0.17.Final.jar:1.0.17.Final] > ++++++++++++++++++++++ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2021) EE Component interceptor chains should be stateless

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2021?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2021: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1022265|https://bugzilla.redhat.com/show_bug.cgi?id=1022265] from MODIFIED to ON_QA > EE Component interceptor chains should be stateless > --------------------------------------------------- > > Key: WFLY-2021 > URL: https://issues.jboss.org/browse/WFLY-2021 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EE, EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > > This will allow them to be shared by all instances, rather than having a new chain allocated for each method. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2908) The formatter attribute is changed every time it's processed

by James Perkins (JIRA)

James Perkins created WFLY-2908: ----------------------------------- Summary: The formatter attribute is changed every time it's processed Key: WFLY-2908 URL: https://issues.jboss.org/browse/WFLY-2908 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Logging Reporter: James Perkins Assignee: James Perkins Priority: Minor Fix For: 8.0.1.Final The {{HandlerOperations.equalValue()}} method uses the incorrect property name when comparing values resulting in the method always returning {{false}}. This does not harm anything, but just changes the format pattern each time a resource is processed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2884) WildFly issuing new cookie for every request, when faces view is not directly in root (/ )

by André Prata (JIRA)

[ https://issues.jboss.org/browse/WFLY-2884?page=com.atlassian.jira.plugin.... ] André Prata commented on WFLY-2884: ----------------------------------- Has anyone been able to reproduce it? Is this a "valid" reproducer app? > WildFly issuing new cookie for every request, when faces view is not directly in root (/ ) > ------------------------------------------------------------------------------------------ > > Key: WFLY-2884 > URL: https://issues.jboss.org/browse/WFLY-2884 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: André Prata > Assignee: Stuart Douglas > Attachments: test.war > > > Hello everyone. > I have seen possibly similar issues, but people just aren't able to reproduce them anymore and they seem to be closed without further inspection. Maybe this is the same problem. > I started seeing a problem in a new application I'm developing. For views such as "/view.xhtml" everything is working fine. But if I move the view to another directory, e.g. "/admin/view.xtml", I get ViewExpiredExceptions when interacting with backing beans. > Two things: > - This does not happen if there is already a cookie associated with the session. I.e., I can only reproduce the issue if the first cookie is created by accessing "/admin/view.xhtml". Accessing something in the root and then the other directories works just fine (the server won't send set-cookies again). > - When accessing "/admin/view.xhtml" new cookies are issued for every .xhtml request. Fetching PrimeFaces .js.xhtml files after the initial page is loaded, for example, triggers new sessions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2898) JNDI Name lookup of the DataSource returns NULL

by Igor Shulika (JIRA)

[ https://issues.jboss.org/browse/WFLY-2898?page=com.atlassian.jira.plugin.... ] Igor Shulika updated WFLY-2898: ------------------------------- Attachment: jaffa-oracle-driver-6.0.0.Alpha2-SNAPSHOT.jar Attaching driver-class - This class is an extension to the OracleDriver class > JNDI Name lookup of the DataSource returns NULL > ----------------------------------------------- > > Key: WFLY-2898 > URL: https://issues.jboss.org/browse/WFLY-2898 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming, Web (Undertow) > Affects Versions: 8.0.0.CR1, 8.0.0.Final > Reporter: Igor Shulika > Assignee: Eduardo Martins > Attachments: 1.PNG, 2.PNG, 3.PNG, jaffa-oracle-driver-6.0.0.Alpha2-SNAPSHOT.jar > > > Hi, > I'm having a problem to obtain DataSource using JNDI Name lookup. > Please see my code below: > Connection connection = null; > DataSource dataSource = null; > try { > final Context initContext = new InitialContext(); > dataSource = (DataSource) initContext.lookup("java:/MyDataSource"); connection = dataSource.getConnection(); > } catch (Exception e) { > LOGGER.error(e); > } > I'm doing initContext.lookup from a servlet, everything is working on JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14). > Also I can find and test connection of my “java:/MyDataSource” under the “Datasources” section of the WildFly Administration Console just fine(anoter word the datasource is there). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 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 2014