[JBoss JIRA] Updated: (JBAS-2477) Exception in web-console j2ee domain after undeploy of application
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2477?page=all ]
Dimitris Andreadis updated JBAS-2477:
-------------------------------------
Component/s: Web Console
(was: Management services)
Assignee: 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: Darran Lofthouse
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> 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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-1748) hot deploying JMX invoker service fails
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1748?page=all ]
Dimitris Andreadis updated JBAS-1748:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-4.0.5.GA)
> hot deploying JMX invoker service fails
> ---------------------------------------
>
> Key: JBAS-1748
> URL: http://jira.jboss.com/jira/browse/JBAS-1748
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.2 Final
> Reporter: Norman Richards
> Assigned To: Vicky Kak
> Priority: Minor
> Fix For: JBossAS-5.0.0.CR1
>
>
> jmx-invoker-service.xml cannot be hot deployed. Trying to hot deploy it causes a failure when redeploying the web console. After this failure, I the JMX invoker cannot be contacted. Here's the resulting web console error:
> 22:49:04,904 ERROR [WebModule] Starting failed jboss.web.deployment:id=-1500951031,war=web-console.war
> java.lang.NullPointerException
> at org.jboss.web.WebModule.startModule(WebModule.java:67)
> at org.jboss.web.WebModule.startService(WebModule.java:46)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:911)
> at $Proxy0.start(Unknown Source)
> at org.jboss.system.ServiceController.start(ServiceController.java:416)
> at org.jboss.system.ServiceController.start(ServiceController.java:438)
> at org.jboss.system.ServiceController.start(ServiceController.java:438)
> at org.jboss.system.ServiceController.start(ServiceController.java:438)
> at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
> at $Proxy4.start(Unknown Source)
> at org.jboss.deployment.SARDeployer.start(SARDeployer.java:273)
> at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
> at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:738)
> at sun.reflect.GeneratedMethodAccessor50.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:121)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
> at $Proxy8.deploy(Unknown Source)
> at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:325)
> at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:483)
> at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:204)
> at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:215)
> at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:194)
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-3187) Improve web-console logging
by Darran Lofthouse (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-3187?page=all ]
Darran Lofthouse updated JBAS-3187:
-----------------------------------
Component/s: Web Console
(was: Management services)
> 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: Darran Lofthouse
> Fix For: JBossAS-4.0.6.CR1
>
>
> 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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-2037) Bug in the JBoss HTML adaptor.
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-2037?page=all ]
Dimitris Andreadis updated JBAS-2037:
-------------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
> Bug in the JBoss HTML adaptor.
> ------------------------------
>
> Key: JBAS-2037
> URL: http://jira.jboss.com/jira/browse/JBAS-2037
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.0 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2 Final, JBossAS-3.2.5 Final, JBossAS-4.0.2RC1, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.3RC1
> Reporter: jean deruelle
> Fix For: JBossAS-4.0.6.CR1
>
>
> "The set of characters in a value is also limited. If
> special characters may occur, it is recommended that the
> value be quoted, using ObjectName.quote. If the value for a
> given key is sometimes quoted, then it should always be
> quoted. By default, if a value is a string (rather than a
> number, say), then it should be quoted unless you are sure
> that it will never contain special characters." quoted from
> java management best practices (see
> http://java.sun.com/products/JavaManagement/best-practices.html#mozTocId6...
> in section ObjectNameSyntax)
> When a JMX value is quoted, it causes problems to invoke methods through thr Jboss jmx web console :
> So my feeling is that the problem comes from the jboss jmx
> console jsp pages.
> The thing is that the quotes in the jmx object name are not
> encoded to the html format in the jsp pages and so the first
> opening quote is interpreted as the final quote of the html
> field.
> Here is a quick fix for Jboss-3.2.6 :
> Add the following lines to
> %JBOSS_HOME%\server\all\deploy\jmx-console.war\inspectMBean.jsp
> after line 141
> <%objectNameString=objectNameString.replaceAll("\"",""");
> //objectNameString=URLEncoder.encode(objectNameString);%>
> It was a quick fix to fit my needs but the
> line should really be the one commented but in that case the
> HtmlAdaptorServlet from Jboss cannot handle it correctly
> because it doesn't do a URLDecoder.decode of the
> objectNameString stored in the request parameter called "name".
> But I might be wrong here in saying that it comes from
> jboss, maybe I missed something along the way.
> Can someone confirm this bug or help me out there ?
> Thx
> Best regards
> Jean
--
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
19 years, 10 months
[JBoss JIRA] Assigned: (JBAS-1608) Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
by Amit Bhayani (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1608?page=all ]
Amit Bhayani reassigned JBAS-1608:
----------------------------------
Assignee: Amit Bhayani
> Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
> -------------------------------------------------------------------------------
>
> Key: JBAS-1608
> URL: http://jira.jboss.com/jira/browse/JBAS-1608
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.0 Final, JBossAS-3.2.5 Final, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2RC1
> Environment: Nothing specific
> Reporter: Amit Bhayani
> Assigned To: Amit Bhayani
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> The Configuration (RW) attribute of jboss:service=Mail MBean breaks (doesn't display the whole property but while setting it works fine) when encounters " (double inverted comma).
> For example set the following in Configuration (RW) attribute <configuration><property name="mail.from" value="xyz(a)nosuchhost.nosuchdomain.com"/></configuration> and apply changes. Now on Configuration textbox you can see <configuration><property name= only.
--
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
19 years, 10 months
[JBoss JIRA] Commented: (JBAS-1608) Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
by Amit Bhayani (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1608?page=comments#action_12343461 ]
Amit Bhayani commented on JBAS-1608:
------------------------------------
Will take a look at this latter.
> Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
> -------------------------------------------------------------------------------
>
> Key: JBAS-1608
> URL: http://jira.jboss.com/jira/browse/JBAS-1608
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.0 Final, JBossAS-3.2.5 Final, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2RC1
> Environment: Nothing specific
> Reporter: Amit Bhayani
> Assigned To: Amit Bhayani
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> The Configuration (RW) attribute of jboss:service=Mail MBean breaks (doesn't display the whole property but while setting it works fine) when encounters " (double inverted comma).
> For example set the following in Configuration (RW) attribute <configuration><property name="mail.from" value="xyz(a)nosuchhost.nosuchdomain.com"/></configuration> and apply changes. Now on Configuration textbox you can see <configuration><property name= only.
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-1608) Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1608?page=all ]
Dimitris Andreadis updated JBAS-1608:
-------------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
Defer minor issues for now, unless Amit you want to provide a patch.
> Configuration (RW) attribute on JMX-Console breaks for jboss:service=Mail MBean
> -------------------------------------------------------------------------------
>
> Key: JBAS-1608
> URL: http://jira.jboss.com/jira/browse/JBAS-1608
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management services
> Affects Versions: JBossAS-4.0.0 Final, JBossAS-3.2.5 Final, JBossAS-4.0.1RC1, JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2RC1
> Environment: Nothing specific
> Reporter: Amit Bhayani
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> The Configuration (RW) attribute of jboss:service=Mail MBean breaks (doesn't display the whole property but while setting it works fine) when encounters " (double inverted comma).
> For example set the following in Configuration (RW) attribute <configuration><property name="mail.from" value="xyz(a)nosuchhost.nosuchdomain.com"/></configuration> and apply changes. Now on Configuration textbox you can see <configuration><property name= only.
--
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
19 years, 10 months
[JBoss JIRA] Updated: (JBAS-1703) inspectMBean.jsp throws AccessControlException
by Dimitris Andreadis (JIRA)
[ http://jira.jboss.com/jira/browse/JBAS-1703?page=all ]
Dimitris Andreadis updated JBAS-1703:
-------------------------------------
Fix Version/s: JBossAS-4.0.6.CR1
(was: JBossAS-4.0.5.GA)
> inspectMBean.jsp throws AccessControlException
> ----------------------------------------------
>
> Key: JBAS-1703
> URL: http://jira.jboss.com/jira/browse/JBAS-1703
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: JBossAS-4.0.2RC1
> Environment: JBoss Version 4.0.2RC1
> Reporter: Roland R?z
> Priority: Minor
> Fix For: JBossAS-4.0.6.CR1
>
>
> The inspectMBean.jsp page throws a AccessControlException (javax.management.MBeanServerPermission is
> missing) although the codesource from where the JSP servlet is loaded (I use precompiled JSPs) has those
> permission.
> This is the code section where the AccessControlException is thrown
> for(int a = 0; a < attributeInfo.length; a ++)
> {
> final MBeanAttributeInfo attrInfo = attributeInfo[a];
> String attrName = attrInfo.getName();
> String attrType = attrInfo.getType();
> AttrResultInfo attrResult = Server.getMBeanAttributeResultInfo(objectNameString, attrInfo);
> ...
> You should use AccessController.doPrivileged to execute the code
> AttrResultInfo attrResult = Server.getMBeanAttributeResultInfo(objectNameString, attrInfo);
> Regards
--
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
19 years, 10 months