[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment
by Guy Kaisin (JIRA)
[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ]
Guy Kaisin edited comment on AS7-5584 at 12/12/12 11:28 AM:
------------------------------------------------------------
Philippe,
I also tried build 1342 from that branche.
Same problem!
It looks like the patch has not been merged into this branche...
Am I wrong somewhere?
Regards,
guy
Here is the stacktrace:
17:15:35,368 INFO [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) fullName=java:glob
al/mid/UserContext
17:15:35,508 WARN [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) Starting failed na
me=be.post.mid.services:dao=UserContextMBean: java.lang.UnsupportedOperationException: JBAS011859: Naming cont
ext is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.ja
va:131)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:103
)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:90)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:261)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:158)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:269)
at javax.naming.InitialContext.rebind(InitialContext.java:408) [rt.jar:1.6.0_25]
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:185)
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:250)
at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.java:63)
at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:50)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:250)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:158)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:229)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)
at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:364)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:192) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerIntercep
tor.java:1035) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterc
eptor.java:974) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.
java:917) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.j
ava:312) [rt.jar:1.6.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.ja
va:551) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-a
s-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:90) [jboss-as-jmx-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-m
sc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_2
5]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
was (Author: kaising):
Philippe,
I also tried build 1342 from that branche.
Same problem!
it looks like the patch has not been merged into this branche...
Am I wrong somwhere?
Regards,
guy
Here is the stacktrace:
17:15:35,368 INFO [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) fullName=java:glob
al/mid/UserContext
17:15:35,508 WARN [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) Starting failed na
me=be.post.mid.services:dao=UserContextMBean: java.lang.UnsupportedOperationException: JBAS011859: Naming cont
ext is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.ja
va:131)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:103
)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:90)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:261)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:158)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:269)
at javax.naming.InitialContext.rebind(InitialContext.java:408) [rt.jar:1.6.0_25]
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:185)
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:250)
at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.java:63)
at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:50)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:250)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:158)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:229)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)
at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:364)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:192) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerIntercep
tor.java:1035) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterc
eptor.java:974) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.
java:917) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.j
ava:312) [rt.jar:1.6.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.ja
va:551) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-a
s-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:90) [jboss-as-jmx-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-m
sc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_2
5]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
> Naming context read-only during SAR deployment
> ----------------------------------------------
>
> Key: AS7-5584
> URL: https://issues.jboss.org/browse/AS7-5584
> Project: Application Server 7
> Issue Type: Bug
> Components: POJO
> Affects Versions: 7.1.1.Final
> Reporter: Philippe Marschall
> Assignee: Philippe Marschall
> Fix For: 7.2.0.Alpha1
>
>
> During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}}
> http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment
by Guy Kaisin (JIRA)
[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ]
Guy Kaisin edited comment on AS7-5584 at 12/12/12 11:27 AM:
------------------------------------------------------------
Philippe,
I also tried build 1342 from that branche.
Same problem!
it looks like the patch has not been merged into this branche...
Am I wrong somwhere?
Regards,
guy
Here is the stacktrace:
17:15:35,368 INFO [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) fullName=java:glob
al/mid/UserContext
17:15:35,508 WARN [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) Starting failed na
me=be.post.mid.services:dao=UserContextMBean: java.lang.UnsupportedOperationException: JBAS011859: Naming cont
ext is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.ja
va:131)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:103
)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:90)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:261)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:158)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:269)
at javax.naming.InitialContext.rebind(InitialContext.java:408) [rt.jar:1.6.0_25]
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:185)
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:250)
at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.java:63)
at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:50)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:250)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:158)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:229)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)
at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:364)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:192) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerIntercep
tor.java:1035) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterc
eptor.java:974) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.
java:917) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.j
ava:312) [rt.jar:1.6.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.ja
va:551) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-a
s-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:90) [jboss-as-jmx-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-m
sc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_2
5]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
was (Author: kaising):
Philippe,
I also tried build 1342 from that branche.
Same problem!
Regards,
guy
Here is the stacktrace:
17:15:35,368 INFO [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) fullName=java:glob
al/mid/UserContext
17:15:35,508 WARN [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) Starting failed na
me=be.post.mid.services:dao=UserContextMBean: java.lang.UnsupportedOperationException: JBAS011859: Naming cont
ext is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.ja
va:131)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:103
)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:90)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:261)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:158)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:269)
at javax.naming.InitialContext.rebind(InitialContext.java:408) [rt.jar:1.6.0_25]
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:185)
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:250)
at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.java:63)
at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:50)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:250)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:158)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:229)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)
at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:364)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:192) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerIntercep
tor.java:1035) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterc
eptor.java:974) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.
java:917) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.j
ava:312) [rt.jar:1.6.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.ja
va:551) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-a
s-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:90) [jboss-as-jmx-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-m
sc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_2
5]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
> Naming context read-only during SAR deployment
> ----------------------------------------------
>
> Key: AS7-5584
> URL: https://issues.jboss.org/browse/AS7-5584
> Project: Application Server 7
> Issue Type: Bug
> Components: POJO
> Affects Versions: 7.1.1.Final
> Reporter: Philippe Marschall
> Assignee: Philippe Marschall
> Fix For: 7.2.0.Alpha1
>
>
> During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}}
> http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5584) Naming context read-only during SAR deployment
by Guy Kaisin (JIRA)
[ https://issues.jboss.org/browse/AS7-5584?page=com.atlassian.jira.plugin.s... ]
Guy Kaisin edited comment on AS7-5584 at 12/12/12 11:16 AM:
------------------------------------------------------------
Philippe,
I also tried build 1342 from that branche.
Same problem!
Regards,
guy
Here is the stacktrace:
17:15:35,368 INFO [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) fullName=java:glob
al/mid/UserContext
17:15:35,508 WARN [be.post.common.servicebinder.ObjectJndiBinder] (MSC service thread 1-2) Starting failed na
me=be.post.mid.services:dao=UserContextMBean: java.lang.UnsupportedOperationException: JBAS011859: Naming cont
ext is read-only
at org.jboss.as.naming.WritableServiceBasedNamingStore.requireOwner(WritableServiceBasedNamingStore.ja
va:131)
at org.jboss.as.naming.WritableServiceBasedNamingStore.unbind(WritableServiceBasedNamingStore.java:103
)
at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:90)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:261)
at org.jboss.as.naming.InitialContext.rebind(InitialContext.java:158)
at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:269)
at javax.naming.InitialContext.rebind(InitialContext.java:408) [rt.jar:1.6.0_25]
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:185)
at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerializableFactory.java:250)
at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.java:63)
at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:50)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:250)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:158)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:229)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:154)
at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:364)
at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSupport.java:192) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegisterInvoke(DefaultMBeanServerIntercep
tor.java:1035) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterc
eptor.java:974) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.
java:917) [rt.jar:1.6.0_25]
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.j
ava:312) [rt.jar:1.6.0_25]
at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:482) [rt.jar:1.6.0_25]
at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.ja
va:551) [jboss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-a
s-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:90) [jboss-as-jmx-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-m
sc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_2
5]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
was (Author: kaising):
Philippe,
I also tried build 1342 from that branche.
Same problem!
Regards,
guy
> Naming context read-only during SAR deployment
> ----------------------------------------------
>
> Key: AS7-5584
> URL: https://issues.jboss.org/browse/AS7-5584
> Project: Application Server 7
> Issue Type: Bug
> Components: POJO
> Affects Versions: 7.1.1.Final
> Reporter: Philippe Marschall
> Assignee: Philippe Marschall
> Fix For: 7.2.0.Alpha1
>
>
> During the #start() #stop() method of a legacy SAR the naming context is read only. The problem seems to be that {{org.jboss.as.service.AbstractService.invokeLifecycleMethod(Method)}} only sets the thread context class loader and does not do {{WritableServiceBasedNamingStore.pushOwner}}
> http://stackoverflow.com/questions/12419234/how-to-bind-an-object-to-jndi...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5182) properly transform/resolve expression values
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5182?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil edited comment on AS7-5182 at 12/12/12 11:16 AM:
-------------------------------------------------------------
an intermediate step would be to check if the expression provide a default value and use it.
We could check if for the pattern "${exp:default}" and use the default value for the transformation.
This is less involving than resolving the expression and would allow a greater compatibility for legacy versions that could safely failback on the default value.
was (Author: jmesnil):
an intermediate step would be to check if the expression provide a default value and use it.
We could check if for the pattern ${exp:default} and use the default value for the transformation.
This is less involving than resolving the expression and would allow a greater compatibility for legacy versions that could safely failback on the default value.
> properly transform/resolve expression values
> --------------------------------------------
>
> Key: AS7-5182
> URL: https://issues.jboss.org/browse/AS7-5182
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Priority: Optional
> Fix For: 7.3.0.Alpha1
>
>
> We need to be able to properly handle values which are getting changed to allow expressions.
> The problem is that older HCs won't understand the expression value, therefore they need be resolved before sending the initial model. At this point this can only be done against domain/host specific system properties. Server-group and server level overrides would be lost when starting a managed server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5182) properly transform/resolve expression values
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5182?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil edited comment on AS7-5182 at 12/12/12 11:17 AM:
-------------------------------------------------------------
an intermediate step would be to check if the expression provide a default value and use it.
We could check if for the pattern $\{exp:default\} and use the default value for the transformation.
This is less involving than resolving the expression and would allow a greater compatibility for legacy versions that could safely failback on the default value.
was (Author: jmesnil):
an intermediate step would be to check if the expression provide a default value and use it.
We could check if for the pattern "${exp:default}" and use the default value for the transformation.
This is less involving than resolving the expression and would allow a greater compatibility for legacy versions that could safely failback on the default value.
> properly transform/resolve expression values
> --------------------------------------------
>
> Key: AS7-5182
> URL: https://issues.jboss.org/browse/AS7-5182
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Priority: Optional
> Fix For: 7.3.0.Alpha1
>
>
> We need to be able to properly handle values which are getting changed to allow expressions.
> The problem is that older HCs won't understand the expression value, therefore they need be resolved before sending the initial model. At this point this can only be done against domain/host specific system properties. Server-group and server level overrides would be lost when starting a managed server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months
[JBoss JIRA] (AS7-5182) properly transform/resolve expression values
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5182?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil commented on AS7-5182:
----------------------------------
an intermediate step would be to check if the expression provide a default value and use it.
We could check if for the pattern ${exp:default} and use the default value for the transformation.
This is less involving than resolving the expression and would allow a greater compatibility for legacy versions that could safely failback on the default value.
> properly transform/resolve expression values
> --------------------------------------------
>
> Key: AS7-5182
> URL: https://issues.jboss.org/browse/AS7-5182
> Project: Application Server 7
> Issue Type: Sub-task
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Priority: Optional
> Fix For: 7.3.0.Alpha1
>
>
> We need to be able to properly handle values which are getting changed to allow expressions.
> The problem is that older HCs won't understand the expression value, therefore they need be resolved before sending the initial model. At this point this can only be done against domain/host specific system properties. Server-group and server level overrides would be lost when starting a managed server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 7 months