May 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-3188) Reduce the dependencies specified by web-console so it can be installed in more profiles.

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3188?page=all ] Clive Saldanha reassigned JBAS-3188: ------------------------------------ Assignee: Jon Prindiville (was: Clive Saldanha) > Reduce the dependencies specified by web-console so it can be installed in more profiles. > ----------------------------------------------------------------------------------------- > > Key: JBAS-3188 > URL: http://jira.jboss.com/jira/browse/JBAS-3188 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Jon Prindiville > > The web-console has been implemented to it is not strictly dependent on the components it makes available through it's interface, if any component it makes available through the interface is not installed then initialisation will fail just for that component and it will not be added to the tree. The remaining components will still be added to the tree and the web-console will continue to work correctly. > The installer should be updated so the web-console is dependent on less components so it can be installed in more profiles. > This will also get rid of another problem where the web console is dependent on specifc versions of components e.g. At the moment it is dependent on the JDK 1.4 version of AOP so can not be installed in any profile that uses the JDK 5.0 version of AOP. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2477) Exception in web-console j2ee domain after undeploy of application

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2477?page=all ] Fernando Nasser reassigned JBAS-2477: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > Exception in web-console j2ee domain after undeploy of application > ------------------------------------------------------------------ > > Key: JBAS-2477 > URL: http://jira.jboss.com/jira/browse/JBAS-2477 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.3 SP1 > Environment: Both Linux and Windows > Reporter: Lennart Petersson > Assigned To: Clive Saldanha > Priority: Minor > > Had listed all apps in web-console j2ee domains. Then undeployed one app. Then list again in web-console ---> exception below. > 10:31:54,896 INFO [TomcatDeployer] undeploy, ctxPath=/crimeportal, warUrl=.../tmp/deploy/tmp65013crimeportal.war/ > 10:31:54,914 INFO [EJBDeployer] Undeploying: file:/home/lenp/sources/jboss-4.0.3SP1/build/output/jboss-4.0.3SP1/server/lenp/deploy/CrimePortal.ear/CrimePortalBeans.jar > 10:31:55,162 INFO [ProxyFactory] Unbind EJB Home 'SicilianLaundry' from jndi 'SicilianLaundry' > 10:31:55,172 INFO [EjbModule] Undeployed SicilianLaundry > 10:31:55,173 INFO [ProxyFactory] Unbind EJB Home 'ShanghaiLaundry' from jndi 'ShanghaiLaundry' > 10:31:55,173 INFO [EjbModule] Undeployed ShanghaiLaundry > 10:31:55,190 INFO [EARDeployer] Undeploying J2EE application, destroy step: file:/home/lenp/sources/jboss-4.0.3SP1/build/output/jboss-4.0.3SP1/server/lenp/deploy/CrimePortal.ear/ > 10:32:01,401 INFO [STDOUT] javax.management.InstanceNotFoundException: jboss.management.local:J2EEApplication=CrimePortal.ear,J2EEServer=Local,j2eeType=EJBModule,name=CrimePortalBeans.jar is not registered. > 10:32:01,406 INFO [STDOUT] at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:508) > 10:32:01,406 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:651) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.createDeployedObjects(JSR77Lister.java:167) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.createServer(JSR77Lister.java:194) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.createServers(JSR77Lister.java:218) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.createDomain(JSR77Lister.java:233) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.createDomains(JSR77Lister.java:256) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.JSR77Lister.getTreeForResource(JSR77Lister.java:282) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.plugins.helpers.AbstractPluginWrapper.getSubTreeForResource(AbstractPluginWrapper.java:201) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.manager.PluginManager.getTreesForResource(PluginManager.java:392) > 10:32:01,410 INFO [STDOUT] at org.jboss.console.manager.PluginManager.getTreeForProfile(PluginManager.java:192) > 10:32:01,410 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 10:32:01,410 INFO [STDOUT] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > 10:32:01,410 INFO [STDOUT] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > 10:32:01,411 INFO [STDOUT] at java.lang.reflect.Method.invoke(Method.java:324) > 10:32:01,411 INFO [STDOUT] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) > 10:32:01,411 INFO [STDOUT] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) > 10:32:01,411 INFO [STDOUT] at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) > 10:32:01,411 INFO [STDOUT] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245) > 10:32:01,411 INFO [STDOUT] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) > 10:32:01,411 INFO [STDOUT] at org.jboss.console.remote.InvokerServlet.processRequest(InvokerServlet.java:90) > 10:32:01,411 INFO [STDOUT] at org.jboss.console.remote.InvokerServlet.doPost(InvokerServlet.java:133) > 10:32:01,411 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) > 10:32:01,411 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > 10:32:01,411 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) > 10:32:01,411 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 10:32:01,411 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) > 10:32:01,412 INFO [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) > 10:32:01,412 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) > 10:32:01,412 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) > 10:32:01,412 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) > 10:32:01,412 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > 10:32:01,430 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) > 10:32:01,430 INFO [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) > 10:32:01,430 INFO [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) > 10:32:01,430 INFO [STDOUT] at java.lang.Thread.run(Thread.java:534) > 1 -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1901) web-console shows dead archives after redeploy

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1901?page=all ] Fernando Nasser reassigned JBAS-1901: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > web-console shows dead archives after redeploy > ---------------------------------------------- > > Key: JBAS-1901 > URL: http://jira.jboss.com/jira/browse/JBAS-1901 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.2 Final > Reporter: Bill Burke > Assigned To: Clive Saldanha > Priority: Minor > > if you redeploy an ear multiple times you will see it show up multiple times > under the web-console/j2ee applications tree in the applet. If you try to browse one of those dead archives, it will blow up the j2ee applications tree structure -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2008) web console statistics view does not show properly in Firefox

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2008?page=all ] Fernando Nasser reassigned JBAS-2008: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > web console statistics view does not show properly in Firefox > ------------------------------------------------------------- > > Key: JBAS-2008 > URL: http://jira.jboss.com/jira/browse/JBAS-2008 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.2 Final > Environment: Firefox > Reporter: Kevin Barfield > Assigned To: Clive Saldanha > Priority: Minor > > The statistics view in the web console has a box though it when viewed through the Firefox browser. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1832) Improving JBoss WebConsole's snapshots

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1832?page=all ] Fernando Nasser reassigned JBAS-1832: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > Improving JBoss WebConsole's snapshots > -------------------------------------- > > Key: JBAS-1832 > URL: http://jira.jboss.com/jira/browse/JBAS-1832 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.0 Final > Environment: Not relevant > Reporter: Mathieu Bourrier > Assigned To: Clive Saldanha > Priority: Minor > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The snapshots in the Webconsole cannot be started automatically on startup, as the Recording field isn't an attribute. > 2 classes need to be modified, and the changes are quite small. > Given topic describes changes to be made in order to manage it. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3188) Reduce the dependencies specified by web-console so it can be installed in more profiles.

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3188?page=all ] Fernando Nasser reassigned JBAS-3188: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > Reduce the dependencies specified by web-console so it can be installed in more profiles. > ----------------------------------------------------------------------------------------- > > Key: JBAS-3188 > URL: http://jira.jboss.com/jira/browse/JBAS-3188 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.4.GA > Reporter: Darran Lofthouse > Assigned To: Clive Saldanha > > The web-console has been implemented to it is not strictly dependent on the components it makes available through it's interface, if any component it makes available through the interface is not installed then initialisation will fail just for that component and it will not be added to the tree. The remaining components will still be added to the tree and the web-console will continue to work correctly. > The installer should be updated so the web-console is dependent on less components so it can be installed in more profiles. > This will also get rid of another problem where the web console is dependent on specifc versions of components e.g. At the moment it is dependent on the JDK 1.4 version of AOP so can not be installed in any profile that uses the JDK 5.0 version of AOP. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3187) Improve web-console logging

by Fernando Nasser (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3187?page=all ] Fernando Nasser reassigned JBAS-3187: ------------------------------------- Assignee: Clive Saldanha (was: Darran Lofthouse) > Improve web-console logging > --------------------------- > > Key: JBAS-3187 > URL: http://jira.jboss.com/jira/browse/JBAS-3187 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Console > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Darran Lofthouse > Assigned To: Clive Saldanha > > The web-console application has been implemented so that it is not strictly dependent on the components that it makes available in the tree. > On initialisation if there are any errors initialising the viewer for any components in the tree view an error is output but the component is not added to the tree and the remaining components are initialised correctly. The web-console continues to work correctly for the components that were correctly initialised with no negative effects from the components that failed to initialise. > The web-console does not make use of Log4j at the moment. > The web-console should be updated to use Log4j (Being careful with classes sent to the applet) and the initialisation failures should be logged at a low level (either DEBUG or even TRACE). This will allow the web-console to be installed in more configurations without as many dependencies. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-381) Add param on destination to disable persistence

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-381?page=all ] Tim Fox closed JBMESSAGING-381. ------------------------------- Fix Version/s: Unscheduled (was: 2.0.0 Alpha) Resolution: Out of Date > Add param on destination to disable persistence > ----------------------------------------------- > > Key: JBMESSAGING-381 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-381 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Jeff Mesnil > Fix For: Unscheduled > > Attachments: patch-JBMESSAGING-381.txt > > Original Estimate: 1 day > Remaining Estimate: 1 day > > We should add a configuration param on destinations which id true prevents messages being persisted even if they are persistent. > This should give equivalent functionality to the JBossMQ NullPersistenceManager. > in some circumstances uses want to override persistence for messages but have no access to change the delivery mode at the sender. -- 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

18 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-681) Consolidate JMS related aspects into one JMS aspect

by Tim Fox (JIRA)

Consolidate JMS related aspects into one JMS aspect --------------------------------------------------- Key: JBMESSAGING-681 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-681 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 Currently, client side JMS functionality is implemented in a set of aspects: SessionAspect, TransactionAspect, FactoryAspect, etc. There seems no good reason to have these as separate aspects since we either provide all the jms functionality or none of it. Having the functionality distributed across several aspects makes it hard to communicate between them meaning the code is messy and hard to follow. We should consolidate into one aspect, from which hang a set of classes Session, Connection, Consumer etc which implement the jms functionality in a nice OO way. This will make the code simpler and easier to understand and possibly more performant since we would avoid unnecessary calls through the stack. -- 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

18 years, 2 months

4
28
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1198) Support SSL

by Jeff Mesnil (JIRA)

Support SSL ----------- Key: JBMESSAGING-1198 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1198 Project: JBoss Messaging Issue Type: Sub-task Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha the new remoting code which is based on MINA does not support SSL. All communications between JMS clients and servers must support SSL regardless of the transport which is used (TCP, HTTP) -- 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

18 years, 2 months

2
1
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 May 2008