January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3250) jboss-ejb-client.xml parse error

by Yokoyama Yasuo (Created) (JIRA)

jboss-ejb-client.xml parse error -------------------------------- Key: AS7-3250 URL: https://issues.jboss.org/browse/AS7-3250 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.CR1b Reporter: Yokoyama Yasuo Assignee: David Lloyd Deploy application with jboss-ejb-client.xml cause following parse error. {noformat} Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011096: Exception while parsing jboss-ejb-client.xml file found at C:\git\jorsef\jboss-as\jboss-as\build\target\jboss-as-7.1.0.Final-SNAPSHOT\standalone\tmp\vfs\tempf48fc3926988e074\content-d91a2f2ac23e7a89\contents\META-INF\jboss-ejb-client.xml at org.jboss.as.ee.structure.EJBClientDescriptorParsingProcessor.parse(EJBClientDescriptorParsingProcessor.java:144) at org.jboss.as.ee.structure.EJBClientDescriptorParsingProcessor.parse(EJBClientDescriptorParsingProcessor.java:122) at org.jboss.as.ee.structure.EJBClientDescriptorParsingProcessor.deploy(EJBClientDescriptorParsingProcessor.java:104) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT] ... 5 more Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[7,4] Message: JBAS011094: Unexpected element '{urn:jboss:ejb-client:1.0}remoting-ejb-receiver' encountered at org.jboss.as.ee.structure.EJBClientDescriptor10Parser.unexpectedElement(EJBClientDescriptor10Parser.java:270) at org.jboss.as.ee.structure.EJBClientDescriptor10Parser.parseClientContext(EJBClientDescriptor10Parser.java:171) at org.jboss.as.ee.structure.EJBClientDescriptor10Parser.readElement(EJBClientDescriptor10Parser.java:138) at org.jboss.as.ee.structure.EJBClientDescriptor10Parser.readElement(EJBClientDescriptor10Parser.java:60) at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) at org.jboss.as.ee.structure.EJBClientDescriptorParsingProcessor.parse(EJBClientDescriptorParsingProcessor.java:138) ... 8 more {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3264) JBoss AS 7 + Struts2 File upload gives error

by Nick . (Created) (JIRA)

JBoss AS 7 + Struts2 File upload gives error -------------------------------------------- Key: AS7-3264 URL: https://issues.jboss.org/browse/AS7-3264 Project: Application Server 7 Issue Type: Bug Components: EE Affects Versions: 7.1.0.CR1 Environment: Windows + JBoss AS7.1.0 CR1 + Struts2- 2.3.1 Reporter: Nick . Assignee: David Lloyd Almost 2 weeks since i have posted the same in JBoss forum but there is no reply. I'm getting the following error while i try to upload a file using Struts2 FileUpload. After this error Server is getting shut down, when we restart the server and upload a file again then its not showing the error and file is getting uploaded. I guess this could be a bug in JBoss AS7. 20:58:33,484 INFO [org.apache.struts2.dispatcher.Dispatcher] (http-127.0.0.1-127.0.0.1-8080-5) Unable to find 'struts.multipart.saveDir' property setting. Defaulting to javax.servlet.context.tempdir 20:58:34,297 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Server\jboss-as-7.1.0.CR1-SNAPSHOT\jboss-modules.jar' 20:58:34,465 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\resources.jar' 20:58:34,563 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\rt.jar' 20:58:42,285 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\jsse.jar' 20:58:42,541 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\jce.jar' 20:58:42,668 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\charsets.jar' 20:58:42,887 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\ext\dnsns.jar' 20:58:42,903 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\ext\localedata.jar' 20:58:43,025 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\ext\sunjce_provider.jar' 20:58:43,098 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\ext\sunmscapi.jar' 20:58:43,136 ERROR [stderr] (http-127.0.0.1-127.0.0.1-8080-5) *sys-package-mgr*: processing new jar, 'C:\Program Files\Java\jdk1.6.0\jre\lib\ext\sunpkcs11.jar' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
6
0 / 0

[JBoss JIRA] (EJBTHREE-2274) GetCallerPrincipal in timeout callback doesn't behave correctly

by arjan tijms (Created) (JIRA)

GetCallerPrincipal in timeout callback doesn't behave correctly ---------------------------------------------------------------- Key: EJBTHREE-2274 URL: https://issues.jboss.org/browse/EJBTHREE-2274 Project: EJB 3.0 Issue Type: Bug Reporter: arjan tijms When {{getCallerPrincipal}} is called from within a timeout callback method, JBoss AS either throws an exception or returns the unauthenticated identity, but with the roles of the principal that scheduled the timer (if any). Per section 18.2.5.3 of the EJB 3.1 specification this is not correct: {quote} Since a timeout callback method is an internal method of the bean class, it has no client security context. When getCallerPrincipal is called from within a timeout callback method, it returns the container's representation of the unauthenticated identity. {quote} EJBTHREE-1036 seems related. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
7
0 / 0

[JBoss JIRA] (AS7-2970) Method getCallerPrincipal in @PreDestroy of SFSB returns null

by Ondřej Chaloupka (Created) (JIRA)

Method getCallerPrincipal in @PreDestroy of SFSB returns null ------------------------------------------------------------- Key: AS7-2970 URL: https://issues.jboss.org/browse/AS7-2970 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: Stuart Douglas Method getCallerPrincipal in @PreDestroy method of SFSB returns null. Calling of getCallerPrincipal in @PostConstruct and @PreDestroy method is allowed (EJB3.1 4.6.1). And for not authenticated user it should return "anonymous". Test: https://github.com/ochaloup/jboss-as/commits/JBQA-5483-test-migration-get... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
4
0 / 0

[JBoss JIRA] (AS7-3102) CLONE - Add security schema v1.1 with the vault element

by Dmitri Voronov (Created) (JIRA)

CLONE - Add security schema v1.1 with the vault element ------------------------------------------------------- Key: AS7-3102 URL: https://issues.jboss.org/browse/AS7-3102 Project: Application Server 7 Issue Type: Sub-task Components: Security Reporter: Dmitri Voronov Assignee: Anil Saldhana Fix For: 7.0.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

7
12
0 / 0

[JBoss JIRA] (AS7-2776) Injection by <ejb-ref> doesn't work for interceptors in ejb-jar.xml descriptor

by Ondřej Chaloupka (Created) (JIRA)

Injection by <ejb-ref> doesn't work for interceptors in ejb-jar.xml descriptor ------------------------------------------------------------------------------- Key: AS7-2776 URL: https://issues.jboss.org/browse/AS7-2776 Project: Application Server 7 Issue Type: Bug Reporter: Ondřej Chaloupka Assignee: Stuart Douglas Injection of session bean doesn't work when is specified in ejb-jar.xml for interceptors. {code:xml} <interceptors> <interceptor> <interceptor-class>org.jboss.as.test.integration.ejb.interceptor.complex.a.XMLInterceptorB</interceptor-class> <around-invoke> <method-name>intercept</method-name> </around-invoke> <ejb-ref> <ejb-ref-name>ejb/Session2</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <remote>org.jboss.as.test.integration.ejb.interceptor.complex.a.MySession2RemoteB</remote> <ejb-link>MySession2BeanB</ejb-link> <injection-target> <injection-target-class>org.jboss.as.test.integration.ejb.interceptor.complex.a.XMLInterceptorB</injection-target-class> <injection-target-name>session2</injection-target-name> </injection-target> </ejb-ref> </interceptor> </interceptors> {code:xml} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
2
0 / 0

[JBoss JIRA] (AS7-3279) Upgrade to Hibernate 4.0.1.Final

by Scott Marlow (JIRA)

Scott Marlow created AS7-3279: --------------------------------- Summary: Upgrade to Hibernate 4.0.1.Final Key: AS7-3279 URL: https://issues.jboss.org/browse/AS7-3279 Project: Application Server 7 Issue Type: Task Components: JPA / Hibernate Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-37) Ignore interruption when writing from OutputStreamHandlers

by David Lloyd (JIRA)

David Lloyd created LOGMGR-37: --------------------------------- Summary: Ignore interruption when writing from OutputStreamHandlers Key: LOGMGR-37 URL: https://issues.jboss.org/browse/LOGMGR-37 Project: JBoss Log Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.2.2.GA, 1.3.0.Beta1 If an interruption occurs, just retry/continue the operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

1
1
0 / 0

[JBoss JIRA] (AS7-3239) Convert ee-deployment subsystem to i18n logging and exceptions messages as per ANDIAMO-2

by Brian Stansberry (Created) (JIRA)

Convert ee-deployment subsystem to i18n logging and exceptions messages as per ANDIAMO-2 ---------------------------------------------------------------------------------------- Key: AS7-3239 URL: https://issues.jboss.org/browse/AS7-3239 Project: Application Server 7 Issue Type: Task Components: JSR88 Reporter: Brian Stansberry Assignee: Thomas Diesler Fix For: 7.1.0.Final The EeDeploymentLogger and EeDeploymentMessages classes are currently empty shells. The INFO and above logging and any exception messages in the subsystem needs to be converted to use these classes. See EJB subsystem for an example. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
3
0 / 0

[JBoss JIRA] (AS7-3262) Fix Domain CLI Tests (CLITestSuite)

by Kabir Khan (Created) (JIRA)

Fix Domain CLI Tests (CLITestSuite) ----------------------------------- Key: AS7-3262 URL: https://issues.jboss.org/browse/AS7-3262 Project: Application Server 7 Issue Type: Feature Request Reporter: Kabir Khan Assignee: Dominik Pospisil Priority: Critical These fail frequently when running the full testsuite with {code} testDeployRedeployUndeploy(org.jboss.as.test.integration.domain.management.cli.DeploySingleServerGroupTestCase) Time elapsed: 5.018 sec <<< ERROR! java.lang.Exception: CLI read timeout. at org.jboss.as.test.integration.management.util.CLIWrapper.readLine(CLIWrapper.java:168) at org.jboss.as.test.integration.management.util.CLIWrapper.sendLine(CLIWrapper.java:123) at org.jboss.as.test.integration.domain.management.cli.DeploySingleServerGroupTestCase.testRedeploy(DeploySingleServerGroupTestCase.java:104) at org.jboss.as.test.integration.domain.management.cli.DeploySingleServerGroupTestCase.testDeployRedeployUndeploy(DeploySingleServerGroupTestCase.java:77) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:2 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) at {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
4
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 January 2012