October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2397) When using weld resource injection happens twice

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/WFLY-2397?page=com.atlassian.jira.plugin.... ] Jozef Hartinger reassigned WFLY-2397: ------------------------------------- Assignee: Jozef Hartinger (was: Stuart Douglas) > When using weld resource injection happens twice > ------------------------------------------------ > > Key: WFLY-2397 > URL: https://issues.jboss.org/browse/WFLY-2397 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: CDI / Weld > Affects Versions: 8.0.0.Beta1 > Reporter: Stuart Douglas > Assignee: Jozef Hartinger > > When using CDI to inject non-EJB components such as Servlets it appears both Weld and WF are performing resource injections. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1979) Default EE default bindings per-deployment

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1979?page=com.atlassian.jira.plugin.... ] Eduardo Martins resolved WFLY-1979. ----------------------------------- Resolution: Won't Fix I will reject this for now, and wait for community asking for such feature. > Default EE default bindings per-deployment > ------------------------------------------ > > Key: WFLY-1979 > URL: https://issues.jboss.org/browse/WFLY-1979 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: EE > Reporter: Eduardo Martins > Assignee: Eduardo Martins > > Deployments/Components should have the possibility of overriding what EE default bindings, introduced by WFLY-2158. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2201) Server-side XTS handlers not added if @WebService#portName is missing

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/WFLY-2201?page=com.atlassian.jira.plugin.... ] Gytis Trikleris closed WFLY-2201. --------------------------------- > Server-side XTS handlers not added if @WebService#portName is missing > --------------------------------------------------------------------- > > Key: WFLY-2201 > URL: https://issues.jboss.org/browse/WFLY-2201 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 8.0.0.CR1 > > > To reproduce, remove portName or targetNameSpace attributes from org.jboss.narayana.compensations.functional.distributed.DistributedTest in the TXFramework suite. You will see that the test fails with: > {code} > "MustUnderstand headers: [{http://docs.oasis-open.org/ws-tx/wscoor/2006/06}CoordinationContext] are not understood" > {code} > The problem is that the Endpoint is not recognised, by the XTS subsytem, as having a valid @WebService annotation if these attributes are missing. In reality they are optional and an application should be allowed to leave them off. However, these attribute values are used by the XTS subsytem, so we would need to find a way of using the defaults if they are missing from the annotation. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2027) EE Default DataSource is not working

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2027?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-2027. ------------------------------ Resolution: Done Fix for WFLY-2212 was merged. > EE Default DataSource is not working > ------------------------------------ > > Key: WFLY-2027 > URL: https://issues.jboss.org/browse/WFLY-2027 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ConfigAdmin, Domain Management, EE, JCA, JPA / Hibernate, Web Console > Affects Versions: 8.0.0.Alpha4 > Reporter: Lincoln Baxter III > Assignee: Eduardo Martins > Fix For: 8.0.0.Beta1 > > > The EE spec states that a default datasource must be supplied under: java:comp/DefaultDataSource, and if none is specified by the @Resource or persistence.xml, it must be assumed: > {code}EE 5.19 > The Java EE Platform requires that a Java EE Product Provider provide a database > in the operational environment (see Section EE.2.6, “Database”). The Java EE > Product Provider must also provide a preconfigured, default data source for use by > the application in accessing this database. > The Java EE Product Provider must make the default data source accessible to > the application under the JNDI name java:comp/DefaultDataSource. > The Application Component Provider or Deployer may explicitly bind a > DataSource resource reference to the default data source using the lookup element > of the Resource annotation or the lookup-name element of the resource-ref > deployment descriptor element. For example, > @Resource(lookup="java:comp/DefaultDataSource") > DataSource myDS; > In the absence of such a binding, the mapping of the reference will default to > the product's default data source. > For example, the following will map to a preconfigured data source for the > product's default database: > @Resource > DataSource myDS;{code} > This, isn't working however: > {code} > <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://www.oracle.com/webfolder/technetwork/jsc/xml/ns/persistence/persis..."> > <persistence-unit name="default" transaction-type="JTA"> > </persistence-unit> > </persistence>{code} > Results in: > {code} > 10:41:31,002 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 50) MSC000001: Failed to start service jboss.persistenceunit."jpa-standard.war#default": org.jboss.msc.service.StartException in service jboss.persistenceunit."jpa-standard.war#default": org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:134) [wildfly-jpa-8.0.0.Alpha4.jar:8.0.0.Alpha4] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final] > Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:98) > at org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:66) > at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:193) > at org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:88) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159) > at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131) > at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1844) > at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1802) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:844) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) > at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) > at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) > at org.jboss.as.jpa.hibernate4.management.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44) > at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:115) [wildfly-jpa-8.0.0.Alpha4.jar:8.0.0.Alpha4] > ... 4 more > 10:41:31,010 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"jpa-standard.war#default\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"jpa-standard.war#default\": org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set > Caused by: org.hibernate.HibernateException: Connection cannot be null when 'hibernate.dialect' not set"}} > {code} > Additionally, actually specifying the expected JDNI name of the default DS like this: > {code} <persistence-unit name="default" transaction-type="JTA"> > <jta-data-source>java:comp/DefaultDataSource</jta-data-source> > <exclude-unlisted-classes>false</exclude-unlisted-classes> > </persistence-unit>{code} > Results in this: > {code} > JBAS014775: New missing/unsatisfied dependencies: > service jboss.naming.context.java.module.jpa-standard.jpa-standard.DefaultDataSource (missing) dependents: [service jboss.persistenceunit."jpa-standard.war#default".__FIRST_PHASE__] > service jboss.persistenceunit."jpa-standard.war#default".__FIRST_PHASE__ (missing) dependents: [service jboss.deployment.unit."jpa-standard.war".POST_MODULE] > {code} -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2407) Upgrade to MSC 1.2.0.CR1

by Richard Opalka (JIRA)

Richard Opalka created WFLY-2407: ------------------------------------ Summary: Upgrade to MSC 1.2.0.CR1 Key: WFLY-2407 URL: https://issues.jboss.org/browse/WFLY-2407 Project: WildFly Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: MSC Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 8.0.0.CR1 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2017) Add ability to set XNIO options for listeners

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2017?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-2017. ------------------------------- Fix Version/s: 8.0.0.CR1 Resolution: Done now you can set all options defined in UndertowOptions on all listeners SSL_CLIENT_AUTH_MODE for https listener. > Add ability to set XNIO options for listeners > --------------------------------------------- > > Key: WFLY-2017 > URL: https://issues.jboss.org/browse/WFLY-2017 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Reporter: Stuart Douglas > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2169) Add support to change various Undertow listener options

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2169?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved WFLY-2169. ------------------------------- Fix Version/s: 8.0.0.CR1 Resolution: Done Exposed all options available under UndertowOptions > Add support to change various Undertow listener options > ------------------------------------------------------- > > Key: WFLY-2169 > URL: https://issues.jboss.org/browse/WFLY-2169 > Project: WildFly > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.0.0.Alpha4 > Environment: Ubuntu 12.04 LTS, openjdk-7-jdk-7u25-2.3.10-1ubuntu0.12.04.2 > Reporter: Bernd Nigmann > Assignee: Tomaz Cerar > Fix For: 8.0.0.CR1 > > > Undertow's default for the maximum number of HTTP parameter it parses in a GET or POST is 1000: > {noformat} > 15:05:41,276 ERROR [io.undertow.request] (default task-17) > Servlet request failed HttpServerExchange{ POST /***/*******/****}: > java.lang.IllegalStateException: UT000047: The number of > parameters exceeded the maximum of 1000 > {noformat} > In the Undertow sources (https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io...), I found this to be a configurable option: "{{MAX_PARAMETERS}}". > Please allow changing some of these Undertow options through the WildFly {{standalone.xml}}. Tomaz Cerar asked me to create a ticket for this, based on the referenced forum thread. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2406) Inconsistence in runtime updates for outbound LDAP connections.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2406: -------------------------------------- Summary: Inconsistence in runtime updates for outbound LDAP connections. Key: WFLY-2406 URL: https://issues.jboss.org/browse/WFLY-2406 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 8.0.0.CR1 Adding a new outbound LDAP connection results in runtime updates for all processes but modifying an attribute runtime is only updates for a normal server. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2405) Update 'LdapConnectionManagerService' to use the attribute definitions to read from the model.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-2405: -------------------------------------- Summary: Update 'LdapConnectionManagerService' to use the attribute definitions to read from the model. Key: WFLY-2405 URL: https://issues.jboss.org/browse/WFLY-2405 Project: WildFly Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBAS-6998) ProfileServiceBootstrap: Failed to build ManagedDeployment

by sai sri harsha gudladona (JIRA)

[ https://issues.jboss.org/browse/JBAS-6998?page=com.atlassian.jira.plugin.... ] sai sri harsha gudladona commented on JBAS-6998: ------------------------------------------------ The Link for the cause of this issue posted under http://www.jboss.org/community/wiki/ClassLoaderhasnotbeensetexceptioninbo... is not working. A fix or the new Link is appreciated. > ProfileServiceBootstrap: Failed to build ManagedDeployment > ---------------------------------------------------------- > > Key: JBAS-6998 > URL: https://issues.jboss.org/browse/JBAS-6998 > Project: Application Server 3 4 5 and 6 > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: JBoss AS 5.1.0, WinXP, jdk 1.6.0u13 > Reporter: Ondrej Medek > Assignee: Andrew Rubinger > Fix For: No Release > > Attachments: boot.log, boot.log.zip > > > I see two exception in my boot.log: DEBUG [ProfileServiceBootstrap] Failed to build ManagedDeployment for: > 1) AbstractKernelDeployment@1cd427a{name=file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/vfs.xml installed=true beanFactories=[AbstractBeanMetaData@c791f4{name=VFSCache bean=null properties=[realCache, permanentRoots] constructor=AbstractConstructorMetaData@198defc{parameters=[null] factoryClass=org.jboss.virtual.spi.cache.VFSCacheFactory factoryMethod=getInstance} autowireCandidate=true start=AbstractLifecycleMetaData@1579a30{ whenRequired=ControllerState@3f58bb{Start} parameters= }}, AbstractBeanMetaData@da9067{name=VfsNamesExceptionHandler bean=org.jboss.virtual.plugins.context.helpers.NamesExceptionHandler properties= constructor=AbstractConstructorMetaData(a)13e9934{parameters=[java.lang.String]} autowireCandidate=true}]} > org.jboss.deployers.spi.DeploymentException: Error deploying: file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/vfs.xml > at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) > 2) AbstractKernelDeployment@17044c5{name=file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml installed=true beanFactories=[AbstractBeanMetaData@1b2e44d{name=LogBridgeHandler bean=org.jboss.logbridge.LogBridgeHandler properties= constructor=null autowireCandidate=true}]} > org.jboss.deployers.spi.DeploymentException: Error deploying: file:/C:/data/a/jboss-5.1.0.GA/server/default/conf/bootstrap/logging.xml > at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) -- 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, 9 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 October 2013