newbie install question - errors running server
installed 1.0.2.
run gives me:
Starting WSO2 Mashup Server v1.0.2 (in JDK 1.5)
Using WSO2MASHUP_HOME: /Users/daniel/opt/wso2-mashup-server-1.0.2
Using JAVA_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
Start signal posted to WSO2 Mashup Server.
Please check the server's log file for startup status.
INFO [2008-04-01 09:05:11,210] Starting WSO2 Mashup Server 1.0.2 (Powered by Apache Axis2)
INFO [2008-04-01 09:05:11,214] Using Java Home : /System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home
INFO [2008-04-01 09:05:11,214] Using Java Version : 1.5.0_13
INFO [2008-04-01 09:05:11,214] Using WSO2 Mashup Server Home : /Users/daniel/opt/wso2-mashup-server-1.0.2
INFO [2008-04-01 09:05:14,330] Using Server Info Class: org.wso2.wsas.serverinfo.EmbeddedTomcatServerInfo
INFO [2008-04-01 09:05:21,822] Deploying module: addressing-1.35 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/addressing-1.35.mar
INFO [2008-04-01 09:05:21,873] Deploying module: rahas-1.35 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/rahas-1.35.mar
INFO [2008-04-01 09:05:21,906] Deploying module: rampart-1.35 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/rampart-1.35.mar
INFO [2008-04-01 09:05:22,017] Deploying module: DynamicResponseHandler-1.0 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2dynamic-response-1.0.mar
INFO [2008-04-01 09:05:22,049] Deploying module: wso2mashup-admin - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2mashup-adminModule.mar
INFO [2008-04-01 09:05:22,080] Deploying module: wso2mex-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2mex-2.2.mar
INFO [2008-04-01 09:05:22,377] Deploying module: sandesha2-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2sandesha2-persistence-2.2.mar
INFO [2008-04-01 09:05:22,390] Deploying module: wso2statistics-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2statistics-2.2.mar
INFO [2008-04-01 09:05:22,425] Deploying module: wso2throttle-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2throttle-2.2.mar
INFO [2008-04-01 09:05:22,451] Deploying module: wso2tracer-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2tracer-2.2.mar
INFO [2008-04-01 09:05:22,455] Deploying module: wso2wsas-admin-2.21 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2wsas-admin-2.21.mar
INFO [2008-04-01 09:05:22,482] Deploying module: wso2xfer-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/modules/wso2xfer-2.2.mar
INFO [2008-04-01 09:05:22,988] Deploying module: addressing-1.35 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/lib/axis2-1.35.jar
INFO [2008-04-01 09:05:23,021] Deploying module: wso2mex-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/lib/wso2mex-2.2.jar
INFO [2008-04-01 09:05:23,096] Deploying module: wso2xfer-2.2 - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/lib/wso2xfer-2.2.jar
INFO [2008-04-01 09:05:23,189] Job execution threads will use class loader of thread: Thread-1
INFO [2008-04-01 09:05:23,210] Quartz Scheduler v.1.5.2 created.
INFO [2008-04-01 09:05:23,212] RAMJobStore initialized.
INFO [2008-04-01 09:05:23,212] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
INFO [2008-04-01 09:05:23,212] Quartz scheduler version: 1.5.2
INFO [2008-04-01 09:05:23,213] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
INFO [2008-04-01 09:05:28,521] Deploying Web service: archive-validator.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/archive-validator.aar
INFO [2008-04-01 09:05:29,003] Deploying Web service: wsdlconverter.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wsdlconverter.aar
INFO [2008-04-01 09:05:29,048] Deploying Web service: wsdlview.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wsdlview.aar
INFO [2008-04-01 09:05:29,507] Deploying Web service: wso2codegen.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2codegen.aar
INFO [2008-04-01 09:05:29,574] Deploying Web service: wso2mashup-adminServices.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-adminServices.aar
INFO [2008-04-01 09:05:29,653] Deploying Web service: wso2mashup-coreservices-JSStubGenaratorService.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-coreservices-JSStubGenaratorService.aar
INFO [2008-04-01 09:05:29,673] Deploying Web service: wso2mashup-coreservices-servicemetadatalister.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-coreservices-servicemetadatalister.aar
INFO [2008-04-01 09:05:29,698] Deploying Web service: wso2mashup-coreservices-servicesharinghelper.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-coreservices-servicesharinghelper.aar
INFO [2008-04-01 09:05:29,868] Deploying Web service: wso2mashup-coreservices-sharingservice.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-coreservices-sharingservice.aar
INFO [2008-04-01 09:05:30,320] Deploying Web service: wso2mashup-scraperService.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2mashup-scraperService.aar
INFO [2008-04-01 09:05:30,826] Deploying Web service: wso2wsas-administration.aar - file:/Users/daniel/opt/wso2-mashup-server-1.0.2/services/wso2wsas-administration.aar
INFO [2008-04-01 09:05:32,183] Deploying Web service: digit2image.js - {1}
INFO [2008-04-01 09:05:32,552] Deploying Web service: storexml.js - {1}
INFO [2008-04-01 09:05:33,187] Deploying Web service: upgradeChecker.js - {1}
INFO [2008-04-01 09:05:33,767] Deploying Web service: version.js - {1}
INFO [2008-04-01 09:05:35,283]
INFO [2008-04-01 09:05:35,283] Repository : /Users/daniel/opt/wso2-mashup-server-1.0.2/
ERROR [2008-04-01 09:06:50,377] Could not initialize MBean server
java.io.IOException: Cannot bind to URL [rmi://169.254.157.224:7999/server]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: 169.254.157.224; nested exception is:
the list goes on...
Why is trying to bind to that address? My local I.P is 192.168.1.101 on en0.
ifconfig:
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::217:f2ff:fed0:9557%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.101 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:17:f2:d0:95:57
media: autoselect (100baseTX <full-duplex,flow-control>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
inet 169.254.157.224 netmask 0xffff0000 broadcast 169.254.255.255
lladdr 00:19:e3:ff:fe:6d:16:20
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
- Login or register to post comments
- Printer friendly version
- 561 reads











Are you using VMWare or a
Are you using VMWare or a similar virtualization solution in this machine? Sometimes Java confuses localhost IP address in such scenarios.
Nope - just plain old OSX.
Nope - just plain old OSX.
Can disable JMX and continue
Hi Daniel,
Looks like it's trying to retrieve the localhost IP and getting something unexpected. For now, you can simply disable the JMX by commenting out the <JMX>7999</JMX> line in the conf\server.xml file and your server should start without any problems.
We'll post further details to this thread.
Bye,
Channa.
Alright, that did it
Alright, that did it now.
INFO [2008-04-01 12:13:18,328] WSO2 Mashup Server started in 27401 ms
Looks like Java picked 169.254.157.224 as your prominent IP
Lookig at the output of ifconfig
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
inet 169.254.157.224 netmask 0xffff0000 broadcast 169.254.255.255
lladdr 00:19:e3:ff:fe:6d:16:20
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
Looks like Java picked 169.254.157.224 as your prominent IP. We'll try and reproduce this and come up with a workaround.
Thanks,
Keith.