Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #88 has FAILED. Change made by 6 authors.
On Tue, Feb 28, 2012 at 12:43 PM, Shammi Jayasinghe sha...@wso2.com wrote: Hi , We have got the previously mentioned intermittent issue of synapse distribution again. According to the offline discussion we had with sameera and pradeep, we are commenting out the distribution module of the synapse in the builder machine locally and trigger a new build. +1. Synapse distribution module is not related to any of the products. So lets comment it out. Sameera. Thanks Shammi On Tue, Feb 28, 2012 at 12:05 PM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Carbon-Platformhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #88http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88/ failed This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-88/ (Default Stage) 34 minutes 4817 passed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-88/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-88/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88/commit/ View all 8 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88/commit/ lakmali http://builder4.us1.wso2.org:/bamboo/browse/author/lakmali Adding thrift version to org.wso2.carbon.bam.receiver and org.wso2.carbon.bam.service poms. 121550 madhukahttp://builder4.us1.wso2.org:/bamboo/browse/author/madhuka Added JSP UI for API Provider 121548 chamarahttp://builder4.us1.wso2.org:/bamboo/browse/author/chamara test anti pattern issue fixed 121547 5 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-88?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #89 was SUCCESSFUL (with 4817 tests). Change made by 5 authors.
--- Carbon-Kernel Carbon-Platform #89 was successful. --- This build was manually triggered by BambooBuilder. 4817 tests in total. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89/ -- Code Changes -- madhuka (121556): Added API Provider host object madhuka (121554): Updated hostobjects/api pom.xml by adding API for dependencies rajika (121555): Mode code comments. -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #89 was SUCCESSFUL (with 4817 tests). Change made by 5 authors.
Wonderful news.. :) Final we get a build successful mail for the Carbon Platform(Except products). Devs, please don't break it again. Sameera. On Tue, Feb 28, 2012 at 2:19 PM, Bamboo cbuil...@wso2.org wrote: [image: Successful] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Carbon-Platformhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #89http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89/ was successful This build was manually triggered by BambooBuilderhttp://builder4.us1.wso2.org:/bamboo/browse/user/bamboo_builder . *4817* tests in total. Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89/commit/ View all 12 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89/commit/ lalaji http://builder4.us1.wso2.org:/bamboo/browse/author/lalaji Updated addAPI.jss file 121565 dilshanhttp://builder4.us1.wso2.org:/bamboo/browse/author/dilshan Updating Howto documentation 121564 ajithnhttp://builder4.us1.wso2.org:/bamboo/browse/author/ajithn fix media type 121563 9 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-89?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Updated Invitation: Context Mapping to Stratos AS with current carbon @ Wed Feb 29 11:30am - 12pm (carbon-dev@wso2.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20120229T06Z DTEND:20120229T063000Z DTSTAMP:20120228T095132Z ORGANIZER;CN=r...@wso2.com:mailto:r...@wso2.com UID:872lnmb06no8fk5v88g1pph...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Selvaratnam Uthaiyashankar;X-NUM-GUESTS=0:mailto:shan...@wso2.com ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE;C N=LK #59 2nd Floor Room;X-NUM-GUESTS=0:mailto:wso2.com_38323432343934383931 3...@resource.calendar.google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Pradeep Fernando;X-NUM-GUESTS=0:mailto:prad...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Afkham Azeez;X-NUM-GUESTS=0:mailto:az...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=r...@wso2.com;X-NUM-GUESTS=0:mailto:r...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Amani Soysa;X-NUM-GUESTS=0:mailto:am...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=carbon-dev@wso2.org;X-NUM-GUESTS=0:mailto:carbon-dev@wso2.org ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Sameera Jayasoma;X-NUM-GUESTS=0:mailto:same...@wso2.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=Dimuthu Leelarathne;X-NUM-GUESTS=0:mailto:dimut...@wso2.com CREATED:20120228T080601Z DESCRIPTION:Since carbon is not currently deployed as a web-app\, how possi bly forward a request from carbon to another context.\nSecurity is a concer n when fetching resources from another context by enabling crossContext to AS.\nWe need to decide on how to handle the request forwarding?\nView your event at http://www.google.com/calendar/event?action=VIEWeid=ODcybG5tYjA2b m84Zms1djg4ZzFwcGhqbWMgY2FyYm9uLWRldkB3c28yLm9yZwtok=MTMjcmVrYUB3c28yLmNvb TdhMmFiNWExMWZkZGQ2MTliYjc2M2VlNDdkMGY2M2IyMWI1NTUwZTQctz=Asia%2FColomboh l=en. LAST-MODIFIED:20120228T095132Z LOCATION:LK #59 2nd Floor Room SEQUENCE:1 STATUS:CONFIRMED SUMMARY:Context Mapping to Stratos AS with current carbon TRANSP:TRANSPARENT END:VEVENT END:VCALENDAR invite.ics Description: application/ics ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Server Startup Error with cassandra feature
Hi ,
I was able to solve this problem. This error was due to not passing
credentials when creating the cassandra cluster.
-cluster = HFactory.getOrCreateCluster(clusterName,
hostConfigurator);
+cluster = HFactory.createCluster(clusterName,
hostConfigurator,credentials);
When i did the above fix, i was able to get rid of the problem.
Thanks
Shammi
On Tue, Feb 28, 2012 at 8:44 AM, Deependra Ariyadewa d...@wso2.com wrote:
On Mon, Feb 27, 2012 at 3:41 PM, Shammi Jayasinghe sha...@wso2.comwrote:
Hi,
I am using wso2 cassandra server feature in MB. When using that i am
getting the following error[1] when starting up the server. I have added
the following files to
repository/conf advanced folder also. Have someone experienced this error
before.
It looks like MB is trying to access a Cassandra keyspace
with invalid credentials. You can try the Cassandra feature with a Carbon
Core to verify your Cassandra configuration.
Thanks,
Deependra.
Thanks
Shammi
cassandra-auth.xml
cassandra-component.xml
cassandra-endpoint.xml
cassanda.yaml
cassandra-auth.xml Cassandra
EPRhttps://localhost:9443/services/CassandraSharedKeyPublisher/EPR
UserUSERNAME/User
PasswordPASSWD/Password
/Cassandra
[2012-02-27 15:32:24,732] INFO
{org.apache.cassandra.service.GCInspector} - GC for PS MarkSweep: 307 ms,
65344 reclaimed leaving 152492296 used; max is 813301760
[2012-02-27 15:32:25,052] INFO
{me.prettyprint.cassandra.connection.CassandraHostRetryService} - Downed
Host Retry service started with queue size 3 and retry delay 10s
[2012-02-27 15:32:40,135] INFO
{me.prettyprint.cassandra.service.JmxMonitor} - Registering JMX
me.prettyprint.cassandra.service:ServiceType=hector,MonitorType=hector
[2012-02-27 15:32:40,136] WARN
{me.prettyprint.cassandra.service.JmxMonitor} - Unable to locate
hectorLog4j.xml; performance counters will not be exported
Exception during startup:
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:You have not logged in)
me.prettyprint.hector.api.exceptions.HInvalidRequestException:
InvalidRequestException(why:You have not logged in)
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:42)
at
me.prettyprint.cassandra.service.AbstractCluster$4.execute(AbstractCluster.java:190)
at
me.prettyprint.cassandra.service.AbstractCluster$4.execute(AbstractCluster.java:180)
at
me.prettyprint.cassandra.service.Operation.executeAndSetResult(Operation.java:101)
at
me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:156)
at
me.prettyprint.cassandra.service.AbstractCluster.describeKeyspace(AbstractCluster.java:194)
at
org.apache.qpid.server.store.CassandraMessageStore.createKeyspace(CassandraMessageStore.java:535)
at
org.apache.qpid.server.store.CassandraMessageStore.performCommonConfiguration(CassandraMessageStore.java:1549)
at
org.apache.qpid.server.store.CassandraMessageStore.configureConfigStore(CassandraMessageStore.java:1587)
at
org.apache.qpid.server.virtualhost.VirtualHostImpl.initialiseMessageStore(VirtualHostImpl.java:389)
at
org.apache.qpid.server.virtualhost.VirtualHostImpl.init(VirtualHostImpl.java:233)
at
org.apache.qpid.server.virtualhost.VirtualHostImpl.init(VirtualHostImpl.java:169)
at
org.apache.qpid.server.registry.ApplicationRegistry.createVirtualHost(ApplicationRegistry.java:566)
at
org.apache.qpid.server.registry.ApplicationRegistry.initialiseVirtualHosts(ApplicationRegistry.java:325)
at
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:263)
at
org.apache.qpid.server.registry.ApplicationRegistry.initialise(ApplicationRegistry.java:149)
at org.apache.qpid.server.Broker.startupImpl(Broker.java:122)
at org.apache.qpid.server.Broker.startup(Broker.java:97)
at org.apache.qpid.server.Main.startBroker(Main.java:228)
at org.apache.qpid.server.Main.execute(Main.java:221)
at org.apache.qpid.server.Main.init(Main.java:64)
at org.apache.qpid.server.Main.main(Main.java:54)
at
org.wso2.carbon.qpid.internal.QpidServiceComponent.activate(QpidServiceComponent.java:103)
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.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:252)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
at
org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:346)
at
[Carbon-dev] [ANN] Jaggery Milestone-3 Released
*Introducing Jaggery*
Jaggery is a framework to write webapps and HTTP-focused web services for
all aspects of the application: front-end, communication, Server-side logic
and persistence in pure Javascript. One of the intents of this framework is
to reduce the gap between writing web apps and web services.
This Framework uses Mozilla Rhino to process Javascript at the server and
also contains a powerful caching layer with the support of Rhino compiled
scripts; so its as fast as the JVM. As few key features, Jaggery has native
JSON support and also E4X support for XML manipulation.
M3 can be downloaded at http://dist.wso2.org/products/jaggery/dl/jaggery
-1.0.0-SNAPSHOT_M3.zip
*Say Hello to Jaggery*
html
body
h1
%
var name = 'Jaggery';
print(Hello + name);
%
/h1
/body
/html
*Setting up Jaggery*
1. Extract jaggery-1.0.0-SNAPSHOT_M3.zip
2. This will generate a bin directory with execution scripts.
3. Run sh bin/wso2server.sh (bin/wso2server.bat) command to start the
server.
4. Upon successful startup, {http://localhost:9763/docs} should take you
to the documentation Jaggery App.
*Key Features*
- Compose server side scripts purely in javascript (.jss)
- Script caching support
- Script include support
- Module include support
- Command line tool for easy development
- Try-it tool for web based script validation
- Includes support for,
- HTTP request/response and session
- JSON send/receive
- Server side XMLHttpRequest
- URIMatcher
- Web Service invocation
- File I/O
- Email
- XSLT
- Atom
- Read/write feed
- Relational database
- WSO2 Registry/Repository
For more information and samples you can refer to Jaggery docs at (
http://{yourip}:9763/docs/documentation.jsshttp://localhost:9763/docs/documentation.jss
) which are shipped with the distribution
Thanks,
*Jaggery Development Team*
http://www.nuwanbando.com/
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Finalize all SVN moves create the new structure in Crucible
Folks, We need to finalize this. If it is going to be; carbon/kernel/[trunk/branches/tags] model we need to do it now. Changing the SVN structure from time to time screws up all other dependent tools we use. I'm in the middle of reviewing some components, and cannot continue since the SVN structure has changed. Who is going to own this? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open
Hi Azeez, I tried to instantiate the Socket in a separate client class after debug gets hold in the same corresponding place in ClientConnectionUtil class. Same result. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.init(Socket.java:375) at java.net.Socket.init(Socket.java:218) at Main.main(Main.java:23) 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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez az...@wso2.com wrote: Increasing the timeout will not help. For some reason, the server is not successfully starting up. On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso ach...@wso2.com wrote: Hi, I also got the same issue with GS integration tests. Increasing the timeout didn't work for me too. On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga sub...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando nir...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi, I am getting GReg integration recent test failures due to Port 9443 is not open. Happens at server startup in RegistryTestServerManager. Here is the sure fire report log. Any reason for this to happen ? This happens when it failed to open the port (9443) within the time out (6 ms). Increasing it might solve the problem!! I increased the delay 8 times longer than earlier (in ClientConnectionUtil class in integration framework.). It didn't worked Not sure what exactly causing this. Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed: 324.265 sec FAILURE! startServer(org.wso2.carbon.registry.RegistryTestServerManager) Time elapsed: 0 sec FAILURE! org.testng.internal.thread.ThreadExecutionException: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: java.lang.RuntimeException: Port 9443 is not open at org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25) at org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242) at org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) Caused by: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: java.lang.RuntimeException: Port 9443 is not open at org.testng.internal.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:49) at
Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open
The HTTP/S ports are not open due to some reason. We need to investigate why the server is not properly starting up. May be it is waiting for required OSGi services, and not starting up due to OSGi dependency issues. Try manually starting up the respective servers. On Tue, Feb 28, 2012 at 5:32 PM, Subash Chaturanga sub...@wso2.com wrote: Hi Azeez, I tried to instantiate the Socket in a separate client class after debug gets hold in the same corresponding place in ClientConnectionUtil class. Same result. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.init(Socket.java:375) at java.net.Socket.init(Socket.java:218) at Main.main(Main.java:23) 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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez az...@wso2.com wrote: Increasing the timeout will not help. For some reason, the server is not successfully starting up. On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso ach...@wso2.com wrote: Hi, I also got the same issue with GS integration tests. Increasing the timeout didn't work for me too. On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga sub...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando nir...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi, I am getting GReg integration recent test failures due to Port 9443 is not open. Happens at server startup in RegistryTestServerManager. Here is the sure fire report log. Any reason for this to happen ? This happens when it failed to open the port (9443) within the time out (6 ms). Increasing it might solve the problem!! I increased the delay 8 times longer than earlier (in ClientConnectionUtil class in integration framework.). It didn't worked Not sure what exactly causing this. Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed: 324.265 sec FAILURE! startServer(org.wso2.carbon.registry.RegistryTestServerManager) Time elapsed: 0 sec FAILURE! org.testng.internal.thread.ThreadExecutionException: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: java.lang.RuntimeException: Port 9443 is not open at org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25) at org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242) at org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) 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.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at
Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open
Hi Azeez, On Tue, Feb 28, 2012 at 5:35 PM, Afkham Azeez az...@wso2.com wrote: The HTTP/S ports are not open due to some reason. We need to investigate why the server is not properly starting up. May be it is waiting for required OSGi services, and not starting up due to OSGi dependency issues. Try manually starting up the respective servers. You are quite right.!! This has nothing to do with integration tests. It's due to the problem of the trunk pack. Server hangs and waits for org.wso2.carbon.registry.ws.api bundle. Hi Senaka, We have to first fix the trunk GReg pack issue. I will start working on it. On Tue, Feb 28, 2012 at 5:32 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Azeez, I tried to instantiate the Socket in a separate client class after debug gets hold in the same corresponding place in ClientConnectionUtil class. Same result. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.init(Socket.java:375) at java.net.Socket.init(Socket.java:218) at Main.main(Main.java:23) 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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez az...@wso2.com wrote: Increasing the timeout will not help. For some reason, the server is not successfully starting up. On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso ach...@wso2.com wrote: Hi, I also got the same issue with GS integration tests. Increasing the timeout didn't work for me too. On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga sub...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando nir...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi, I am getting GReg integration recent test failures due to Port 9443 is not open. Happens at server startup in RegistryTestServerManager. Here is the sure fire report log. Any reason for this to happen ? This happens when it failed to open the port (9443) within the time out (6 ms). Increasing it might solve the problem!! I increased the delay 8 times longer than earlier (in ClientConnectionUtil class in integration framework.). It didn't worked Not sure what exactly causing this. Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed: 324.265 sec FAILURE! startServer(org.wso2.carbon.registry.RegistryTestServerManager) Time elapsed: 0 sec FAILURE! org.testng.internal.thread.ThreadExecutionException: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: java.lang.RuntimeException: Port 9443 is not open at org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25) at org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242) at org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99) at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:111) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open
Hi Subash, Start G-Reg with -DosgiConsole. After the server hangs, do an ss. Figure out the ws.api bundle's ID and run a start ID command. Then you should see the dependency resolution errors being reported. Thanks, Senaka. On Tue, Feb 28, 2012 at 5:54 PM, Subash Chaturanga sub...@wso2.com wrote: Hi Azeez, On Tue, Feb 28, 2012 at 5:35 PM, Afkham Azeez az...@wso2.com wrote: The HTTP/S ports are not open due to some reason. We need to investigate why the server is not properly starting up. May be it is waiting for required OSGi services, and not starting up due to OSGi dependency issues. Try manually starting up the respective servers. You are quite right.!! This has nothing to do with integration tests. It's due to the problem of the trunk pack. Server hangs and waits for org.wso2.carbon.registry.ws.api bundle. Hi Senaka, We have to first fix the trunk GReg pack issue. I will start working on it. On Tue, Feb 28, 2012 at 5:32 PM, Subash Chaturanga sub...@wso2.comwrote: Hi Azeez, I tried to instantiate the Socket in a separate client class after debug gets hold in the same corresponding place in ClientConnectionUtil class. Same result. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:529) at java.net.Socket.connect(Socket.java:478) at java.net.Socket.init(Socket.java:375) at java.net.Socket.init(Socket.java:218) at Main.main(Main.java:23) 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 com.intellij.rt.execution.application.AppMain.main(AppMain.java:120) On Tue, Feb 28, 2012 at 10:40 AM, Afkham Azeez az...@wso2.com wrote: Increasing the timeout will not help. For some reason, the server is not successfully starting up. On Tue, Feb 28, 2012 at 9:11 AM, Achala Aponso ach...@wso2.com wrote: Hi, I also got the same issue with GS integration tests. Increasing the timeout didn't work for me too. On Mon, Feb 27, 2012 at 4:31 PM, Subash Chaturanga sub...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:35 PM, Nirmal Fernando nir...@wso2.comwrote: On Mon, Feb 27, 2012 at 3:26 PM, Subash Chaturanga sub...@wso2.comwrote: Hi, I am getting GReg integration recent test failures due to Port 9443 is not open. Happens at server startup in RegistryTestServerManager. Here is the sure fire report log. Any reason for this to happen ? This happens when it failed to open the port (9443) within the time out (6 ms). Increasing it might solve the problem!! I increased the delay 8 times longer than earlier (in ClientConnectionUtil class in integration framework.). It didn't worked Not sure what exactly causing this. Tests run: 270, Failures: 2, Errors: 0, Skipped: 268, Time elapsed: 324.265 sec FAILURE! startServer(org.wso2.carbon.registry.RegistryTestServerManager) Time elapsed: 0 sec FAILURE! org.testng.internal.thread.ThreadExecutionException: org.testng.internal.InvokeMethodRunnable$TestNGRuntimeException: java.lang.RuntimeException: Port 9443 is not open at org.testng.internal.thread.FutureResultAdapter.get(FutureResultAdapter.java:25) at org.testng.internal.MethodInvocationHelper.invokeWithTimeoutWithNewExecutor(MethodInvocationHelper.java:242) at org.testng.internal.MethodInvocationHelper.invokeWithTimeout(MethodInvocationHelper.java:200) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:528) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:202) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:130) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:277) at org.testng.SuiteRunner.run(SuiteRunner.java:240) at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52) at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86) at org.testng.TestNG.runSuitesSequentially(TestNG.java:1158) at org.testng.TestNG.runSuitesLocally(TestNG.java:1083) at org.testng.TestNG.run(TestNG.java:999) at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:60) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:153) at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99) at
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Products #22 has FAILED (18 tests failed, 15 failures were new). Change made by 15 authors.
--- Carbon-Kernel Carbon-Products #22 failed. --- This build was manually triggered by BambooBuilder. 18/170 tests failed, 15 failures were new. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONPRODUCTS-22/ -- Failing Jobs -- - Default Job (Default Stage): 18 of 170 tests failed. -- Code Changes -- madhuka (121556): Added API Provider host object lalaji (121574): Updated index.jss file nuwanw (121541): updated dataservice class names in testConfig -- Tests -- New Test Failures (15) - GreetingServiceDeploymentTestCase: Call greet - ISTestServerManager: Stop server - MSTestServerManager: Stop server - MashupAdminTestCase: Save mashup service source - EmailHostObjectTestCase: Email - FileHostObjectTestCase: File - HttpClientHostObjectTestCase: Search google - RequestHostObjectTestCase: Test invoked url - RequestHostObjectTestCase: Test remote ip - ScrapperHostObjectTestCase: Scrap - SessionHostObjectTestCase: Put value - SystemHostObjectTestCase: Log a string - SystemHostObjectTestCase: Include js file - SystemHostObjectTestCase: Wait some time - SystemHostObjectTestCase: Local host name Existing Test Failures (3) - CEPTestServerManager: Start server - DSSTestServerManager: Start server - GSTestServerManager: Start server -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Mediator for Complex SOAP Processing
I want to deploy a mediator on ESB. It will take SOAP messages as input and by using some parts of it, it will create new SOAP messages, send them, get response and according to responses create and send new SOAP messages and finally return a response to base request. Is creating such as mediator possible in ESB? If yes, do you have any example ? Thanks. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Exception thrown when a product started in log4j.DEBUG mode
Hi, I'm getting this exception in trunk. [2012-02-28 19:17:12,468] DEBUG - PersistenceActivator - JPA-PersistenceUnits:ode-dao,ode-store [2012-02-28 19:17:12,485] DEBUG - StAXUtils - About to create XMLInputFactory implementation with classloader=org.eclipse.core.runtime.internal.adaptor.ContextFinder@3a0b53e [2012-02-28 19:17:12,496] DEBUG - AbstractContext - OnDemandLogger initialized for class org.apache.axis2.context.AbstractContext is:org.apache.commons.logging.impl.Log4JLogger@2c42a818 [2012-02-28 19:17:14,701] INFO - CarbonCoreActivator - Starting WSO2 Carbon... [2012-02-28 19:17:14,722] INFO - BootupValidationActivator - Bootup Validator is activated... [2012-02-28 19:17:16,058] DEBUG - StAXUtils - About to create XMLInputFactory implementation with classloader=org.eclipse.core.runtime.internal.adaptor.ContextFinder@3a0b53e [2012-02-28 19:17:16,160] DEBUG - StAXUtils - About to create XMLInputFactory implementation with classloader=org.eclipse.core.runtime.internal.adaptor.ContextFinder@3a0b53e [2012-02-28 19:17:16,279] DEBUG - PersistenceActivator - JPA-PersistenceUnits:ode-dao,ode-store [2012-02-28 19:17:16,285] INFO - CarbonCoreActivator - Starting WSO2 Carbon... [2012-02-28 19:17:16,291] INFO - BootupValidationActivator - Bootup Validator is activated... [2012-02-28 19:17:16,292] DEBUG - StAXUtils - About to create XMLInputFactory implementation with classloader=org.eclipse.core.runtime.internal.adaptor.ContextFinder@3a0b53e [2012-02-28 19:17:16,313] DEBUG - StAXUtils - About to create XMLInputFactory implementation with classloader=org.eclipse.core.runtime.internal.adaptor.ContextFinder@3a0b53e [2012-02-28 19:17:16,382] INFO - ExtendedStandardService - starting extended standard service : StandardService[Catalina] Exception in thread Thread-2 java.lang.NoClassDefFoundError: Could not initialize class org.wso2.carbon.utils.multitenancy.CarbonContextHolder at org.wso2.carbon.utils.multitenancy.CarbonContextHolder.getCurrentCarbonContextHolder(CarbonContextHolder.java:550) at org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantPatternConverter.getFullyQualifiedName(TenantAwarePatternLayout.java:296) at org.wso2.carbon.utils.logging.TenantAwarePatternLayout$TenantAwarePatternParser$TenantAwareNamedPatternConverter.convert(TenantAwarePatternLayout.java:161) at org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:64) at org.apache.log4j.PatternLayout.format(PatternLayout.java:503) at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:301) at org.apache.log4j.DailyRollingFileAppender.subAppend(DailyRollingFileAppender.java:358) at org.apache.log4j.WriterAppender.append(WriterAppender.java:159) at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:230) at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:65) at org.apache.log4j.Category.callAppenders(Category.java:203) at org.apache.log4j.Category.forcedLog(Category.java:388) at org.apache.log4j.Category.log(Category.java:853) at org.apache.commons.logging.impl.Log4JLogger.info(Log4JLogger.java:199) at org.wso2.carbon.tomcat.ext.service.ExtendedStandardService.startInternal(ExtendedStandardService.java:41) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:727) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.wso2.carbon.tomcat.internal.CarbonTomcat.start(CarbonTomcat.java:65) at org.wso2.carbon.tomcat.server.ServerManager$1.run(ServerManager.java:80) at java.lang.Thread.run(Thread.java:662) -- Thanks, Denis -- *Denis Weerasiri* Software Engineer Integration Technologies Team, WSO2 Inc.; http://wso2.com, *email: denis http://goog_277208233/** [AT] wso2.com http://wso2.com/* *phone: +94117639629 * *site: **https://sites.google.com/site/ddweerasiri/*https://sites.google.com/site/ddweerasiri/ *blog: **http://ddweerasiri.blogspot.com* http://ddweerasiri.blogspot.com/ * twitter: **http://twitter.com/ddweerasiri* http://twitter.com/ddweerasiri* linked-in: **http://lk.linkedin.com/in/ddweerasiri*http://lk.linkedin.com/in/ddweerasiri ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #90 has FAILED. Change made by 12 authors.
--- Carbon-Kernel Carbon-Platform #90 failed. --- This build occurred because it is a dependant of WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-43. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-90/ -- Failing Jobs -- - Default Job (Default Stage): 4817 tests passed. -- Code Changes -- lalaji (121574): Updated index.jss file dilshan (121599): Command line and war upload changes madhuka (121581): Added getting Key for subscriber -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Compilation failure in system test framework.
Fixed all package naming convention violations. Thanks for pointing this out. Thanks, Krishantha. On Sat, Feb 25, 2012 at 3:35 PM, Afkham Azeez az...@wso2.com wrote: On a side note, I see coding convention violations. Package names should be all lower case, with no _ or - separation -- Afkham Azeez Sent from my phone On Feb 25, 2012 1:17 AM, Krishantha Samaraweera krishan...@wso2.com wrote: Hi All, I see very obvious compilation failure in system-test-framework trunk [1]. This is the second time I came across with such an issue for last two days. Charitha also got a compilation failure while building the framework trunk yesterday. We all need to follow best practices before committing changes. Please make sure to build the framework or run all the test relevant to your domain before you commit. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project system-stratos-test-auto: Compilation failure [ERROR] /home/krishantha/svn/trunk/graphite/platform-integration/system-test-framework/scenario/org.wso2.stratos.test.auto/src/test/java/org/wso2/stratos/automation/test/esb/mediators/test/MediatorTest.java:[418,47] sendReceive(org.apache.axiom.om.OMElement,java.lang.String,java.lang.String) in org.wso2.platform.test.core.utils.axis2Client.AxisServiceClient cannot be applied to (org.apache.axiom.om.OMElement,java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String) Thanks, Krishantha. [1] https://svn.wso2.org/repos/wso2/trunk/graphite/platform-integration/system-test-framework ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mediator for Complex SOAP Processing
You can simply use existing XSLT mediator to create new soap message.. -Ratha On 28 February 2012 19:16, metin d met...@yahoo.com wrote: I want to deploy a mediator on ESB. It will take SOAP messages as input and by using some parts of it, it will create new SOAP messages, send them, get response and according to responses create and send new SOAP messages and finally return a response to base request. Is creating such as mediator possible in ESB? If yes, do you have any example ? Thanks. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] TestNG tests fails due to:Port 9443 is not open
Hi, its due to old carbon-kernel (some recent commits missing), working now after getting an update in carbon-kernel. subash is running the integration tests. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #90 has FAILED. Change made by 12 authors.
bamboo build ordering issue. platform have got built before the kernel. should be fixed once the new kernel gets built. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Tomcat Osgification issue
A simple CXF webapp which was working earlier doesn't work on trunk now.
Following is the exception. There's an additional '/' in the jndi resource
it's trying to load. But I'm not sure how this is related to Tomcat
OSgification. I'm looking into this, but please let me know if anyone has
an idea about the root cause.
[2012-02-28 19:02:18,958] INFO
{org.springframework.web.context.support.XmlWebApplicationContext} -
Refreshing Root WebApplicationContext: startup date [Tue Feb 28 19:02:18
IST 2012]; parent: Root WebApplicationContext
[2012-02-28 19:02:18,959] INFO
{org.springframework.beans.factory.xml.XmlBeanDefinitionReader} - Loading
XML bean definitions from ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]
Feb 28, 2012 7:02:18 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
org.springframework.beans.factory.BeanDefinitionStoreException: IOException
parsing XML document from ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]; nested exception is
java.io.FileNotFoundException: Could not open ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
Thanks,
~Isuru
--
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Tomcat Osgification issue
Isuru,
The JNDI url looks invalid to me. It should be something in the line of
jndi://localhost/cxf-library. assuming 'cxf-library' is the name of the
war file.
AFAIR, part 'jndi' is referred as type binding in JNDI world.
So when you say earlier 'jndi:' is now appearing as '/jndi:', it is quite
possible that recognizing the type got screwed up when OSGification was
introduced.
Reading 'JNDI Services Specification' section in
http://www.osgi.org/Release4/Errata might help?
And also check slide number 13 in
http://www.slideshare.net/bosschaert/whats-newinos-gi42enterprise
May be how CXF should load cxf-servlet.xml needs to be changed. And, I
don't think this is CXF specific. If we have a war file doing same type of
resource loading through JNDI should re-produce the problem.
/sumedha
On Tue, Feb 28, 2012 at 8:44 PM, Isuru Suriarachchi is...@wso2.com wrote:
A simple CXF webapp which was working earlier doesn't work on trunk now.
Following is the exception. There's an additional '/' in the jndi resource
it's trying to load. But I'm not sure how this is related to Tomcat
OSgification. I'm looking into this, but please let me know if anyone has
an idea about the root cause.
[2012-02-28 19:02:18,958] INFO
{org.springframework.web.context.support.XmlWebApplicationContext} -
Refreshing Root WebApplicationContext: startup date [Tue Feb 28 19:02:18
IST 2012]; parent: Root WebApplicationContext
[2012-02-28 19:02:18,959] INFO
{org.springframework.beans.factory.xml.XmlBeanDefinitionReader} - Loading
XML bean definitions from ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]
Feb 28, 2012 7:02:18 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable
org.springframework.beans.factory.BeanDefinitionStoreException:
IOException parsing XML document from ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]; nested exception is
java.io.FileNotFoundException: Could not open ServletContext resource
[/jndi:/localhost/cxf-library/WEB-INF/cxf-servlet.xml]
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:341)
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
Thanks,
~Isuru
--
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #91 was SUCCESSFUL (with 4817 tests). Change made by 9 authors.
--- Carbon-Kernel Carbon-Platform #91 was successful. --- This build occurred because it is a dependant of WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-44. 4817 tests in total. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-91/ -- Code Changes -- tharindu (121612): modifying fault detection sample johann (121625): Commiting pom for api-mgt-bam ajithn (121614): Adding registry service -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Tomcat Osgification issue
Hi, we should reproduce the issue with a simple hello world web app. debugging with cxf app is bit difficult. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Products #23 has FAILED (17 tests failed, 1 failures were new). Change made by 13 authors.
--- Carbon-Kernel Carbon-Products #23 failed. --- This build occurred because it is a dependant of WSO2CARBONKERNEL-GRAPHITEBUILD-91. 17/157 tests failed, 1 failure was new. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONPRODUCTS-23/ -- Failing Jobs -- - Default Job (Default Stage): 17 of 157 tests failed. -- Code Changes -- tharindu (121612): modifying fault detection sample dilshan (121599): Command line and war upload changes krishantha (121628): code refactoring to fix vialation of package naming convention -- Tests -- New Test Failures (1) - MBTestServerManager: Start server Existing Test Failures (16) - CEPTestServerManager: Start server - DSSTestServerManager: Start server - GSTestServerManager: Start server - MSTestServerManager: Stop server - MashupAdminTestCase: Save mashup service source - EmailHostObjectTestCase: Email - FileHostObjectTestCase: File - HttpClientHostObjectTestCase: Search google - RequestHostObjectTestCase: Test remote ip - RequestHostObjectTestCase: Test invoked url - ScrapperHostObjectTestCase: Scrap - SessionHostObjectTestCase: Put value - SystemHostObjectTestCase: Log a string - SystemHostObjectTestCase: Include js file - SystemHostObjectTestCase: Wait some time - SystemHostObjectTestCase: Local host name Fixed Tests (1) - GreetingServiceDeploymentTestCase: Call greet -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #45 has FAILED (1 tests failed). Change made by dinusha.
--- Carbon-Kernel Carbon-Kernel #45 failed. --- This build occurred because it is a dependant of WSO2CARBONKERNEL-CARBONKERNELBUILD-16. 1/2784 tests failed. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/ -- Failing Jobs -- - Default Job (Default Stage): 1 of 2784 tests failed. -- Code Changes -- dinusha (121638): Remove atomikos transaction manager related code from carbon core. -- Tests -- New Test Failures (1) - ServerRestartTestCase: Graceful server restart -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] looks like shindig needs to be built with tests?
got this error, [ERROR] Failed to execute goal on project shindig-gadgets: Could not resolve dependencies for project org.apache.shindig:shindig-gadgets:jar:2.5.0-SNAPSHOT: Could not find artifact org.apache.shindig:shindig-common:jar:tests:2.5.0-SNAPSHOT in diff_match_patch ( http://google-diff-match-patch.googlecode.com/svn/trunk/maven) - [Help 1] thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] looks like shindig needs to be built with tests?
yes, Regards, /Nuwan On Wed, Feb 29, 2012 at 5:23 AM, Supun Malinga sup...@wso2.com wrote: got this error, [ERROR] Failed to execute goal on project shindig-gadgets: Could not resolve dependencies for project org.apache.shindig:shindig-gadgets:jar:2.5.0-SNAPSHOT: Could not find artifact org.apache.shindig:shindig-common:jar:tests:2.5.0-SNAPSHOT in diff_match_patch ( http://google-diff-match-patch.googlecode.com/svn/trunk/maven) - [Help 1] thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Thanks Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * http://www.nuwanbando.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Products #24 has FAILED (17 tests failed, no failures were new). Change made by 5 authors.
--- Carbon-Kernel Carbon-Products #24 failed. --- Code has been updated by tharindu, sumedha, dinusha, nirmal, buddhikac. 17/157 tests failed, no failures were new. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONPRODUCTS-24/ -- Failing Jobs -- - Default Job (Default Stage): 17 of 157 tests failed. -- Code Changes -- nirmal (121633): AgentManagementServiceClient throws a message with the exception nirmal (121634): Making JVMAdaptor to try other available Agents, if it fails to start an instance in a particular Agent. dinusha (121642): Adding transaction-manager module to parent pom. -- Tests -- Existing Test Failures (17) - CEPTestServerManager: Start server - DSSTestServerManager: Start server - GSTestServerManager: Start server - MBTestServerManager: Start server - MSTestServerManager: Stop server - MashupAdminTestCase: Save mashup service source - EmailHostObjectTestCase: Email - FileHostObjectTestCase: File - HttpClientHostObjectTestCase: Search google - RequestHostObjectTestCase: Test remote ip - RequestHostObjectTestCase: Test invoked url - ScrapperHostObjectTestCase: Scrap - SessionHostObjectTestCase: Put value - SystemHostObjectTestCase: Log a string - SystemHostObjectTestCase: Include js file - SystemHostObjectTestCase: Wait some time - SystemHostObjectTestCase: Local host name -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] looks like shindig needs to be built with tests?
On Tue, Feb 28, 2012 at 4:47 PM, Nuwan Bandara nu...@wso2.com wrote: yes, I see.. Thought we got rid of this limitation. thanks, Regards, /Nuwan On Wed, Feb 29, 2012 at 5:23 AM, Supun Malinga sup...@wso2.com wrote: got this error, [ERROR] Failed to execute goal on project shindig-gadgets: Could not resolve dependencies for project org.apache.shindig:shindig-gadgets:jar:2.5.0-SNAPSHOT: Could not find artifact org.apache.shindig:shindig-common:jar:tests:2.5.0-SNAPSHOT in diff_match_patch ( http://google-diff-match-patch.googlecode.com/svn/trunk/maven) - [Help 1] thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Thanks Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * http://www.nuwanbando.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] looks like shindig needs to be built with tests?
Shindig is directly taken from Apache trunk we haven't branched it, we need their most recent changes for OS 2.0 On Wed, Feb 29, 2012 at 6:48 AM, Supun Malinga sup...@wso2.com wrote: On Tue, Feb 28, 2012 at 4:47 PM, Nuwan Bandara nu...@wso2.com wrote: yes, I see.. Thought we got rid of this limitation. thanks, Regards, /Nuwan On Wed, Feb 29, 2012 at 5:23 AM, Supun Malinga sup...@wso2.com wrote: got this error, [ERROR] Failed to execute goal on project shindig-gadgets: Could not resolve dependencies for project org.apache.shindig:shindig-gadgets:jar:2.5.0-SNAPSHOT: Could not find artifact org.apache.shindig:shindig-common:jar:tests:2.5.0-SNAPSHOT in diff_match_patch ( http://google-diff-match-patch.googlecode.com/svn/trunk/maven) - [Help 1] thanks, -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Thanks Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * http://www.nuwanbando.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Supun Malinga, Software Engineer, WSO2 Inc. http://wso2.com http://wso2.org email - sup...@wso2.com sup...@wso2.com mobile - 071 56 91 321 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Thanks Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * http://www.nuwanbando.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #45 has FAILED (1 tests failed). Change made by dinusha.
Hi Pradeep, The testGracefulServerRestart test is failing with a login failed assertion error. Please have a look. java.lang.AssertionError: Login failed! at org.wso2.carbon.integration.framework.LoginLogoutUtil.login(LoginLogoutUtil.java:80) at org.wso2.carbon.integration.framework.ClientConnectionUtil.waitForLogin(ClientConnectionUtil.java:48) at org.wso2.carbon.integration.framework.utils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:103) at org.wso2.carbon.integration.framework.TestServerManager.startServer(TestServerManager.java:78) at org.wso2.carbon.integration.tests.CarbonTestServerManager.startServer(CarbonTestServerManager.java:47) at org.wso2.carbon.integration.tests.ServerRestartTestCase.startServerForRestartTest(ServerRestartTestCase.java:78) at org.wso2.carbon.integration.tests.ServerRestartTestCase.testGracefulServerRestart(ServerRestartTestCase.java:42) Regards, SanjayaV On Wed, Feb 29, 2012 at 3:52 AM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD/› #45http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/ failed This build occurred because it is a dependant of WSO2CARBONKERNEL-CARBONKERNELBUILD-16http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONKERNELBUILD-16 . *1/2784* tests failed. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-JOB1-45/ (Default Stage) 59 minutes 1 of 2784 failed Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-JOB1-45/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-JOB1-45/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/commit/ View full change detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/commit/ dinusha http://builder4.us1.wso2.org:/bamboo/browse/author/dinusha Remove atomikos transaction manager related code from carbon core. 121638 Testshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/test View full test detailshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45/test 1 New Test Failures Test Job ServerRestartTestCase testGracefulServerRestarthttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-JOB1-45/test/case/7637724 Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-JOB1-45/test View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-45?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sanjaya Vithanagama WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 342 2881 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #93 has FAILED. Change made by 4 authors.
--- Carbon-Kernel Carbon-Platform #93 failed. --- Code has been updated by tharindu, supunm, dinusha, buddhikac. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/ -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- supunm (121656): removing changes done for service-mgt as discussed on : [carbon-dev] changes in service listing page. dinusha (121642): Adding transaction-manager module to parent pom. tharindu (121650): completing analyzer docs -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Finalize all SVN moves create the new structure in Crucible
Hi Azeez, Its going be trunk/carbon/[kernel,orbit,platform]. We decided this after a offline discussion with Samisa. As per Samisa, in order to get the other structure, it might take quite a bit of effort. We hold this svn move, because of the build failures. Now that the Carbon kernel and platform builds are successful we can do it. Only the products are failing.. I will do this tonight. We need to freeze the trunk for 1 hour. Thanks, Sameera. On Tue, Feb 28, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: Folks, We need to finalize this. If it is going to be; carbon/kernel/[trunk/branches/tags] model we need to do it now. Changing the SVN structure from time to time screws up all other dependent tools we use. I'm in the middle of reviewing some components, and cannot continue since the SVN structure has changed. Who is going to own this? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Integration test failures in MB
Hi,
I get this error logs,
[2012-02-29 08:54:08,532] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
[2012-02-29 08:54:08,529] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - 'admin'
logged in at [2012-02-29 08:54:08,0529] from IP address 192.168.1.2
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.LoginLogoutUtil} - Successfully
logged in : JSESSIONID=74B141B181978C2B969957A8AFC7C94A; Path=/;
Secure=null; HttpOnly=null
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} - Server started
successfully.
[2012-02-29 08:54:08,625] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:09,626] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:10,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:11,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:12,628] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:13,629] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
server started on 9443. please have a look and if it is a problem with
carbon-core, please give me some context.
--Pradeep
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Finalize all SVN moves create the new structure in Crucible
We cannot keep changing the SVN structure from time to time. It messes up all other related systems we run. We might as well change it now or simply forget about it. -- Afkham Azeez Sent from my phone On Feb 29, 2012 8:16 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Azeez, Its going be trunk/carbon/[kernel,orbit,platform]. We decided this after a offline discussion with Samisa. As per Samisa, in order to get the other structure, it might take quite a bit of effort. We hold this svn move, because of the build failures. Now that the Carbon kernel and platform builds are successful we can do it. Only the products are failing.. I will do this tonight. We need to freeze the trunk for 1 hour. Thanks, Sameera. On Tue, Feb 28, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: Folks, We need to finalize this. If it is going to be; carbon/kernel/[trunk/branches/tags] model we need to do it now. Changing the SVN structure from time to time screws up all other dependent tools we use. I'm in the middle of reviewing some components, and cannot continue since the SVN structure has changed. Who is going to own this? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Integration test failures in MB
Here the test complains about the tcp port MB opens up for AMQP
communication.
Shammi was working on creating a MB product out of new broker dependency.
So looks like a broker 2 start-up issue.
Since we are in the process of merging new broker 2 features to the trunk.
You can expect this kind of a failures in the MB product for a while.
Will have a look.
thanks,
Charith
On Wed, Feb 29, 2012 at 8:56 AM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
I get this error logs,
[2012-02-29 08:54:08,532] INFO
{org.wso2.carbon.integration.framework.utils.InputStreamHandler} -
[2012-02-29 08:54:08,529] INFO
{org.wso2.carbon.core.services.util.CarbonAuthenticationUtil} - 'admin'
logged in at [2012-02-29 08:54:08,0529] from IP address 192.168.1.2
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.LoginLogoutUtil} - Successfully
logged in : JSESSIONID=74B141B181978C2B969957A8AFC7C94A; Path=/;
Secure=null; HttpOnly=null
[2012-02-29 08:54:08,609] INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} - Server started
successfully.
[2012-02-29 08:54:08,625] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:09,626] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:10,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:11,627] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:12,628] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
[2012-02-29 08:54:13,629] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 5672
server started on 9443. please have a look and if it is a problem with
carbon-core, please give me some context.
--Pradeep
--
Charith Dhanushka Wickramarachchi
Software Engineer
WSO2 Inc
http://wso2.com/
http://wso2.org/
blog
http://charithwiki.blogspot.com/
twitter
http://twitter.com/charithwiki
Mobile : 0776706568
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Finalize all SVN moves create the new structure in Crucible
Yes I agree. For Carbon 4.0.0, the plan is to have the following structure. trunk/carbon/[kernel,orbit,platform] Since the other structure takes a bit of time, we decided to delay it for Carbon 5.0.0. Thanks, Sameera. On Wed, Feb 29, 2012 at 9:08 AM, Afkham Azeez az...@wso2.com wrote: We cannot keep changing the SVN structure from time to time. It messes up all other related systems we run. We might as well change it now or simply forget about it. -- Afkham Azeez Sent from my phone On Feb 29, 2012 8:16 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Azeez, Its going be trunk/carbon/[kernel,orbit,platform]. We decided this after a offline discussion with Samisa. As per Samisa, in order to get the other structure, it might take quite a bit of effort. We hold this svn move, because of the build failures. Now that the Carbon kernel and platform builds are successful we can do it. Only the products are failing.. I will do this tonight. We need to freeze the trunk for 1 hour. Thanks, Sameera. On Tue, Feb 28, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: Folks, We need to finalize this. If it is going to be; carbon/kernel/[trunk/branches/tags] model we need to do it now. Changing the SVN structure from time to time screws up all other dependent tools we use. I'm in the middle of reviewing some components, and cannot continue since the SVN structure has changed. Who is going to own this? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] CEP integration test failures
7611 ( for SSL) and 7711 and the ports, Thrift server starts on CEP.
If the declarative service of the org.wso2.carbon.agent.server component
is not activated CEP's Thrift server won't start
Regards
Suho
On Wed, Feb 29, 2012 at 7:58 AM, Pradeep Fernando prad...@wso2.com wrote:
Hi,
i'm getting this error log.
[2012-02-29 00:54:10,639] INFO
{org.wso2.carbon.integration.framework.LoginLogoutUtil} - Successfully
logged in : JSESSIONID=7D09316AC27A87DF6EA115EC8F54C6F3; Path=/;
Secure=null; HttpOnly=null
[2012-02-29 00:54:10,639] INFO
{org.wso2.carbon.integration.framework.utils.ServerUtils} - Server started
successfully.
[2012-02-29 00:54:10,640] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 7611
[2012-02-29 00:54:11,641] INFO
{org.wso2.carbon.integration.framework.ClientConnectionUtil} - Waiting
until server starts on port 7611
can somebody please give me some context. what is this port. FYI, server
starts on 9443.
--Pradeep
--
*S. Suhothayan
*
Software Engineer,
Data Technologies Team,
*WSO2, Inc. **http://wso2.com
http://wso2.com/*
*lean.enterprise.middleware.*
*email: **s...@wso2.com* s...@wso2.com* cell: (+94) 779 756 757
blog: **http://suhothayan.blogspot.com/* http://suhothayan.blogspot.com/*
twitter: **http://twitter.com/suhothayan* http://twitter.com/suhothayan*
linked-in: **http://lk.linkedin.com/in/suhothayan*
*
*
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Finalize all SVN moves create the new structure in Crucible
What are these difficulties related to creating an svn structure? It is not as if some major feature needs to be implemented to wait for the next major release. -- Afkham Azeez Sent from my phone On Feb 29, 2012 9:15 AM, Sameera Jayasoma same...@wso2.com wrote: Yes I agree. For Carbon 4.0.0, the plan is to have the following structure. trunk/carbon/[kernel,orbit,platform] Since the other structure takes a bit of time, we decided to delay it for Carbon 5.0.0. Thanks, Sameera. On Wed, Feb 29, 2012 at 9:08 AM, Afkham Azeez az...@wso2.com wrote: We cannot keep changing the SVN structure from time to time. It messes up all other related systems we run. We might as well change it now or simply forget about it. -- Afkham Azeez Sent from my phone On Feb 29, 2012 8:16 AM, Sameera Jayasoma same...@wso2.com wrote: Hi Azeez, Its going be trunk/carbon/[kernel,orbit,platform]. We decided this after a offline discussion with Samisa. As per Samisa, in order to get the other structure, it might take quite a bit of effort. We hold this svn move, because of the build failures. Now that the Carbon kernel and platform builds are successful we can do it. Only the products are failing.. I will do this tonight. We need to freeze the trunk for 1 hour. Thanks, Sameera. On Tue, Feb 28, 2012 at 5:31 PM, Afkham Azeez az...@wso2.com wrote: Folks, We need to finalize this. If it is going to be; carbon/kernel/[trunk/branches/tags] model we need to do it now. Changing the SVN structure from time to time screws up all other dependent tools we use. I'm in the middle of reviewing some components, and cannot continue since the SVN structure has changed. Who is going to own this? -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * http://www.apache.org/** email: **az...@wso2.com* az...@wso2.com* cell: +94 77 3320919 blog: **http://blog.afkham.org* http://blog.afkham.org* twitter: **http://twitter.com/afkham_azeez*http://twitter.com/afkham_azeez * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware* -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware -- Sameera Jayasoma Technical Lead and Product Manager, WSO2 Carbon WSO2, Inc. (http://wso2.com) email: same...@wso2.com blog: http://tech.jayasoma.org Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [ANN] Jaggery Milestone-3 Released
Hi,
I was observing the start-up time in the M3 pack with gradual load. At the
addition of every 10 web apps I used to restart the server and check the
start-up time. The trend was as the table below. It was a flat trend within
11-13 secs.
After 100 webapp load, I restarted the machine and restarted the server.
This time the start-up delay was 22 secs. Any clue why this increase could
be?
# of webapps Server startup time (sec) Default server 2 11 With load
10 11 With
load 20 12 With load 30 12 With load 40 12 With load 50 12 With load 60
12 With load 70 13 With load 80 13 With load 90 12 With load 100 13 With
load after host is restarted 100 22
[image: Inline image 1]
Thanks,
Yumani
On Tue, Feb 28, 2012 at 5:31 PM, Nuwan Bandara nu...@wso2.com wrote:
Hi All,
Internally we have hosted the M3 pack at [1] welcome your feedback, and
please report the issues at [2]
[1] http://jaggery.private.wso2.com:9767/docs
[2] https://wso2.org/jira/browse/JAGGERY
-- Forwarded message --
From: Nuwan Bandara nu...@wso2.com
Date: Tue, Feb 28, 2012 at 5:29 PM
Subject: [ANN] Jaggery Milestone-3 Released
To: carbon-dev carbon-dev@wso2.org
*Introducing Jaggery*
Jaggery is a framework to write webapps and HTTP-focused web services for
all aspects of the application: front-end, communication, Server-side logic
and persistence in pure Javascript. One of the intents of this framework is
to reduce the gap between writing web apps and web services.
This Framework uses Mozilla Rhino to process Javascript at the server and
also contains a powerful caching layer with the support of Rhino compiled
scripts; so its as fast as the JVM. As few key features, Jaggery has native
JSON support and also E4X support for XML manipulation.
M3 can be downloaded at http://dist.wso2.org/products/jaggery/dl/jaggery
-1.0.0-SNAPSHOT_M3.zip
*Say Hello to Jaggery*
html
body
h1
%
var name = 'Jaggery';
print(Hello + name);
%
/h1
/body
/html
*Setting up Jaggery*
1. Extract jaggery-1.0.0-SNAPSHOT_M3.zip
2. This will generate a bin directory with execution scripts.
3. Run sh bin/wso2server.sh (bin/wso2server.bat) command to start the
server.
4. Upon successful startup, {http://localhost:9763/docs} should take
you to the documentation Jaggery App.
*Key Features*
- Compose server side scripts purely in javascript (.jss)
- Script caching support
- Script include support
- Module include support
- Command line tool for easy development
- Try-it tool for web based script validation
- Includes support for,
- HTTP request/response and session
- JSON send/receive
- Server side XMLHttpRequest
- URIMatcher
- Web Service invocation
- File I/O
- Email
- XSLT
- Atom
- Read/write feed
- Relational database
- WSO2 Registry/Repository
For more information and samples you can refer to Jaggery docs at (
http://{yourip}:9763/docs/documentation.jsshttp://localhost:9763/docs/documentation.jss
) which are shipped with the distribution
Thanks,
*Jaggery Development Team*
http://www.nuwanbando.com/
--
*Thanks Regards,
Nuwan Bandara
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware
http://nuwan.bandara.co
*
http://www.nuwanbando.com/
--
Yumani Ranaweera
Associate Technical Lead - QA
WSO2, Inc. - http://wso2.org
Email : yum...@wso2.com
Cell: +94 077 7795242
Blog : http://yumani.blogspot.com/
Screenshot-13.png___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #93 has FAILED. Change made by 4 authors.
Hi, This should be fixed with the revision 121667. I removed the atomikos module from carbon/core and could able to build it successfully since i'm not using a clean repo. Sorry for the inconvenience. Regards, Dinusha. On Wed, Feb 29, 2012 at 8:08 AM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Carbon-Platformhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #93http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/ failed Code has been updated by tharinduhttp://builder4.us1.wso2.org:/bamboo/browse/author/tharindu, supunm http://builder4.us1.wso2.org:/bamboo/browse/author/supunm, dinusha http://builder4.us1.wso2.org:/bamboo/browse/author/dinusha, buddhikachttp://builder4.us1.wso2.org:/bamboo/browse/author/buddhikac . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/ (Default Stage) Unknown No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit/ View all 13 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit/ supunm http://builder4.us1.wso2.org:/bamboo/browse/author/supunm removing changes done for service-mgt stub as discussed on : [carbon-dev] changes in service listing page. 121658 supunmhttp://builder4.us1.wso2.org:/bamboo/browse/author/supunm reverting back service-mgt to earlier version (removing changes in r120368) 121657 supunmhttp://builder4.us1.wso2.org:/bamboo/browse/author/supunm removing changes done for service-mgt as discussed on : [carbon-dev] changes in service listing page. 121656 10 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #93 has FAILED. Change made by 4 authors.
Hi Dinusha, Thanks for looking in to the failure. At the same time I noticed in the log (#93) that $CARBON_PLATFORM/components/service-mgt/org.wso2.carbon.service.mgt/src/test/resources refer to a non existing svn external location ( https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home). Someone from the AS team please have a look. Regards, SanjayaV. On Wed, Feb 29, 2012 at 10:05 AM, Dinusha Senanayaka dinu...@wso2.comwrote: Hi, This should be fixed with the revision 121667. I removed the atomikos module from carbon/core and could able to build it successfully since i'm not using a clean repo. Sorry for the inconvenience. Regards, Dinusha. On Wed, Feb 29, 2012 at 8:08 AM, Bamboo cbuil...@wso2.org wrote: [image: Failed] Carbon-Kernelhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL/› Carbon-Platformhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD/› #93http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/ failed Code has been updated by tharinduhttp://builder4.us1.wso2.org:/bamboo/browse/author/tharindu, supunm http://builder4.us1.wso2.org:/bamboo/browse/author/supunm, dinusha http://builder4.us1.wso2.org:/bamboo/browse/author/dinusha, buddhikachttp://builder4.us1.wso2.org:/bamboo/browse/author/buddhikac . No failed tests found, a possible compilation error. Failing Jobshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/ Job Duration Tests[image: Failed] Default Jobhttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/ (Default Stage) Unknown No tests found Logshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/log| Artifactshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-93/artifact Code Changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit/ View all 13 code changeshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit/ supunm http://builder4.us1.wso2.org:/bamboo/browse/author/supunm removing changes done for service-mgt stub as discussed on : [carbon-dev] changes in service listing page. 121658 supunmhttp://builder4.us1.wso2.org:/bamboo/browse/author/supunm reverting back service-mgt to earlier version (removing changes in r120368) 121657 supunmhttp://builder4.us1.wso2.org:/bamboo/browse/author/supunm removing changes done for service-mgt as discussed on : [carbon-dev] changes in service listing page. 121656 10 more changes…http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93/commit View Onlinehttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93 | Add Commentshttp://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-93?commentMode=true This message was sent by Atlassian Bamboohttp://builder4.us1.wso2.org:/bamboo . If you wish to stop receiving these emails edit your user profilehttp://builder4.us1.wso2.org:/bamboo/profile/userNotifications.actionor notify your administratorhttp://builder4.us1.wso2.org:/bamboo/viewAdministrators.action . ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Sanjaya Vithanagama WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 71 342 2881 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #94 has FAILED. Change made by supunm.
--- Carbon-Kernel Carbon-Platform #94 failed. --- Code has been updated by supunm. No failed tests found, a possible compilation error. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-GRAPHITEBUILD-94/ -- Failing Jobs -- - Default Job (Default Stage): No tests found. -- Code Changes -- supunm (121659): reverting back service-mgt stub to earlier version(r120366) -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Mediator for Complex SOAP Processing
Or you can use the enrich mediator. Rajika On Tue, Feb 28, 2012 at 8:18 PM, Vijayaratha Vijayasingam rat...@wso2.comwrote: You can simply use existing XSLT mediator to create new soap message.. -Ratha On 28 February 2012 19:16, metin d met...@yahoo.com wrote: I want to deploy a mediator on ESB. It will take SOAP messages as input and by using some parts of it, it will create new SOAP messages, send them, get response and according to responses create and send new SOAP messages and finally return a response to base request. Is creating such as mediator possible in ESB? If yes, do you have any example ? Thanks. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] All Jaggery based implementations can now move to stable M3
Hi Folks, Since there are alot of Jaggery based implementations happening on top of Jaggery M1 and M2, It would be ideal if all the teams move to Jaggery M3 (Latest). Mainly in M3, the API is changed, and it is stable. we have finalized almost all the peices of Jaggery core and there wont be any drastic changes to the API in coming releases. The complete API is documented at [1] and if there are any issues, the Jaggery team is happy to assist. [1] http://jaggery.private.wso2.com:9767/docs/documentation.jss -- *Thanks Regards, Nuwan Bandara Senior Software Engineer WSO2 Inc. | http://wso2.com lean . enterprise . middleware http://nuwan.bandara.co * http://www.nuwanbando.com/ ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Update] JVM Autoscaler
Hi, I have few other concerns to get clarified and few thoughts. 1. Original design was to spawn EC2 instances after the number of live instances exceed a threshold value (eg: 25). What if we spawn an EC2 instance only if we failed to spawn a JVM instance in any Agent? As far as I see, the latter may be bit inefficient but cost effective (since we're not spawning an EC2 instance when we can spawn a JVM instance). 2. What's the standard way of specifying Agent's working directory? I thought of adding it to the autoscaler_agent_config.xml. Please see [a]. 3. How to specify the path to the autoscaler_agent_config.xml? Currently it is hard coded. 4. How to let AutoscalerService know the EPR of the AgentManagementService? Currently it is hard coded. Is it good to assume that both autoscaler service and agent management service are hosted in one location, and deriving the EPR of the AgentManagementService? 5. Agent should be smart enough to decide whether it can spawn a new JVM instance, i.e. whether it has the minimum required memory etc. available. What about using Dileepa's boot-up validator component for this purpose? [a] !-- This file should specify all the Agent related configuration details. -- agentConfig !-- This points to the place where helper services such as AgentManagementService and AutoscalerService hosted. -- autoscalerHost url=http://localhost:8080/axis2/services// !-- Following element should points to the working directory of this Agent. This is the directory where Agent will copy the extratcted carbon-home directories when a new instance is spawned.-- workingDir path=/home/nirmal/Documents/autoscaler/work// !-- image element contains the details of the image. Each image element should have two attributes. 1. path: path to the image. 2. domain: domain this particular image belongs to. -- image path=/home/nirmal/Documents/autoscaler/wso2as-4.1.0-SNAPSHOT.zip domain=wso2.as.domain/ image path=/home/nirmal/Desktop/wso2cep-4.1.0-SNAPSHOT.zip domain=wso2.cep.domain/ /agentConfig On Mon, Feb 27, 2012 at 9:56 AM, Nirmal Fernando nir...@wso2.com wrote: Hi, Please find the sequence type of diagram of starting instance scenario, attached herewith. On Wed, Feb 22, 2012 at 12:36 PM, Afkham Azeez az...@wso2.com wrote: On Wed, Feb 22, 2012 at 9:50 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: On Wed, Feb 22, 2012 at 8:27 AM, Nirmal Fernando nir...@wso2.com wrote: Hi Shankar, On Wed, Feb 22, 2012 at 8:12 AM, Selvaratnam Uthaiyashankar shan...@wso2.com wrote: Hi Nirmal, On Tue, Feb 21, 2012 at 11:04 AM, Nirmal Fernando nir...@wso2.com wrote: On Tue, Feb 21, 2012 at 10:18 AM, Nirmal Fernando nir...@wso2.com wrote: Hi All, I need your views on following. In the Agent side we need to have a configuration file (say instances_config.xml) which specifies the paths and names of the instances belong to domains. I thought to have following structure: Value of the path attribute should change like this: domain name=wso2.as.domain instance name=wso2as-4.1.0-SNAPSHOT path=/home/nirmal/Desktop/wso2as-4.1.0-SNAPSHOT/bin/wso2server.sh/ instance name=wso2as-4.1.0-SNAPSHOT path=/home/nirmal/Temp/wso2as-4.1.0-SNAPSHOT/bin/wso2server.sh/ . /domain domain name=wso2.bps.domain instance name=wso2bps-4.1.0-SNAPSHOT path=/home/nirmal/Desktop/wso2bps-4.1.0-SNAPSHOT/bin/wso2server.sh/ instance name=wso2bps-4.1.0-SNAPSHOT path=/home/nirmal/Temp/wso2bps-4.1.0-SNAPSHOT/bin/wso2server.sh/ . /domain What are these two instances? Why they should be in the configuration file? If they are the paths of instances that can be started, then if I want to start a third instance what should I do? Agents should know the instances that it can spawn. Thus, each Agent machine has a configuration file which points to those instances. An Agent can only spawn instances it has. This configuration file will be loaded each time an Agent get registered. So if you want to add a new instance, you can unregister the Agent, edit the configuration file and re-register. Then the Agent Service will locate the newly added instance and list it as an instance that can be spawned. This might become a maintanance problem. Suppose I have a machine which can run 5 instance of stratos service. This service can be ESB, AppServer, GS, MS, Manager, We have 13 service, so I have to give 13 * 5 configuration. I would like to give the location of binary pack location for 13 services, and when an instance is required, agent can copy the pack into its working directory and run it. So, actual instance location is not needed and will be handled by agent. This is the normal way most of the software work (e.g. eucalyptus). In this method, the configuration for all JVM autoscale agent
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #46 has FAILED (1 tests failed). Change made by dinusha.
--- Carbon-Kernel Carbon-Kernel #46 failed. --- Code has been updated by dinusha. 1/2784 tests failed. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-46/ -- Failing Jobs -- - Default Job (Default Stage): 1 of 2784 tests failed. -- Code Changes -- dinusha (121667): Fixing carbon kernel build failure. -- Tests -- New Test Failures (1) - MultipleCarbonInstancesTestCase: Start servers Fixed Tests (1) - ServerRestartTestCase: Graceful server restart -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Update] JVM Autoscaler
On Wed, Feb 29, 2012 at 11:41 AM, Nirmal Fernando nir...@wso2.com wrote: 4. How to let AutoscalerService know the EPR of the AgentManagementService? Currently it is hard coded. Is it good to assume that both autoscaler service and agent management service are hosted in one location, and deriving the EPR of the AgentManagementService? You can specify two different URLs. Ok, but how to let AutoscalerService know the EPR of the AgentManagementService? It does not need to know. I think both services can run in the same runtime, and share a single data structure for sharing the agents. Both the services can be within the same OSGi bundle. ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Orbit build failed in trunk
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge between
'Vertex{label='com.jezhumble.wso2:javasysmon'}' and
'Vertex{label='com.jezhumble.wso2:javasysmon'}' introduces to cycle in the
graph com.jezhumble.wso2:javasysmon -- com.jezhumble.wso2:javasysmon
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94714631794
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Axis2-aar maven plugin : How to exclude a particular dependency from a AAR file
Hi, $subject ? I tried to use excludes in the plugin and it does not affects for dependencies. Also just tried by setting includeDependenciesfalse/includeDependencies and then the lib not get created. Is there a way to do this ? Thanks -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Drools Guvnor can be used with Business rule server
Hi, How this going to get integrated to carbon-platfrom. we ourselves have a repository component in carbon-platform. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Platform #94 has FAILED. Change made by supunm.
Hi Supun, Please have a look at the svn-external location which is pointing to an invalid URL; Clean up of '/home/bamboo/Bamboo-3.4/source-repository/build-dir/WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1/components/service-mgt/org.wso2.carbon.service.mgt/src/test/resources/carbon-home' completed 28-Feb-2012 21:01:59 Failed to clean up Subversion workspace for WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1-94, reason: too many directories to clean up 28-Feb-2012 21:01:59 Error occurred while running Task 'Checkout Default Repository(1)'. This build will fail. Caused by: 28-Feb-2012 21:01:59 java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: Unable to retrieve source code for revision '121661', plan 'WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1': svn: URL '* https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home*' at revision 121672 doesn't exist 28-Feb-2012 21:01:59 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:119) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.executor.RetryingTaskExecutor.runTask(RetryingTaskExecutor.java:79) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.executor.RetryingTaskExecutor.retry(RetryingTaskExecutor.java:174) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.execute(VcsCheckoutTask.java:97) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:180) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.task.TaskExecutorImpl.executePreparationTasks(TaskExecutorImpl.java:64) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.build.pipeline.tasks.PrepareBuildTask.call(PrepareBuildTask.java:66) 28-Feb-2012 21:01:59 at sun.reflect.GeneratedMethodAccessor953.invoke(Unknown Source) 28-Feb-2012 21:01:59 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 28-Feb-2012 21:01:59 at java.lang.reflect.Method.invoke(Method.java:597) 28-Feb-2012 21:01:59 at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304) 28-Feb-2012 21:01:59 at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) 28-Feb-2012 21:01:59 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) 28-Feb-2012 21:01:59 at org.springframework.orm.hibernate.HibernateInterceptor.invoke(HibernateInterceptor.java:117) 28-Feb-2012 21:01:59 at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) 28-Feb-2012 21:01:59 at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) 28-Feb-2012 21:01:59 at $Proxy479.call(Unknown Source) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:198) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:103) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:107) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:50) 28-Feb-2012 21:01:59 at java.lang.Thread.run(Thread.java:662) 28-Feb-2012 21:01:59 Caused by: com.atlassian.bamboo.repository.RepositoryException: Unable to retrieve source code for revision '121661', plan 'WSO2CARBONKERNEL-GRAPHITEBUILD-JOB1': svn: URL ' https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home' at revision 121672 doesn't exist 28-Feb-2012 21:01:59 at com.atlassian.bamboo.repository.svn.SvnRepository.retrieveSourceCode(SvnRepository.java:530) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.checkoutCode(VcsCheckoutTask.java:153) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask.access$100(VcsCheckoutTask.java:41) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$1.call(VcsCheckoutTask.java:102) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.plugins.vcs.task.VcsCheckoutTask$1.call(VcsCheckoutTask.java:98) 28-Feb-2012 21:01:59 at com.atlassian.bamboo.executor.RetryingTaskExecutor.rerun(RetryingTaskExecutor.java:100) 28-Feb-2012 21:01:59 ... 21 more 28-Feb-2012 21:01:59 Caused by: com.atlassian.bamboo.repository.svn.ExternalsLockException: svn: URL ' https://svn.wso2.org/repos/wso2/trunk/carbon/core/distribution/carbon-home' at revision 121672 doesn't exist 28-Feb-2012 21:01:59 at com.atlassian.bamboo.repository.svn.UpdateEventHandler.handleEvent(UpdateEventHandler.java:87) 28-Feb-2012 21:01:59 at
Re: [Carbon-dev] Orbit build failed in trunk
On Wed, Feb 29, 2012 at 11:54 AM, Ajith Vitharana aji...@wso2.com wrote:
[ERROR] BUILD FAILURE
[INFO]
[INFO] The projects in the reactor contain a cyclic reference: Edge
between 'Vertex{label='com.jezhumble.wso2:javasysmon'}' and
'Vertex{label='com.jezhumble.wso2:javasysmon'}' introduces to cycle in the
graph com.jezhumble.wso2:javasysmon -- com.jezhumble.wso2:javasysmon
Sorry , I forgot to switch maven3 , after building a previous branch.
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94714631794
--
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email : aji...@wso2.com
Mobile : +94714631794
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] [Bamboo-Build] Carbon-Kernel Carbon-Kernel #47 has FAILED (1 tests failed, no failures were new)
--- Carbon-Kernel Carbon-Kernel #47 failed. --- This build occurred because it is a dependant of WSO2CARBONKERNEL-CARBONKERNELBUILD-17. 1/2778 tests failed, no failures were new. http://builder4.us1.wso2.org:/bamboo/browse/WSO2CARBONKERNEL-CARBONCOREKERNELBUILD-47/ -- Failing Jobs -- - Default Job (Default Stage): 1 of 2778 tests failed. -- Tests -- Existing Test Failures (1) - MultipleCarbonInstancesTestCase: Start servers -- This message is automatically generated by Atlassian Bamboo___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] {org.wso2.carbon.core.bootup.validator.internal.BootupValidationActivator} - Bootup Validator is activated...
Should be a debug level log. Rajika ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Synapse in trunk still points to frozen branch
Hi all, carbon/trunk/graphite/dependencies/synapse/2.1.0-wso2v5 points to carbon/3.2.0/dependencies/synapse/2.1.0-wso2v5 which is frozen after 3.2.3 release. So currently it's not possible to commit synapse fixes to carbon trunk. We have 2 options 1. copy carbon/3.2.0/dependencies/synapse/2.1.0-wso2v5 to carbon/trunk/graphite/dependencies/synapse with new synapse version (2.1.0-wso2v6) 2. point synapse to apache trunk WDYT? -- Thanks, Miyuru ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Axis2-aar maven plugin : How to exclude a particular dependency from a AAR file
Basically you have to make sure that your maven class path only has the needed set of dependencies. Try a mvn dependency:tree and exclude what is not needed. Thanks, ~Isuru On Wed, Feb 29, 2012 at 11:56 AM, Subash Chaturanga sub...@wso2.com wrote: Hi, $subject ? I tried to use excludes in the plugin and it does not affects for dependencies. Also just tried by setting includeDependenciesfalse/includeDependencies and then the lib not get created. Is there a way to do this ? Thanks -- Subash Chaturanga Software Engineer WSO2 Inc. http://wso2.com email - sub...@wso2.com phone - 077 2225922 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
[Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
Hi Folks,
I am experiencing this error time to time. But cannot reproduce it
consistently. In the next restart, this error does not appear.
[2012-02-29 12:26:39,763] INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Registry Mode: READ-WRITE
org.osgi.framework.BundleException: The activator
org.wso2.identity.styles.internal.Activator for bundle
org.wso2.identity.styles is invalid
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:291)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.applyConfiguration(ProfileSynchronizer.java:781)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:134)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:461)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:176)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException:
org.wso2.identity.styles.internal.Activator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:164)
... 27 more
[2012-02-29 12:26:41,609] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Starting Carbon
initialization...
Thanks,
Thilina
--
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Axis2-aar maven plugin : How to exclude a particular dependency from a AAR file
Or else you can use external dependencies which are somewhere on the file
system as follows.
plugin
groupIdorg.apache.axis2/groupId
artifactIdaxis2-aar-maven-plugin/artifactId
version1.6-wso2v3/version
extensionstrue/extensions
configuration
aarNameCalculator/aarName
fileSets
fileSet
directory
/home/isuru/foo/bar
/directory
outputDirectorylib/outputDirectory
includes
includecal-dep-1.0.0.jar/include
/includes
/fileSet
/fileSets
/configuration
executions
execution
idcreate-aar1/id
phaseinstall/phase
goals
goalaar/goal
/goals
configuration
aarName
Calculator
/aarName
servicesXmlFile
${basedir}/src/main/resources/META-INF/services.xml
/servicesXmlFile
includeDependenciesfalse/includeDependencies
/configuration
/execution
/executions
/plugin
~Isuru
On Wed, Feb 29, 2012 at 12:29 PM, Isuru Suriarachchi is...@wso2.com wrote:
Basically you have to make sure that your maven class path only has the
needed set of dependencies. Try a mvn dependency:tree and exclude what is
not needed.
Thanks,
~Isuru
On Wed, Feb 29, 2012 at 11:56 AM, Subash Chaturanga sub...@wso2.comwrote:
Hi,
$subject ?
I tried to use excludes in the plugin and it does not affects for
dependencies. Also just tried by setting
includeDependenciesfalse/includeDependencies and then the lib not get
created.
Is there a way to do this ?
Thanks
--
Subash Chaturanga
Software Engineer
WSO2 Inc. http://wso2.com
email - sub...@wso2.com
phone - 077 2225922
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
--
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
--
Isuru Suriarachchi
Technical Lead
WSO2 Inc. http://wso2.com
email : is...@wso2.com
blog : http://isurues.wordpress.com/
lean . enterprise . middleware
___
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
I also experienced the same yesterday and I thought it's because I've
installed some external bundles on my carbon instance. Looks like a bundle
ordering issue.
~Isuru
On Wed, Feb 29, 2012 at 12:31 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
I am experiencing this error time to time. But cannot reproduce it
consistently. In the next restart, this error does not appear.
[2012-02-29 12:26:39,763] INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Registry Mode: READ-WRITE
org.osgi.framework.BundleException: The activator
org.wso2.identity.styles.internal.Activator for bundle
org.wso2.identity.styles is invalid
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:291)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.applyConfiguration(ProfileSynchronizer.java:781)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:134)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:461)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:176)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException:
org.wso2.identity.styles.internal.Activator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:164)
... 27 more
[2012-02-29 12:26:41,609] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Starting Carbon
initialization...
Thanks,
Thilina
--
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware
phone : +94 77 44 88 727
blog : http://blog.thilinamb.com
___
Carbon-dev mailing list
Carbon-dev@wso2.org
Re: [Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
Actually this started appearing after I copied some bundles into the
dropins directory.
Thanks,
Thilina
On Wed, Feb 29, 2012 at 12:33 PM, Isuru Suriarachchi is...@wso2.com wrote:
I also experienced the same yesterday and I thought it's because I've
installed some external bundles on my carbon instance. Looks like a bundle
ordering issue.
~Isuru
On Wed, Feb 29, 2012 at 12:31 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
I am experiencing this error time to time. But cannot reproduce it
consistently. In the next restart, this error does not appear.
[2012-02-29 12:26:39,763] INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Registry Mode: READ-WRITE
org.osgi.framework.BundleException: The activator
org.wso2.identity.styles.internal.Activator for bundle
org.wso2.identity.styles is invalid
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:291)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.applyConfiguration(ProfileSynchronizer.java:781)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:134)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:461)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:176)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException:
org.wso2.identity.styles.internal.Activator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:164)
... 27 more
[2012-02-29 12:26:41,609] INFO
{org.wso2.carbon.core.init.CarbonServerManager} - Starting Carbon
initialization...
Thanks,
Thilina
--
Thilina Buddhika
Associate Technical Lead
WSO2 Inc. ; http://wso2.com
Re: [Carbon-dev] {org.wso2.carbon.core.bootup.validator.internal.BootupValidationActivator} - Bootup Validator is activated...
Hi Rajika, Changed the log level to DEBUG for this initial message. Committed to revision 121687 Thanks, Dileepa On Wed, Feb 29, 2012 at 12:24 PM, Rajika Kumarasiri raj...@wso2.com wrote: Should be a debug level log. Rajika ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Dileepa Jayakody, Software Engineer, WSO2 Inc. Lean . Enterprise . Middleware Mobile : +94777-857616 ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
On Wed, Feb 29, 2012 at 12:39 PM, Thilina Buddhika thili...@wso2.comwrote:
Actually this started appearing after I copied some bundles into the
dropins directory.
I did the same. So may be that's how to reproduce..
Thanks,
Thilina
On Wed, Feb 29, 2012 at 12:33 PM, Isuru Suriarachchi is...@wso2.comwrote:
I also experienced the same yesterday and I thought it's because I've
installed some external bundles on my carbon instance. Looks like a bundle
ordering issue.
~Isuru
On Wed, Feb 29, 2012 at 12:31 PM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
I am experiencing this error time to time. But cannot reproduce it
consistently. In the next restart, this error does not appear.
[2012-02-29 12:26:39,763] INFO
{org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent} -
Registry Mode: READ-WRITE
org.osgi.framework.BundleException: The activator
org.wso2.identity.styles.internal.Activator for bundle
org.wso2.identity.styles is invalid
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:171)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:679)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:299)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:291)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.startBundles(ConfigApplier.java:307)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplier.install(ConfigApplier.java:108)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:129)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfiguratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:143)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.applyConfiguration(ProfileSynchronizer.java:781)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.ProfileSynchronizer.synchronize(ProfileSynchronizer.java:134)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.synchronize(Activator.java:461)
at
org.eclipse.equinox.internal.p2.reconciler.dropins.Activator.start(Activator.java:176)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.ClassNotFoundException:
org.wso2.identity.styles.internal.Activator
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
at
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:345)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadBundleActivator(AbstractBundle.java:164)
... 27 more
[2012-02-29 12:26:41,609] INFO
{org.wso2.carbon.core.init.CarbonServerManager}
Re: [Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
we have to get rid of the styles.Activator class. No use. Try removing it and see. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
Re: [Carbon-dev] Random Error in IS Start Up - The activator org.wso2.identity.styles.internal.Activator for bundle org.wso2.identity.styles is invalid
Hi Pradeep, This would solve the issue related to the styles bundle, but I too noticed an error in trunk, where when you add bundles into dropins (which were fragments), other bundles are throwing errors. That's probably a bug. Thanks, Senaka. On Wed, Feb 29, 2012 at 1:13 PM, Pradeep Fernando prad...@wso2.com wrote: we have to get rid of the styles.Activator class. No use. Try removing it and see. --Pradeep ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware ___ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
