March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBAS-1748) hot deploying JMX invoker service fails

by Mike Clark (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-1748?page=com.atlassian.jira.plug... ] Mike Clark reassigned JBAS-1748: -------------------------------- Assignee: Mike Clark (was: Vicky Kak) > hot deploying JMX invoker service fails > --------------------------------------- > > Key: JBAS-1748 > URL: https://jira.jboss.org/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 > Assignee: Mike Clark > Priority: Minor > Fix For: JBossAS-6.0.0.M3 > > > 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: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2034) Require JDK6

by Andrew Lee Rubinger (JIRA)

Require JDK6 ------------ Key: EJBTHREE-2034 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2034 Project: EJB 3.0 Issue Type: Task Components: build Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger We no longer support any JDK5 runtimes, so bump to JDK6 and enforce as part of the build -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1202) Allow realm specification in connect URI

by David Lloyd (JIRA)

Allow realm specification in connect URI ---------------------------------------- Key: JBREM-1202 URL: https://jira.jboss.org/jira/browse/JBREM-1202 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Priority: Minor Fix For: 3.1.0.Beta2 Syntax is: remote://host:123/ - use the user/realm configured in the OptionMap or client callback remote://user@host:123/ - use "user" as the authorization ID, realm is configured in the OptionMap or client callback remote://user;realm@host:123/ - user "user" as the authorization ID and "realm" as the default authentication realm -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-465) Remove role-name constraint from 'Security Domain Test' servlet within jboss-negotation-toolkit

by Darran Lofthouse (JIRA)

Remove role-name constraint from 'Security Domain Test' servlet within jboss-negotation-toolkit ----------------------------------------------------------------------------------------------- Key: SECURITY-465 URL: https://jira.jboss.org/jira/browse/SECURITY-465 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP3, Negotiation_2.0.4.GA The jboss-negotiation-toolkit is tested against the end users installation, for this reason we should not assume the user will be in the 'Users' role and allow any roles. The toolkit still displays all the roles loaded for the user so can still be used for testing the role searching. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-466) Error handling groups containing '/' in name using AdvancedLDAPLoginModule

by Darran Lofthouse (JIRA)

Error handling groups containing '/' in name using AdvancedLDAPLoginModule -------------------------------------------------------------------------- Key: SECURITY-466 URL: https://jira.jboss.org/jira/browse/SECURITY-466 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: Negotiation Affects Versions: Negotiation_2.0.3.SP2 Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.3.SP3, Negotiation_2.0.4.GA For the following search configuration: - <module-option name="baseCtxDN">CN=Users,DC=vm137domain,DC=gsslab</module-option> <module-option name="baseFilter">(userPrincipalName={0})</module-option> <module-option name="rolesCtxDN">CN=Users,DC=vm137domain,DC=gsslab</module-option> <module-option name="roleFilter">(distinguishedName={1})</module-option> <module-option name="roleAttributeID">memberOf</module-option> <module-option name="roleAttributeIsDN">true</module-option> <module-option name="roleNameAttributeID">cn</module-option> <module-option name="recurseRoles">true</module-option> If groups are found with '/' in the name e.g. 'CN=A/B,CN=Users,DC=vm137domain,DC=gsslab' the following is logged and the group skipped: - 2010-03-03 16:23:52,600 TRACE [org.jboss.security.negotiation.AdvancedLdapLoginModule] (http-10.32.224.157-8080-1) Failed to query roleNameAttrName javax.naming.NamingException: [LDAP: error code 1 - 000020D6: SvcErr: DSID-031006CC, problem 5012 (DIR_ERROR), data 0 -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1199) Add marshaller version to negotiation phase

by David Lloyd (JIRA)

Add marshaller version to negotiation phase ------------------------------------------- Key: JBREM-1199 URL: https://jira.jboss.org/jira/browse/JBREM-1199 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 Identify the marshaller version so that if one side is using a newer version, it can "downgrade" to the greatest common version. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1201) RequestListener.handleClose is redundant

by David Lloyd (JIRA)

RequestListener.handleClose is redundant ---------------------------------------- Key: JBREM-1201 URL: https://jira.jboss.org/jira/browse/JBREM-1201 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: r3 core: api Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.1.0.Beta2 If the user wants to take some action when the client closes, they should register a close handler on ClientContext. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6820) MDBs are hard-coded to use jms-ra.rar

by Clebert Suconic (JIRA)

MDBs are hard-coded to use jms-ra.rar ------------------------------------- Key: JBAS-6820 URL: https://jira.jboss.org/jira/browse/JBAS-6820 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3, JCA service Affects Versions: JBossAS-5.1.0.Beta1 Reporter: Clebert Suconic Assignee: Carlo de Wolf Priority: Critical We may have to deploy several resource-adapters for JBossMessaging. (Say.. remote servers, backup-servers and other configurations). It seems that the JNDI for Inbound is simply ignored at some level. Instead of getting the spec Inbound from the JCA configured factory, EJB3 is hard-coding the dependency to the resource adapter and this is not acceptable for JBoss Messaging. -- 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

16 years, 4 months

4
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2186) Extraction of the WSRP component to only rely on JBoss Portlet Container.

by Lionel ROSIER (JIRA)

Extraction of the WSRP component to only rely on JBoss Portlet Container. ------------------------------------------------------------------------- Key: JBPORTAL-2186 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2186 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.7.0 CR1 Reporter: Lionel ROSIER Assignee: Chris Laprun I need to make remote portlets without rely on the entire portal application. I have one Jboss AS running with my portal, and i have others JBoss AS running with business applications and portlets. I would like to have the minimum stuff with portal-wsrp component and portlet container to make it works in my "business" JBoss servers. thank you -- 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

16 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1124) aix UDP issue

by Aleksandar Kostadinov (JIRA)

aix UDP issue ------------- Key: JGRP-1124 URL: https://jira.jboss.org/jira/browse/JGRP-1124 Project: JGroups Issue Type: Bug Environment: aix 5 Reporter: Aleksandar Kostadinov Assignee: Bela Ban With SOA-P 5.0 ER6 I'm seeing the following exception starting server on aix5: 12:03:27,571 ERROR [UDP] failed sending message to null (154 bytes) java.lang.Exception: dest=/238.14.15.16:45688 (157 bytes) at org.jgroups.protocols.UDP._send(UDP.java:361) at org.jgroups.protocols.UDP.sendToAllMembers(UDP.java:302) at org.jgroups.protocols.TP.doSend(TP.java:1474) at org.jgroups.protocols.TP.send(TP.java:1464) at org.jgroups.protocols.TP.down(TP.java:1185) at org.jgroups.protocols.TP$ProtocolAdapter.down(TP.java:2304) at org.jgroups.protocols.Discovery.down(Discovery.java:374) at org.jgroups.protocols.MERGE2.down(MERGE2.java:175) at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:360) at org.jgroups.protocols.FD.down(FD.java:315) at org.jgroups.protocols.VERIFY_SUSPECT.down(VERIFY_SUSPECT.java:95) at org.jgroups.protocols.BARRIER.down(BARRIER.java:107) at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:803) at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:604) at org.jgroups.protocols.UNICAST.down(UNICAST.java:455) at org.jgroups.protocols.pbcast.STABLE$1.run(STABLE.java:644) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:452) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:109) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:218) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:896) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:735) Caused by: java.io.IOException: The socket name is not available on this system. at java.net.DatagramSocket.send(DatagramSocket.java:623) at org.jgroups.protocols.UDP._send(UDP.java:352) ... 23 more -- 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

16 years, 4 months

2
7
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 March 2010