You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "chenwei (Created) (JIRA)" <ji...@apache.org> on 2012/03/19 05:02:49 UTC

[jira] [Created] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

camel route cannot be configured again if the former configure()  failed
------------------------------------------------------------------------

                 Key: CAMEL-5106
                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.6.0
         Environment: linux
            Reporter: chenwei
            Priority: Critical


e.g.
from("http://ip:port/path").end();
if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "chenwei (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232495#comment-13232495 ] 

chenwei commented on CAMEL-5106:
--------------------------------

my source code in configure() is:
from(sourceUri630)
		.log("receive 6.3.0 mo ")
		.process(mm7SchemaREL6MM710ReceiverUtils).log("deliverRoute -> End").end();
sourceUri630 is a cxf endpoint like: "cxf://http://0.0.0.0:port/mm7"+"?serviceClass=" + serviceClass_630 + "&bus=#cxf".
the port is configurable,when I configure it as 12, there will be error like:


com.alcatel_lucent.ae.ais.pp.scfdao.exception.ProvisionableException: Error return from proxy method: java.util.concurrent.ExecutionException: com.alcatel_lucent.aes.scf.component.common.ContextDataChangeException: Failed to build routes for AES_1.SCF_1.ScfAgent_1.EnablerNnsMMS_115 caused by Fault [Could not start Jetty server on port 12: Permission denied] caused by SocketException [Permission denied]

at com.alcatel_lucent.aes.scf.jmxagent.agent.ComponentManagerImpl.execProxyMethod(ComponentManagerImpl.java:453)

at com.alcatel_lucent.aes.scf.jmxagent.agent.ComponentManagerImpl.writeContextDataNotify(ComponentManagerImpl.java:1500)

at com.alcatel_lucent.aes.scf.modao.entity.ManagedElement.writeContextData(ManagedElement.java:395)

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.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:167)

at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:96)

at com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:33)

at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:208)

at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:120)

at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:262)

at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836)

at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761)

at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)

at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)

at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)

at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1360)

at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)

at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)

at sun.rmi.transport.Transport$1.run(Transport.java:159)

at java.security.AccessController.doPrivileged(Native Method)

at sun.rmi.transport.Transport.serviceCall(Transport.java:155)

at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)

at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:619)


                
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233223#comment-13233223 ] 

Claus Ibsen commented on CAMEL-5106:
------------------------------------

Well the port number 12 is in use, and therefore the route cannot be started.
> Could not start Jetty server on port 12: Permission denied

Also its really discouraged to use such low port numbers. Either use port 80, or 443.
Or better use a higher range port number such as 8080, etc.

This is not a bug in Camel / SerivceMix.
                
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>             Fix For: 2.10.0
>
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "Claus Ibsen (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233225#comment-13233225 ] 

Claus Ibsen commented on CAMEL-5106:
------------------------------------

And please use the discussion forum for help with Camel.

You can find details about the forum / mailing list here
http://camel.apache.org/discussion-forums.html
http://camel.apache.org/mailing-lists.html

This JIRA tracker is not for support in general. But for tracking issues in the Camel software.
                
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0
>
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "chenwei (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232497#comment-13232497 ] 

chenwei commented on CAMEL-5106:
--------------------------------

we are using serviceMix to run the bundle. once this error occurs, the route cannot be used any more.
                
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5106.
--------------------------------

       Resolution: Not A Problem
    Fix Version/s: 2.10.0
         Assignee: Claus Ibsen
    
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0
>
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (CAMEL-5106) camel route cannot be configured again if the former configure() failed

Posted by "Claus Ibsen (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5106:
-------------------------------

    Priority: Major  (was: Critical)

Please make a better effort when reporting a ticket.

See some instructions/suggestions at this page
http://camel.apache.org/support

For example:
- What error do you see?
- Do you have a stack trace?
- Your route is invalid, you cannot just have from() -> end. You need something more, such as from -> to -> end
- Have your tried to upgrade Camel? 
- How do you run the application? eg standalone, from a WAR file in Tomcat, JEE server, etc.


                
> camel route cannot be configured again if the former configure()  failed
> ------------------------------------------------------------------------
>
>                 Key: CAMEL-5106
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5106
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.6.0
>         Environment: linux
>            Reporter: chenwei
>
> e.g.
> from("http://ip:port/path").end();
> if the port is in use, the configure() will throw an exception, but when I changed the port and try to reconfigure it, the right port cannot be start up.
> I am not sure it is a jetty issue or camel issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira