[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850094#comment-16850094
]
Kamil commented on KARAF-4154:
--
[~ffang] - thanks a lot. Here is the bundle:
https://issues.apache.org/jira/browse/CAMEL-13560#comment-16850091
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849875#comment-16849875
]
Kamil commented on KARAF-4154:
--
I can try. I'm using Apache Camel with "imaps" component
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849856#comment-16849856
]
Freeman Fang commented on KARAF-4154:
-
Hi [~eximius],
Any chance you put a testcase here?
Thanks!
Freeman
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-4154) javax.mail.Message.getContent() returns IMAPInputStream
[
https://issues.apache.org/jira/browse/KARAF-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849835#comment-16849835
]
Kamil commented on KARAF-4154:
--
I'm having exactly the same problem.
Funny thing is when I run Karaf on JDK8, then message.getContent() returns
javax.mail.internet.MimeMultipart but when I run Karaf on JDK9 or JDK11,
com.sun.mail.imap.IMAPInputStream is returned.
Do you have any idea why version of JDK matters here?
> javax.mail.Message.getContent() returns IMAPInputStream
> ---
>
> Key: KARAF-4154
> URL: https://issues.apache.org/jira/browse/KARAF-4154
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.4.2
> Environment: Linux Mint 17.2 Cinnamon
> Oracle JDK 1.7
>Reporter: Anton Johansson
>Assignee: Christian Schneider
>Priority: Critical
> Labels: javax.mail, mail
>
> I'm using JavaMail API to read emails from Gmail IMAP. The emails are of type
> multipart. I open up a Store, then I open up a Folder ("INBOX"), then I get
> the messages from that folder.
> Outside of Karaf, when doing message.getContent() I get a
> javax.mail.internet.MimeMultipart object back. Doesn't matter if I use
> version 1.4.5 (the one that Karaf provides) or 1.5.4 (the latest).
> Inside Karaf, I get an IMAPInputStream back, which isn't ideal. I'd very much
> like to get the MimeMultipart object back. I've tried not adding any JavaMail
> libraries to Karaf, and relying on the one that Karaf itself provides (which
> is 1.4.5, according to the version matrix:
> http://karaf.apache.org/index/documentation/karaf-dependencies/karaf-deps-2.4.x.html
> I've also tried adding both javax.mail/javax.mail-api/1.5.4 and
> com.sun.mail/javax.mail/1.5.4 to Karaf, but the same problem occurs. I guess
> it still chooses the JAR's that Karaf provides.
> Even in the latest version of Karaf, 1.4.5 is used, so I'd guess the same
> problem exists there, but I cannot say for sure, I haven't tested.
> Am I missing something, or is there some workaround for this?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849814#comment-16849814
]
ASF subversion and git services commented on KARAF-6290:
Commit 3055768c9a9ea60aaff7b2710d943f4b23e9af44 in karaf's branch
refs/heads/master from Baptiste DA ROIT
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=3055768 ]
[KARAF-6290] Enhance wrapper pid management on Solaris
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6290:
Labels: wrapper (was: )
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: wrapper
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-6290.
-
Resolution: Fixed
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: wrapper
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849813#comment-16849813
]
ASF subversion and git services commented on KARAF-6290:
Commit 175a8f15dbe8dc49d89fab99b338433accd913a6 in karaf's branch
refs/heads/karaf-4.2.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=175a8f1 ]
Merge pull request #855 from baptistedaroit/KARAF-6290
[KARAF-6290] Enhance wrapper pid management on Solaris
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849811#comment-16849811
]
ASF subversion and git services commented on KARAF-6290:
Commit ef37f7a983c955cf60aa1930dede391ce9ccb6e9 in karaf's branch
refs/heads/karaf-4.2.x from Baptiste DA ROIT
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ef37f7a ]
[KARAF-6290] Enhance wrapper pid management on Solaris
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849810#comment-16849810
]
ASF GitHub Bot commented on KARAF-6290:
---
jbonofre commented on pull request #855: [KARAF-6290] Enhance wrapper pid
management on Solaris
URL: https://github.com/apache/karaf/pull/855
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849812#comment-16849812
]
ASF subversion and git services commented on KARAF-6290:
Commit 175a8f15dbe8dc49d89fab99b338433accd913a6 in karaf's branch
refs/heads/karaf-4.2.x from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=karaf.git;h=175a8f1 ]
Merge pull request #855 from baptistedaroit/KARAF-6290
[KARAF-6290] Enhance wrapper pid management on Solaris
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849774#comment-16849774
]
ASF GitHub Bot commented on KARAF-6290:
---
baptistedaroit commented on pull request #855: [KARAF-6290] Enhance wrapper pid
management on Solaris
URL: https://github.com/apache/karaf/pull/855
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849770#comment-16849770
]
ASF GitHub Bot commented on KARAF-6290:
---
baptistedaroit commented on pull request #855: [KARAF-6290] Enhance wrapper pid
management on Solaris
URL: https://github.com/apache/karaf/pull/855
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6204) bin/client doesn't appear to honour -p password if it has to retry connection
[
https://issues.apache.org/jira/browse/KARAF-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849637#comment-16849637
]
Tom Quarendon commented on KARAF-6204:
--
I'm no longer in a position to try this out, primarily because we no longer use
Karaf.
> bin/client doesn't appear to honour -p password if it has to retry connection
> -
>
> Key: KARAF-6204
> URL: https://issues.apache.org/jira/browse/KARAF-6204
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Tom Quarendon
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: client
> Fix For: 4.3.0, 4.2.7
>
>
> For reasons I can't establish from the source code, it appears that if the
> client has to retry the connection it forgets the password. I get:
> {code:java}
> Logging in as admin
> retrying (attempt 1) ...
> retrying (attempt 2) ...
> Password:
> {code}
> I have specified the -u and -p command line options to the client.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849556#comment-16849556 ] ASF subversion and git services commented on KARAF-6293: Commit 19f1d092b2ec7aa458e4ebda58904a448080f0f9 in karaf's branch refs/heads/karaf-4.2.x from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=19f1d09 ] [KARAF-6293] Upgrade to XBean 4.14 > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6293. - Resolution: Fixed > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849552#comment-16849552 ] ASF GitHub Bot commented on KARAF-6293: --- jbonofre commented on pull request #854: [KARAF-6293] Upgrade to XBean 4.14 URL: https://github.com/apache/karaf/pull/854 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849554#comment-16849554 ] ASF subversion and git services commented on KARAF-6293: Commit c9eadc2db95f0849dfdc735174cf5b5c1dafe7bc in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=c9eadc2 ] Merge pull request #854 from jbonofre/KARAF-6293 [KARAF-6293] Upgrade to XBean 4.14 > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849555#comment-16849555 ] ASF subversion and git services commented on KARAF-6293: Commit c9eadc2db95f0849dfdc735174cf5b5c1dafe7bc in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=c9eadc2 ] Merge pull request #854 from jbonofre/KARAF-6293 [KARAF-6293] Upgrade to XBean 4.14 > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849553#comment-16849553 ] ASF subversion and git services commented on KARAF-6293: Commit ea8259230320ff4f32089ab3e076bc78048f681e in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=ea82592 ] [KARAF-6293] Upgrade to XBean 4.14 > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849534#comment-16849534
]
Baptiste DA ROIT commented on KARAF-6290:
-
I have an updated version that I need to double check: I can make a PR by the
end of the day if it's okay with you.
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6115) Avoid repeated calls to ACLConfigurationParser.trimKeys/removeSpaces
[ https://issues.apache.org/jira/browse/KARAF-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-6115: Fix Version/s: (was: 4.2.6) 4.2.7 > Avoid repeated calls to ACLConfigurationParser.trimKeys/removeSpaces > > > Key: KARAF-6115 > URL: https://issues.apache.org/jira/browse/KARAF-6115 > Project: Karaf > Issue Type: Improvement > Components: karaf >Affects Versions: 4.1.7 >Reporter: Martin Lichtin >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.3.0, 4.1.8, 4.2.7 > > Attachments: image-2019-01-27-09-23-40-248.png > > > Repeated calls to this method allocate quite a bit of memory that is showing > during GC. > Excerpt from flight recorder: > !image-2019-01-27-09-23-40-248.png! > It would be better to 'trim' the configuration once only, e.g. in > SecuredSessionFactoryImpl -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-6204) bin/client doesn't appear to honour -p password if it has to retry connection
[
https://issues.apache.org/jira/browse/KARAF-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6204:
Fix Version/s: (was: 4.2.6)
4.2.7
> bin/client doesn't appear to honour -p password if it has to retry connection
> -
>
> Key: KARAF-6204
> URL: https://issues.apache.org/jira/browse/KARAF-6204
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Tom Quarendon
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: client
> Fix For: 4.3.0, 4.2.7
>
>
> For reasons I can't establish from the source code, it appears that if the
> client has to retry the connection it forgets the password. I get:
> {code:java}
> Logging in as admin
> retrying (attempt 1) ...
> retrying (attempt 2) ...
> Password:
> {code}
> I have specified the -u and -p command line options to the client.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6204) bin/client doesn't appear to honour -p password if it has to retry connection
[
https://issues.apache.org/jira/browse/KARAF-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849525#comment-16849525
]
Jean-Baptiste Onofré commented on KARAF-6204:
-
Unfortunately I'm not able to reproduce. Anything special on your box in order
to reproduce it ?
> bin/client doesn't appear to honour -p password if it has to retry connection
> -
>
> Key: KARAF-6204
> URL: https://issues.apache.org/jira/browse/KARAF-6204
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Reporter: Tom Quarendon
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: client
> Fix For: 4.3.0, 4.2.6
>
>
> For reasons I can't establish from the source code, it appears that if the
> client has to retry the connection it forgets the password. I get:
> {code:java}
> Logging in as admin
> retrying (attempt 1) ...
> retrying (attempt 2) ...
> Password:
> {code}
> I have specified the -u and -p command line options to the client.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6224) Race condition in BaseActivator on first launch
[
https://issues.apache.org/jira/browse/KARAF-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849524#comment-16849524
]
Jean-Baptiste Onofré commented on KARAF-6224:
-
I would like to take a time to evaluate the impacts. I will improve the
{{BaseActivator}} for next release cycle.
> Race condition in BaseActivator on first launch
> ---
>
> Key: KARAF-6224
> URL: https://issues.apache.org/jira/browse/KARAF-6224
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.0.10, 4.1.7, 4.2.4
>Reporter: Kurt Westerfeld
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.3.0, 4.2.7
>
>
> We have several karaf containers we run on single machine that contains a
> large number of cores (20). The machine core count is high so this may be a
> hard problem to reproduce. We have customized the RMI and JMX ports for each
> of the containers so that they do not conflict. However, after the first
> karaf VM is launched and claims ports 1099/4, the second VM will attempt
> to do the same briefly before its customized configuration can be read from
> the ${karaf.etc} directory. You can see that the management bundle gets
> started and then a configuration update will happen immediately with the
> corrected values.
> In looking over BaseActivator, it seems that a thread is created to dispatch
> the initialization and sometimes this thread will encounter a null field
> "config" before the asynchronous managed service event arrives. In this
> case, the configuration is missing and defaults will be used. Because of
> this, ports 1099 and 4 are temporarily attempted to be used until the
> first managed service event arrives with the updated() method. Immediately
> after that, the service reconfigures and uses the proper customized values.
> This is a problem for us because at times this temporary event can cause a
> client to mistakenly connect to the wrong container. We use JMX over RMI to
> perform a number of management operations and this initial startup is
> unreliable. Our three karaf containers have some interdependencies that this
> temporary condition is causing problems with.
> This problem does not occur as often on subsequent restarts, which means that
> initial provisioning of the ${karaf.etc} must be racing here. We have seen
> it happen, however, although rarer, at any time. It is believed that the
> high core count of the server this happens to be running on results in the
> race condition.
> Suggested fix is to make a call to config admin at run() to read the
> configuration if this.config is null. This would handle the race here but it
> could cause other bad interactions with config admin? Not sure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-6224) Race condition in BaseActivator on first launch
[
https://issues.apache.org/jira/browse/KARAF-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-6224:
Fix Version/s: (was: 4.2.6)
4.2.7
> Race condition in BaseActivator on first launch
> ---
>
> Key: KARAF-6224
> URL: https://issues.apache.org/jira/browse/KARAF-6224
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.0.10, 4.1.7, 4.2.4
>Reporter: Kurt Westerfeld
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.3.0, 4.2.7
>
>
> We have several karaf containers we run on single machine that contains a
> large number of cores (20). The machine core count is high so this may be a
> hard problem to reproduce. We have customized the RMI and JMX ports for each
> of the containers so that they do not conflict. However, after the first
> karaf VM is launched and claims ports 1099/4, the second VM will attempt
> to do the same briefly before its customized configuration can be read from
> the ${karaf.etc} directory. You can see that the management bundle gets
> started and then a configuration update will happen immediately with the
> corrected values.
> In looking over BaseActivator, it seems that a thread is created to dispatch
> the initialization and sometimes this thread will encounter a null field
> "config" before the asynchronous managed service event arrives. In this
> case, the configuration is missing and defaults will be used. Because of
> this, ports 1099 and 4 are temporarily attempted to be used until the
> first managed service event arrives with the updated() method. Immediately
> after that, the service reconfigures and uses the proper customized values.
> This is a problem for us because at times this temporary event can cause a
> client to mistakenly connect to the wrong container. We use JMX over RMI to
> perform a number of management operations and this initial startup is
> unreliable. Our three karaf containers have some interdependencies that this
> temporary condition is causing problems with.
> This problem does not occur as often on subsequent restarts, which means that
> initial provisioning of the ${karaf.etc} must be racing here. We have seen
> it happen, however, although rarer, at any time. It is believed that the
> high core count of the server this happens to be running on results in the
> race condition.
> Suggested fix is to make a call to config admin at run() to read the
> configuration if this.config is null. This would handle the race here but it
> could cause other bad interactions with config admin? Not sure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-6290) Karaf Wrapper does not properly manage process on Solaris
[
https://issues.apache.org/jira/browse/KARAF-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849519#comment-16849519
]
Jean-Baptiste Onofré commented on KARAF-6290:
-
Finally, I prefer to avoid the switch to YAJSW on 4.2.x branch (I will do the
move only on master/4.3.x). Do you have a patch ready for this issue or do you
want me to do it ?
> Karaf Wrapper does not properly manage process on Solaris
> -
>
> Key: KARAF-6290
> URL: https://issues.apache.org/jira/browse/KARAF-6290
> Project: Karaf
> Issue Type: Bug
> Components: karaf
>Affects Versions: 4.2.5
> Environment: Solaris
> HP
>Reporter: Baptiste DA ROIT
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Fix For: 4.3.0, 4.2.6
>
>
> On Solaris platform, the restriction of ps command does not allow the Karaf
> Service Wrapper to properly manage associated karaf process:
> {code}
> [root ~] # cat
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> 6043
> [root ~] # ps -p 6043 -o comm
> COMMAND
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> {code}
> As we can see, if the path to wrapper executable is too long, il will cause
> the service to fail to stop associated karaf instance, as detailed below:
> {code}
> [root ~] # /etc/init.d/smartcollector-dev2 status
> Removed stale pid file:
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/smartcollector-dev2.wrapper.pid
> smartcollector-dev2 is not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> [root ~] # /etc/init.d/smartcollector-dev2 stop
> Stopping smartcollector-dev2...
> smartcollector-dev2 was not running.
> [root ~] # ps -ef | grep smartco
> smcdev 6043 1 0 02:20:27 ? 0:01
> /opt/smartcollector-dev2/smartcollector-dist-5.7.5-SNAPSHOT/bin/smartcollector-
> smcdev 6044 6043 0 02:20:28 ? 4:11
> /opt/smartcollector-dev2/smartcollector-java/bin/java
> -Djava.endorsed.dirs=/opt
> {code}
> This issue can also appears on HP-UX platform, where default ps command is
> also limited to a certain amount of characters (it seems to be 128).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5540) Document new "features processor"
[ https://issues.apache.org/jira/browse/KARAF-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5540: Fix Version/s: (was: 4.2.6) 4.2.7 > Document new "features processor" > - > > Key: KARAF-5540 > URL: https://issues.apache.org/jira/browse/KARAF-5540 > Project: Karaf > Issue Type: Documentation > Components: karaf >Reporter: Grzegorz Grzybek >Assignee: Grzegorz Grzybek >Priority: Major > Labels: documentation > Fix For: 4.3.0, 4.2.7 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849428#comment-16849428 ] ASF GitHub Bot commented on KARAF-6286: --- jbonofre commented on pull request #853: [KARAF-6286] Upgrade to Felix WebConsole 4.3.12 URL: https://github.com/apache/karaf/pull/853 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-6286. - Resolution: Fixed > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849431#comment-16849431 ] ASF subversion and git services commented on KARAF-6286: Commit 40ecfc6b57d06e1862554c7d9babd268e974a391 in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=40ecfc6 ] Merge pull request #853 from jbonofre/KARAF-6286 [KARAF-6286] Upgrade to Felix WebConsole 4.3.12 > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849432#comment-16849432 ] ASF subversion and git services commented on KARAF-6286: Commit e7d966124b667e0caa4447982e8aa74baebc2297 in karaf's branch refs/heads/karaf-4.2.x from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=e7d9661 ] [KARAF-6286] Upgrade to Felix WebConsole 4.3.12 > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849430#comment-16849430 ] ASF subversion and git services commented on KARAF-6286: Commit 40ecfc6b57d06e1862554c7d9babd268e974a391 in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=40ecfc6 ] Merge pull request #853 from jbonofre/KARAF-6286 [KARAF-6286] Upgrade to Felix WebConsole 4.3.12 > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6286) Upgrade to Apache Felix Webconsole 4.3.12
[ https://issues.apache.org/jira/browse/KARAF-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849429#comment-16849429 ] ASF subversion and git services commented on KARAF-6286: Commit 44b7ce8fcffb394036e5297d3dc921d71d60d1ae in karaf's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=44b7ce8 ] [KARAF-6286] Upgrade to Felix WebConsole 4.3.12 > Upgrade to Apache Felix Webconsole 4.3.12 > - > > Key: KARAF-6286 > URL: https://issues.apache.org/jira/browse/KARAF-6286 > Project: Karaf > Issue Type: Dependency upgrade > Components: webconsole >Reporter: Francois Papon >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > > Related to: > Improvement: > * [FELIX-5934] - The web console stores unsalted hashed password > Bug: > * [FELIX-6128] - Escape bundle name and manifest headers > * [FELIX-6127] - Escape name hint in configuration listing -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-6293) Upgrade to XBean 4.14
[ https://issues.apache.org/jira/browse/KARAF-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849422#comment-16849422 ] ASF GitHub Bot commented on KARAF-6293: --- jbonofre commented on pull request #854: [KARAF-6293] Upgrade to XBean 4.14 URL: https://github.com/apache/karaf/pull/854 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to XBean 4.14 > - > > Key: KARAF-6293 > URL: https://issues.apache.org/jira/browse/KARAF-6293 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.3.0, 4.2.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
