Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MySQL++ - Programming with the C++ API to MySQL
MaxDB - Everything about MaxDB, formerly known as SAP DB
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
Update one field with more fields from another table
Getting Identity after INSERT
ERROR 2002: Can 't connect to local MySQL server through socket
mysql test 4 1 fails with the gis test
MySQL Cluster Software
Downgrade Mysql from 4 to 3 23
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Can 't access mysql after kernel upgrade
Executing MySQL Commands From Within C Program
Comparing and writing out BLOBS
Preventing Duplicate Entries
FULLTEXT query format question
Strange behavior, Table Level Permission
Does the binary log enabling affect the MySQL performances?
mysql:it 's a db not a dbms how it 's possible?!
mysql have same function mthod as Oracle decode()
 
AW: Subscriber id exists

AW: Subscriber id exists

2007-05-02       - By Auer, Wolfgang

 Back
Hello,

a SyncMan Client is a durable consumer in the MessageHub. If the MessageHub
detects that a socket breaks down, it should reset the state from the consumer
to inactive.
If this fails you could restart the message server (and your clients) or you
can call the admin client to reset one special consumer.

e.g.:
java  -classpath ".\msgserver.jar;"  com.sap.sdb.msgServer.AdminClient
-password SECRET123 -msgserver_host localhost -msgserver_admin_port 1234
"unregister consumer 1178116659124000008 durable"

The name of the consumer is an ID, which should stay constant as long as you
don't delete the consumer on the message server. You can select the consumer ID
with
SELECT * FROM "MESSAGESERVICE"."MSGSERVER_CONSUMER"

Regards
   Wolfgang


Wolfgang Auer
Developer
mailto:wolfgang.auer@(protected)
http://www.sap.com

Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), L?o Apotheker
(stellvertretender Sprecher/Deputy CEO), Werner Brandt, Claus Heinrich, Gerhard
Oswald, Peter Zencke
Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso
Plattner
Registergericht/Commercial Register Mannheim No HRB 350269

Diese E-Mail kann Betriebs- oder Gesch?ftsgeheimnisse oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrt?mlich
erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielf?ltigung
oder Weitergabe der E-Mail ausdr?cklich untersagt.
Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen
Dank.

This e-mail may contain trade secrets or privileged, undisclosed, or otherwise
confidential information. If you have received this e-mail in error, you are
hereby notified that any review, copying, or distribution of it is strictly
prohibited. Please inform us immediately and destroy the original transmittal.
Thank you for your cooperation.


-- --Urspr?ngliche Nachricht-- --
Von: Linos [mailto:info@(protected)]
Gesendet: Montag, 30. April 2007 18:26
An: maxdb@(protected)
Betreff: Re: Subscriber id exists

If i manually use "deactivate Selected Consumers" in Monitor inside
Synchronization Manager GUI i can launch synchronization service in the
client but i would like to know if i have any way to force this from the
command line in the client side or any other automatic way to handle
this, i can have many problems maintaining synchronization if every time
a computer reboots i have to do this manually to get the synchronization
working. Thanks.

Best Regards,
Miguel Angel.


Linos escribi?:
> Hello,
>   i am testing synchronization stability and when is disconnect from
> network or reboot the client machine with syncservice started, when i
> try to relaunch it (after reboot for example) i have this error in
> syncservice console:
>
> INFO: starting administration thread at port 7223 ...
> INFO: ... done.
> javax.jms.JMSException: Unable to get a consumer id for topic subscriber
> from the server: com.sap.sdb.msgServer.util.NotificationException:
> ErrorNotification: [com.sap.sdb.msgServer.agents.AdminException:
> javax.jms.JMSException: ConsumerList : Active subscription
> <1177927038954000578> with ID <1177928873924000699> for destination
> 1177848311880000445> already exists
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.register(AdminAgent.java:446)
>
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.doCommand(AdminAgent.java:173
> )
>         at com.sap.sdb.msgServer.agents.Agent.doWork(Agent.java:79)
>         at
> com.sap.sdb.msgServer.agents.JmsThread.run(JmsThread.java:189)]
> (Client:192.168.1.235:1108/7295144,ServerAgent:null,Type:-1)
> javax.jms.JMSException: Unable to get a consumer id for topic subscriber
> from the server: com.sap.sdb.msgServer.util.NotificationException:
> ErrorNotification: [com.sap.sdb.msgServer.agents.AdminException:
> javax.jms.JMSException: ConsumerList : Active subscription
> <1177927038954000578> with ID <1177928873924000699> for destination
> <1177848311880000445> already exists
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.register(AdminAgent.java:446)
>
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.doCommand(AdminAgent.java:173
> )
>         at com.sap.sdb.msgServer.agents.Agent.doWork(Agent.java:79)
>         at com.sap.sdb.msgServer.agents.JmsThread.run(JmsThread.java:189)
> ] (Client:192.168.1.235:1108/7295144,ServerAgent:null,Type:-1)
>
>
> and this in the msgserver machine.
>
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connected to 192.168.1.235:1107 on
> port 7221 for service com.sap.sdb.msgServer.jndi.JndiService
> [Mon Apr 30 12:54:34 GMT+01:00 2007] JndiNotification: lookup
> jms.TopicConnectionFactory
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connection 192.168.1.235:1107 closed.
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connected to 192.168.1.235:1108 on
> port 7222 for service com.sap.sdb.msgServer.service.JmsService
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connected to 192.168.1.235:1109 on
> port 7221 for service com.sap.sdb.msgServer.jndi.JndiService
> [Mon Apr 30 12:54:34 GMT+01:00 2007] JndiNotification: lookup
> jms.topic.SYNC_TOPIC_DEST_1177844605606000005
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connection 192.168.1.235:1109 closed.
> [Mon Apr 30 12:54:34 GMT+01:00 2007] javax.jms.JMSException:
> ConsumerList : Active subscription <1177927038954000578> with ID
> <1177928873924000699> for destination <1177848311880000445> already exists
> com.sap.sdb.msgServer.agents.AdminException: javax.jms.JMSException:
> ConsumerList : Active subscription <1177927038954000578> with ID
> <1177928873924000699> for destination <1177848311880000445> already exists
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.register(AdminAgent.java:446)
>         at
> com.sap.sdb.msgServer.agents.AdminAgent.doCommand(AdminAgent.java:173)
>         at com.sap.sdb.msgServer.agents.Agent.doWork(Agent.java:79)
>         at com.sap.sdb.msgServer.agents.JmsThread.run(JmsThread.java:189)
> [Mon Apr 30 12:54:34 GMT+01:00 2007] AdminAgent-1 (See http://ent-1.ora-code.com): Unexpected exception
> in JMS Thread: javax.jms.JMSException: ConsumerList : Active
> subscription <1177927038954000578> with ID <1177928873924000699> for
> destination <1177848311880000445> already exists
> [Mon Apr 30 12:54:34 GMT+01:00 2007]
> com.sap.sdb.msgServer.agents.AdminException: javax.jms.JMSException:
> ConsumerList : Active subscription <1177927038954000578> with ID
> <1177928873924000699> for destination <1177848311880000445> already exists
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connected to 192.168.1.235:1110 on
> port 7221 for service com.sap.sdb.msgServer.jndi.JndiService
> [Mon Apr 30 12:54:34 GMT+01:00 2007] JndiNotification: lookup
> jms.QueueConnectionFactory
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connection 192.168.1.235:1110 closed.
> [Mon Apr 30 12:54:34 GMT+01:00 2007] Connected to 192.168.1.235:1111 on
> port 7222 for service com.sap.sdb.msgServer.service.JmsService
>
>
> How i can cancel/expire this subscription to reconnect after unexpected
> reboot in client machine?
>
>
> Regards,
> Miguel Angel.
>


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=wolfgang.auer@(protected)


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)