[JBoss JIRA] (AS7-6387) Improper error handling when attempting to remove a server-config with a running server
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-6387:
-------------------------------------
Summary: Improper error handling when attempting to remove a server-config with a running server
Key: AS7-6387
URL: https://issues.jboss.org/browse/AS7-6387
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP), 7.1.2.Final (EAP)
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.2.0.Alpha1
Trying to remove the config for server-one while it's still running produces an uninformative failure:
[domain@localhost:9999 /] /host=master/server-config=server-one:remove
{
"outcome" => "failed",
"result" => undefined,
"rolled-back" => true,
"server-groups" => undefined
}
An EAP 6 user reported a similar problem but with a different response:
[domain@localhost:9999 /] /host=xyz/server-config=as1:remove
{
"outcome" => "success",
"result" => {
"outcome" => "failed",
"failure-description" => "[core-service, path, server-config, system-property, jvm, interface]",
"rolled-back" => true
},
"failure-description" => undefined
}
--
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
12 years
[JBoss JIRA] (LOGMGR-57) Log files cleanup for periodic-rotating-file-handler
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-57?page=com.atlassian.jira.plugin.... ]
James Perkins moved JBLOGGING-89 to LOGMGR-57:
----------------------------------------------
Project: JBoss Log Manager (was: JBoss Logging)
Key: LOGMGR-57 (was: JBLOGGING-89)
> Log files cleanup for periodic-rotating-file-handler
> ----------------------------------------------------
>
> Key: LOGMGR-57
> URL: https://issues.jboss.org/browse/LOGMGR-57
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Razvan Popa
> Assignee: David Lloyd
> Priority: Minor
>
> Hi,
> It would be useful for the periodic-rotating-file-handler to have a "max-backup-index" attribute to allow the removal of older files like in the size-rotating-file-handler.
> It would also be nice to have something like "archive-older-than" and "delete-older-than" to also keep some older files archived for a while.
> Regards,
> Razvan
--
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
12 years
[JBoss JIRA] (AS7-6334) Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/AS7-6334?page=com.atlassian.jira.plugin.s... ]
James Perkins updated AS7-6334:
-------------------------------
Description:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner
ee
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa (OK)
jsf [PR https://github.com/jbossas/jboss-as/pull/3925]
jsr77 - nothing to do, empty subsystem
logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
mail
messaging [OK]
modcluster
naming [PR https://github.com/jbossas/jboss-as/pull/3910]
osgi (OK)
pojo - nothing to do, empty subsystem
remoting - [OK]
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts - nothing to do, susbystem model has not changed since 7.1.2 & 7.1.3
was:
Task to track the work we've all been doing on expressions/transformers.
See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
2) Basic transformation testing against 7.1.2 and 7.1.3
3) Reject-expression testing against 7.1.2 and 7.1.3
Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
Please edit this description and put an OK after the subsystem name to indicate it's good to go.
clustering/jgroups (OK)
clustering/infinispan
cmp
configadmin [OK]
connector/datasource
connector/jca [OK]
connector/resource-adapter
deployment-scanner
ee
ejb3 [OK]
jacorb - Just a note: the 'security' attribute transformation is not tested
jaxr OK
jaxrs - nothing to do, empty subsystem
jdr - nothing to do, empty subsystem
jmx (OK)
jpa (OK)
jsf [PR https://github.com/jbossas/jboss-as/pull/3925]
jsr77 - nothing to do, empty subsystem
logging
mail
messaging [OK]
modcluster
naming [PR https://github.com/jbossas/jboss-as/pull/3910]
osgi (OK)
pojo - nothing to do, empty subsystem
remoting - [OK]
sar - nothing to do, empty subsystem
security
threads
transactions (just needs AS7-6336)
web
webservices
weld - nothing to do, empty subsystem
xts - nothing to do, susbystem model has not changed since 7.1.2 & 7.1.3
> Ensure there is expression testing, basic transformation testing and reject-expression transformation testing for all subsystems
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: AS7-6334
> URL: https://issues.jboss.org/browse/AS7-6334
> Project: Application Server 7
> Issue Type: Task
> Components: Domain Management
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.2.0.Alpha1
>
>
> Task to track the work we've all been doing on expressions/transformers.
> See JaxrSubsystemTestCase for an example of what I'd like to see for each subsystem:
> 1) The standard subsystem test applied to a config that covers the full xsd with expressions added to each relevant attribute.
> 2) Basic transformation testing against 7.1.2 and 7.1.3
> 3) Reject-expression testing against 7.1.2 and 7.1.3
> Assigned to me but this is really a team effort, with a big chunk already done. Please use comments on this JIRA to indicate if you're looking at something.
> Please edit this description and put an OK after the subsystem name to indicate it's good to go.
> clustering/jgroups (OK)
> clustering/infinispan
> cmp
> configadmin [OK]
> connector/datasource
> connector/jca [OK]
> connector/resource-adapter
> deployment-scanner
> ee
> ejb3 [OK]
> jacorb - Just a note: the 'security' attribute transformation is not tested
> jaxr OK
> jaxrs - nothing to do, empty subsystem
> jdr - nothing to do, empty subsystem
> jmx (OK)
> jpa (OK)
> jsf [PR https://github.com/jbossas/jboss-as/pull/3925]
> jsr77 - nothing to do, empty subsystem
> logging - PR sent https://github.com/jbossas/jboss-as/pull/3930
> mail
> messaging [OK]
> modcluster
> naming [PR https://github.com/jbossas/jboss-as/pull/3910]
> osgi (OK)
> pojo - nothing to do, empty subsystem
> remoting - [OK]
> sar - nothing to do, empty subsystem
> security
> threads
> transactions (just needs AS7-6336)
> web
> webservices
> weld - nothing to do, empty subsystem
> xts - nothing to do, susbystem model has not changed since 7.1.2 & 7.1.3
--
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
12 years
[JBoss JIRA] (JBRULES-3708) Map-accessing constraints stop matching after they are jit-optimized
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3708?page=com.atlassian.jira.plug... ]
Mario Fusco resolved JBRULES-3708.
----------------------------------
Fix Version/s: 6.0.0.Alpha1
Resolution: Done
> Map-accessing constraints stop matching after they are jit-optimized
> --------------------------------------------------------------------
>
> Key: JBRULES-3708
> URL: https://issues.jboss.org/browse/JBRULES-3708
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.5.0.Final
> Reporter: Esteban Aliverti
> Assignee: Mario Fusco
> Labels: jit
> Fix For: 6.0.0.Alpha1
>
> Attachments: JITProblems.zip
>
>
> Having the following rules:
> declare TestObject
> data : java.util.Map //This is a Map<Parameter, Double>
> end
> rule "Rule 2"
> when
> TestObject(data[Parameter.PARAM_A] > 3)
> then
> System.out.println("Rule 2 fired!");
> end
> And repeatedly inserting a TestObject with data[PARAM_A] = 4 into a session makes the rule to stop matching.
> Maybe the title of the issue is wrong and JIT has nothing to do, but that is the only explanation I've found.
--
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
12 years
[JBoss JIRA] (JBRULES-3708) Map-accessing constraints stop matching after they are jit-optimized
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3708?page=com.atlassian.jira.plug... ]
Mario Fusco commented on JBRULES-3708:
--------------------------------------
A third (even better) workaround would be to to write the constraint like:
TestObject(data[Parameter.PARAM_A] > 3.0)
> Map-accessing constraints stop matching after they are jit-optimized
> --------------------------------------------------------------------
>
> Key: JBRULES-3708
> URL: https://issues.jboss.org/browse/JBRULES-3708
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core
> Affects Versions: 5.5.0.Final
> Reporter: Esteban Aliverti
> Assignee: Mario Fusco
> Labels: jit
> Attachments: JITProblems.zip
>
>
> Having the following rules:
> declare TestObject
> data : java.util.Map //This is a Map<Parameter, Double>
> end
> rule "Rule 2"
> when
> TestObject(data[Parameter.PARAM_A] > 3)
> then
> System.out.println("Rule 2 fired!");
> end
> And repeatedly inserting a TestObject with data[PARAM_A] = 4 into a session makes the rule to stop matching.
> Maybe the title of the issue is wrong and JIT has nothing to do, but that is the only explanation I've found.
--
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
12 years
[JBoss JIRA] (AS7-6187) NullPointerException during SAR Service deployment
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/AS7-6187?page=com.atlassian.jira.plugin.s... ]
Kabir Khan updated AS7-6187:
----------------------------
Assignee: Eduardo Martins (was: Kabir Khan)
Component/s: Naming
(was: JMX)
> NullPointerException during SAR Service deployment
> --------------------------------------------------
>
> Key: AS7-6187
> URL: https://issues.jboss.org/browse/AS7-6187
> Project: Application Server 7
> Issue Type: Bug
> Components: Naming
> Affects Versions: 7.2.0.Alpha1
> Reporter: Guy Kaisin
> Assignee: Eduardo Martins
>
> Hi all,
> Still continuing to test/verify how to use mbean...
> Here is now how I implement the bind/rebind:
> <code>
> private void rebind() throws NamingException
> {
> InitialContext rootCtx = new InitialContext();
> Name fullName = rootCtx.getNameParser("").parse(getFullJndiName());
> ServiceName servName=ServiceName.parse(getFullJndiName());
> WritableServiceBasedNamingStore.pushOwner(servName);
> try
> {
> logger.info("fullName=" + fullName+" -> rebind ...");
> org.jboss.util.naming.NonSerializableFactory.rebind(fullName, sHelper, true);
> logger.info("fullName=" + fullName+" -> rebind ok");
> }
> catch(NamingException ex)
> { ex.printStackTrace(); throw ex; }
> finally
> { WritableServiceBasedNamingStore.popOwner(); }
> }
> </code>
> Like that, I don't have the 'context is read only' issue any more.
> But I get another exception...
> 13:54:54,997 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO
> 13:54:55,012 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO -> rebind ...
> 13:54:55,013 ERROR [stderr] (MSC service thread 1-2) javax.naming.NamingException: Failed to bind [Reference Class Name:
> be.post.common.servicelocator.helper.ServiceHelper
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Type: nns
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Content: java:global/mid/be.post.mid.dao.AddressDAO
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) ] at location [service jboss.naming.context.java.global.mid."be.pos
> t.mid.dao.AddressDAO"] [Root exception is java.lang.NullPointerException]
> 13:54:55,015 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.util.NamingUtils.namingException(NamingUt
> ils.java:151)
> 13:54:55,061 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:80)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(Wr
> itableServiceBasedNamingStore.java:95)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 61)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.InitialContext.rebind(InitialContext.java
> :158)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 69)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at javax.naming.InitialContext.rebind(InitialContext.java:408)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:185)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:250)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.jav
> a:72)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.startService(JndiBind
> er.java:52)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(Servi
> ceMBeanSupport.java:250)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSuppor
> t.java:158)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(Serv
> iceMBeanSupport.java:229)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSuppo
> rt.java:154)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBea
> nSupport.java:364)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSuppor
> t.java:192)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postReg
> isterInvoke(DefaultMBeanServerInterceptor.java:1035)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rDynamicMBean(DefaultMBeanServerInterceptor.java:974)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rObject(DefaultMBeanServerInterceptor.java:917)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rMBean(DefaultMBeanServerInterceptor.java:312)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBean
> Server.java:482)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.reg
> isterMBean(PluggableMBeanServerImpl.java:551)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(Plugg
> ableMBeanServerImpl.java:319)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistra
> tionService.java:90)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startSe
> rvice(ServiceControllerImpl.java:1811)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(Ser
> viceControllerImpl.java:1746)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread
> PoolExecutor.java:886)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
> Executor.java:908)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.lang.Thread.run(Thread.java:662)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) Caused by: java.lang.NullPointerException
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:77)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) ... 28 more
> 13:54:55,076 WARN [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) Starting failed mid.services.da
> o:service=AddressDAOMBean: javax.naming.NamingException: Failed to bind [Reference Class Name: be.post.common.serviceloc
> ator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> at org.jboss.as.naming.util.NamingUtils.namingException(NamingUtils.java:151)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:80)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:95)
> 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:72)
> at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:52)
> 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(DefaultMBeanServerInterceptor.java:1
> 035) [rt.jar:1.6.0_25]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.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.java: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.java:551) [j
> boss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-as-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-ms
> c-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.G
> A.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
> 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]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:77)
> ... 28 more
> 13:54:55,087 ERROR [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) javax.naming.NamingException: F
> ailed to bind [Reference Class Name: be.post.common.servicelocator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> I use a jboss-service.xml file, containing the following:
> <mbean name="mid.services.dao:service=AddressDAOMBean"
> code="be.post.common.servicebinder.DaoJndiBinder">
> <attribute name="JndiName">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="DataSourceJndiName">java:MIDCoreOracleDS</attribute>
> <attribute name="InterfaceClass">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="ImplementationClass">be.post.mid.dao.oracle.AddressOracle</attribute>
> </mbean>
> I could identify the line giving the exception:
> // add the service name to runtime bindings management service, which on stop releases the services.
> final Set<ServiceName> duBindingReferences = (Set<ServiceName> getServiceRegistry().getService(JndiNamingDependencyProcessor.serviceName(deploymentUnitServiceName)).getValue();
> But what is the root cause of it?
> any suggestion?
> thanks a lot...
--
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
12 years
[JBoss JIRA] (AS7-6187) NullPointerException during SAR Service deployment
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/AS7-6187?page=com.atlassian.jira.plugin.s... ]
Tomaz Cerar commented on AS7-6187:
----------------------------------
can you provide simple deployment to reproduce this?
otherwise contribution in form of git pull request is always welcome.
> NullPointerException during SAR Service deployment
> --------------------------------------------------
>
> Key: AS7-6187
> URL: https://issues.jboss.org/browse/AS7-6187
> Project: Application Server 7
> Issue Type: Bug
> Components: Naming
> Affects Versions: 7.2.0.Alpha1
> Reporter: Guy Kaisin
> Assignee: Eduardo Martins
>
> Hi all,
> Still continuing to test/verify how to use mbean...
> Here is now how I implement the bind/rebind:
> <code>
> private void rebind() throws NamingException
> {
> InitialContext rootCtx = new InitialContext();
> Name fullName = rootCtx.getNameParser("").parse(getFullJndiName());
> ServiceName servName=ServiceName.parse(getFullJndiName());
> WritableServiceBasedNamingStore.pushOwner(servName);
> try
> {
> logger.info("fullName=" + fullName+" -> rebind ...");
> org.jboss.util.naming.NonSerializableFactory.rebind(fullName, sHelper, true);
> logger.info("fullName=" + fullName+" -> rebind ok");
> }
> catch(NamingException ex)
> { ex.printStackTrace(); throw ex; }
> finally
> { WritableServiceBasedNamingStore.popOwner(); }
> }
> </code>
> Like that, I don't have the 'context is read only' issue any more.
> But I get another exception...
> 13:54:54,997 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO
> 13:54:55,012 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO -> rebind ...
> 13:54:55,013 ERROR [stderr] (MSC service thread 1-2) javax.naming.NamingException: Failed to bind [Reference Class Name:
> be.post.common.servicelocator.helper.ServiceHelper
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Type: nns
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Content: java:global/mid/be.post.mid.dao.AddressDAO
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) ] at location [service jboss.naming.context.java.global.mid."be.pos
> t.mid.dao.AddressDAO"] [Root exception is java.lang.NullPointerException]
> 13:54:55,015 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.util.NamingUtils.namingException(NamingUt
> ils.java:151)
> 13:54:55,061 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:80)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(Wr
> itableServiceBasedNamingStore.java:95)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 61)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.InitialContext.rebind(InitialContext.java
> :158)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 69)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at javax.naming.InitialContext.rebind(InitialContext.java:408)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:185)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:250)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.jav
> a:72)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.startService(JndiBind
> er.java:52)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(Servi
> ceMBeanSupport.java:250)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSuppor
> t.java:158)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(Serv
> iceMBeanSupport.java:229)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSuppo
> rt.java:154)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBea
> nSupport.java:364)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSuppor
> t.java:192)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postReg
> isterInvoke(DefaultMBeanServerInterceptor.java:1035)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rDynamicMBean(DefaultMBeanServerInterceptor.java:974)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rObject(DefaultMBeanServerInterceptor.java:917)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rMBean(DefaultMBeanServerInterceptor.java:312)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBean
> Server.java:482)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.reg
> isterMBean(PluggableMBeanServerImpl.java:551)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(Plugg
> ableMBeanServerImpl.java:319)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistra
> tionService.java:90)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startSe
> rvice(ServiceControllerImpl.java:1811)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(Ser
> viceControllerImpl.java:1746)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread
> PoolExecutor.java:886)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
> Executor.java:908)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.lang.Thread.run(Thread.java:662)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) Caused by: java.lang.NullPointerException
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:77)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) ... 28 more
> 13:54:55,076 WARN [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) Starting failed mid.services.da
> o:service=AddressDAOMBean: javax.naming.NamingException: Failed to bind [Reference Class Name: be.post.common.serviceloc
> ator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> at org.jboss.as.naming.util.NamingUtils.namingException(NamingUtils.java:151)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:80)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:95)
> 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:72)
> at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:52)
> 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(DefaultMBeanServerInterceptor.java:1
> 035) [rt.jar:1.6.0_25]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.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.java: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.java:551) [j
> boss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-as-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-ms
> c-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.G
> A.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
> 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]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:77)
> ... 28 more
> 13:54:55,087 ERROR [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) javax.naming.NamingException: F
> ailed to bind [Reference Class Name: be.post.common.servicelocator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> I use a jboss-service.xml file, containing the following:
> <mbean name="mid.services.dao:service=AddressDAOMBean"
> code="be.post.common.servicebinder.DaoJndiBinder">
> <attribute name="JndiName">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="DataSourceJndiName">java:MIDCoreOracleDS</attribute>
> <attribute name="InterfaceClass">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="ImplementationClass">be.post.mid.dao.oracle.AddressOracle</attribute>
> </mbean>
> I could identify the line giving the exception:
> // add the service name to runtime bindings management service, which on stop releases the services.
> final Set<ServiceName> duBindingReferences = (Set<ServiceName> getServiceRegistry().getService(JndiNamingDependencyProcessor.serviceName(deploymentUnitServiceName)).getValue();
> But what is the root cause of it?
> any suggestion?
> thanks a lot...
--
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
12 years
[JBoss JIRA] (AS7-6187) NullPointerException during SAR Service deployment
by Guy Kaisin (JIRA)
[ https://issues.jboss.org/browse/AS7-6187?page=com.atlassian.jira.plugin.s... ]
Guy Kaisin commented on AS7-6187:
---------------------------------
Hi all,
Seems there is NO activity on resolving this issue...
G.
> NullPointerException during SAR Service deployment
> --------------------------------------------------
>
> Key: AS7-6187
> URL: https://issues.jboss.org/browse/AS7-6187
> Project: Application Server 7
> Issue Type: Bug
> Components: JMX
> Affects Versions: 7.2.0.Alpha1
> Reporter: Guy Kaisin
> Assignee: Kabir Khan
>
> Hi all,
> Still continuing to test/verify how to use mbean...
> Here is now how I implement the bind/rebind:
> <code>
> private void rebind() throws NamingException
> {
> InitialContext rootCtx = new InitialContext();
> Name fullName = rootCtx.getNameParser("").parse(getFullJndiName());
> ServiceName servName=ServiceName.parse(getFullJndiName());
> WritableServiceBasedNamingStore.pushOwner(servName);
> try
> {
> logger.info("fullName=" + fullName+" -> rebind ...");
> org.jboss.util.naming.NonSerializableFactory.rebind(fullName, sHelper, true);
> logger.info("fullName=" + fullName+" -> rebind ok");
> }
> catch(NamingException ex)
> { ex.printStackTrace(); throw ex; }
> finally
> { WritableServiceBasedNamingStore.popOwner(); }
> }
> </code>
> Like that, I don't have the 'context is read only' issue any more.
> But I get another exception...
> 13:54:54,997 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO
> 13:54:55,012 INFO [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) fullName=java:global/mid/be.pos
> t.mid.dao.AddressDAO -> rebind ...
> 13:54:55,013 ERROR [stderr] (MSC service thread 1-2) javax.naming.NamingException: Failed to bind [Reference Class Name:
> be.post.common.servicelocator.helper.ServiceHelper
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Type: nns
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) Content: java:global/mid/be.post.mid.dao.AddressDAO
> 13:54:55,014 ERROR [stderr] (MSC service thread 1-2) ] at location [service jboss.naming.context.java.global.mid."be.pos
> t.mid.dao.AddressDAO"] [Root exception is java.lang.NullPointerException]
> 13:54:55,015 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.util.NamingUtils.namingException(NamingUt
> ils.java:151)
> 13:54:55,061 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:80)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(Wr
> itableServiceBasedNamingStore.java:95)
> 13:54:55,066 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 61)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.InitialContext.rebind(InitialContext.java
> :158)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.NamingContext.rebind(NamingContext.java:2
> 69)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at javax.naming.InitialContext.rebind(InitialContext.java:408)
> 13:54:55,067 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:185)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at org.jboss.util.naming.NonSerializableFactory.rebind(NonSerial
> izableFactory.java:250)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.rebind(JndiBinder.jav
> a:72)
> 13:54:55,068 ERROR [stderr] (MSC service thread 1-2) at be.post.common.servicebinder.JndiBinder.startService(JndiBind
> er.java:52)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(Servi
> ceMBeanSupport.java:250)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSuppor
> t.java:158)
> 13:54:55,069 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(Serv
> iceMBeanSupport.java:229)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSuppo
> rt.java:154)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBea
> nSupport.java:364)
> 13:54:55,070 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.MBeanSupport.postRegister(MBeanSuppor
> t.java:192)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postReg
> isterInvoke(DefaultMBeanServerInterceptor.java:1035)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rDynamicMBean(DefaultMBeanServerInterceptor.java:974)
> 13:54:55,071 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rObject(DefaultMBeanServerInterceptor.java:917)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registe
> rMBean(DefaultMBeanServerInterceptor.java:312)
> 13:54:55,072 ERROR [stderr] (MSC service thread 1-2) at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBean
> Server.java:482)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.reg
> isterMBean(PluggableMBeanServerImpl.java:551)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(Plugg
> ableMBeanServerImpl.java:319)
> 13:54:55,073 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistra
> tionService.java:90)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startSe
> rvice(ServiceControllerImpl.java:1811)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(Ser
> viceControllerImpl.java:1746)
> 13:54:55,074 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread
> PoolExecutor.java:886)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool
> Executor.java:908)
> 13:54:55,075 ERROR [stderr] (MSC service thread 1-2) at java.lang.Thread.run(Thread.java:662)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) Caused by: java.lang.NullPointerException
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(Writ
> ableServiceBasedNamingStore.java:77)
> 13:54:55,076 ERROR [stderr] (MSC service thread 1-2) ... 28 more
> 13:54:55,076 WARN [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) Starting failed mid.services.da
> o:service=AddressDAOMBean: javax.naming.NamingException: Failed to bind [Reference Class Name: be.post.common.serviceloc
> ator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> at org.jboss.as.naming.util.NamingUtils.namingException(NamingUtils.java:151)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:80)
> at org.jboss.as.naming.WritableServiceBasedNamingStore.rebind(WritableServiceBasedNamingStore.java:95)
> 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:72)
> at be.post.common.servicebinder.JndiBinder.startService(JndiBinder.java:52)
> 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(DefaultMBeanServerInterceptor.java:1
> 035) [rt.jar:1.6.0_25]
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.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.java: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.java:551) [j
> boss-as-jmx-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
> at org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:319) [jboss-as-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-ms
> c-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.G
> A.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
> 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]
> Caused by: java.lang.NullPointerException
> at org.jboss.as.naming.WritableServiceBasedNamingStore.bind(WritableServiceBasedNamingStore.java:77)
> ... 28 more
> 13:54:55,087 ERROR [be.post.common.servicebinder.DaoJndiBinder] (MSC service thread 1-2) javax.naming.NamingException: F
> ailed to bind [Reference Class Name: be.post.common.servicelocator.helper.ServiceHelper
> Type: nns
> Content: java:global/mid/be.post.mid.dao.AddressDAO
> ] at location [service jboss.naming.context.java.global.mid."be.post.mid.dao.AddressDAO"] [Root exception is java.lang.N
> ullPointerException]
> I use a jboss-service.xml file, containing the following:
> <mbean name="mid.services.dao:service=AddressDAOMBean"
> code="be.post.common.servicebinder.DaoJndiBinder">
> <attribute name="JndiName">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="DataSourceJndiName">java:MIDCoreOracleDS</attribute>
> <attribute name="InterfaceClass">be.post.mid.dao.AddressDAO</attribute>
> <attribute name="ImplementationClass">be.post.mid.dao.oracle.AddressOracle</attribute>
> </mbean>
> I could identify the line giving the exception:
> // add the service name to runtime bindings management service, which on stop releases the services.
> final Set<ServiceName> duBindingReferences = (Set<ServiceName> getServiceRegistry().getService(JndiNamingDependencyProcessor.serviceName(deploymentUnitServiceName)).getValue();
> But what is the root cause of it?
> any suggestion?
> thanks a lot...
--
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
12 years
[JBoss JIRA] (DROOLS-18) [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
by Michiel Vermandel (JIRA)
[ https://issues.jboss.org/browse/DROOLS-18?page=com.atlassian.jira.plugin.... ]
Michiel Vermandel commented on DROOLS-18:
-----------------------------------------
I'll send you my current version of the project, like I did the previous time.
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-18
> URL: https://issues.jboss.org/browse/DROOLS-18
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Windows 7 64Bit
> Java 1.7.0
> Drools-core 5.5.0.Final
> Drools-compiler 5.5.0.Final
> Mvel2 2.1.3.Final
> Reporter: Michiel Vermandel
> Assignee: Mario Fusco
> Priority: Critical
>
> In about one out of ten JUnit runs, I get a crash with stack trace.
> The process terminates immediately.
> Unit test output is 100% the same on successful runs.
> Stack trace:
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> [Near : {... this == lead ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.ast.BinaryOperation.<init>(BinaryOperation.java:84)
> at org.mvel2.util.CompilerTools.finalizePayload(CompilerTools.java:118)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:287)
> at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62)
> at org.mvel2.MVEL.compileExpression(MVEL.java:810)
> at org.drools.base.mvel.MVELCompilationUnit.compile(MVELCompilationUnit.java:435)
> at org.drools.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:238)
> at org.drools.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:206)
> at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:190)
> at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:157)
> at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:137)
> at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:497)
> at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:382)
> at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:235)
> at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:240)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:350)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:311)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:903)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847)
> at org.drools.planner.core.score.director.drools.DroolsScoreDirector.afterEntityAdded(DroolsScoreDirector.java:103)
> at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.moveIterator(PlanningVariableWalker.java:145)
> at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:74)
> at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:65)
> at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:190)
> at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:155)
> at be.axi.planner.app.InspectionSchedule.solve(InspectionSchedule.java:192)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:288)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:298)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:315)
> at be.axi.planner.TaskGroupingTest.communitySuccess02(TaskGroupingTest.java:289)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
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
12 years
[JBoss JIRA] (DROOLS-18) [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-18?page=com.atlassian.jira.plugin.... ]
Mario Fusco commented on DROOLS-18:
-----------------------------------
This second bug is not related with jitting and then neither with the other bug you reported.
Reading the exception probably I know the cause and if I am right it has been already fixed on the master.
Anyway I'd need a reproducer to check it by myself.
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> ---------------------------------------------------------------------------------------------------
>
> Key: DROOLS-18
> URL: https://issues.jboss.org/browse/DROOLS-18
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: Windows 7 64Bit
> Java 1.7.0
> Drools-core 5.5.0.Final
> Drools-compiler 5.5.0.Final
> Mvel2 2.1.3.Final
> Reporter: Michiel Vermandel
> Assignee: Mario Fusco
> Priority: Critical
>
> In about one out of ten JUnit runs, I get a crash with stack trace.
> The process terminates immediately.
> Unit test output is 100% the same on successful runs.
> Stack trace:
> [Error: incompatible types in statement: boolean (compared from: class be.axi.planner.domain.Task)]
> [Near : {... this == lead ....}]
> ^
> [Line: 1, Column: 1]
> at org.mvel2.ast.BinaryOperation.<init>(BinaryOperation.java:84)
> at org.mvel2.util.CompilerTools.finalizePayload(CompilerTools.java:118)
> at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:287)
> at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:62)
> at org.mvel2.MVEL.compileExpression(MVEL.java:810)
> at org.drools.base.mvel.MVELCompilationUnit.compile(MVELCompilationUnit.java:435)
> at org.drools.base.mvel.MVELCompilationUnit.getCompiledExpression(MVELCompilationUnit.java:238)
> at org.drools.rule.constraint.MvelConstraint.createMvelConditionEvaluator(MvelConstraint.java:206)
> at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:190)
> at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:157)
> at org.drools.reteoo.AlphaNode.assertObject(AlphaNode.java:137)
> at org.drools.reteoo.CompositeObjectSinkAdapter.doPropagateAssertObject(CompositeObjectSinkAdapter.java:497)
> at org.drools.reteoo.CompositeObjectSinkAdapter.propagateAssertObject(CompositeObjectSinkAdapter.java:382)
> at org.drools.reteoo.ObjectTypeNode.assertObject(ObjectTypeNode.java:235)
> at org.drools.reteoo.EntryPointNode.assertObject(EntryPointNode.java:240)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:350)
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:311)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:903)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:847)
> at org.drools.planner.core.score.director.drools.DroolsScoreDirector.afterEntityAdded(DroolsScoreDirector.java:103)
> at org.drools.planner.core.heuristic.selector.variable.PlanningVariableWalker.moveIterator(PlanningVariableWalker.java:145)
> at org.drools.planner.core.constructionheuristic.greedyFit.decider.DefaultGreedyDecider.decideNextStep(DefaultGreedyDecider.java:74)
> at org.drools.planner.core.constructionheuristic.greedyFit.DefaultGreedyFitSolverPhase.solve(DefaultGreedyFitSolverPhase.java:65)
> at org.drools.planner.core.solver.DefaultSolver.runSolverPhases(DefaultSolver.java:190)
> at org.drools.planner.core.solver.DefaultSolver.solve(DefaultSolver.java:155)
> at be.axi.planner.app.InspectionSchedule.solve(InspectionSchedule.java:192)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:288)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:298)
> at be.axi.planner.testcore.AbstractPlanningTestClass.solve(AbstractPlanningTestClass.java:315)
> at be.axi.planner.TaskGroupingTest.communitySuccess02(TaskGroupingTest.java:289)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
> at org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
--
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
12 years