Hi, Is this fixed? In a separate thread you mentioned this is resolved.
On Sat, Mar 15, 2014 at 12:29 AM, Supun Malinga <[email protected]> wrote: > Hi, > > I'm really sorry guys. Found one problem related to the andes-client.jar. > Seems it doesn't pack "org.apache.mina.filter.SSLFilter" class though the > previous andes-client jar packed it. > Hence I'm getting an CNF in the Consumer (ESB) side. Error happens when > the jms receiving proxy is being deployed. > > Any thoughts on how to overcome this?. > > TID: [0] [ESB] [2014-03-14 14:33:51,055] ERROR > {org.apache.axis2.transport.jms.JMSListener} - Unexpected error when > configuring service PingServiceJMSListenerProxy for the JMS transport. It > will be disabled for this transport and marked as faulty. > {org.apache.axis2.transport.jms.JMSListener} > java.lang.NoClassDefFoundError: org/apache/mina/filter/SSLFilter > at > org.wso2.andes.transport.network.mina.MinaNetworkTransport$IoConnectorCreator.connect(MinaNetworkTransport.java:203) > at > org.wso2.andes.transport.network.mina.MinaNetworkTransport.connect(MinaNetworkTransport.java:74) > at > org.wso2.andes.client.AMQConnectionDelegate_8_0.makeBrokerConnection(AMQConnectionDelegate_8_0.java:120) > at > org.wso2.andes.client.AMQConnection.makeBrokerConnection(AMQConnection.java:616) > at org.wso2.andes.client.AMQConnection.<init>(AMQConnection.java:398) > at > org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:328) > at > org.wso2.andes.client.AMQConnectionFactory.createConnection(AMQConnectionFactory.java:38) > at > org.apache.axis2.transport.jms.JMSUtils.createConnection(JMSUtils.java:629) > at > org.apache.axis2.transport.jms.JMSListener.checkJMSConnection(JMSListener.java:148) > at > org.apache.axis2.transport.jms.JMSListener.startEndpoint(JMSListener.java:94) > at > org.apache.axis2.transport.jms.JMSListener.startEndpoint(JMSListener.java:53) > at > org.apache.axis2.transport.base.AbstractTransportListenerEx.startListeningForService(AbstractTransportListenerEx.java:154) > at > org.apache.axis2.transport.base.AbstractTransportListener.internalStartListeningForService(AbstractTransportListener.java:213) > at > org.apache.axis2.transport.base.AbstractTransportListener$2.serviceAdded(AbstractTransportListener.java:126) > at > org.apache.axis2.transport.base.tracker.AxisServiceTracker.serviceAdded(AxisServiceTracker.java:212) > at > org.apache.axis2.transport.base.tracker.AxisServiceTracker$1.serviceUpdate(AxisServiceTracker.java:98) > at > org.apache.axis2.engine.AxisConfiguration.notifyObservers(AxisConfiguration.java:666) > at > org.apache.axis2.engine.AxisConfiguration.addServiceGroup(AxisConfiguration.java:420) > at > org.apache.axis2.engine.AxisConfiguration.addService(AxisConfiguration.java:350) > at > org.apache.synapse.core.axis2.ProxyService.buildAxisService(ProxyService.java:657) > at > org.apache.synapse.deployers.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:75) > at > org.wso2.carbon.proxyadmin.ProxyServiceDeployer.deploySynapseArtifact(ProxyServiceDeployer.java:46) > at > org.apache.synapse.deployers.AbstractSynapseArtifactDeployer.deploy(AbstractSynapseArtifactDeployer.java:190) > at > org.wso2.carbon.application.deployer.synapse.SynapseAppDeployer.deployArtifacts(SynapseAppDeployer.java:140) > at > org.wso2.carbon.application.deployer.internal.ApplicationManager.deployCarbonApp(ApplicationManager.java:251) > at > org.wso2.carbon.application.deployer.CappAxis2Deployer.deploy(CappAxis2Deployer.java:71) > at > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136) > at > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807) > at > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144) > at > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377) > at > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254) > at > org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371) > at > org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59) > at > org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67) > at > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79) > at > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Caused by: java.lang.ClassNotFoundException: > org.apache.mina.filter.SSLFilter > at > org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421) > at > org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412) > at > org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107) > at java.lang.ClassLoader.loadClass(ClassLoader.java:247) > ... 45 more > > thanks, > > > > > On Fri, Mar 14, 2014 at 1:46 PM, Hasitha Hiranya <[email protected]>wrote: > >> WSO2 Message Broker 2.1.1 - Released! >> >> WSO2 MB team is pleased to announce the 2.1.1 release of the WSO2 Message >> Broker. >> >> WSO2 Message Broker 2.1.1, JMS message broker backed up with the wso2 >> distributed message brokering engine "Andes" is compliant with AMQP 0-91 >> version.The new 2.1.1 version is containing many bug fixes. This version is >> focused as a bug fix release of previous 2.1.0 version. Various bug fixes >> includes following areas, >> >> - Message delivery issues in the clustered environment >> - Queue message losses due to repeated subscription closing >> - Topic message delivery unreliability with high loads and >> concurrent access >> - Complete revamp of durable topic message delivery >> - Durable topic message delivery can now operate with cluster >> - Rigorous and Tested Failover Capability with message broker >> graceful shutdown and also sudden kill of the broker >> - SSL Capability - Messages can now be transferred securely using SSL >> configuration. When fail-over is configured it can support brokers with >> different trusted certificates. >> - Hector Configurations - Now you can fine tune hector client to >> efficiently communicate with Cassandra >> - Minor fixes in configuration file defaults >> - Performance improvements at various points of Message Brokering >> - Intermittent issues fixes at various scenarios introduced by high >> concurrency >> - Improved robustness in message re-delivery >> - Improved integration with other WSO2 Products >> - Tested message delivery in clustered environment for 1 million >> message burst. >> >> >> You can download this distribution from >> http://wso2.com/products/message-broker/ >> >> 1. Extract the downloaded zip >> 2. Go to the bin directory in the extracted folder >> 3. Run the wso2server.sh or wso2server.bat as appropriate >> 4. Point your browser to the URL https://localhost:9443/carbon >> 5. Use "admin", "admin" as the username and password to login as an >> admin and create a user account >> 6. Use the documentation to get to know on how to creating clients, >> using clients and deployment guide to do clustering. >> >> *Fixed Issues* >> >> This release of WSO2 MB comes with a number of bug fixes, both in the >> base framework and the MB specific components. All the issues which have >> been fixed in MB 2.1.1 are recorded at following locations: >> >> >> >> - Fixed MB specific issues<https://wso2.org/jira/issues/?filter=11739> >> >> >> *Known Issues* >> >> Known issues are listed at the following url: >> >> >> - WSO2 MB 2.1.1 component >> issues<https://wso2.org/jira/issues/?filter=11740> >> >> >> >> >> -- WSO2 Message Broker Team -- >> >> -- >> *Hasitha Abeykoon* >> Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >> >> > > > -- > Supun Malinga, > > Senior Software Engineer, > WSO2 Inc. > http://wso2.com > email: [email protected] <[email protected]> > mobile: +94 (0)71 56 91 321 > -- *Hasitha Abeykoon* Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
