[JBoss JIRA] (AS7-5514) Local access to admin console hangs with spinning "Loading..." icon. Remote access works.
by Dean Schulze (JIRA)
Dean Schulze created AS7-5514:
---------------------------------
Summary: Local access to admin console hangs with spinning "Loading..." icon. Remote access works.
Key: AS7-5514
URL: https://issues.jboss.org/browse/AS7-5514
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro 64-bit, JDK 1.7 64-bit
Reporter: Dean Schulze
Assignee: Heiko Braun
Installed JBoss 7.1.1 Final from .zip archive. Added a management user. Started standalone.bat. localhost:8080 shows the splash page. Clicking on the Admin Console link hangs with the "Loading..." icon spinning.
Modified standalone.xml to allow remote access (management and public) and opened up Windows firewall to the java.exe program that is running JBoss. I can access the splash page and admin console remotely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails
by Dominik Pospisil (Created) (JIRA)
Management - readding file handler logger fails
-----------------------------------------------
Key: AS7-2385
URL: https://issues.jboss.org/browse/AS7-2385
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Logging
Affects Versions: 7.1.0.Beta1
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly.
Steps to reproduce:
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{
"outcome" => "failed",
"failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered",
"rolled-back" => true
}
[standalone@localhost:9999 /]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBRULES-3613) Support "Defeasible" rules in Drools
by Davide Sottara (JIRA)
Davide Sottara created JBRULES-3613:
---------------------------------------
Summary: Support "Defeasible" rules in Drools
Key: JBRULES-3613
URL: https://issues.jboss.org/browse/JBRULES-3613
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-compiler, drools-core
Reporter: Davide Sottara
Assignee: Mark Proctor
Priority: Critical
Very roughly speaking, "defeasiblity" is about rules being able to prevent other rules from firing, or canceling the conclusions other rules.
It is used to manage "exceptions" or "(counter)arguments", where different rules lead to conflicting conclusions and a resolution strategy has to be applied, depending on some relative ordering (strength, salience, temporal, weight, etc..).
While an ad-hoc implementation is possible combining salience, appropriate insertions/retractions and the rule-based agenda, a more declarative approach should be provided to the user.
This lack of a feature is currently a blocker for the adoption of Drools in several medical and legal communities, just to cite some.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBAS-9516) java.lang.IllegalStateException: Channel id map for node 1 already contains binding for queue 60
by Asawari Pawar (JIRA)
Asawari Pawar created JBAS-9516:
-----------------------------------
Summary: java.lang.IllegalStateException: Channel id map for node 1 already contains binding for queue 60
Key: JBAS-9516
URL: https://issues.jboss.org/browse/JBAS-9516
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.1.0.GA
Environment: jboss 5.1.0 GA cluster setup with jboss messaging 1.4.3GA as HA singleton.
Reporter: Asawari Pawar
Assignee: Paul Ferraro
Fix For: No Release
<R,09/05/12 08:09:28 UTC,ExceptionUtil,[AsynchKeyChangeHandler Thread]> SessionEndpoint[vxz-sh4c5q6h-1-fi4m3p6h-eb2bav-8386js4] createConsumerDelegate [2yz-ek4c5q6h-1-fi4m3p6h-eb2bav-8386js4]
java.lang.IllegalStateException: Channel id map for node 1 already contains binding for queue 60
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2394)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1882)
at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:464)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1909)
at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:262)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:94)
at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeTarget(SessionAdvised$createConsumerDelegate_8721389917985689973.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:123)
at sun.reflect.GeneratedMethodAccessor1462.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:122)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java)
at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100)
at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891)
at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1724)
at org.jboss.remoting.Client.invoke(Client.java:629)
at org.jboss.remoting.Client.invoke(Client.java:617)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:189)
at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:160)
at org.jboss.jms.client.delegate.ClientSessionDelegate.org$jboss$jms$client$delegate$ClientSessionDelegate$createConsumerDelegate$aop(ClientSessionDelegate.java:267)
at org.jboss.jms.client.delegate.ClientSessionDelegate$createConsumerDelegate_8721389917985689973.invokeTarget(ClientSessionDelegate$createConsumerDelegate_8721389917985689973.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
at org.jboss.jms.client.container.StateCreationAspect.handleCreateConsumerDelegate(StateCreationAspect.java:142)
at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConsumerDelegate_1089614993.invoke(StateCreationAspect_z_handleCreateConsumerDelegate_1089614993.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ConsumerAspect.handleCreateConsumerDelegate(ConsumerAspect.java:76)
at org.jboss.aop.advice.org.jboss.jms.client.container.ConsumerAspect_z_handleCreateConsumerDelegate_1089614993.invoke(ConsumerAspect_z_handleCreateConsumerDelegate_1089614993.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:92)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientSessionDelegate.createConsumerDelegate(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.createConsumer(JBossSession.java:237)
at org.jboss.jms.client.JBossSession.createSubscriber(JBossSession.java:426)
at com.bmc.websdk.util.jms.TopicSessionImpl.createTSI(TopicSessionImpl.java:109)
at com.bmc.websdk.util.jms.TopicSessionImpl.createSubscriber(TopicSessionImpl.java:63)
at com.bmc.websdk.services.licensemonitor.login.jmx.LoginEventMonitor.initThresholdUpdateListener(LoginEventMonitor.java:577)
at com.bmc.websdk.services.licensemonitor.login.jmx.LoginEventMonitor.startService(LoginEventMonitor.java:92)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:322)
at sun.reflect.GeneratedMethodAccessor1456.invoke(Unknown Source)
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:189)
at $Proxy38.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
at org.jboss.system.ServiceController.start(ServiceController.java:460)
at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
at sun.reflect.GeneratedMethodAccessor281.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:286)
at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1568)
at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1533)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:943)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
at org.jboss.ha.singleton.HASingletonProfileActivator.activateProfile(HASingletonProfileActivator.java:189)
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.ha.singleton.HASingletonController.invokeSingletonMethod(HASingletonController.java:229)
at org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:153)
at org.jboss.ha.framework.server.HASingletonImpl.startNewMaster(HASingletonImpl.java:263)
at org.jboss.ha.framework.server.HASingletonImpl.makeThisNodeMaster(HASingletonImpl.java:243)
at org.jboss.ha.framework.server.HASingletonImpl.partitionTopologyChanged(HASingletonImpl.java:182)
at org.jboss.ha.framework.server.HAServiceImpl.replicantsChanged(HAServiceImpl.java:295)
at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:882)
at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.processEvent(DistributedReplicantManagerImpl.java:403)
at org.jboss.ha.framework.server.AsynchEventHandler.run(AsynchEventHandler.java:108)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy
by Carlo de Wolf (Created) (JIRA)
EJB not defining an EJB 2 view method should not deploy
-------------------------------------------------------
Key: AS7-2873
URL: https://issues.jboss.org/browse/AS7-2873
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: Carlo de Wolf
Assignee: Stuart Douglas
A bean which does not implement the sayHello method of the following EJB 2 remote view:
{code:title=HelloRemote.java}
public interface HelloRemote extends EJBObject {
String sayHello(String name) throws RemoteException;
}
{code}
gets the following exception during invocation:
{noformat}
Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56)
... 126 more
{noformat}
Instead the EJB should not have deployed properly and throw a DeploymentException.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (AS7-5509) Upgrade to Remoting JMX 1.0.5
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-5509:
-------------------------------------
Summary: Upgrade to Remoting JMX 1.0.5
Key: AS7-5509
URL: https://issues.jboss.org/browse/AS7-5509
Project: Application Server 7
Issue Type: Task
Components: JMX, Remoting
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.4.Final (EAP)
This will be an AS 7.1.x specific upgrade as master will be switching to Remoting JMX 1.1.x
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBMESSAGING-1933) Drop Durable Subscriptions from the MBean JMX console
by Doug Grove (JIRA)
Doug Grove created JBMESSAGING-1933:
---------------------------------------
Summary: Drop Durable Subscriptions from the MBean JMX console
Key: JBMESSAGING-1933
URL: https://issues.jboss.org/browse/JBMESSAGING-1933
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core
Affects Versions: 1.4.8.SP5
Reporter: Doug Grove
Priority: Minor
Currently, the durable subscribers and the number of messages awaiting delivery for those subscribers are shown for a Topic in the web console.
It would be beneficial to be able to drop a durable subscriber from the web console.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months
[JBoss JIRA] (JBMESSAGING-1932) Migration of Messages Between Versions
by Doug Grove (JIRA)
Doug Grove created JBMESSAGING-1932:
---------------------------------------
Summary: Migration of Messages Between Versions
Key: JBMESSAGING-1932
URL: https://issues.jboss.org/browse/JBMESSAGING-1932
Project: JBoss Messaging
Issue Type: Feature Request
Components: Messaging Core Persistence
Affects Versions: 1.4.8.SP5
Reporter: Doug Grove
Priority: Minor
The database used for JBoss Messaging can change between versions. When this happens, the database must be dropped and rebuilt. A mechanism should be provided to migrate messages.
This becomes difficult when transactions and durable subscriptions are taken into account.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 9 months