Telegram notifications, again(

sph1nx8 days ago

Hello, can you tell me what I'm doing wrong so that notifications come to Telegram? I've read the entire forum and docs. Logs empty

<entry key='notificator.types'>web,telegram</entry>
<entry key='notificator.telegram.token'>7789235164:AAFqOWipdXZMvNdl9Go2wDvfUcVjuGuN030</entry>
<entry key='notificator.telegram.chatId'>-4915749525</entry>

2.jpg

2-2.jpg

2-3.jpg

Anton Tananaev8 days ago

Looks correct, assuming ids and keys are correct.

sph1nx8 days ago
2025-05-24 15:58:06 DEBUG: NameNotFoundException (... < NotificatorTelegram:95 < Notificator:39 < NotificationManager:139 < ... < *:132 < ... < *:131 < *:176 < ConnectionManager:251 < ...)

I guess this is the main reason?

Anton Tananaev7 days ago

Try enabling full stack traces. But I suspect most likely it means a network issue.

sph1nx7 days ago
2025-05-24 18:58:18 DEBUG: nextAction(false) COMPLETE HttpChannelState@4a766869{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0}
2025-05-24 18:58:18 DEBUG: action COMPLETE HttpChannelOverHttp@4e49e578{s=HttpChannelState@4a766869{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0},r=8,c=false/false,a=HANDLING,uri=http://localhost:8082/api/notifications/test/telegram,age=120}
2025-05-24 18:58:18 DEBUG: consumeAll HttpInput@72892953 cs=HttpChannelState@4a766869{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0} cp=org.eclipse.jetty.server.BlockingContentProducer@3961d5d1 eof=false
2025-05-24 18:58:18 TRACE: consumeAll AsyncContentProducer@7cf05010[r=null,t=null,i=null,error=false,c=HttpChannelOverHttp@4e49e578{s=HttpChannelState@4a766869{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0},r=8,c=false/false,a=HANDLING,uri=http://localhost:8082/api/notifications/test/telegram,age=121}] - 
org.eclipse.jetty.util.StaticException: Unconsumed content
    at org.eclipse.jetty.server.AsyncContentProducer.consumeAll(AsyncContentProducer.java:188)
    at org.eclipse.jetty.server.BlockingContentProducer.consumeAll(BlockingContentProducer.java:93)
    at org.eclipse.jetty.server.HttpInput.consumeAll(HttpInput.java:179)
    at org.eclipse.jetty.server.HttpChannel.ensureConsumeAllOrNotPersistent(HttpChannel.java:684)
    at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:616)
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:287)
    at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
    at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
    at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:421)
    at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:390)
    at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:277)
    at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.run(AdaptiveExecutionStrategy.java:199)
    at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:969)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.doRunJob(QueuedThreadPool.java:1194)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1149)
    at java.base/java.lang.Thread.run(Thread.java:1583)

2025-05-24 18:58:18 DEBUG: failing all content with org.eclipse.jetty.util.StaticException: Unconsumed content HttpChannelOverHttp@4e49e578{s=HttpChannelState@4a766869{s=HANDLING rs=COMPLETING os=OPEN is=IDLE awp=false se=false i=false al=0},r=8,c=false/false,a=HANDLING,uri=http://localhost:8082/api/notifications/test/telegram,age=121}
2025-05-24 18:58:18 DEBUG: produceContent has no content, parsing and filling
Anton Tananaev7 days ago

This seems completely unrelated.

sph1nx7 days ago
:~$ curl -X POST "https://api.telegram.org/bot7789235164:AAFqOWipdXZMvNdl9Go2wDvfUcVjuGuN030/sendMessage?chat_id=-4915749525&text=TEST"
{"ok":true,"result":{"message_id":53,"from":{"id":7789235164,"is_bot":true,"first_name":"GPS Tracking BOT","username":"***tracking_bot"},"chat":{"id":-4915749525,"title":"GPS","type":"group","all_members_are_administrators":true,"accepted_gift_types":{"unlimited_gifts":false,"limited_gifts":false,"unique_gifts":false,"premium_subscription":false}},"date":1748096830,"text":"TEST"}}

Works like a charm from cli...

Anton Tananaev7 days ago

Do you still see the original NameNotFoundException? That's the one we need to see full stack trace of.

sph1nx7 days ago

not anymore

sph1nx7 days ago

can the use of nginx proxy somehow affect it?

Anton Tananaev7 days ago

I don't think so.

sph1nx7 days ago

Finally! i've found the problem

<entry key='notificator.telegram.token'>7789235164:AAFqOWipdXZMvNdl9Go2wDvfUcVjuGuN030</entry>

entry key should be notificator.telegram.key not token

sph1nx7 days ago

Thank you so much for your work!