April 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2104) KnowledgeAgentImpl cannot build Resources with paramatereised ResourceConfiguration's

by Graham Gear (JIRA)

KnowledgeAgentImpl cannot build Resources with paramatereised ResourceConfiguration's ------------------------------------------------------------------------------------- Key: JBRULES-2104 URL: https://jira.jboss.org/jira/browse/JBRULES-2104 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Graham Gear Assignee: Mark Proctor The KnowledgeAgentImpl does not pass through ResourceConfiguration's through to KnowledgeBuilderImpl, making the building of configuration parametrised Resources not possible. Eg, trying to compile a DecisionTable (XLS) results in a NPE: Caused by: java.lang.NullPointerException at org.drools.decisiontable.DecisionTableProviderImpl.compileStream(DecisionTableProviderImpl.java:26) at org.drools.decisiontable.DecisionTableProviderImpl.loadFromInputStream(DecisionTableProviderImpl.java:19) at org.drools.compiler.DecisionTableFactory.loadFromInputStream(DecisionTableFactory.java:16) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:508) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:25) at org.drools.agent.impl.KnowledgeAgentImpl.rebuildResources(KnowledgeAgentImpl.java:385) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:119) at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:108) at com.jboss.brms.poc.KnowledgeBaseManager.loadChangeSet(KnowledgeBaseManager.java:78) at com.jboss.brms.poc.test.rule.DecisionTableBRLClassPathRuleTest.<clinit>(DecisionTableBRLClassPathRuleTest.java:18) ... 17 more In general it would be good if the KnowledgeAgent would behave exactly as the KnowledgeBuilder under the same ChangeSet configuration. -- 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

14 years, 9 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-7828) Create a JSR-160 connecter service with a dedicated deployment descriptor type

by David Lloyd (JIRA)

Create a JSR-160 connecter service with a dedicated deployment descriptor type ------------------------------------------------------------------------------ Key: JBAS-7828 URL: https://jira.jboss.org/jira/browse/JBAS-7828 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JMX Reporter: David Lloyd Fix For: JBossAS-6.0.0.M4 -- 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

14 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JASSIST-97) Javassist doesn't serialize the handler along with the proxy

by Pete Muir (JIRA)

Javassist doesn't serialize the handler along with the proxy ------------------------------------------------------------ Key: JASSIST-97 URL: https://jira.jboss.org/jira/browse/JASSIST-97 Project: Javassist Issue Type: Feature Request Reporter: Pete Muir Assignee: Shigeru Chiba When serializing a proxy, Javassist doesn't consider serializing the instance handler, but only the default handler. -- 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

14 years, 9 months

6
14
0 / 0

[JBoss JIRA] Created: (JBAS-7092) Server fails to deploy war files in ear.

by Michal Rorat (JIRA)

Server fails to deploy war files in ear. ---------------------------------------- Key: JBAS-7092 URL: https://jira.jboss.org/jira/browse/JBAS-7092 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployers Affects Versions: JBossAS-4.2.3.GA Environment: Windows XP 32 bit Windows 2003 Server Reporter: Michal Rorat Assignee: Ales Justin I have an ear file which contains ejbs and wars. It started to fail when I added sars. The problem is, it doesn't matter what wars I'm deploying, its always the second one and nothing gets deployed after this exception. aplication.xml file: <?xml version="1.0" encoding="UTF-8"?> <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:application="http://java.sun.com/xml/ns/javaee/application_5.xsd" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" id="Application_ID" version="5"> <module> <java>OracleQueue.sar</java> </module> <module> <java>SONController.sar</java> </module> <module> <ejb>Admin.jar</ejb> </module> <module> <ejb>Settings.jar</ejb> </module> <module> <ejb>Layer3Msg.jar</ejb> </module> <module> <java>Layer3MsgLoader.sar</java> </module> <module> <ejb>Layer3MsgMdb.jar</ejb> </module> <module> <ejb>Common.jar</ejb> </module> <module> <ejb>Attributes.jar</ejb> </module> <module> <ejb>Data.jar</ejb> </module> <module> <ejb>Model.jar</ejb> </module> <module> <ejb>Users.jar</ejb> </module> <module> <ejb>Tasks.jar</ejb> </module> <module> <ejb>Survey.jar</ejb> </module> <module> <ejb>BenchmarkQpis.jar</ejb> </module> <module> <ejb>Cellrefutils.jar</ejb> </module> <module> <ejb>ConfigChanges.jar</ejb> </module> <module> <ejb>Engine.jar</ejb> </module> <module> <ejb>Events.jar</ejb> </module> <module> <ejb>QueryDefs.jar</ejb> </module> <module> <ejb>QueryData.jar</ejb> </module> <module> <ejb>GeoTagging.jar</ejb> </module> <module> <ejb>Kpievents.jar</ejb> </module> <module> <ejb>Modules.jar</ejb> </module> <module> <ejb>Network.jar</ejb> </module> <module> <ejb>Qpis.jar</ejb> </module> <module> <ejb>RadioNetworkAnalysis.jar</ejb> </module> <module> <ejb>VirtualEarth.jar</ejb> </module> <module> <ejb>WMS.jar</ejb> </module> <module> <ejb>ReportData.jar</ejb> </module> <module> <ejb>ReportsMetadata.jar</ejb> </module> <module> <ejb>ReportProducer.jar</ejb> </module> <module> <web> <web-uri>Quorre.war</web-uri> <context-root>ActixOne/Quorre</context-root> </web> </module> <module> <web> <web-uri>TestWar.war</web-uri> <context-root>TestWar</context-root> </web> </module> <module> <web> <web-uri>Download.war</web-uri> <context-root>ActixOne/Download</context-root> </web> </module> </application> Exception: 2009-07-10 12:28:30,687 INFO [org.jboss.ejb3.EJB3Deployer] Deployed: file:/C:/jboss-4.2/server/default/tmp/deploy/tmp4660403835223254272ActixOne.ear-contents/ReportProducer.jar 2009-07-10 12:28:30,687 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/ActixOne/Quorre, warUrl=.../tmp/deploy/tmp4660403835223254272ActixOne.ear-contents/Quorre-exp.war/ 2009-07-10 12:28:30,875 INFO [org.rhq.helpers.rtfilter.filter.RtFilter] Initialized response-time filter for webapp with context root 'ActixOne/Quorre'. 2009-07-10 12:28:31,687 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/TestWar, warUrl=.../tmp/deploy/tmp4660403835223254272ActixOne.ear-contents/TestWar-exp.war/ 2009-07-10 12:28:31,687 WARN [org.jboss.system.ServiceController] Problem starting service jboss.web.deployment:war=TestWar.war,id=2043149425 org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:384) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy45.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Unknown Source) Caused by: javax.naming.NameAlreadyBoundException at org.jnp.server.NamingServer.bind(NamingServer.java:144) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:591) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:552) at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:495) at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:878) at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:159) at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375) ... 112 more 2009-07-10 12:28:31,718 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/C:/jboss-4.2/server/default/tmp/deploy/tmp4660403835223254272ActixOne.ear-contents/TestWar.war org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:384) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy45.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.GeneratedMethodAccessor85.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:87) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy46.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:304) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) 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.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Unknown Source) Caused by: javax.naming.NameAlreadyBoundException at org.jnp.server.NamingServer.bind(NamingServer.java:144) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:591) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:552) at org.jboss.web.AbstractWebDeployer.parseWebAppDescriptors(AbstractWebDeployer.java:495) at org.jboss.web.AbstractWebDeployer$DescriptorParser.parseWebAppDescriptors(AbstractWebDeployer.java:878) at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(TomcatDeployer.java:159) at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeployer.java:104) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375) ... 112 more 2009-07-10 12:28:31,718 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@11dba24c { url=file:/C:/jboss-4.2/server/default/deploy/ActixOne.ear } deployer: org.jboss.deployment.EARDeployer@7981d5 status: Deployment FAILED reason: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException) state: FAILED watch: file:/C:/jboss-4.2/server/default/deploy/ActixOne.ear altDD: null lastDeployed: 1247225246750 lastModified: 1247225222906 mbeans: jboss.j2ee:ear=ActixOne.ear,jar=Admin.jar,name=Admin,service=EJB3 state: Started persistence.units:ear=ActixOne.ear,jar=Settings.jar,unitName=SettingsStorage state: Started jboss.j2ee:ear=ActixOne.ear,jar=Settings.jar,name=Settings,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Layer3Msg.jar,name=Layer3Msg,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Layer3MsgMdb.jar,name=ReportProducerMDB,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Common.jar,name=Common,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Attributes.jar,name=Attributes,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Data.jar,name=Data,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Model.jar,name=Model,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Users.jar,name=Users,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Tasks.jar,name=Tasks,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Survey.jar,name=Survey,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=BenchmarkQpis.jar,name=Benchmarkqpis,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Cellrefutils.jar,name=Cellrefutils,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=ConfigChanges.jar,name=Configchanges,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Engine.jar,name=Engine,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Events.jar,name=Events,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=QueryDefs.jar,name=QueryDefs,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=QueryData.jar,name=QueryData,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=GeoTagging.jar,name=Geotagging,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Kpievents.jar,name=Kpievents,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Modules.jar,name=Modules,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Network.jar,name=Network,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=Qpis.jar,name=Qpis,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=RadioNetworkAnalysis.jar,name=RadioNetworkAnalysis,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=VirtualEarth.jar,name=VirtualEarth,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=WMS.jar,name=Wms,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=ReportData.jar,name=ReportData,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=ReportsMetadata.jar,name=ReportsMetadata,service=EJB3 state: Started jboss.j2ee:ear=ActixOne.ear,jar=ReportProducer.jar,name=ReportProducerMDB,service=EJB3 state: Started --- MBeans waiting for other MBeans --- ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo State: CONFIGURED I Depend On: jboss:service=TransactionManager jboss.jca:service=DataSourceBinding,name=DefaultDS ObjectName: jboss.cache:service=InvalidationBridge,type=JavaGroups State: CONFIGURED I Depend On: jboss:service=DefaultPartition jboss.cache:service=InvalidationManager ObjectName: jboss.mq:service=InvocationLayer,type=HTTP State: CONFIGURED I Depend On: jboss.mq:service=Invoker jboss.web:service=WebServer ObjectName: jboss.mq:service=StateManager State: CONFIGURED I Depend On: jboss.jca:service=DataSourceBinding,name=DefaultDS Depends On Me: jboss.mq:service=DestinationManager ObjectName: jboss.mq:service=DestinationManager State: CONFIGURED I Depend On: jboss.mq:service=MessageCache jboss.mq:service=PersistenceManager jboss.mq:service=StateManager jboss.mq:service=ThreadPool jboss:service=Naming Depends On Me: jboss.mq.destination:service=Topic,name=testTopic jboss.mq.destination:service=Topic,name=securedTopic jboss.mq.destination:service=Topic,name=testDurableTopic jboss.mq.destination:service=Queue,name=testQueue jboss.mq.destination:service=Queue,name=A jboss.mq.destination:service=Queue,name=B jboss.mq.destination:service=Queue,name=C jboss.mq.destination:service=Queue,name=D jboss.mq.destination:service=Queue,name=ex jboss.mq:service=SecurityManager jboss.mq.destination:service=Queue,name=DLQ ObjectName: jboss.mq:service=PersistenceManager State: CONFIGURED I Depend On: jboss.jca:service=DataSourceBinding,name=DefaultDS Depends On Me: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Topic,name=testTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Topic,name=securedTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Queue,name=testQueue State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq.destination:service=Queue,name=A State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=B State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=C State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=D State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq.destination:service=Queue,name=ex State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager ObjectName: jboss.mq:service=Invoker State: CONFIGURED I Depend On: jboss.mq:service=TracingInterceptor jboss:service=Naming Depends On Me: jboss.mq:service=InvocationLayer,type=HTTP jboss.mq:service=InvocationLayer,type=JVM jboss.mq:service=InvocationLayer,type=UIL2 ObjectName: jboss.mq:service=TracingInterceptor State: CONFIGURED I Depend On: jboss.mq:service=SecurityManager Depends On Me: jboss.mq:service=Invoker ObjectName: jboss.mq:service=SecurityManager State: CONFIGURED I Depend On: jboss.security:service=JaasSecurityManager jboss.mq:service=DestinationManager Depends On Me: jboss.mq.destination:service=Topic,name=testTopic jboss.mq.destination:service=Topic,name=securedTopic jboss.mq.destination:service=Topic,name=testDurableTopic jboss.mq.destination:service=Queue,name=testQueue jboss.mq:service=TracingInterceptor jboss.mq.destination:service=Queue,name=DLQ ObjectName: jboss.mq.destination:service=Queue,name=DLQ State: CONFIGURED I Depend On: jboss.mq:service=DestinationManager jboss.mq:service=SecurityManager ObjectName: jboss.mq:service=InvocationLayer,type=JVM State: CONFIGURED I Depend On: jboss.mq:service=Invoker ObjectName: jboss.mq:service=InvocationLayer,type=UIL2 State: CONFIGURED I Depend On: jboss.mq:service=Invoker ObjectName: jboss.web.deployment:war=TestWar.war,id=2043149425 State: FAILED Reason: org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException) --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.web.deployment:war=TestWar.war,id=2043149425 State: FAILED Reason: org.jboss.deployment.DeploymentException: Error during deploy; - nested throwable: (javax.naming.NameAlreadyBoundException) ObjectName: jboss.cache:service=InvalidationManager State: NOTYETINSTALLED Depends On Me: jboss.cache:service=InvalidationBridge,type=JavaGroups ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS State: NOTYETINSTALLED Depends On Me: jboss:service=KeyGeneratorFactory,type=HiLo jboss.mq:service=StateManager jboss.mq:service=PersistenceManager ********************************************************************* I found out that I'm not the only one with problem like that: http://www.techienuggets.com/Detail?tx=27457 Regards, Michal Rorat -- 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

14 years, 9 months

5
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1137) ClusterChooserInterceptor does not support transaction failover authorisations

by Galder Zamarreno (JIRA)

ClusterChooserInterceptor does not support transaction failover authorisations ------------------------------------------------------------------------------ Key: EJBTHREE-1137 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1137 Project: EJB 3.0 Issue Type: Bug Components: Clustering Affects Versions: AS 4.2.2.GA, AS 5.0.0.Beta3 Reporter: Galder Zamarreno org.jboss.aspects.remoting.ClusterChooserInterceptor does not contain logic to deal with transaction failover authorisations, contrary to legacy JRMP invoker or Unified invoker. The reason I'm entering this as a bug rather than as a feature request is because not having such logic is allowing failovers when they shouldn't happen. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1141) LoadBalancePolicy that tries to pin all requests associated with a tx to one server

by Galder Zamarreno (JIRA)

LoadBalancePolicy that tries to pin all requests associated with a tx to one server ----------------------------------------------------------------------------------- Key: EJBTHREE-1141 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1141 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Create EJB3 transaction sticky load balance policies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBCOMMON-102) Release jboss-common-core 2.2.18

by Dimitris Andreadis (JIRA)

Release jboss-common-core 2.2.18 -------------------------------- Key: JBCOMMON-102 URL: https://jira.jboss.org/jira/browse/JBCOMMON-102 Project: JBoss Common Issue Type: Release Security Level: Public (Everyone can see) Components: common-core (2.x) Reporter: Dimitris Andreadis Assignee: Dimitris Andreadis Fix For: 2.2.18.GA -- 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

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4514) CLONE -Deadlock when logging trace

by chris effenberger (JIRA)

CLONE -Deadlock when logging trace ---------------------------------- Key: JBAS-4514 URL: http://jira.jboss.com/jira/browse/JBAS-4514 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: chris effenberger Assigned To: Scott M Stark SourceForge Submitter: genman . This was caused when trace was enabled. I imagine it was caused by the classloader trying to load a class while it was being rendered (?) to disk. Probably not a big issue, unless trace-logging is enabled. Java stack information for the threads listed above: =================================================== "SMPP-TIMER-0": at com.logica.smpp.util.ByteBuffer.getHexDump(ByteBuffer.java:379) at com.logica.smpp.util.ByteBuffer.toString(ByteBuffer.java:387) at org.apache.log4j.or.DefaultRenderer.doRender(DefaultRenderer.java:26) at org.apache.log4j.or.RendererMap.findAndRender(RendererMap.java:70) at org.apache.log4j.spi.LoggingEvent.getRenderedMessage(LoggingEvent.java:288) at org.apache.log4j.helpers.PatternParser$BasicPatternConverter.convert(PatternParser.java:395) at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:56) at org.apache.log4j.PatternLayout.format(PatternLayout.java:495) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:292) at org.apache.log4j.WriterAppender.append(WriterAppender.java:150) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:221) - locked <0x473874c8> (a org.apache.log4j.ConsoleAppender) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:57) at org.apache.log4j.Category.callAppenders(Category.java:187) - locked <0x46829180> (a org.apache.log4j.spi.RootCategory) at org.apache.log4j.Category.forcedLog(Category.java:372) at org.apache.log4j.Category.debug(Category.java:241) at com.logica.smpp.debug.Log4JDebug.write(Log4JDebug.java:79) at com.logica.smpp.TCPIPConnection.send(TCPIPConnection.java:301) at com.logica.smpp.Transmitter.send(Transmitter.java:81) at com.logica.smpp.Session.send(Session.java:983) at com.logica.smpp.Session.bind(Session.java:452) at ... "SMSC-Accept-16910": at org.apache.log4j.Category.callAppenders(Category.java:185) - waiting to lock <0x46829180> (a org.apache.log4j.spi.RootCategory) at org.apache.log4j.Category.forcedLog(Category.java:372) at org.apache.log4j.Category.log(Category.java:864) at org.jboss.logging.Log4jLoggerPlugin.trace(Log4jLoggerPlugin.java:96) at org.jboss.logging.Logger.trace(Logger.java:113) at org.jboss.mx.loading.UnifiedClassLoader3.attempt(UnifiedClassLoader3.java:242) at org.jboss.mx.loading.UnifiedClassLoader3.loadClass(UnifiedClassLoader3.java:126) - locked <0x472e2f38> (a org.jboss.mx.loading.UnifiedClassLoader3) at java.lang.ClassLoader.loadClass(ClassLoader.java:255) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315) - locked <0x472e2f38> (a org.jboss.mx.loading.UnifiedClassLoader3) at com.proteusmobile.smsgw.server.ServerService.listen(ServerService.java:187) at com.proteusmobile.smsgw.server.ServerService.access$3(ServerService.java:46) at com.proteusmobile.smsgw.server.ServerService$Listener.run0(ServerService.java:163) at com.proteusmobile.smsgw.server.ServerService$Listener.run(ServerService.java:154) at java.lang.Thread.run(Thread.java:536) Found 1 deadlock. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1037) JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint)

by Mariusz Olejnik (JIRA)

JDBCPersistenceManager.java - reference should be inserted after message (ORA-02291: integrity constraint) ---------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1037 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1037 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.4.0.CR1 Environment: Windows XP / Oracle 10g Reporter: Mariusz Olejnik Assigned To: Tim Fox Priority: Critical Fix For: 1.4.0.CR1 Reference should be inserted after message because: oracle-persistence-service.xml CREATE TABLE JBM_MSG_REF ( CHANNEL_ID INTEGER, MESSAGE_ID INTEGER REFERENCES JBM_MSG(MESSAGE_ID) [...] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

5
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2487) NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession

by hoogenbj (JIRA)

NPE on line 69 of ConcurrentNodeMemories.java when calling JPAKnowledgeService.loadStatefulKnowledgeSession ----------------------------------------------------------------------------------------------------------- Key: JBRULES-2487 URL: https://jira.jboss.org/jira/browse/JBRULES-2487 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss 4.2.3, Java 6 64-bit, Windows Vista 64-bit Reporter: hoogenbj Assignee: Mark Proctor Hi, I get a NullPointerException on line 69 of ConcurrentNodeMemories when calling JPAKnowledgeService.loadStatefulKnowledgeSession(...) in order to complete a work item using session.getWorkItemManager().completeWorkItem(...). Further investigation reveals that the objectType on line 332 of InputMarshaller refers to one of my objects that I passed as part of the second argument object when calling startProcess on the knowledge session that I got with JPAKnowledgeService.newStatefulKnowledgeSession. The objectTypeNode on line 333 of InputMarshaller is null which eventually causes the NPE in ConcurrentNodeMemories. This error does not occurr when starting and completing the whole process without retrieving the session from the database. Which seems to indicate that something is not persisted or correctly retrieved from the database. This is a serious problem for us. It means we have to find an alternative for Drools flow... -- 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

14 years, 10 months

6
9
0 / 0

[JBoss JIRA] Created: (JBRULES-2279) Cached ObjectTypeNodes are not restored when deserializing session

by Kris Verlaenen (JIRA)

Cached ObjectTypeNodes are not restored when deserializing session ------------------------------------------------------------------ Key: JBRULES-2279 URL: https://jira.jboss.org/jira/browse/JBRULES-2279 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert) Reporter: Kris Verlaenen Assignee: Edson Tirelli When the InputMarshaller is restoring facts in the working memory, it is using the ObjectTypeNodes of the rete tree to link the facts to their object type nodes. This currently fails if no ObjectTypeNode is present for that type (because the type is not used in a rule somewhere). This ObjectTypeNode should be recreated on request if necessary. -- 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

14 years, 10 months

4
9
0 / 0

[JBoss JIRA] Created: (JBAS-7218) ENC EM injection erroneously happens only once for web modules

by henk de boer (JIRA)

ENC EM injection erroneously happens only once for web modules -------------------------------------------------------------- Key: JBAS-7218 URL: https://jira.jboss.org/jira/browse/JBAS-7218 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.1.0.GA Environment: Observed problem on Mac OS X 10.5.7 and Debian Lenny 64 bits using JDK 6 Reporter: henk de boer Using a persistence-context-ref element in the web.xml of a web module, it appears that this causes an EntityManager instance to be injected only once into the ENC of this component. However, the EJB 3.0 spec states in section 16.2.1: "In general, lookups of objects in the JNDI java: namespace are required to return a new instance of the requested object every time." So the observed behavior seems to violate the spec. In addition, this is particularly troublesome since an EntityManager is explicitly not thread-safe. Using the same EM instance for simultaneous requests therefor doesn't work. Of course there are several other methods to obtain an EM reference, for instance binding an EM factory directly to JNDI and using that to obtain the reference. -- 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

14 years, 10 months

6
11
0 / 0

[JBoss JIRA] Created: (JBBUILD-602) Missing javax.jms:jms:jar:1.1

by Thomas Diesler (JIRA)

Missing javax.jms:jms:jar:1.1 ----------------------------- Key: JBBUILD-602 URL: https://jira.jboss.org/jira/browse/JBBUILD-602 Project: JBoss Build System Issue Type: Bug Components: Artifact Repositories Reporter: Thomas Diesler Fix For: Maven Repository 2.0 Missing: ---------- 1) javax.jms:jms:jar:1.1 Try downloading the file manually from: http://java.sun.com/products/jms/docs.html Then, install it using the command: mvn install:install-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.jms -DartifactId=jms -Dversion=1.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.jboss.osgi.framework:jboss-osgi-framework:jar:1.0.0.Alpha5-SNAPSHOT 2) org.jboss.logging:jboss-logging-log4j:jar:2.2.0.CR1 3) log4j:log4j:jar:1.2.15 4) javax.jms:jms:jar:1.1 -- 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

14 years, 10 months

3
7
0 / 0

[JBoss JIRA] Created: (JBXB-209) Enum parsing requires value equal to type name

by Thomas Diesler (JIRA)

Enum parsing requires value equal to type name ---------------------------------------------- Key: JBXB-209 URL: https://jira.jboss.org/jira/browse/JBXB-209 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.GA Reporter: Thomas Diesler Caused by: java.lang.RuntimeException: Invalid value mandatory valid are [MANDATORY, OPTIONAL] at org.jboss.xb.builder.runtime.EnumValueAdapter.cast(EnumValueAdapter.java:136) at org.jboss.xb.builder.runtime.AbstractPropertyHandler.attribute(AbstractPropertyHandler.java:115) at org.jboss.xb.binding.sunday.unmarshalling.AttributesHandler.attributes(AttributesHandler.java:51) at org.jboss.xb.binding.sunday.unmarshalling.DefaultElementHandler.attributes(DefaultElementHandler.java:65) at org.jboss.xb.builder.runtime.BeanHandler.startParticle(BeanHandler.java:124) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:630) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) public enum TAvailability { MANDATORY("mandatory"), OPTIONAL("optional"); private final String value; TAvailability(String v) { value = v; } public String value() { return value; } public static TAvailability fromValue(String v) { for (TAvailability c : TAvailability.values()) { if (c.value.equals(v)) { return c; } } throw new IllegalArgumentException(v); } } -- 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

14 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-245) Prevent unexpected dependee state changes

by Thomas Diesler (JIRA)

Prevent unexpected dependee state changes ----------------------------------------- Key: JBDEPLOY-245 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-245 Project: JBoss Deployers Issue Type: Feature Request Reporter: Thomas Diesler B --> X install(X) install(B) start(B) B == ACTIVE X == RESOLVED uninstall(X) B == ACTIVE The MC framework unexpectedly changes the state of B to RESOLVED -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-435) Aggregate the respective API docs

by Thomas Diesler (JIRA)

Aggregate the respective API docs --------------------------------- Key: JBMICROCONT-435 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-435 Project: JBoss Microcontainer Issue Type: Task Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossMC-2.2.x -- 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

14 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1287) EJB3 client with service-ref

by Thomas Diesler (JIRA)

EJB3 client with service-ref ---------------------------- Key: EJBTHREE-1287 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1287 Project: EJB 3.0 Issue Type: Sub-task Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCL-133) Add resolver preferences

by Thomas Diesler (JIRA)

Add resolver preferences ------------------------ Key: JBCL-133 URL: https://jira.jboss.org/jira/browse/JBCL-133 Project: JBoss ClassLoader Issue Type: Sub-task Reporter: Thomas Diesler -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-415) Comprehensive deployer framework documentation

by Thomas Diesler (JIRA)

Comprehensive deployer framework documentation ---------------------------------------------- Key: JBMICROCONT-415 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-415 Project: JBoss Microcontainer Issue Type: Task Components: Deployment Reporter: Thomas Diesler Fix For: JBossMC-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- 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

14 years, 10 months

2
7
0 / 0

[JBoss JIRA] Created: (JBXB-201) Cannot parse schema/jbxb_1_0.xsd

by Thomas Diesler (JIRA)

Cannot parse schema/jbxb_1_0.xsd -------------------------------- Key: JBXB-201 URL: https://jira.jboss.org/jira/browse/JBXB-201 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler This code String jbxbSchema = "schema/jbxb_1_0.xsd"; URL jbxbXSD = context.getBundle().getResource(jbxbSchema); if (jbxbXSD == null) throw new IllegalStateException("Cannot find: " + jbxbSchema); XSModel xsModel = Util.loadSchema(jbxbXSD.toExternalForm(), (SchemaBindingResolver)null); if (xsModel == null) throw new IllegalStateException("Cannot load schema: " + jbxbSchema); fails with Caused by: org.jboss.xb.binding.JBossXBRuntimeException: -1:-1 94:47 src-element.3: Element 'class' has both a 'type' attribute and a 'anonymous type' child. Only one of these is allowed for an element. at org.jboss.xb.binding.sunday.unmarshalling.XsdBinderTerminatingErrorHandler.handleError(XsdBinderTerminatingErrorHandler.java:40) at org.apache.xerces.impl.xs.XMLSchemaLoader.reportDOMFatalError(Unknown Source) at org.apache.xerces.impl.xs.XSLoaderImpl.loadURI(Unknown Source) at org.jboss.xb.binding.Util.loadSchema(Util.java:367) -- 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

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-202) Incosistent initialization of XSImplementation

by Thomas Diesler (JIRA)

Incosistent initialization of XSImplementation ---------------------------------------------- Key: JBXB-202 URL: https://jira.jboss.org/jira/browse/JBXB-202 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler Fix For: JBossXB-2.0.1.GA In Util there is private static XSImplementation xsImpl; which gets initialized lazily in public static XSModel loadSchema(String xsdURL, SchemaBindingResolver schemaResolver) { if(xsImpl == null) { xsImpl = getXSImplementation(); } All other loadSchema method do not reuse the static property Also, private static XSImplementation getXSImplementation() relies on the thread context classloader, which is not available in an OSGi environment. Could you please provide an JBossXB initialization entry point that is public and does not make an assumption on the availability of the TCCL -- 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

14 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1282) Add jaxws test coverage

by Thomas Diesler (JIRA)

Add jaxws test coverage ----------------------- Key: EJBTHREE-1282 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1282 Project: EJB 3.0 Issue Type: Task Reporter: Thomas Diesler Assigned To: Heiko Braun Fix For: AS 5.0.0.CR1 Container issues for required WS functionality -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
13
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1284) jaxws handler access to ejb3 security context

by Thomas Diesler (JIRA)

jaxws handler access to ejb3 security context --------------------------------------------- Key: EJBTHREE-1284 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1284 Project: EJB 3.0 Issue Type: Sub-task Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-225) Create ErrorHandler to DeploymentControllerContext

by Thomas Diesler (JIRA)

Create ErrorHandler to DeploymentControllerContext --------------------------------------------------- Key: JBDEPLOY-225 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-225 Project: JBoss Deployers Issue Type: Feature Request Reporter: Thomas Diesler The MC Framework incorrectly uninstalls the bundle if there is a failure in bundle.start() The controller context reached its required stage DESCRIBED after bundle install. A subsequent call to bundle.start() is supposed to transition to stages CLASSLOADER and then INSTALLED, which corresponds to the Bundle states RESOLVED and ACTIVE respectively. If the transition to INSTALLED fails, the controller context gets undeployed, which causes the bundle to transition to UNINSTALLED. The desired behaviour is: * on fail to resolve: remain in state INSTALLED * on fail to start: remain in state RESOLVED The proposed solution is to add an ErrorHandler to the DeploymentControllerContext if it is an OSGi deployment -- 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

14 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-234) Comprehensive classloading framework documentation

by Thomas Diesler (JIRA)

Comprehensive classloading framework documentation -------------------------------------------------- Key: JBDEPLOY-234 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-234 Project: JBoss Deployers Issue Type: Task Components: general Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBDEPLOY-2.2.x Please provide comprehensive documentation for the deployer framework. It should cover the individual types of deployers, deployment states, dependency items, modules, etc. Improved javadoc is also covered by this issue. For trunk it is possible to publish the javadoc in the hudson QA environment. -- 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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBXB-210) Property order cannot be defained on super type

by Thomas Diesler (JIRA)

Property order cannot be defained on super type ----------------------------------------------- Key: JBXB-210 URL: https://jira.jboss.org/jira/browse/JBXB-210 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.1.GA Reporter: Thomas Diesler Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Property order is not specified for type org.jboss.osgi.blueprint.parser.xb.TReference bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: referenceListeners dependsOn initialization componentName description any interfaceNames otherAttributes timeout filter availability at org.jboss.xb.builder.JBossXBNoSchemaBuilder.assertPropOrderNotRequired(JBossXBNoSchemaBuilder.java:1278) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1071) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482) at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684) @XmlType(name = "Treference", namespace = BlueprintContext.XMLNS_BLUEPRINT) public class TReference extends TServiceReference @XmlType(name = "TserviceReference", namespace = BlueprintContext.XMLNS_BLUEPRINT, propOrder = { "description" }) public class TServiceReference extends TComponent -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBXB-208) Provide an annotation based tutorial for JBossXB

by Thomas Diesler (JIRA)

Provide an annotation based tutorial for JBossXB ------------------------------------------------ Key: JBXB-208 URL: https://jira.jboss.org/jira/browse/JBXB-208 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Reporter: Thomas Diesler You've specified the namespace using JBossXmlSchema annotation. Which is correct. You should still add namespace element to the XmlRootElement annotation, which is a bit confusing having JBossXmlSchema. You don't have to do that XmlElement annotations. Unfortunately, we don't have JAXB tutorial for JBossXB. But you can find one for JAXB on Sun's web-site and use javadoc. For examples you can see tests in XB http://anonsvn.jboss.org/repos/common/jbossxb/trunk/src/test/java/org/jbo... -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-214) Add listener hooks for deployment processing

by Thomas Diesler (JIRA)

Add listener hooks for deployment processing -------------------------------------------- Key: JBDEPLOY-214 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-214 Project: JBoss Deployers Issue Type: Feature Request Reporter: Thomas Diesler Currently JBossOSGi wraps the Deployers to do some post processing public void process(List<DeploymentContext> deploy, List<DeploymentContext> undeploy) { // Delegate to the original deployers deployers.process(deploy, undeploy); // OSGi bundles resolve phase afterDeployersProcess(deploy, undeploy); } Perhaps this should be supported by the Deployers natively -- 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

14 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-122) Links should be recognized

by Thomas Diesler (JIRA)

Links should be recognized -------------------------- Key: JBFORUMS-122 URL: http://jira.jboss.com/jira/browse/JBFORUMS-122 Project: JBoss Forums Issue Type: Feature Request Components: Forum Enhancements Reporter: Thomas Diesler Assigned To: Sohil Shah Instead of [url]http://jira.jboss.com/jira/secure/CreateIssue.jspa[/url] I like to simply use http://jira.jboss.com/jira/secure/CreateIssue.jspa There are a lot of user provided links that I cannot click on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-7910) jmx-console does not display CompositeData properly

by Thomas Diesler (JIRA)

jmx-console does not display CompositeData properly --------------------------------------------------- Key: JBAS-7910 URL: https://jira.jboss.org/jira/browse/JBAS-7910 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Thomas Diesler The JMX spec defines with Open MBean generic data transfer types that are self describing. The jmx-console should display these open types properly instead of just showing their string representation. http://localhost:8080/jmx-console/HtmlAdaptor?action=inspectMBean&name=os... listBundles javax.management.openmbean.TabularDataSupport(tabularType=javax.management.openmbean.TabularType(name=BUNDLES,rowType=javax.management.openmbean.CompositeType(name=BUNDLE,items=((itemName=ExportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=Fragment,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Fragments,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Headers,itemType=javax.management.openmbean.TabularType(name=HEADERS,rowType=javax.management.openmbean.CompositeType(name=HEADER,items=((itemName=Key,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=Value,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)))),indexNames=(Key))),(itemName=Hosts,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=Identifier,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=ImportedPackages,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.String;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.String),primitiveArray=false)),(itemName=LastModified,itemType=javax.management.openmbean.SimpleType(name=java.lang.Long)),(itemName=Location,itemType=javax.management.openmbean.SimpleType(name=java.lang.String)),(itemName=PersistentlyStarted,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=RegisteredServices,itemType=javax.management.openmbean.ArrayType(name=[Ljava.lang.Long;,dimension=1,elementType=javax.management.openmbean.SimpleType(name=java.lang.Long),primitiveArray=false)),(itemName=RemovalPending,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)),(itemName=Required,itemType=javax.management.openmbean.SimpleType(name=java.lang.Boolean)), ... -- 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

14 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1152) service-ref in ejb-jar.xml is ignored

by Thomas Diesler (JIRA)

service-ref in ejb-jar.xml is ignored ------------------------------------- Key: EJBTHREE-1152 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1152 Project: EJB 3.0 Issue Type: Bug Reporter: Thomas Diesler Fix For: AS 5.0.0.Beta3 [tdiesler@tddell trunk]$ ant -Dtest=org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase one-test one-test: [junit] Running org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase [junit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 8.761 sec [junit] Test org.jboss.test.ws.jaxws.samples.serviceref.ServiceRefEJBTestCase FAILED Caused by: javax.naming.NameNotFoundException: service1 not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:542) at org.jnp.server.NamingServer.getBinding(NamingServer.java:550) at org.jnp.server.NamingServer.getObject(NamingServer.java:556) at org.jnp.server.NamingServer.lookup(NamingServer.java:296) at org.jnp.server.NamingServer.lookup(NamingServer.java:270) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:669) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:776) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:629) at javax.naming.InitialContext.lookup(InitialContext.java:351) at org.jboss.test.ws.jaxws.samples.serviceref.EJBClient.echo(EJBClient.java:52) <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"> <enterprise-beans> <session> <ejb-name>EJBClient</ejb-name> <remote>org.jboss.test.ws.jaxws.samples.serviceref.EJBRemote</remote> <ejb-class>org.jboss.test.ws.jaxws.samples.serviceref.EJBClient</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> <service-ref> <service-ref-name>service1</service-ref-name> <service-interface>javax.xml.ws.Service</service-interface> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname> </service-ref> <service-ref> <service-ref-name>service2</service-ref-name> <service-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpointService</service-interface> <wsdl-file>META-INF/wsdl/TestEndpoint.wsdl</wsdl-file> <service-qname xmlns:ns1="http://serviceref.samples.jaxws.ws.test.jboss.org/">ns1:TestEndpointService</service-qname> <port-component-ref> <service-endpoint-interface>org.jboss.test.ws.jaxws.samples.serviceref.TestEndpoint</service-endpoint-interface> <enable-mtom>true</enable-mtom> </port-component-ref> </service-ref> </session> </enterprise-beans> </ejb-jar> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

4
13
0 / 0

[JBoss JIRA] Created: (JBRULES-1787) Undocumented Panels for Eclipse Guided Rule Editor

by Steve Nunez (Illation) (JIRA)

Undocumented Panels for Eclipse Guided Rule Editor -------------------------------------------------- Key: JBRULES-1787 URL: https://jira.jboss.org/jira/browse/JBRULES-1787 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0.7 Reporter: Steve Nunez (Illation) Assignee: Mark Proctor In the Guided Rule Editor section: http://downloads.jboss.com/drools/docs/4.0.7.19894.GA/html_single/index.h... There is an explanation of the guided editor. However there is no explanation of what to expect to see in the various tabs, except the first one. What I expect to see in the "Generated DRL (read-only)" tab is the actual DRL that will be sent to the compiler, similar to that we see in the "DRL Viewer" pane of a .dslr file. What I actually see is the same sort of text that I see in the .dslr file, with no idea if it's actually be rendered correctly (in a subsequent step). -- 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

14 years, 10 months

5
14
0 / 0

[JBoss JIRA] Created: (JBRULES-1889) figures not properly displayed in Drools Expert User Guide

by Jaroslaw Kijanowski (JIRA)

figures not properly displayed in Drools Expert User Guide ---------------------------------------------------------- Key: JBRULES-1889 URL: https://jira.jboss.org/jira/browse/JBRULES-1889 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-docs-expert Affects Versions: 5.0.0.M3 Reporter: Jaroslaw Kijanowski Assignee: Mark Proctor Affected figures: 1.1.; 1.4.; 1.5 -- 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

14 years, 10 months

4
6
0 / 0

[JBoss JIRA] Created: (JBAS-7447) PersistentManager for sessions is broken

by Emilio Davis (JIRA)

PersistentManager for sessions is broken ---------------------------------------- Key: JBAS-7447 URL: https://jira.jboss.org/jira/browse/JBAS-7447 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.1.0.GA Reporter: Emilio Davis Assignee: Remy Maucherat Using the following context.xml <Context cookies="true" crossContext="true"> <Manager className="org.apache.catalina.session.PersistentManager" maxIdleSwap="1200" saveOnRestart="true"> <Store checkInterval="60" className="org.apache.catalina.session.JDBCStore" connectionURL="jdbc:mysql://localhost:3306/XXX?user=XXX&password=XXX" driverName="com.mysql.jdbc.Driver" sessionAppCol="app_name" sessionDataCol="session_data" sessionIdCol="session_id" sessionLastAccessedCol="last_access" sessionMaxInactiveCol="max_inactive" sessionTable="tomcat_sessions" sessionValidCol="valid_session"/> </Manager> <InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener> </Context> That used to work in jboss4.0.5GA and correct according to tomcat 6 documentation jboss 5.1.0GA fails to start tomcat with the following exception: 2009-11-02 23:11:54,292 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deplo y, ctxPath=/ 2009-11-02 23:11:55,619 ERROR [org.jboss.web.tomcat.service.deployers.JBossContextConfig] (main) XML error parsing: context.xml org.jboss.xb.binding.JBossXBException: Failed to parse source: Store not found as a child of Manager in unordered_sequence: attributes? at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextCo nfig.java:573) at org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:536) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5436) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4148) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeploymen t.java:310) at org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:1 42) at org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461) at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118) at org.jboss.web.deployers.WebModule.start(WebModule.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206) at $Proxy38.start(Unknown Source) I opened a thread in the tomcat integration forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=163337) but got no response. -- 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

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2289) Support JPA Resource Local EntityTransaction based Transactions

by Michael Youngstrom (JIRA)

Support JPA Resource Local EntityTransaction based Transactions --------------------------------------------------------------- Key: JBRULES-2289 URL: https://jira.jboss.org/jira/browse/JBRULES-2289 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.0.1.FINAL Reporter: Michael Youngstrom Assignee: Mark Proctor It would be nice if wherever JPA is used in Drools (drools-flow in particular) there was support for RESOURCE_LOCAL transactions through JPA's EntityTransaction interface as an alternative to JTA. Support for resource local transactions would reduce the base Drools Flow dependency footprint (no need for bitronix) as well as allow Drools to be used in a containerless or Tomcat like environment without a JTA implementation available. Although embeddable solutions are available they are often either buggy or complex. It would be nice to not have to deal with them if possible. If the idea is acceptable I'd be willing to put together an initial patch. -- 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

14 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1771) NotSerializableException is thrown from DayCounter class

by Tyronne Wickramarathne (JIRA)

NotSerializableException is thrown from DayCounter class -------------------------------------------------------- Key: JBMESSAGING-1771 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1771 Project: JBoss Messaging Issue Type: Bug Components: Configuration and Management Affects Versions: 1.4.0.SP3.CP08 Environment: JBoss-SOA-4.3_CP2, JBM-1.4.0.SP3-CP08.patch01 Reporter: Tyronne Wickramarathne Even though the MessageCounter class implements Serializable interface as per JBMESSAGING-1430; the NotSerializableException is still thrown when accessing MessageCounter via JMX console. The root cause seems to be the DayCounter class. -- 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

14 years, 10 months

4
7
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1791) ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally

by Tamas Cserveny (JIRA)

ConcurrentModificationException at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally ----------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1791 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1791 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.SP3 Environment: JBoss AS 4.2.3.GA Release (JBossESB 4.7) jboss.messaging.jmsVersion=1.1 jboss.messaging.jmsMajorVersion=1 jboss.messaging.jmsMinorVersion=1 jboss.messaging.jmsProviderName=JBoss Messaging jboss.messaging.providerVersion=1.4.0.SP3 jboss.messaging.providerMajorVersion=1 jboss.messaging.providerMinorVersion=4 jboss.messaging.providerIncrementingVersion=21 Reporter: Tamas Cserveny Hi, I found a CME in the JBoss-messageing. Test scenario: Vanilla JBossESB 4.7 with a simple flow. (file -> queue, bridge queue to another queue, queue -> file) I kept this server running on a 2 core system with a load of 10 messages / sec. (ca 3kb messages). I received many of these exception during the test. It caused some messages to stuck into the queue, but eventually they were redelivered. (Not after 5s, but after some other messages). They were counted in the 'DeliveringCount', and stayed like that. Cheers, Tamas 2010-02-26 00:00:50,083 ERROR [org.jboss.jms.client.container.ClientConsumer] Failed to deliver message javax.jms.JMSException: There is no transaction with id LocalTx[m0r-676r546g-1-2tbmq36g-nq5p47-51zk6a] at org.jboss.jms.tx.ResourceManager.addAck(ResourceManager.java:186) at org.jboss.jms.client.container.SessionAspect.handlePreDeliver(SessionAspect.java:293) at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect19.invoke(SessionAspect19.java) at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java) at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170) at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) at org.jboss.jms.client.delegate.ClientSessionDelegate$preDeliver_5548846795541436298.invokeNext(ClientSessionDelegate$preDeliver_5548846795541436298.java) at org.jboss.jms.client.delegate.ClientSessionDelegate.preDeliver(ClientSessionDelegate.java) at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:152) at org.jboss.jms.client.container.ClientConsumer$ListenerRunner.run(ClientConsumer.java:976) at org.jboss.messaging.util.JBMExecutor$TCLExecutor.run(JBMExecutor.java:78) at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89) at java.lang.Thread.run(Thread.java:619) 2010-02-26 00:03:22,084 ERROR [org.jboss.messaging.util.ExceptionUtil] ConnectionEndpoint[uip-txvw446g-1-2tbmq36g-nq5p47-51zk6a] sendTransaction [f6r-ghfu546g-1-2tbmq36g-nq5p47-5 java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.acknowledgeTransactionally(ServerSessionEndpoint.java:1474) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:810) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:473) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) -- 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

14 years, 10 months

4
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1795) HTTPS transport support for JBM

by Tyronne Wickramarathne (JIRA)

HTTPS transport support for JBM ------------------------------- Key: JBMESSAGING-1795 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1795 Project: JBoss Messaging Issue Type: Task Components: JMS Remoting Affects Versions: 1.4.0.SP3.CP10 Environment: JBoss-EAP-4.3_CP7 Reporter: Tyronne Wickramarathne Priority: Minor Fix For: 1.4.0.SP3.CP11 At present HTTPS transport support isn't available by default for JBM. However, as per Remoting manual, it is possible to configure HTTPS transport for JBM -- 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

14 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-619) Change getState semantics

by Vladimir Blagojevic (JIRA)

Change getState semantics ------------------------- Key: JGRP-619 URL: http://jira.jboss.com/jira/browse/JGRP-619 Project: JGroups Issue Type: Task Affects Versions: 2.5, 2.4, 2.3, 2.2.9 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 3.0 Currently Channel's getState method returns boolean indicating only whether state was successfully received by state receiver and not whether it was successfully processed at relevant channel listener. This anomaly lead convoluted application code that had to do rather complicated lock synchronization and notification mechanism on the progress of entire state transfer. We have to simplify this process! State receiver should simply call blocking getState and be notified in the form of Exception of anything that went wrong; be it that state could not be received at all or that it was received but could not be installed at channel listener. This issue is closely related to revamping of channel state transfer callbacks - JGRP-563 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1026) Refactor extended persistence context

by Carlo de Wolf (JIRA)

Refactor extended persistence context ------------------------------------- Key: EJBTHREE-1026 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1026 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
19
0 / 0

[JBoss JIRA] Created: (JBAS-7944) Move GlobalDiscoveryDisableTestCase to defaultcfg package

by Brian Stansberry (JIRA)

Move GlobalDiscoveryDisableTestCase to defaultcfg package --------------------------------------------------------- Key: JBAS-7944 URL: https://jira.jboss.org/jira/browse/JBAS-7944 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-6.0.0.M4 AFAICT this test doesn't need to be run with different JGroups stacks. -- 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

14 years, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-229) Comparison of String objects using == in FamilyClusterInfoImpl.equals(Object)

by Brian Stansberry (JIRA)

Comparison of String objects using == in FamilyClusterInfoImpl.equals(Object) ------------------------------------------------------------------------------ Key: JBCLUSTER-229 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-229 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Client 2.0.0.BETA1 return fr.familyName == this.familyName; Minor issue as this is semi-valid since the familyName field comes via ClusteringTargetsRepository, which ensures only a single String gets passed. -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-231) ClusteringTargetsRepository.families isn't final but should be

by Brian Stansberry (JIRA)

ClusteringTargetsRepository.families isn't final but should be -------------------------------------------------------------- Key: JBCLUSTER-231 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-231 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Client 2.0.0.BETA1 -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-237) Improve ClusterChooserInterceptor exception messages

by Brian Stansberry (JIRA)

Improve ClusterChooserInterceptor exception messages ---------------------------------------------------- Key: JBCLUSTER-237 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-237 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Client Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: HA-Client 2.0.0.BETA1 Stuff like the following needs improvement: target = (InvokerLocator) lb.chooseTarget(family.get()); if (target == null) { if (lastException != null) { throw new RuntimeException("cluster invocation failed, last exception was: ", lastException); } else { throw new RuntimeException("cluster invocation failed"); } } failoverCounter++; } // if we get here this means list was exhausted throw new RuntimeException("Unreachable?: Service unavailable."); -- 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

14 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-203) Genericize FamilyClusterInfo

by Brian Stansberry (JIRA)

Genericize FamilyClusterInfo ---------------------------- Key: JBCLUSTER-203 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-203 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Components: HA-Client Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 1.1.0.GA Mostly using List<Object> for the targets -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-204) Replication-based clustered Quartz job store

by Brian Stansberry (JIRA)

Replication-based clustered Quartz job store -------------------------------------------- Key: JBCLUSTER-204 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-204 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Backlog A Quartz job store impl that uses JBoss Cache or PojoCache to coordinate around the cluster instead of the db. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-226) Make FamilyClusterInfoImpl internal members volatile

by Brian Stansberry (JIRA)

Make FamilyClusterInfoImpl internal members volatile ---------------------------------------------------- Key: JBCLUSTER-226 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-226 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Client Affects Versions: HA-Client 1.1.1.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: HA-Client 2.0.0.BETA1 At a minimum the "cursor" and "arbitraryObject" fields should be volatile. -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-240) Gravitated sessions still exposed to background cleanup

by Brian Stansberry (JIRA)

Gravitated sessions still exposed to background cleanup ------------------------------------------------------- Key: JBCLUSTER-240 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-240 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Components: HA-Server-Cache-JBC Affects Versions: HA-Server-Cache-JBC 2.0.1.GA Reporter: Brian Stansberry Assignee: Brian Stansberry Follow up to JBCLUSTER-238. Still seeing an issue: [JBoss] 19:08:26,233 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (OOB-58,10.34.32.156:38607) Executing command: GravitateDataCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, searchSubtrees=true} [sender=10.34.32.154:46273] [JBoss] 19:08:26,234 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (OOB-58,10.34.32.156:38607) Command : GravitateDataCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, searchSubtrees=true} executed, result is: GravitateResult dataFound=true nodeData=[NodeData {fqn: /JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, attrs={0=3, 1=1250615302074, 2=org.jboss.web.tomcat.service.session.distributedcache.spi.DistributableSessionMetadata@30176a8f, 3=org.jboss.ha.framework.server.SimpleCachableMarshalledValue{raw=nullserialized=true}}}] fqn=/_BUDDY_BACKUP_/10.34.32.153_2585/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__ [JBoss] 19:08:26,571 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (Incoming-15,10.34.32.156:38607) Executing command: DataGravitationCleanupCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, backup=/_BUDDY_BACKUP_/10.34.32.153_2585/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__} [sender=10.34.32.154:46273] [JBoss] 19:08:26,572 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (Incoming-15,10.34.32.156:38607) Command : DataGravitationCleanupCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, backup=/_BUDDY_BACKUP_/10.34.32.153_2585/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__} executed, result is: null [JBoss] 19:11:36,727 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (Incoming-7,10.34.32.156:38607) Executing command: DataGravitationCleanupCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, backup=/_BUDDY_BACKUP_/10.34.32.154_46273:DEAD/1/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__} [sender=10.34.32.155:60743] [JBoss] 19:11:36,728 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (Incoming-7,10.34.32.156:38607) Command : DataGravitationCleanupCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, backup=/_BUDDY_BACKUP_/10.34.32.154_46273:DEAD/1/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__} executed, result is: null [JBoss] 19:14:24,493 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) dests=null, command=GravitateDataCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, searchSubtrees=true}, mode=2, timeout=17500 [JBoss] 19:14:24,496 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) responses: [sender=10.34.32.153:47135, retval=GravitateResult dataFound=true nodeData=[NodeData {fqn: /JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, attrs={0=92, 1=1250615662411, 2=org.jboss.web.tomcat.service.session.distributedcache.spi.DistributableSessionMetadata@2e075959, 3=org.jboss.ha.framework.server.SimpleCachableMarshalledValue{raw=nullserialized=true}}}] fqn=/_BUDDY_BACKUP_/10.34.32.155_60743/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, received=true, suspected=false] [JBoss] [sender=10.34.32.155:60743, retval=GravitateResult dataFound=true nodeData=[NodeData {fqn: /JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, attrs={0=92, 1=1250615662411, 2=org.jboss.web.tomcat.service.session.distributedcache.spi.DistributableSessionMetadata@647af9aa, 3=org.jboss.ha.framework.server.SimpleCachableMarshalledValue{raw=nullserialized=true}}}] fqn=/_BUDDY_BACKUP_/10.34.32.155_60743/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, received=true, suspected=false] [JBoss] 19:14:24,497 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) dests=[10.34.32.155:60743], command=ReplicateCommand{cmds=PrepareCommand{globalTransaction=GlobalTransaction:<10.34.32.156:38607>:203, modifications=[PutDataMapCommand{fqn=/_BUDDY_BACKUP_/10.34.32.156_38607/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, dataVersion=null, data={0=92, 1=1250615662411, 2=org.jboss.web.tomcat.service.session.distributedcache.spi.DistributableSessionMetadata@2e075959, 3=org.jboss.ha.framework.server.SimpleCachableMarshalledValue{raw={payLoad=org.jboss.test.cluster.servlet.SessionPayload@55a9181d}serialized=false}}, globalTransaction=null, erase=false}], localAddress=10.34.32.156:38607, onePhaseCommit=false}}, mode=2, timeout=17500 [JBoss] 19:14:24,499 TRACE [org.jboss.cache.marshall.CommandAwareRpcDispatcher] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) dests=null, command=DataGravitationCleanupCommand{fqn=/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__, backup=/_BUDDY_BACKUP_/10.34.32.155_60743/JSESSION/st_localhost/S8EqfyNmGtWeAeTjRnG5fA__}, mode=6, timeout=-1 The background thread should not be interested in this session. -- 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

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7272) Handle MergeViews in AbstractClusterLockSupport variants

by Brian Stansberry (JIRA)

Handle MergeViews in AbstractClusterLockSupport variants -------------------------------------------------------- Key: JBAS-7272 URL: https://jira.jboss.org/jira/browse/JBAS-7272 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-6.0.0.Alpha1 org.jboss.ha.framework.server.lock.AbstractClusterLockSupport and/or its subclasses need to deal with cluster merges, i.e. AS instances in groups {A, B} and {C, D} discover each other and form a single group {A, B, C, D}. Following a merge, it's possible a node in each of the merged subgroups thinks it has the cluster wide lock. A simple approach that *may* work in all cases is to handle a merge by having each node abandon the cluster-wide lock, forcing the next attempt by a local caller to re-acquire the lock. Need to think through though whether that is the correct semantic in all cases. AbstractClusterLockSupport needs to implement HAExtendedMembershipListener instead of just HAMembershipListener; this will allow it to know whether a view change was due to a merge. -- 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

14 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-188) Possible further extraction of clustering code from AS codebase

by Brian Stansberry (JIRA)

Possible further extraction of clustering code from AS codebase --------------------------------------------------------------- Key: JBCLUSTER-188 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-188 Project: JBoss Clustering Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: Q3Y8 Container task for evaluating further extractions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
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 April 2010