You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicemix.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2015/03/03 13:54:04 UTC
[jira] [Commented] (SM-2439) jsmpp session fails to connect with
java.lang.NoSuchMethodError
[ https://issues.apache.org/jira/browse/SM-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345027#comment-14345027 ]
Jean-Baptiste Onofré commented on SM-2439:
------------------------------------------
https://git-wip-us.apache.org/repos/asf?p=servicemix-bundles.git;a=commitdiff;h=17389fd68d5c7ceb8722b36e9d17ee2198ef44c9
> jsmpp session fails to connect with java.lang.NoSuchMethodError
> ---------------------------------------------------------------
>
> Key: SM-2439
> URL: https://issues.apache.org/jira/browse/SM-2439
> Project: ServiceMix
> Issue Type: Bug
> Components: bundles
> Environment: {noformat}
> $ java -version
> java version "1.7.0_75"
> OpenJDK Runtime Environment (IcedTea 2.5.4) (Slackware)
> OpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)
> Slackware current 64 bit
> Linux 3.14.29 x86_64
> {noformat}
> Reporter: Andrew Clemons
> Assignee: Jean-Baptiste Onofré
> Fix For: bundles-2015.02
>
> Attachments: 0001-Fix-failing-session-connect-b-c-of-NoSuchMethodError.patch
>
>
> Starting a session to an SMS-C with jsmpp fails with a java.lang.NoSuchMethodError.
> {noformat}
> java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: org.jsmpp.session.SMPPSessionContext.fireStateChanged(Lorg/jsmpp/extra/SessionState;Lorg/jsmpp/extra/SessionState;Ljava/lang/Object;)V
> at java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.util.concurrent.FutureTask.get(FutureTask.java:188)
> at nz.geek.caffe.smpp.session.AbstractSession.reconnect(AbstractSession.java:377)
> at nz.geek.caffe.smpp.session.AbstractSession$1.run(AbstractSession.java:119)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoSuchMethodError: org.jsmpp.session.SMPPSessionContext.fireStateChanged(Lorg/jsmpp/extra/SessionState;Lorg/jsmpp/extra/SessionState;Ljava/lang/Object;)V
> at org.jsmpp.session.SMPPSessionContext.changeState(SMPPSessionContext.java:61)
> at org.jsmpp.session.AbstractSessionContext.open(AbstractSessionContext.java:42)
> at org.jsmpp.session.SMPPSession.connectAndBind(SMPPSession.java:226)
> at org.jsmpp.session.SMPPSession.connectAndBind(SMPPSession.java:200)
> at nz.geek.caffe.smpp.session.AbstractSession.connect(AbstractSession.java:176)
> at nz.geek.caffe.smpp.session.AbstractSession$2.run(AbstractSession.java:351)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> ... 1 more
> {noformat}
> The patch applied to jsmpp for SMX4-1748 has changed the signature of the method fireStateChanged().
> The attached patch fixes the issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)