December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4149) NamingExceptions not properly handled in InitialContext

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4149?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4149: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1170359|https://bugzilla.redhat.com/show_bug.cgi?id=1170359] from ASSIGNED to MODIFIED > NamingExceptions not properly handled in InitialContext > ------------------------------------------------------- > > Key: WFLY-4149 > URL: https://issues.jboss.org/browse/WFLY-4149 > Project: WildFly > Issue Type: Bug > Components: Naming > Reporter: David Lloyd > Assignee: Eduardo Martins > Fix For: 9.0.0.Beta1 > > > The change in https://github.com/jbossas/jboss-eap/commit/db525bf1d90a40eb909c8f915fca7... catches all Exception and rewraps them with NamingException. This behavior is undesirable if the original exception was already a NamingException. Catch and re-throw that exception type as-is before wrapping other exceptions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4153) Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4153?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4153: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 900798|https://bugzilla.redhat.com/show_bug.cgi?id=900798] from POST to MODIFIED > Incorrect interface definition in ejb-jar.xml for entity beans shows just NullPointer exception > ----------------------------------------------------------------------------------------------- > > Key: WFLY-4153 > URL: https://issues.jboss.org/browse/WFLY-4153 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Minor > > {noformat} > In case that you specify interface type for entity bean in ejb-jar.xml that does not correspond with definition in the class of the bean then just Null Pointer exception is shown without any other info what's happening. > I mean when you define bean through interface as remote and the ejb-jar.xml describes bean interfaces as local > {code} > public interface SomeBean extends EJBObject { > ... > } > public interface SomeBeanHome extends EJBHome { > ... > } > {code} > and the ejb-jar.xml looks like > {code} > <ejb-jar 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/ejb-jar_3_1.xsd" version="3.1"> > <enterprise-beans> > <entity> > <ejb-name>SomeBean</ejb-name> > <local-home>package.SomeBeanHome</local-home> > <local>package.SomeBean</local> > <ejb-class>package.SomeBeanBean</ejb-class> > <persistence-type>Bean</persistence-type> > <prim-key-class>java.lang.Integer</prim-key-class> > <reentrant>true</reentrant> > </entity> > </enterprise-beans> > </ejb-jar> > {code} > then NullPointerException is thrown > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."entitybeanbmp.jar".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "entitybeanbmp.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:123) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_23] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_23] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011058: Failed to install component SimpleBMPBean > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:102) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:116) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT] > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:108) > at org.jboss.as.ejb3.component.entity.EntityBeanObjectViewConfigurator$2.configureDependency(EntityBeanObjectViewConfigurator.java:105) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:139) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more > {code} > instead of some informative one. > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-445) Add support for some default JAAS configs for use by GSSAPI in the CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-445?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-445: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168918, https://bugzilla.redhat.com/show_bug.cgi?id=1168900 > Add support for some default JAAS configs for use by GSSAPI in the CLI > ---------------------------------------------------------------------- > > Key: WFCORE-445 > URL: https://issues.jboss.org/browse/WFCORE-445 > Project: WildFly Core > Issue Type: Task > Components: CLI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > > Where GSSAPI is in use in the CLI we need to be able to switch off prompting the user for their password, we also have issues depending on the JDK version where an error is reported if a file can not be found to be loaded. > In general we need a best efforts use the configuration of the JVM with a quiet fallback to default domain definitions with the appropriate Krb5LoginModule definitions. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4156) WildFly is not able to parse ejb-jar.xml of version 2.0

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4156?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4156: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from POST to MODIFIED > WildFly is not able to parse ejb-jar.xml of version 2.0 > ------------------------------------------------------- > > Key: WFLY-4156 > URL: https://issues.jboss.org/browse/WFLY-4156 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 9.0.0.Beta1 > > > - While using "ejb-jar.xml" of version 2.0 as following EAP/WildFly throws the parsing error: > {code} > <?xml version="1.0"?> > <!DOCTYPE ejb-jar > PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" > "http://java.sun.com/dtd/ejb-jar_2_0.dtd"> > <ejb-jar> > <enterprise-beans> > <message-driven> > <ejb-name>ExampleMDB</ejb-name> > <ejb-class>test.mdb.ExampleMDB</ejb-class> > <transaction-type>Container</transaction-type> > <message-driven-destination> > <destination-type>javax.jms.Queue</destination-type> > </message-driven-destination> > <resource-ref> > <res-ref-name>jms/QueueConnectionFactory</res-ref-name> > <res-type>javax.jms.QueueConnectionFactory</res-type> > <res-auth>Container</res-auth> > </resource-ref> > </message-driven> > </enterprise-beans> > </ejb-jar> > {code} > - The following error is encountered at the time of deployment: > {code} > 17:40:04,405 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."TestEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TestEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "TestEJB.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_45] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_45] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_45] > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:250) > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.deploy(EjbJarParsingDeploymentUnitProcessor.java:121) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14] > ... 5 more > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10] > Message: Unexpected element 'message-driven-destination' encountered > at org.jboss.metadata.parser.util.MetaDataElementParser.unexpectedElement(MetaDataElementParser.java:109) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElement(AbstractMetaDataParser.java:56) > at org.jboss.metadata.ejb.parser.spec.AbstractNamedMetaDataWithDescriptionGroupParser.processElement(AbstractNamedMetaDataWithDescriptionGroupParser.java:67) > at org.jboss.metadata.ejb.parser.spec.AbstractEnterpriseBeanMetaDataParser.processElement(AbstractEnterpriseBeanMetaDataParser.java:85) > at org.jboss.metadata.ejb.parser.spec.AbstractMessageDrivenBeanParser.processElement(AbstractMessageDrivenBeanParser.java:94) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:77) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.processElement(MessageDrivenBean31Parser.java:37) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.MessageDrivenBean31Parser.parse(MessageDrivenBean31Parser.java:44) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:99) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.processElement(EnterpriseBeansMetaDataParser.java:40) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:75) > at org.jboss.metadata.ejb.parser.spec.EnterpriseBeansMetaDataParser.parse(EnterpriseBeansMetaDataParser.java:68) > at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:112) > at org.jboss.metadata.ejb.parser.spec.AbstractEjbJarMetaDataParser.processElement(AbstractEjbJarMetaDataParser.java:39) > at org.jboss.metadata.ejb.parser.spec.AbstractMetaDataParser.processElements(AbstractMetaDataParser.java:69) > at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parseDocument(EjbJarMetaDataParser.java:110) > at org.jboss.metadata.ejb.parser.spec.EjbJarMetaDataParser.parse(EjbJarMetaDataParser.java:54) > at org.jboss.as.ejb3.deployment.processors.EjbJarParsingDeploymentUnitProcessor.parseEjbJarXml(EjbJarParsingDeploymentUnitProcessor.java:247) > ... 7 more > 17:40:04,422 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "TestEJB.jar" was rolled back with the following failure message: > {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"TestEJB.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"TestEJB.jar\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"TestEJB.jar\" > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014185: Exception while parsing ejb-jar.xml: /content/TestEJB.jar/META-INF/ejb-jar.xml > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,10] > Message: Unexpected element 'message-driven-destination' encountered"}} > {code} > **NOTE:** According to the link [1] EJB2.0 is supported with EAP6 so ideally JBoss should be able to parse the "ejb-jar.xml" of version 2.0 DTDs. > **NOTE:** there is a feature request seen for JBossAS7 for requesting support for ejb-jar.xml 2.0 DTDs [2] > [1] https://access.redhat.com/site/articles/113373 > [2] https://issues.jboss.org/browse/JBMETA-354 > Version-Release number of selected component (if applicable): > How reproducible: > Steps to Reproduce: > 1. Deploy an MDB based EJB jar in EAP6/WildFly and use the ejb-jar.xml as mentioned in the issue description. > Actual results: > - EAP6/WildFly should be able to parse the ejb-jar.xml properly and should deploy the MDB properly. > Expected results: > - Deployment should be successful. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1057835|https://bugzilla.redhat.com/show_bug.cgi?id=1057835] from POST to MODIFIED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBMETA-354) Support EJB 2.0 dtd descriptors

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBMETA-354?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBMETA-354: ------------------------------------------------ Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1171105|https://bugzilla.redhat.com/show_bug.cgi?id=1171105] from ASSIGNED to MODIFIED > Support EJB 2.0 dtd descriptors > ------------------------------- > > Key: JBMETA-354 > URL: https://issues.jboss.org/browse/JBMETA-354 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Affects Versions: 7.0.0.Final > Reporter: Carlo de Wolf > Assignee: Ivo Studensky > Fix For: 8.1.2.Final, 7.2.1.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-242) the deployment content is deleted if first undeploy and then deploy the same application using CLI batch

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-242?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-242: ------------------------------------------------ Marek Kopecky <mkopecky(a)redhat.com> changed the Status of [bug 1162444|https://bugzilla.redhat.com/show_bug.cgi?id=1162444] from ON_QA to VERIFIED > the deployment content is deleted if first undeploy and then deploy the same application using CLI batch > -------------------------------------------------------------------------------------------------------- > > Key: WFCORE-242 > URL: https://issues.jboss.org/browse/WFCORE-242 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Jay Kumar SenSharma > Assignee: Emmanuel Hugonnet > Priority: Minor > > - If deploy and undeploy CLI commands executed in a batch mode then it causes missing deployment inside the "data/content" directory which leads to the following error: > {code} > [Host Controller] 10:33:42,387 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "example.war")]) - failure description: "WFLYDC0058: No deployment content with hash d85f1e3106bc8a49838a0dccae9e80819c25e02c is available in the deployment content repository for deployment 'example.war'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuraiton file and restart." > [Host Controller] 10:33:42,390 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-795) jboss-ejb-iiop_1_0.xsd has both use="required" and default attributes on some elements

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-795?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on WFLY-795: ---------------------------------------------- Martin Svehla <msvehla(a)redhat.com> changed the Status of [bug 1028412|https://bugzilla.redhat.com/show_bug.cgi?id=1028412] from ON_QA to VERIFIED > jboss-ejb-iiop_1_0.xsd has both use="required" and default attributes on some elements > -------------------------------------------------------------------------------------- > > Key: WFLY-795 > URL: https://issues.jboss.org/browse/WFLY-795 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: James Livingston > Assignee: David Lloyd > Fix For: 8.0.0.CR1 > > > In jboss-ejb-iiop_1_0.xsd, the "integrity", "confidentiality", "establish-trust-in-client", and "establish-trust-in-target" attributes on the "iorTransportConfigType" complexType, and the "auth-method", "realm" and "required" attributes on the "iorASContextType" complexType have both use="required" and a default attribute. > This does not make sense because default values are only applicable to optional attributes. I'm not sure which is correct, but either the attributes should be optional or the default values removed. This problem causes the XSD to not validate. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-274) The CLI command "read-boot-errors" does not include the timestamp of the error event

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-274?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-274: ------------------------------------------------ Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1160898|https://bugzilla.redhat.com/show_bug.cgi?id=1160898] from ON_QA to VERIFIED > The CLI command "read-boot-errors" does not include the timestamp of the error event > ------------------------------------------------------------------------------------ > > Key: WFCORE-274 > URL: https://issues.jboss.org/browse/WFCORE-274 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Affects Versions: 1.0.0.Alpha13 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > > The CLI command "read-boot-errors" does not include the timestamp of the error event. For anyone using this command for diagnostic purposes, the absence of an event's timestamp decreases the usefulness of the information. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4159) (XA) Data Sources view shows only 5 entries

by Eugen Eisler (JIRA)

[ https://issues.jboss.org/browse/WFLY-4159?page=com.atlassian.jira.plugin.... ] Eugen Eisler updated WFLY-4159: ------------------------------- Attachment: JNDI View - jdbc.png > (XA) Data Sources view shows only 5 entries > ------------------------------------------- > > Key: WFLY-4159 > URL: https://issues.jboss.org/browse/WFLY-4159 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.2.0.Final > Environment: - Windows 7 Pro x64 > - Chrome Web Browser > Reporter: Eugen Eisler > Assignee: Heiko Braun > Priority: Minor > Attachments: JNDI View - jdbc.png, xa data sources.png > > > 20 xa datasources configured, but only 5 are displayed in Runtime / Subsystems / Datasources / XA Data sources. Same problem with non xa datasources. > Runtime / Subsystems / JNDI View shows all 20 datasources. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014