June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-1556) Initial support OSGi webapps in JBossWeb

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-1556?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1556: -------------------------------- Summary: Initial support OSGi webapps in JBossWeb (was: Support OSGi webapp deployments in JBossWeb) Git Pull Request: https://github.com/jbossas/jboss-as/pull/2564 (was: https://github.com/jbossas/jboss-as/pull/2564) Forum Reference: http://community.jboss.org/message/17257#17257 (was: http://community.jboss.org/message/17257#17257) > Initial support OSGi webapps in JBossWeb > ---------------------------------------- > > Key: AS7-1556 > URL: https://issues.jboss.org/browse/AS7-1556 > Project: Application Server 7 > Issue Type: Feature Request > Components: OSGi > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Priority: Critical > Fix For: 7.2.0.Alpha1 > > Attachments: webapp-1.0.pdf > > > OSGi webapps are currently deployed onto jboss-osgi-webapp, which contains an embedded PAX-Web WAR extender that in turn delegates to the PAX-Web provided WebContainer based on Jetty. > In the future, OSGi webapps should be handled by JBossWeb and be deployed onto the JBoss embedded Tomcat instance. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-5081) Memory leak when requesting attributes using JMXConnectorFactory over remoting-jmx via management interface

by Lami Akagwu (JIRA)

Lami Akagwu created AS7-5081: -------------------------------- Summary: Memory leak when requesting attributes using JMXConnectorFactory over remoting-jmx via management interface Key: AS7-5081 URL: https://issues.jboss.org/browse/AS7-5081 Project: Application Server 7 Issue Type: Bug Components: JMX Affects Versions: 7.1.1.Final Environment: java version "1.6.0_31" Reporter: Lami Akagwu Assignee: Darran Lofthouse Priority: Critical Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 Repeated remote request of JMX attributes, as performed by a Nagios plugin, causes heap space to grow to the limit and eventually the server to freeze. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (EJBTHREE-2284) Remotely transmitted EJB context data can not be retreived

by Wouter De Borger (JIRA)

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (AS7-4976) Missing transaction isolation with EJB2.1 EntityBeans with pessimistic locking

by Klaus Benary (JIRA)

Klaus Benary created AS7-4976: --------------------------------- Summary: Missing transaction isolation with EJB2.1 EntityBeans with pessimistic locking Key: AS7-4976 URL: https://issues.jboss.org/browse/AS7-4976 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build Reporter: Klaus Benary Assignee: jaikiran pai On pessimistically locked EntityBeans, a transaction B can see the result of transaction A even if thransaction A threw an exception and thus did not commit. -- 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

13 years, 10 months

4
6
0 / 0

[JBoss JIRA] (AS7-3106) @WebServiceProvider annotation is not processed when implementation class loaded from dependant module

by Peter Skopek (Created) (JIRA)

@WebServiceProvider annotation is not processed when implementation class loaded from dependant module ------------------------------------------------------------------------------------------------------ Key: AS7-3106 URL: https://issues.jboss.org/browse/AS7-3106 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.0.Beta1b Reporter: Peter Skopek Assignee: Alessio Soldano Fix For: 7.1.0.CR1 When deploying picketlink-sts.war with dependent module org.picketlink specified in META-INF/jboss-deployment-structure.xml which contains class referred to as servlet (in web.xml) annotated with @WebServiceProvider it is deployed as servlet and not as webservice. If I copy the class file to war to WEB-INF/classes it works as expected. See two attached .war files. Only correct one creates following log entries: {noformat} 17:30:33,595 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service id=PicketLinkSTS address=http://localhost:8080/picketlink-sts-correct implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort wsdlLocation=null mtomEnabled=false 17:30:33,597 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) register: jboss.ws:context=picketlink-sts-correct,endpoint=PicketLinkSTS 17:30:33,859 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {urn:picketlink:identity-federation:sts}PicketLinkSTS from WSDL: WEB-INF/wsdl/PicketLinkSTS.wsdl 17:30:34,070 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts/PicketLinkSTS 17:30:34,132 INFO [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts-correct 17:30:34,179 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/picketlink-sts-correct {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

13 years, 10 months

6
6
0 / 0

[JBoss JIRA] (AS7-3715) Improve logging for JBAS014101 failed to find in cache

by Radoslav Husar (JIRA)

Radoslav Husar created AS7-3715: ----------------------------------- Summary: Improve logging for JBAS014101 failed to find in cache Key: AS7-3715 URL: https://issues.jboss.org/browse/AS7-3715 Project: Application Server 7 Issue Type: Enhancement Components: EJB Affects Versions: 7.1.0.CR1, 7.1.0.Final Reporter: Radoslav Husar Assignee: jaikiran pai Priority: Minor {code} [JBossINF] 09:36:35,460 INFO [org.jboss.as.ejb3] (EJB default - 7) JBAS014101: Failed to find {[-82, 118, -38, -43, -10, -125, 71, -61, -65, -31, -2, -47, 58, 55, -81, -22]} in cache {code} As per earlier discussions somewhere else please improve logging for JBAS014101. This message is rather cryptic for users. -- 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

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] (AS7-5076) Deploy of OSGi war failed

by Sebastian Nauck (JIRA)

Sebastian Nauck created AS7-5076: ------------------------------------ Summary: Deploy of OSGi war failed Key: AS7-5076 URL: https://issues.jboss.org/browse/AS7-5076 Project: Application Server 7 Issue Type: Bug Environment: JBoss-7.0.1-Final and JBoss-7.1.1-Final Reporter: Sebastian Nauck I will deploy a OSGi bundle with the suffix 'war'. This works fine on glassfish-3.1.2. But on JBoss-7.1.1-Final I get a Nullpointer. 10:10:49,592 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."JavaServerFaces.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."JavaServerFaces.war".POST_MODULE: Failed to process phase POST_MODULE of deployment "JavaServerFaces.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] 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_20] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_20] at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_20] Caused by: java.lang.NullPointerException at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:53) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:63) at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:55) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] ... 5 more -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-663) ContextPolicy.toString() should be improved

by Josef Cacek (JIRA)

Josef Cacek created SECURITY-663: ------------------------------------ Summary: ContextPolicy.toString() should be improved Key: SECURITY-663 URL: https://issues.jboss.org/browse/SECURITY-663 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: PicketBox_v4_0_9.Final Reporter: Josef Cacek Assignee: Anil Saldhana Priority: Minor ContextPolicy.toString() method, which is used for instance by DelegatingPolicy.listContextPolicies(), should return more valid (XML-like) output. There are missing right quotes for permission type attribute in UncheckedPermissions and RolePermissions sections. I would also use only a class name (getClass().getName()) as a value for permission type, so it's <Permission type='javax.security.jacc.WebUserDataPermission' name='/' actions='null' /> instead of <Permission type='class javax.security.jacc.WebUserDataPermission' name='/' actions='null' /> -- 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

13 years, 10 months

1
1
0 / 0

[JBoss JIRA] (JBRULES-3560) Add CSV cell merge explanation to docs

by Daniel Juliano (JIRA)

Daniel Juliano created JBRULES-3560: --------------------------------------- Summary: Add CSV cell merge explanation to docs Key: JBRULES-3560 URL: https://issues.jboss.org/browse/JBRULES-3560 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.4.0.Final Environment: System independent issue Reporter: Daniel Juliano Assignee: Mark Proctor It would be great if the "Drools Expert User Guide" contained a section on "differences between Excel and CSV" that outline some of the changes, like merging cells using ellipses. That one took me many hours to find on a stale forum post. While you're at it, a csv version of the Excel examples would be quite welcome. -- 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

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1769) Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear

by Nikos Ballas (JIRA)

Exposing deployments services through the xml deployment descriptor of the jar/sar/war/ear ------------------------------------------------------------------------------------------ Key: AS7-1769 URL: https://issues.jboss.org/browse/AS7-1769 Project: Application Server 7 Issue Type: Feature Request Components: EJB, JPA / Hibernate Affects Versions: 7.0.1.Final Environment: Linux, Window, MacOS, *BSD Reporter: Nikos Ballas Assignee: Carlo de Wolf Following scenario: Web application which is assembled by 4 different jars/wars: (1)myapp-model.jar -> contains the model + persistence.xml containing the definition of a CMT. (2)myapp-buisness.jar -> contains buisness EJB3's Spring Beans, whatever you can think of. (3)myapp-messaging.jar -> Contains MDB's for sending messages to several queues. (4)myapp-console.war -> Contains the web interface of the app. Now the -> define a dependency from a project to another to function,i.e. A->B means that A project has a dependency in B. Now the graph of dependencies between projects are: (4)->(2)->(1). Currently in jboss as 7 you are able to deploy your application either as module exposing several services(even though there is no clear documentation on how you do that.You follow the old way, you have to do something else?Nowhere in any documentation isn't that documented.) or you can use the deployments folder and copy everything there.Given the previous scenario if we deploy the module(2) then even if we have as dependency in the jboss-deployment-structure.xml the reference to the module(1) then we will get an exception saying that the persistence unit defined isn't accessible or undefined for the module(2). Now with the new version of jboss that allow us to manipulate the dependencies using the module mechanism and the well defined deployment and dependencies between projects it would be really useful if. When we define a dependency from one module to another, in my example from (2)->(1), also the mcs services defined are also exported in the target deployment, thus allowing access to the pu with the name for example is deployed. I don't know if this can be applied for the module architecture also. regards Nick -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
18
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 June 2012