June 2008 - jboss-jira - Jboss List Archives

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

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2477?page=comments#action_12415924 ] Clive Saldanha commented on JBAS-2477: -------------------------------------- The fix is in the related JIRA link http://jira.jboss.com/jira/browse/JBAS-1901 > 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: JMX/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, 1 month

1
0
0 / 0

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

by Clive Saldanha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1901?page=all ] Clive Saldanha updated JBAS-1901: --------------------------------- Attachment: management-fix.patch After a lot of debugging I found out that the wars for an ear get added twice to list of (ObjectNames of) deployedObjects managed by J2EEServer. So I have attached a fix for it which only adds the ObjectName to the list if it is unique. Note: each MBean has a unique ObjectName in a MBeanServer. > 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: JMX/Web Console > Affects Versions: JBossAS-4.0.2 Final > Reporter: Bill Burke > Assigned To: Clive Saldanha > Priority: Minor > Attachments: management-fix.patch > > > 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, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1383) @Init of clustered bean with annotated with @RemoteHome never called

by Galder Zamarreno (JIRA)

@Init of clustered bean with annotated with @RemoteHome never called -------------------------------------------------------------------- Key: EJBTHREE-1383 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1383 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 5.0.0.Beta4, AS 4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno @Init method of a clustered SLSB exposing RemoteHome is never called. Also, the javadoc of @Init in AS is incorrect: "Annotation to mark a method that will initialize a stateful session" Should say: "Designates a method of a session bean that corresponds to the create method of an adapted Home interface or an adapted Local Home interface." Btw is not limited @Init just to SFSBs. -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1949) bad charset encoding on portlet and instances admin

by Luca Stancapiano (JIRA)

bad charset encoding on portlet and instances admin --------------------------------------------------- Key: JBPORTAL-1949 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1949 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.7 Final, 2.6.5 Final Environment: jboss portal 2.6.5 Reporter: Luca Stancapiano Assigned To: Luca Stancapiano Fix For: 2.6.4 Final there is a bug into myfaces 1.1.5 and up..... using <f:param name="id" value="#{instance.id}"> tag inside <h:commandLink> , I see that instance.id value has a bad encoding... if I use a word with special characters as à, è, ù, ì as instance.id for example 'modalità' , it is encoded into 'modalit&#224' instead of 'modalit&agrave' . When I click on a instance through command link into 'portal instances', that id cannot to be decoded and so I haven't access to that instance. I wrote a decoder that resolve this bug. It does the reverse of myfaces HTMLEncoder.It has to be used inside: class: org.jboss.portal.core.admin.ui.PortletManagerBean method: selectPortlet() : 357 row so: selectedPortletId = HTMLDecoder.decode((String)ctx.getExternalContext().getRequestParameterMap().get("id")); and class: org.jboss.portal.core.admin.ui.InstanceManagerBean method: selectInstance() : 356 row so: selectedId = HTMLDecoder.decode((String)params.get("id")); -- 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, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2013) Role admin portlet doesn't work properly for roles with umlauts

by Martin Putz (JIRA)

Role admin portlet doesn't work properly for roles with umlauts --------------------------------------------------------------- Key: JBPORTAL-2013 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2013 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.4 Final Reporter: Martin Putz Attachments: role-umlaut.patch Creating a role containing german umlauts like 'wundertäter' works correctly. But it isn't possible to administrate such a role. In role admin portlet we have the actions "edit role", "members" and "delete". Clicking "edit role" for an umlaut role causes nothing but the refresh of the role list. When clicking "members" or "delete" for an umlaut role the error message "Unable to perform action on role. Please take a look at the logfile for further information." will be displayed above the role list and the actions are not performed. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2032) Admin portlet does not properly handle portlet instance with umlauts in its name

by Martin Putz (JIRA)

Admin portlet does not properly handle portlet instance with umlauts in its name -------------------------------------------------------------------------------- Key: JBPORTAL-2032 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2032 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.5 Final, 2.6.4 Final Reporter: Martin Putz - it's not possible to delete a portlet instance with umlauts in its name - e.g. "Wundertäter". - clicking on the portlet instance name to goto the detail page also fails to show information about the portlet instance -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JGRP-778) Transport: discard messages sent from self if Channel.LOCAL option is false

by Bela Ban (JIRA)

Transport: discard messages sent from self if Channel.LOCAL option is false --------------------------------------------------------------------------- Key: JGRP-778 URL: http://jira.jboss.com/jira/browse/JGRP-778 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Priority: Optional Fix For: 2.6.3, 2.7 If channel.setOpt(Channel.LOCAL, false) is set, we discard messages at the JChannel level. However, since the messages still have to travel up the entire stack, only to be discarded, we should discard local messages (if set) already at the transport level. SOLUTION: send a CONFIG (or INFO?) event down the stack when an option has changed, so the transport can take note. -- 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, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1633) Merge DSL improvements into trunk

by Edson Tirelli (JIRA)

Merge DSL improvements into trunk --------------------------------- Key: JBRULES-1633 URL: http://jira.jboss.com/jira/browse/JBRULES-1633 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 5.0.0-M1 Reporter: Edson Tirelli Assigned To: Edson Tirelli Fix For: 5.0.0-M1 Matt Geis implemented a series of improvements in the DSL engine, including a brand new parser written in ANTLR. All the improvements were committed against branch: https://svn.labs.jboss.com/labs/jbossrules/branches/mattgeis/ We need to merge all his changes into trunk. -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5288) Upgrade jboss-integration to 5.0.0.CR1

by Dimitris Andreadis (JIRA)

Upgrade jboss-integration to 5.0.0.CR1 -------------------------------------- Key: JBAS-5288 URL: http://jira.jboss.com/jira/browse/JBAS-5288 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Assigned To: Heiko Braun Fix For: JBossAS-5.0.0.CR1 I assume that the EJB3/WS spi will be moved to the jboss-integration project, and so a new release will be needed. -- 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, 1 month

4
13
0 / 0

[JBoss JIRA] Created: (JBAOP-461) Resolve outstanding issues on Linux

by Kabir Khan (JIRA)

Resolve outstanding issues on Linux ----------------------------------- Key: JBAOP-461 URL: http://jira.jboss.com/jira/browse/JBAOP-461 Project: JBoss AOP Issue Type: Sub-task Reporter: Kabir Khan -- 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, 1 month

2
8
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 2008