You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Gert Vanthienen <ge...@gmail.com> on 2009/09/24 10:53:19 UTC
Re: Solved - had to use Java 1.5 (Re: Problem running
"WS-Notification Clustered example" - javax.naming.NameAlreadyBoundException)
Hi Brian,
No, ServiceMix should work fine on Java 6 as well -- we usually
develop using JDK 1.5 to ensure compatibility with that release, but
there is no reason why things should not work on a newer version. The
only thing that comes to mind with Java 6 and wsn, is a version
mismatch on the JAXB stuff (where the JDK itself also ships with a
version of JAXB), but even that should give you some kind of
LinkageError. Could you raise a JIRA issue for this, specifying what
your environment looks like, so we can look into it?
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/9/23 Brian Nielsen <br...@sweetxml.org>:
> Today I found out that it works with Java 1.5 (jdk1.5.0_09), but not with
> jdk-6u16 (i586 or x64) or IcedTea6 1.6
>
> I didn't expect this and I'm not sure it's real requirement that only 1.5
> works. In the "getting started" [1] there a requirement for environment:
>
> Java Developer Kit (JDK) 1.5.x (Java 5) for both deployment and compiling.
>
> Will Servicemix only work correctly with Java 1.5?
>
>
> Not that I've understood much yet, but the "NameAlreadyBoundException" was
> just a warning and not a blocking problem. Do notice that I didn't stumble
> upon any extra exceptions it just hanged.
>
> Brgds
> Brian
>
>
> [1] http://servicemix.apache.org/getting-started.html
>
>
>
> Brian Nielsen wrote:
>>
>> Hi users@servicemix.apache.org
>>
>> I'm trying to run the "WS-Notification Clustered example" (
>> http://servicemix.apache.org/ws-notification-clustered.html ) but have only
>> failed so far and would be very happy if someone could help me.
>>
>> I run upon "javax.naming.NameAlreadyBoundException". As far as I can see
>> there's no current reports on this kind of problem. Last year the was a
>> similar problem with the 'basic' example
>> (http://cwiki.apache.org/SM/discussion-forums.html#nabble-td15306536|a15578363).
>>
>> It takes a little time before the warning comes. I don't have any services
>> running on port 1099. I've tried both with 'IcedTea' and the sun jdk, but
>> with same outcome.
>>
>> Here's an example of what i get i my concole windows
>>
>> $ ../../../bin/servicemix ./servicemix1.xml
>> servicemix: JAVA_HOME not set; results may vary
>> java version "1.6.0_0"
>> OpenJDK Runtime Environment (IcedTea6 1.6) (fedora-21.b16.fc10-x86_64)
>> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
>>
>> Starting Apache ServiceMix ESB: 3.3.1
>>
>> Loading Apache ServiceMix from file: ./servicemix1.xml
>> INFO - JBIContainer - ServiceMix 3.3.1 JBI Container
>> (wsn1) is starting
>> INFO - JBIContainer - For help or more information
>> please see: http://servicemix.apache.org/
>> INFO - ComponentMBeanImpl - Initializing component:
>> #SubscriptionManager#
>> INFO - DeploymentService - Restoring service assemblies
>> INFO - JBIContainer - ServiceMix JBI Container (wsn1)
>> started
>> INFO - ConnectorServerFactoryBean - JMX connector available at:
>> service:jmx:rmi:///jndi/rmi://localhost:1091/jmxrmi
>> WARN - ManagementContext - Failed to start jmx connector:
>> Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
>> javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
>> java.rmi.AlreadyBoundException: jmxrmi]
>>
>>
>>
>>
>> $ ../../../bin/servicemix ./servicemix2.xml
>> servicemix: JAVA_HOME not set; results may vary
>> java version "1.6.0_0"
>> OpenJDK Runtime Environment (IcedTea6 1.6) (fedora-21.b16.fc10-x86_64)
>> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
>>
>> Starting Apache ServiceMix ESB: 3.3.1
>>
>> Loading Apache ServiceMix from file: ./servicemix2.xml
>> INFO - JBIContainer - ServiceMix 3.3.1 JBI Container
>> (wsn2) is starting
>> INFO - JBIContainer - For help or more information
>> please see: http://servicemix.apache.org/
>> INFO - ComponentMBeanImpl - Initializing component:
>> #SubscriptionManager#
>> INFO - DeploymentService - Restoring service assemblies
>> INFO - ComponentMBeanImpl - Initializing component: trace
>> INFO - ComponentMBeanImpl - Initializing component:
>> servicemix-wsn2005
>> INFO - JBIContainer - ServiceMix JBI Container (wsn2)
>> started
>> INFO - ConnectorServerFactoryBean - JMX connector available at:
>> service:jmx:rmi:///jndi/rmi://localhost:1092/jmxrmi
>> WARN - ManagementContext - Failed to start jmx connector:
>> Cannot bind to URL [rmi://localhost:1099/jmxrmi]:
>> javax.naming.NameAlreadyBoundException: jmxrmi [Root exception is
>> java.rmi.AlreadyBoundException: jmxrmi]
>>
>>
>>
>> ../../../bin/servicemix ./servicemix3.xml
>> servicemix: JAVA_HOME not set; results may vary
>> java version "1.6.0_0"
>> OpenJDK Runtime Environment (IcedTea6 1.6) (fedora-21.b16.fc10-x86_64)
>> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
>>
>> Starting Apache ServiceMix ESB: 3.3.1
>>
>> Loading Apache ServiceMix from file: ./servicemix3.xml
>> INFO - JBIContainer - ServiceMix 3.3.1 JBI Container
>> (wsn3) is starting
>> INFO - JBIContainer - For help or more information
>> please see: http://servicemix.apache.org/
>> INFO - ComponentMBeanImpl - Initializing component:
>> #SubscriptionManager#
>> INFO - DeploymentService - Restoring service assemblies
>> INFO - ComponentMBeanImpl - Initializing component:
>> servicemix-wsn2005
>> INFO - ComponentMBeanImpl - Initializing component:
>> publisher-proxy
>> INFO - ComponentMBeanImpl - Initializing component:
>> quartz-publisher
>> INFO - SimpleThreadPool - Job execution threads will use
>> class loader of thread: main
>> INFO - QuartzScheduler - Quartz Scheduler v.1.5.1 created.
>> INFO - RAMJobStore - RAMJobStore initialized.
>> INFO - StdSchedulerFactory - Quartz scheduler
>> 'DefaultQuartzScheduler' initialized from default resource file in Quartz
>> package: 'quartz.properties'
>> INFO - StdSchedulerFactory - Quartz scheduler version: 1.5.1
>> INFO - DeliveryChannelImpl - Set default destination endpoint
>> for quartz-publisher to
>> ServiceEndpoint[service={http://servicemix.org/test}publisher,endpoint=endpoint]
>> INFO - QuartzScheduler - Scheduler
>> DefaultQuartzScheduler_$_NON_CLUSTERED started.
>> INFO - JBIContainer - ServiceMix JBI Container (wsn3)
>> started
>> INFO - ConnectorServerFactoryBean - JMX connector available at:
>> service:jmx:rmi:///jndi/rmi://localhost:1093/jmxrmi
>>
>> Best regards
>> Brian
>>
>>
>>
>>
>>
>
>