You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by puneetjain <pu...@wipro.com> on 2008/01/24 16:25:48 UTC
problem while deploying servicemix-web-3.2.1.war on Jboss
Hi,
I am new with ServiceMix. I am trying to deploy servicemix example war on
jboss4.2.2.GA but i am getting some errors. I am explaining the steps i
followed:
1. I downloaded the jboss- deployer source and build it by maven and deploy
the servicemix-jbi container for jboss.
2. Now i am trying to deploy the example provided with servicemix package. I
got error that the port 1099 is already in use. Cannot Bind the jmx:rmi
service. I changed the port in the war with 1011, and error is removed. Now
it is getting some deployed successfully but with some issues:
I am attaching the deploying log with the mail. Please tell me how can i
verify that my componant is properly deployed and how i can check the
functionality of this war file.
20:34:36,393 INFO [TomcatDeployer] deploy, ctxPath=/servicemix-web-3.2.1,
warUrl=.../tmp/deploy/tmp38660servicemix-web-3.2.1-exp.war/
20:34:37,206 INFO [WebappClassLoader]
validateJarFile(D:\OKISoft\jboss-4.2.2.GA\server\default\.\tmp\deploy\tmp38660servicemix-web-3.2.1-exp.war\WEB-INF\lib\servlet-api-2.5-6.1.5.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
20:34:37,987 INFO [1]] Initializing Spring root WebApplicationContext
20:34:41,940 INFO [STDOUT] INFO - ConnectorServerFactoryBean - JMX
connector available at: service:jmx:rmi:///jndi/rmi://localhost:1011/jmxrmi
20:34:57,316 INFO [STDOUT] INFO - jetty - Logging
to org.apache.servicemix.http.jetty.JCLLogger@1162ab9 via
org.apache.servicemix.http.jetty.JCLLogger
20:34:57,503 INFO [STDOUT] INFO - JBIContainer -
ServiceMix 3.2.1 JBI Container (ServiceMix) is starting
20:34:57,503 INFO [STDOUT] INFO - JBIContainer - For
help or more informations please see:
http://incubator.apache.org/servicemix/
20:34:57,519 INFO [STDOUT] WARN - ManagementContext - Failed
to start rmi registry: Port already in use: 1099; nested exception is:
java.net.BindException: Address already in use: JVM_Bind
20:34:57,534 INFO [STDOUT] WARN - ManagementContext - Failed
to start jmx connector: connector:name=rmi already registered.
20:34:57,784 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: #SubscriptionManager#
20:34:57,831 INFO [STDOUT] INFO - DeploymentService -
Restoring service assemblies
20:34:57,925 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: servicemix-http
20:34:58,112 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: echo
20:34:58,144 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: timer
20:34:58,612 INFO [STDOUT] INFO - SimpleThreadPool - Job
execution threads will use class loader of thread: ScannerThread
20:34:58,691 INFO [STDOUT] INFO - QuartzScheduler - Quartz
Scheduler v.1.5.2 created.
20:34:58,691 INFO [STDOUT] INFO - RAMJobStore -
RAMJobStore initialized.
20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory - Quartz
scheduler 'DefaultQuartzScheduler' initialized from default resource file in
Quartz package: 'quartz.properties'
20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory - Quartz
scheduler version: 1.5.2
20:34:58,706 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: inputSender
20:34:58,722 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: inputReceiver
20:34:58,737 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: outputSender
20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: jmsTrace
20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
Initializing component: trace
20:34:58,831 INFO [STDOUT] WARN - ClientFactory - Cound
not start ClientFactory: javax.naming.NameNotFoundException: jbi not bound
20:34:58,894 INFO [STDOUT] INFO - QuartzScheduler -
Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
20:34:58,956 INFO [STDOUT] INFO - JBIContainer -
ServiceMix JBI Container (ServiceMix) started
Puneet Jain
--
View this message in context: http://www.nabble.com/problem-while-deploying-servicemix-web-3.2.1.war-on-Jboss-tp15065853s12049p15065853.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem while deploying servicemix-web-3.2.1.war on Jboss
Posted by puneetjain <pu...@wipro.com>.
Hi,
Thanks a lot for ur reply.
That fine that the port is already in use. The port is actually used by
jboss rmi. I am trying to deploy this war on jboss server and i have already
changes the port defined in .../WEB-INF/jmx.xml file from 1099 to 1011. But
it is still giving me this error.
And could u please provide me some links which contains the tutorial to
start writing the servicemix component.
Puneet
Chris Custine (Apache) wrote:
>
> 1). The port 1099 in use is simply because something else was already
> using
> that port.
> 2). The next error about servlet-api 2.5 just means that the servlet jar
> file is being included in the war package, but it should not be since the
> servlet container provides its own version. This is harmless, but we need
> to make sure that it isn't packaged.
> 3). "Cound not start ClientFactory: javax.naming.NameNotFoundException:
> jbi
> not bound" is a real issue, but only if you need to access the client API
> via the JNDI bound ClientFactory. See
> SM-1206<https://issues.apache.org/activemq/browse/SM-1206>
>
> These are all harmless messages, so your deployment should work fine, if
> you
> have trouble running it post those errors here and we'll take a look.
>
> Chris
>
> On Jan 24, 2008 8:25 AM, puneetjain <pu...@wipro.com> wrote:
>
>>
>> Hi,
>>
>> I am new with ServiceMix. I am trying to deploy servicemix example war on
>> jboss4.2.2.GA but i am getting some errors. I am explaining the steps i
>> followed:
>>
>> 1. I downloaded the jboss- deployer source and build it by maven and
>> deploy
>> the servicemix-jbi container for jboss.
>> 2. Now i am trying to deploy the example provided with servicemix
>> package.
>> I
>> got error that the port 1099 is already in use. Cannot Bind the jmx:rmi
>> service. I changed the port in the war with 1011, and error is removed.
>> Now
>> it is getting some deployed successfully but with some issues:
>>
>> I am attaching the deploying log with the mail. Please tell me how can i
>> verify that my componant is properly deployed and how i can check the
>> functionality of this war file.
>>
>> 20:34:36,393 INFO [TomcatDeployer] deploy,
>> ctxPath=/servicemix-web-3.2.1,
>> warUrl=.../tmp/deploy/tmp38660servicemix-web-3.2.1-exp.war/
>> 20:34:37,206 INFO [WebappClassLoader]
>> validateJarFile(D:\OKISoft\jboss-
>> 4.2.2.GA\server\default\.\tmp\deploy\tmp38660servicemix-web-3.2.1-exp.war\WEB-INF\lib\servlet-api-2.5-6.1.5.jar
>> )
>> - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
>> javax/servlet/Servlet.class
>> 20:34:37,987 INFO [1]] Initializing Spring root WebApplicationContext
>> 20:34:41,940 INFO [STDOUT] INFO - ConnectorServerFactoryBean - JMX
>> connector available at:
>> service:jmx:rmi:///jndi/rmi://localhost:1011/jmxrmi
>> 20:34:57,316 INFO [STDOUT] INFO - jetty -
>> Logging
>> to org.apache.servicemix.http.jetty.JCLLogger@1162ab9 via
>> org.apache.servicemix.http.jetty.JCLLogger
>> 20:34:57,503 INFO [STDOUT] INFO - JBIContainer -
>> ServiceMix 3.2.1 JBI Container (ServiceMix) is starting
>> 20:34:57,503 INFO [STDOUT] INFO - JBIContainer - For
>> help or more informations please see:
>> http://incubator.apache.org/servicemix/
>> 20:34:57,519 INFO [STDOUT] WARN - ManagementContext -
>> Failed
>> to start rmi registry: Port already in use: 1099; nested exception is:
>> java.net.BindException: Address already in use: JVM_Bind
>> 20:34:57,534 INFO [STDOUT] WARN - ManagementContext -
>> Failed
>> to start jmx connector: connector:name=rmi already registered.
>> 20:34:57,784 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: #SubscriptionManager#
>> 20:34:57,831 INFO [STDOUT] INFO - DeploymentService -
>> Restoring service assemblies
>> 20:34:57,925 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: servicemix-http
>> 20:34:58,112 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: echo
>> 20:34:58,144 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: timer
>> 20:34:58,612 INFO [STDOUT] INFO - SimpleThreadPool - Job
>> execution threads will use class loader of thread: ScannerThread
>> 20:34:58,691 INFO [STDOUT] INFO - QuartzScheduler -
>> Quartz
>> Scheduler v.1.5.2 created.
>> 20:34:58,691 INFO [STDOUT] INFO - RAMJobStore -
>> RAMJobStore initialized.
>> 20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory -
>> Quartz
>> scheduler 'DefaultQuartzScheduler' initialized from default resource file
>> in
>> Quartz package: 'quartz.properties'
>> 20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory -
>> Quartz
>> scheduler version: 1.5.2
>> 20:34:58,706 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: inputSender
>> 20:34:58,722 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: inputReceiver
>> 20:34:58,737 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: outputSender
>> 20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: jmsTrace
>> 20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
>> Initializing component: trace
>> 20:34:58,831 INFO [STDOUT] WARN - ClientFactory -
>> Cound
>> not start ClientFactory: javax.naming.NameNotFoundException: jbi not
>> bound
>> 20:34:58,894 INFO [STDOUT] INFO - QuartzScheduler -
>> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
>> 20:34:58,956 INFO [STDOUT] INFO - JBIContainer -
>> ServiceMix JBI Container (ServiceMix) started
>>
>> Puneet Jain
>>
>> --
>> View this message in context:
>> http://www.nabble.com/problem-while-deploying-servicemix-web-3.2.1.war-on-Jboss-tp15065853s12049p15065853.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/problem-while-deploying-servicemix-web-3.2.1.war-on-Jboss-tp15065853s12049p15068936.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: problem while deploying servicemix-web-3.2.1.war on Jboss
Posted by Chris Custine <cc...@apache.org>.
1). The port 1099 in use is simply because something else was already using
that port.
2). The next error about servlet-api 2.5 just means that the servlet jar
file is being included in the war package, but it should not be since the
servlet container provides its own version. This is harmless, but we need
to make sure that it isn't packaged.
3). "Cound not start ClientFactory: javax.naming.NameNotFoundException: jbi
not bound" is a real issue, but only if you need to access the client API
via the JNDI bound ClientFactory. See
SM-1206<https://issues.apache.org/activemq/browse/SM-1206>
These are all harmless messages, so your deployment should work fine, if you
have trouble running it post those errors here and we'll take a look.
Chris
On Jan 24, 2008 8:25 AM, puneetjain <pu...@wipro.com> wrote:
>
> Hi,
>
> I am new with ServiceMix. I am trying to deploy servicemix example war on
> jboss4.2.2.GA but i am getting some errors. I am explaining the steps i
> followed:
>
> 1. I downloaded the jboss- deployer source and build it by maven and
> deploy
> the servicemix-jbi container for jboss.
> 2. Now i am trying to deploy the example provided with servicemix package.
> I
> got error that the port 1099 is already in use. Cannot Bind the jmx:rmi
> service. I changed the port in the war with 1011, and error is removed.
> Now
> it is getting some deployed successfully but with some issues:
>
> I am attaching the deploying log with the mail. Please tell me how can i
> verify that my componant is properly deployed and how i can check the
> functionality of this war file.
>
> 20:34:36,393 INFO [TomcatDeployer] deploy, ctxPath=/servicemix-web-3.2.1,
> warUrl=.../tmp/deploy/tmp38660servicemix-web-3.2.1-exp.war/
> 20:34:37,206 INFO [WebappClassLoader]
> validateJarFile(D:\OKISoft\jboss-
> 4.2.2.GA\server\default\.\tmp\deploy\tmp38660servicemix-web-3.2.1-exp.war\WEB-INF\lib\servlet-api-2.5-6.1.5.jar
> )
> - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
> javax/servlet/Servlet.class
> 20:34:37,987 INFO [1]] Initializing Spring root WebApplicationContext
> 20:34:41,940 INFO [STDOUT] INFO - ConnectorServerFactoryBean - JMX
> connector available at:
> service:jmx:rmi:///jndi/rmi://localhost:1011/jmxrmi
> 20:34:57,316 INFO [STDOUT] INFO - jetty -
> Logging
> to org.apache.servicemix.http.jetty.JCLLogger@1162ab9 via
> org.apache.servicemix.http.jetty.JCLLogger
> 20:34:57,503 INFO [STDOUT] INFO - JBIContainer -
> ServiceMix 3.2.1 JBI Container (ServiceMix) is starting
> 20:34:57,503 INFO [STDOUT] INFO - JBIContainer - For
> help or more informations please see:
> http://incubator.apache.org/servicemix/
> 20:34:57,519 INFO [STDOUT] WARN - ManagementContext -
> Failed
> to start rmi registry: Port already in use: 1099; nested exception is:
> java.net.BindException: Address already in use: JVM_Bind
> 20:34:57,534 INFO [STDOUT] WARN - ManagementContext -
> Failed
> to start jmx connector: connector:name=rmi already registered.
> 20:34:57,784 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: #SubscriptionManager#
> 20:34:57,831 INFO [STDOUT] INFO - DeploymentService -
> Restoring service assemblies
> 20:34:57,925 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: servicemix-http
> 20:34:58,112 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: echo
> 20:34:58,144 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: timer
> 20:34:58,612 INFO [STDOUT] INFO - SimpleThreadPool - Job
> execution threads will use class loader of thread: ScannerThread
> 20:34:58,691 INFO [STDOUT] INFO - QuartzScheduler -
> Quartz
> Scheduler v.1.5.2 created.
> 20:34:58,691 INFO [STDOUT] INFO - RAMJobStore -
> RAMJobStore initialized.
> 20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory -
> Quartz
> scheduler 'DefaultQuartzScheduler' initialized from default resource file
> in
> Quartz package: 'quartz.properties'
> 20:34:58,691 INFO [STDOUT] INFO - StdSchedulerFactory -
> Quartz
> scheduler version: 1.5.2
> 20:34:58,706 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: inputSender
> 20:34:58,722 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: inputReceiver
> 20:34:58,737 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: outputSender
> 20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: jmsTrace
> 20:34:58,753 INFO [STDOUT] INFO - ComponentMBeanImpl -
> Initializing component: trace
> 20:34:58,831 INFO [STDOUT] WARN - ClientFactory - Cound
> not start ClientFactory: javax.naming.NameNotFoundException: jbi not bound
> 20:34:58,894 INFO [STDOUT] INFO - QuartzScheduler -
> Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> 20:34:58,956 INFO [STDOUT] INFO - JBIContainer -
> ServiceMix JBI Container (ServiceMix) started
>
> Puneet Jain
>
> --
> View this message in context:
> http://www.nabble.com/problem-while-deploying-servicemix-web-3.2.1.war-on-Jboss-tp15065853s12049p15065853.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>