Date: Tue, 19 Mar 2024 02:25:41 +0000 (UTC)
Message-ID: <1901791130.54018.1710815141502@cwiki-he-fi.apache.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_54017_785201987.1710815141502"
------=_Part_54017_785201987.1710815141502
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Overview
ServiceMix NMR 1.0.0 is a brand new JBI container based on OSGi. A lot o=
f work has been done to follow more closely the rules from the JBI 1.0 spec=
ification and to have a much better lifecycle processing for various JBI ar=
tifacts. A new clustering engine has been developped which allows endpoints=
to be individually clustered, leveraging the transparent remoting (communi=
cations between two endpoints on different JBI containers) but also load-ba=
lancing and fail-over. Other features include the backporting of the audito=
r package from ServiceMix 3, the integration of the transaction manager and=
a JNDI/OSGi integration.
Getting the Distribut=
ions
Linux/Mac OS X/Unix Downloads
Windows downloads
Release notes
ServiceMix NMR 1.0.0 is a brand new JBI container based on OSGi. A lot o=
f work has been done to follow more closely the rules from the JBI 1.0 spec=
ification and to have a much better lifecycle processing for various JBI ar=
tifacts. A new clustering engine has been developped which allows endpoints=
to be individually clustered, leveraging the transparent remoting (communi=
cations between two endpoints on different JBI containers) but also load-ba=
lancing and fail-over. Other features include the backporting of the audito=
r package from ServiceMix 3, the integration of the transaction manager and=
a JNDI/OSGi integration.
Migration from Servi=
ceMix 3
Most of the applications developped for ServiceMix 3 can be deployed ont=
o this container, however, due to the OSGi layer underneath, some classload=
ing related issues may arise when migrating an application from ServiceMix =
3 because both containers do not behave the same way. Another major change =
compared to ServiceMix 3 is the changed transactional model which allows th=
e use of transactions for asynchronous exchanges: this change will affect y=
our application if you were leveraging the JCA flow in ServiceMix 3.
Change log
The following list shows the bug fixes and enhancements included in this=
release:
- Bug
- SMX4NMR-47 - A full stack trace is di=
splayed when NPE occurs in the ManagementEndpointRegistry when endpoints ar=
e not registered
- SMX4NMR-53 - Upgrade to kernel 1.1.0<=
/li>
- SMX4NMR-54 - osgi update command does=
not stop an endpoint before restarting it
- SMX4NMR-57 - Exchange.toString() does=
not include the error
- SMX4NMR-58 - update spring and spring=
osgi version used in NMR
- SMX4NMR-59 - java.lang.IllegalStateEx=
ception: Alias meta-file does not contain 'ALIAS' attribute: meta:/jbi when=
try to use jbi shell
- SMX4NMR-60 - EndpointRegistryImpl is =
not thread safe
- SMX4NMR-61 - jbi/list output isn't co=
rrect after stop and start jbi deployer bundle
- SMX4NMR-70 - If an error occurs while=
dispatching a message, stopping the assembly will wait forever
- SMX4NMR-76 - When a JBI component is =
uninstalled, it's running state is not remove, which leads to a bad state w=
hen re-installing the component
- SMX4NMR-77 - Uninstalling a bundle fo=
r a JBI packaged component does not update the org.apache.servicemix.jbi.ma=
nagement.InstallationService installers
- SMX4NMR-78 - Uninstalling a bundle fo=
r a JBI packaged component does not update the org.apache.servicemix.jbi.ma=
nagement.InstallationService installers
- SMX4NMR-79 - If the JBI artifact depl=
oyed has a MANIFEST.MF which is not the first entry in the jar, it leads to=
an exception when writing the transformed jar
- SMX4NMR-80 - Listing of JBI artifacts=
through ant tasks are not always valid
- SMX4NMR-81 - Can not deploy a shared =
library with a class path item equals to "."
- SMX4NMR-82 - Once a component has bee=
n shut down, restarting it should call Lifecycle#init()
- SMX4NMR-83 - org.apache.servicemix.sp=
ecs.jbi-api-1.0 version in the features.xml is not correct
- SMX4NMR-84 - JBI deployer puts compon=
ent in start state when installed via install-component ant task. (It shoul=
d be in Shutdown state till start-component is called.)
- SMX4NMR-88 - JBI deployer puts servic=
e assembly in start state when installed via deploy-service-assembly ant ta=
sk. (It should be in Shutdown state) Same holds true for the SU that is dep=
loyed as part of the SA.
- SMX4NMR-90 - When shared libraries re=
ference classes inside the zip of the SL, those are not loaded
- SMX4NMR-97 - The JBI components class=
loader sometime fails to load classes or resources
- SMX4NMR-99 - org.apache.servicemix.jb=
i.deployer.artifacts.ServiceAssemblyImpl.init() needs to do transition from=
start state to stop first before shutdown.
- SMX4NMR-100 - org.apache.servicemix.=
jbi.deployer.impl.ComponentInstaller.uninstall() doesn't call bootstrap.ini=
t() and cleanup() which is required as per JBI specs.
- SMX4NMR-101 - The message exchange p=
attern's URI does not comply with the spec
- SMX4NMR-104 - Each time the OSGi bun=
dle is started / stopped, the JBI artifact is installed / uninstalled
- SMX4NMR-105 - When installing a JBI =
artifact, the JBI->OSGi deployer sometimes throw a ZipException
- SMX4NMR-108 - Stopping / Starting th=
e OSGi bundle for a service assembly does not restart the SA (the previous =
running state is lost)
- SMX4NMR-109 - When a component is st=
opped and restarted, service assemblies are stopped, but not restarted
- SMX4NMR-110 - Starting a service ass=
embly which has a non started component should fail
- SMX4NMR-115 - Do not use spring prox=
ies for tracking endpoints and other NMR lists
- SMX4NMR-116 - Avoid deadlock when sh=
utting down a SA while receiving a sync exchange for it
- SMX4NMR-117 - Refactor the InternalR=
eference to allow references to be serializable
- SMX4NMR-118 - Allow configurable shu=
tdown timeout that ensures that a SA can be stopped by canceling sync reque=
sts
- SMX4NMR-120 - Add missing dependenci=
es to assembly pom
- SMX4NMR-121 - JBI components are not=
able to target NMR endpoints anymore
- SMX4NMR-122 - Wrong TCCL is used whe=
n operating service units
- SMX4NMR-123 - When going through the=
TransactionManager, the TCCL is changed to the transaction manager classlo=
ader
- SMX4NMR-130 - Lifecycle issues when =
using OSGi package service assemblies
- Improvement
- SMX4NMR-55 - Ensure a clean shutdown =
of service assemblies
- SMX4NMR-62 - Use a StringSource inste=
ad of a DOMSource when making an exchange rereadable or using copy to ensur=
e it is serializable
- SMX4NMR-63 - Use a static Transformer=
Factory when converting sources for performance
- SMX4NMR-64 - Use a static converter f=
or speed improvements
- SMX4NMR-65 - Switch the Endpoint.SERV=
ICE_NAME property value to the string representation of the qname for ease =
of use
- SMX4NMR-66 - Refactor ServiceEndpoint=
implementations
- SMX4NMR-68 - Parse interfaces support=
ed by endpoints using the wsdl description
- SMX4NMR-71 - When a component sends a=
new exchange, the DeliveryChannel should select the NMR channel correspond=
ing to this endpoint instead of the one for the component's endpoint
- SMX4NMR-72 - The ExchangeCompletedLis=
tener should only catch done/error exchanges when they are delivered, not s=
ent
- SMX4NMR-73 - Throw an exception when =
sending a message to a closed channel
- SMX4NMR-75 - Upgrade to xbean 3.5
- SMX4NMR-85 - Improve JBI->OSGi tra=
nsformation speed
- SMX4NMR-86 - Thread pools created by =
the EndpointRegistryImpl for ChanneImpl can not be managed / configured
- SMX4NMR-87 - Queues created by Compon=
entContextImpl for DeliveryChannelImpl can not be managed / configured
- SMX4NMR-95 - Allow the customization =
of the OSGi manifest when transforming a JBI artifact to an OSGi bundle
- SMX4NMR-96 - The transaction manager =
given to JBI components should implement RecoverableTransactionManager
- SMX4NMR-119 - Add command completion=
for jbi lifefycles commands
- New Feature
- SMX4NMR-17 - Implement the needed JMX=
mbeans for deployment / installation / management of JBI artifacts
- SMX4NMR-18 - JBI ant tasks
- SMX4NMR-20 - Implement SA connections=
- SMX4NMR-22 - Port the audit feature f=
rom ServiceMix 3
- SMX4NMR-25 - JMS clustering
- SMX4NMR-56 - Handle external endpoint=
s
- SMX4NMR-89 - Implement the JBI bootst=
rap mechanism
- SMX4NMR-94 - JNDI integration
- SMX4NMR-131 - Create interceptor exa=
mple using EndpointListener from NMR eventing api.
- Task
- SMX4NMR-16 - Full JBI 1.0 compatibili=
ty
- SMX4NMR-50 - Make sure that shutting =
down the jbi layer cleanly shuts down all the JBI artifacts deployed (using=
both JBI and OSGi packaging)
- SMX4NMR-69 - Use managed dependencies=
instead of specifying the versions in all poms
- SMX4NMR-74 - Change the distribution =
to include ant tasks and the kernel to have a fully operational minimal jbi=
container
- SMX4NMR-91 - Create an example showin=
g how to access the NMR from an osgi bundle to send exchanges
- SMX4NMR-92 - Create an example showin=
g how to write an NMR endpoint
- SMX4NMR-102 - Move transactions supp=
ort from the features project to the NMR
- SMX4NMR-107 - Use EasyMock for mock =
testing
- SMX4NMR-111 - Make sure the JBI plug=
in can be used to deploy jbi artifacts onto the NMR
-
- Test
- SMX4NMR-126 - Cluster engine tests f=
ails on Hudson =E2=80=93 forked test times out in 60 seconds
- SMX4NMR-127 - ChannelImplTest.testDi=
spatchAsync failed on my box caused by time issue
Known issues
- SMX4NMR-128 - JBI Cluster Engine uni=
t tests stall intermittently
------=_Part_54017_785201987.1710815141502--