November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1131) Add configuration for Remoting servlet transport

by Ron Sigal (JIRA)

Add configuration for Remoting servlet transport ------------------------------------------------ Key: JBMESSAGING-1131 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1131 Project: JBoss Messaging Issue Type: Task Reporter: Ron Sigal Assigned To: Tim Fox Fix For: 2.0.0 Alpha In addition to the "http" transport, Remoting also has the http-based "servlet" transport. The servlet transport is the same as the http transport on the client side (they both use org.jboss.remoting.transport.http.HTTPClientInvokr), but they are different on the server side. In particular, CoyoteInvoker, the http transport server invoker, uses the network layer of tomcat/jbossweb, i.e., a ServerSocket with worker threads. But in the servlet transport, a org.jboss.remoting.transport.servlet.web.ServerInvokerServlet fields invocations and passes them to org.jboss.remoting.transport.servlet.ServletServerInvoker. The advantage, which came up in a forum thread recently (http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4098850#4098850 and http://www.jboss.com/index.html?module=bb&op=viewtopic&t=122218), is that only one ServerSocket is used. In principle, it's the appropriate transport to use when the server is running inside JBossAS. In fact, the wiki page "Accessing_EJB3s_over_HTTP_HTTPS" shows how to change the EJB3 transport from socket to servlet. However, there have been a couple of problems. For one, ServletServerInvoker has been a little behind CoyoteInvoker in its development, though I've been rectifying that (JBREM-675 "Problems with Servlet invoker"). For another, the servlet transport needs tomcat/jbossweb for unit testing, and we've never automated that, so it's not as well tested as CoyoteInvoker (JBREM-139 "need automated test for servlet server invoker"). However, I wanted to verify that JBossMessaging can run with the servlet transport, so I created a servlet example, parallel to the http example, along with the supporting configuration files, and it works. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

8
46
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-266) Provide a mechanism to handle contexts in error

by Ales Justin (JIRA)

Provide a mechanism to handle contexts in error ----------------------------------------------- Key: JBMICROCONT-266 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-266 Project: JBoss MicroContainer Issue Type: Feature Request Components: Kernel Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Create a mechanism to manage the failing beans/contexts without having to re-install them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-265) Concurrent deployments

by Ales Justin (JIRA)

Concurrent deployments ---------------------- Key: JBMICROCONT-265 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-265 Project: JBoss MicroContainer Issue Type: Feature Request Components: Dependency Affects Versions: JBossMC-2.0.0.Beta10 Reporter: Ales Justin Assigned To: Ales Justin Fix For: JBossMC-2.0.0.GA Allow for deployments to be processed in parallel. Enabling this would be set by new Controller Mode - asynchronous. It would still be largely "self-optimizing", depending on the user to worry about possible issues that might result from concurrent usage of resources. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-6108) Testcase for CLIENT-CERT for web application

by Anil Saldhana (JIRA)

Testcase for CLIENT-CERT for web application -------------------------------------------- Key: JBAS-6108 URL: https://jira.jboss.org/jira/browse/JBAS-6108 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Test Suite, Web (Tomcat) service Affects Versions: JBossAS-5.0.0.CR2 Reporter: Anil Saldhana Assignee: Marcus Moyses Fix For: JBossAS-5.0.0.GA Need a simple web application guarded by CLIENT-CERT in the test suite. Use apache httpclient to access the webapp. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1416) Provide complete message ordering

by Tim Fox (JIRA)

Provide complete message ordering --------------------------------- Key: JBMESSAGING-1416 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1416 Project: JBoss Messaging Issue Type: Feature Request Reporter: Tim Fox Assignee: Tim Fox Fix For: 1.4.0.SP3.CP04 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

5
28
0 / 0

[JBoss JIRA] Created: (JBAS-6227) Only way to remove a managedcomponent is to remove its deployment

by Charles Crouch (JIRA)

Only way to remove a managedcomponent is to remove its deployment ----------------------------------------------------------------- Key: JBAS-6227 URL: https://jira.jboss.org/jira/browse/JBAS-6227 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Reporter: Charles Crouch Assignee: Scott M Stark Fix For: JBossAS-5.0.0.GA Right now I'm using the following to remove a component: ManagementView mgtView = ProfileServiceFactory.getCurrentProfileView(); ManagedComponent managedComponent = getManagedComponent(); ManagedDeployment deployment = managedComponent.getDeployment(); mgtView.removeDeployment(deployment.getName(), ManagedDeployment.DeploymentPhase.APPLICATION); mgtView.process(); But if you have other things defined in the deployment, e.g. the hsqldb-ds.xml deployment contains jboss:service=Hypersonic,database=localDB service as well as the datasource, you end up blowing the whole lot away. There is an api on the deployment which *looks* like it would help, but replacing: mgtView.removeDeployment(deployment.getName(), ManagedDeployment.DeploymentPhase.APPLICATION); with deployment.removeComponent(managedComponent.getName()); appears to remove nothing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

6
19
0 / 0

[JBoss JIRA] Created: (JBRULES-1453) boss.seam.Component) - Exception calling component @Destroy method: repository

by Joseph Bonello (JIRA)

boss.seam.Component) - Exception calling component @Destroy method: repository ------------------------------------------------------------------------------ Key: JBRULES-1453 URL: http://jira.jboss.com/jira/browse/JBRULES-1453 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.4 Environment: Windows XP SP2, JDK 1.6, Sun Application Server 9u1 Reporter: Joseph Bonello rg.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.core.Events - 2008-02-07 08:59:20,453 () DEBUG (Events.java:60:org.jboss.seam.core.Events) - Processing event:org.jboss.seam.preDestroy.repository org.jboss.seam.Component - 2008-02-07 08:59:20,453 () WARN (Component.java:1340:org.jboss.seam.Component) - Exception calling component @Destroy method: repository java.lang.IllegalArgumentException: method not found: close for component: repository at org.jboss.seam.Component.callComponentMethod(Component.java:2105) at org.jboss.seam.Component.callDestroyMethod(Component.java:2018) at org.jboss.seam.Component.destroy(Component.java:1336) at org.jboss.seam.contexts.Contexts.destroy(Contexts.java:251) at org.jboss.seam.contexts.Contexts.flushAndDestroyContexts(Contexts.java:394) at org.jboss.seam.contexts.ServletLifecycle.endRequest(ServletLifecycle.java:60) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:49) at org.jboss.seam.web.ContextFilter.doFilter(ContextFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: java.lang.NoSuchMethodException: org.drools.brms.server.repository.RulesRepositoryManager_$$_javassist_2.close() at java.lang.Class.getMethod(Class.java:1605) at org.jboss.seam.Component.callComponentMethod(Component.java:2084) ... 32 more org.jboss.seam.contexts.Contexts - 2008-02-07 08:59:20,453 () DEBUG (Contexts.java:244:org.jboss.seam.contexts.Contexts) - destroying: org.jboss.seam.transaction.transaction org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.core.Events - 2008-02-07 08:59:20,453 () DEBUG (Events.java:60:org.jboss.seam.core.Events) - Processing event:org.jboss.seam.preDestroy.org.jboss.seam.transaction.transaction org.jboss.seam.contexts.Contexts - 2008-02-07 08:59:20,453 () DEBUG (Contexts.java:244:org.jboss.seam.contexts.Contexts) - destroying: org.jboss.seam.core.manager org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1966:org.jboss.seam.Component) - instantiating Seam component: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1387:org.jboss.seam.Component) - initializing new instance of: org.jboss.seam.core.events org.jboss.seam.Component - 2008-02-07 08:59:20,453 () DEBUG (Component.java:1404:org.jboss.seam.Component) - done initializing: org.jboss.seam.core.events -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2051) Problem with user anda role validation

by Keuller Magalhaes (JIRA)

Problem with user anda role validation -------------------------------------- Key: JBPORTAL-2051 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2051 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Identity, Portal Security Affects Versions: Portlet-1.0.2, Identity-1.0.3, 2.6.5 SP1 Environment: JBoss Portal 2.6.5SP1 with Oracle Database Reporter: Keuller Magalhaes When we are attempting to create a new role and its has been created JBoss Portal throws an constraint exception form database and does not handle it. Sometimes Admin interface shows us an error of code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

5
16
0 / 0

[JBoss JIRA] Created: (JBFORUMS-164) lastPostDate must be persisted in database

by Ryszard Kozmik (JIRA)

lastPostDate must be persisted in database ------------------------------------------ Key: JBFORUMS-164 URL: http://jira.jboss.com/jira/browse/JBFORUMS-164 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha Forums are not efficient mainly because of this very big problem of their module and database schema. There is no place to keep lastPostDates so they have to be generated each time what takes big amounts of time as those are very timetaking sql queries. This is main performance killer at this point. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBFORUMS-249) Make Forums compatible with Portal URLMapper

by Ryszard Kozmik (JIRA)

Make Forums compatible with Portal URLMapper -------------------------------------------- Key: JBFORUMS-249 URL: http://jira.jboss.com/jira/browse/JBFORUMS-249 Project: JBoss Forums Issue Type: Task Components: Forum Enhancements, Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC It is now impossible to overwrite url parameter names of Forums by Portal URLMapper and it should be. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2008