Author |
Message
|
migerrits |
Posted: Wed May 04, 2005 5:11 am Post subject: JText: ConnectorName and the .lock file |
|
|
 Apprentice
Joined: 13 Dec 2002 Posts: 35 Location: Canada
|
Just a little hint for everyone...
We had noticed that when using a JText connector, it always creates a file called "JTextConnector.lock" in C:\WebsphereAdapters.
This can be problematic when you're using multiple JText adapters on the same machine as, by default, they all want to use the same name.
However, you can add a custom "ConnectorName" property to the "Connector-Specific Properties" of the adapter configuration (cfg) file that will allow for the creation of a .lock file with the same name as the property Value.
-mike |
|
Back to top |
|
 |
Ratan |
Posted: Wed May 04, 2005 2:13 pm Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
Quote: |
However, you can add a custom "ConnectorName" property to the "Connector-Specific Properties" of the adapter configuration (cfg) file that will allow for the creation of a .lock file with the same name as the property Value. |
Where did you get this information from? It is not documented.
Quote: |
This can be problematic when you're using multiple JText adapters on the same machine as, by default, they all want to use the same name.
|
When you are using multiple connector instances are you copying all he contents of your JText connector directory to a new directory with the instance name? _________________ -Ratan |
|
Back to top |
|
 |
migerrits |
Posted: Thu May 05, 2005 6:39 am Post subject: |
|
|
 Apprentice
Joined: 13 Dec 2002 Posts: 35 Location: Canada
|
Ratan wrote: |
Quote: |
However, you can add a custom "ConnectorName" property to the "Connector-Specific Properties" of the adapter configuration (cfg) file that will allow for the creation of a .lock file with the same name as the property Value. |
Where did you get this information from? It is not documented.
|
We noticed that the Test Connector program was using a .lock file with the same name as the profile I set up. I then scrolled back through the Test Connector log until I found the first reference to that name, which the log was calling "Connector Name". On a hunch, we added the property to the config file for the adapter and it worked.
It was simply an accidental discovery. Since we didn't see it documented anywhere, I thought I'd add it to the knowledge here.
Ratan wrote: |
When you are using multiple connector instances are you copying all he contents of your JText connector directory to a new directory with the instance name? |
Yes, we have each instance in its own directory sub-structure with separate directories (log, etc.), MOs, BOs, cfg, and so on.
Our problem occurred because we have our 15+ connectors configured to come up at server startup. The lock file was preventing this. |
|
Back to top |
|
 |
vennela |
Posted: Thu May 05, 2005 11:34 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Why use 15 instances of the connector? Is it not resource intensive?
One JText connector can read multiple directories right?
If the formats of different files are different, I would think, it could be handled by configuration meta objects. But why so many instances? |
|
Back to top |
|
 |
ChrisW |
Posted: Fri May 06, 2005 5:16 am Post subject: |
|
|
Voyager
Joined: 20 May 2001 Posts: 78 Location: UK
|
The lockfile is to stop more than one instance of the same connector starting. No problems on Wintel. However, if using on AIX etc and you need to use the -kill option to stop it, then you need to add some additional logic to the start scripts to delete the old lockfile if appropriate. Do not just delete it as it will not have the desired effect! |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri May 06, 2005 5:29 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
vennela wrote: |
Why use 15 instances of the connector? Is it not resource intensive?
One JText connector can read multiple directories right?
If the formats of different files are different, I would think, it could be handled by configuration meta objects. But why so many instances? |
Maybe for fault separation? If one connector to one broker dies, it doesn't interrupt the others... _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
migerrits |
Posted: Fri May 06, 2005 9:14 am Post subject: |
|
|
 Apprentice
Joined: 13 Dec 2002 Posts: 35 Location: Canada
|
jefflowrey wrote: |
vennela wrote: |
Why use 15 instances of the connector? Is it not resource intensive?
One JText connector can read multiple directories right?
If the formats of different files are different, I would think, it could be handled by configuration meta objects. But why so many instances? |
Maybe for fault separation? If one connector to one broker dies, it doesn't interrupt the others... |
I can't say why it was done this way. I'm working in an existing environment on which we're upgrading everything to the latest versions. Upgrading to the newest version of JText brought up the lock file issue. |
|
Back to top |
|
 |
|