March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6302) Upgrade Artemis to 1.1.0.wildfly-014

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6302?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-6302: ------------------------------ Priority: Critical (was: Blocker) > Upgrade Artemis to 1.1.0.wildfly-014 > ------------------------------------ > > Key: WFLY-6302 > URL: https://issues.jboss.org/browse/WFLY-6302 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1314) Log datasource name in warn message when Network Adapter fails to establish connection with database.

by Lin Gao (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1314?page=com.atlassian.jira.plugin... ] Lin Gao updated JBJCA-1314: --------------------------- Security: (was: Red Hat Internal) > Log datasource name in warn message when Network Adapter fails to establish connection with database. > ----------------------------------------------------------------------------------------------------- > > Key: JBJCA-1314 > URL: https://issues.jboss.org/browse/JBJCA-1314 > Project: IronJacamar > Issue Type: Feature Request > Components: Core > Affects Versions: 1.2.6.Final > Environment: Red Hat JBoss Enterprise Application Platform > Reporter: Lin Gao > Assignee: Lin Gao > Labels: jboss, l > > When there's following log statement in "server.log": > {code} > WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: javax.resource.ResourceException: Could not create connection > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:331) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:288) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:834) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1] > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.fillToMin(SemaphoreArrayListManagedConnectionPool.java:775) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1] > at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80] > Caused by: java.sql.SQLRecoverableException: I/O-Fehler: The Network Adapter could not establish the connection > at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:517) > at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:557) > at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:233) > at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:29) > at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:556) > at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:303) > ... 5 more > Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection > at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:389) > at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:431) > at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:882) > at oracle.net.ns.NSProtocol.connect(NSProtocol.java:267) > at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1625) > at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:365) > ... 10 more > {code} > With the above warn message how to figure which DB connection could not be established with out testing connection using CLI or management console. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6316) Deploying @Stateless EJB causes default ejb cache to start unnecessarily.

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-6316: ---------------------------------- Summary: Deploying @Stateless EJB causes default ejb cache to start unnecessarily. Key: WFLY-6316 URL: https://issues.jboss.org/browse/WFLY-6316 Project: WildFly Issue Type: Bug Components: Clustering, EJB Affects Versions: 10.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro This cache isn't used for anything. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-952) Use WildFly Common for null param checks

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-952?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-952: ------------------------------------ Component/s: (was: CLI) > Use WildFly Common for null param checks > ---------------------------------------- > > Key: WFCORE-952 > URL: https://issues.jboss.org/browse/WFCORE-952 > Project: WildFly Core > Issue Type: Task > Reporter: David Lloyd > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > For each module, do the following: > * Locate any/all null param check methods in the log msg > * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed > * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1376) Update the module cli command help text

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1376?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1376: ------------------------------------- Component/s: CLI > Update the module cli command help text > --------------------------------------- > > Key: WFCORE-1376 > URL: https://issues.jboss.org/browse/WFCORE-1376 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > Priority: Minor > > The help text from the module CLI command is still referencing AS7 and doesn't explicitly specify that the command is local only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-957) Wildfly not respecting subdeployment dependency order

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-957?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-957: ------------------------------------ Component/s: Server > Wildfly not respecting subdeployment dependency order > ----------------------------------------------------- > > Key: WFCORE-957 > URL: https://issues.jboss.org/browse/WFCORE-957 > Project: WildFly Core > Issue Type: Bug > Components: Server > Reporter: Brian Riehman > Priority: Minor > Attachments: wildfly-deployment-order.ear, wildfly-deployment-order.tar.gz > > > When loading an EAR with {{initialize-in-order}} set to {{true}} within the {{application.xml}} and subdeployment dependencies defined in{{jboss-deployment-structure.xml}}, Wildfly does not load the EAR modules in order as specified nor as defined by the dependencies. > I have attached both a [source repository|https://github.com/briehman/wildfly-deployment-order] and the generated EAR. The {{application.xml}} and {{jboss-deployment-structure.xml}} are as below: > {code} > <?xml version="1.0" encoding="UTF-8"?> > <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd" version="6"> > <display-name>ear</display-name> > <initialize-in-order>true</initialize-in-order> > <module> > <web> > <web-uri>webapp-one-1.0-SNAPSHOT.war</web-uri> > <context-root>/one</context-root> > </web> > </module> > <module> > <web> > <web-uri>webapp-two-1.0-SNAPSHOT.war</web-uri> > <context-root>/two</context-root> > </web> > </module> > <module> > <web> > <web-uri>webapp-three-1.0-SNAPSHOT.war</web-uri> > <context-root>/three</context-root> > </web> > </module> > </application> > {code} > {code} > <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.2"> > <sub-deployment name="webapp-one-1.0-SNAPSHOT.war"> > </sub-deployment> > <sub-deployment name="webapp-two-1.0-SNAPSHOT.war"> > <dependencies> > <module name="deployment.wildfly-deployment-order.ear.webapp-one-1.0-SNAPSHOT.war" /> > </dependencies> > </sub-deployment> > <sub-deployment name="webapp-three-1.0-SNAPSHOT.war"> > <dependencies> > <module name="deployment.wildfly-deployment-order.ear.webapp-two-1.0-SNAPSHOT.war" /> > </dependencies> > </sub-deployment> > </jboss-deployment-structure> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1373) Unable to specify custom configuration directory via -Djboss.server.config.dir

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1373?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1373: ------------------------------------- Component/s: CLI > Unable to specify custom configuration directory via -Djboss.server.config.dir > ------------------------------------------------------------------------------ > > Key: WFCORE-1373 > URL: https://issues.jboss.org/browse/WFCORE-1373 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.1.0.CR1 > Reporter: Sergey Lisovoy > Assignee: ehsavoie Hugonnet > > Broken support for server config files location customization via: {{jboss.server.config.dir}}. > Previous Wildfly 10 versions till CR4 it works as expected. Broken since WF10.0.0.CR5 > See Steps to reproduce. > Error: > Cannot start embedded server: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYCTL0214: Could not get main file: config.xml. Specified files must be relative to the configuration dir: /opt/wildfly-10.0.0.Final/standalone/configuration -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-1360) CLI Options missed in WFCORE-1199

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1360?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1360: ------------------------------------- Component/s: CLI > CLI Options missed in WFCORE-1199 > --------------------------------- > > Key: WFCORE-1360 > URL: https://issues.jboss.org/browse/WFCORE-1360 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Ryan Emerson > Assignee: Ryan Emerson > > The comma-seperated lists for server-groups in DeployHandler and UndeployHandler were missed in the original commit for WFCORE-1199. The --properties field for ASModuleHandler as also omitted by mistake. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-952) Use WildFly Common for null param checks

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-952?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-952: ------------------------------------ Component/s: CLI > Use WildFly Common for null param checks > ---------------------------------------- > > Key: WFCORE-952 > URL: https://issues.jboss.org/browse/WFCORE-952 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: David Lloyd > Priority: Minor > Fix For: 3.0.0.Alpha1 > > > For each module, do the following: > * Locate any/all null param check methods in the log msg > * Replace them with calls to org.wildfly.common.Assert#checkNotNullParam or related method as needed > * Replace the old null param check method with a comment that reserves the ID and shows that it was previously used for that purpose -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-821) Verify correctness of documented / supported Management CLI Operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-821?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-821: ------------------------------------ Component/s: Domain Management > Verify correctness of documented / supported Management CLI Operations > ---------------------------------------------------------------------- > > Key: WFCORE-821 > URL: https://issues.jboss.org/browse/WFCORE-821 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > > See Management CLI Operations: > https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Applicatio... > As an example, server-set-restart-required in EAP 6 is public, but appears to have gone private later. This should be public again. > Side note, the restart-required and reload-required flags probably need to be reworked to ensure correctness when subsequent CLI changes are applied. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016