Home » Archived » Test and Performance Tools Platform (TPTP) » Profiler unable to establish connection with RAC
| Profiler unable to establish connection with RAC [message #20272] |
Tue, 21 June 2005 20:06  |
Eclipse User |
|
|
|
Originally posted by: vadamo.netefficiency.com
I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client machine
running Eclipse SDK 3.0.2. I have also installed the Remote Agent
controller (Release 3.0.2) on a remote server running Microsoft Windows
Server 2003. I am attempting to monitor, from the client machine, a JBoss
4.0.2 JVM that was started on the remote server with
the -XrunpiAgent:server=enabled option. I am able to successfully attach to
the remote Java Profiling Agent from my client machine within the Eclipse
IDE, but when I click the icon to "Start Monitoring", the following error
dialog box pops up:
"IWAT0003E Launch Java Process Error
IWAT0004W Problems occurred while launching the Java process.
Reason:
Profiler unable to establish connection with RAC. Possible fix: Add more
memory or reduce dataChannelSize in serviceconfig.xml."
I reduced the dataChannelSize incrementally down to 128K, but I continue to
get the error. I verified that the RAServer was using the correct
dataChannelSize by looking at the servicelog.log file. I have also
increased the heap size for the JBoss JVM to 1024M and I still continue to
get the same error.
I have looked through the archives and have not found a similar problem
reported. Does anyone have any ideas?
Thanks,
Vince
|
|
|
| Re: Profiler unable to establish connection with RAC [message #20283 is a reply to message #20272] |
Fri, 24 June 2005 07:17  |
 No real name
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
Hi Vince,
Just out of curiosity, are you able to launch the Java application remotely
as opposed to attaching to it?
Please follow the step below to see if you observe any odd behaviour:
- Rename servicelog.log to servicelog.log.back under your
<AC-HOME>\config directory
- Open the serviceconfig.xml file and change the value of the
loggingLevel attribute from "INFORMATION" to "DEBUG".
- Restart the Agent Controller (keep in mind that you need to restart
the agent controller everytime that there is a change made to
serviceconfig.xml) and redo the steps that you have outlined below.
Please attach your log file to this message or import your log file into the
workbench to see if you observe any odd message. You can import the log
file in the workbench by selecting File > Import > Log File > Next > Add >
Common Base Event XML log > Details > specify the path to servicelog.log >
OK > Finish
If you can't narrow down the problem, contact me at amehrega@ca.ibm.com and
I'll try and follow upon the problem.
"Vince Adamo" <vadamo@netefficiency.com> wrote in message
news:d99s0a$77p$1@news.eclipse.org...
> I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client machine
> running Eclipse SDK 3.0.2. I have also installed the Remote Agent
> controller (Release 3.0.2) on a remote server running Microsoft Windows
> Server 2003. I am attempting to monitor, from the client machine, a JBoss
> 4.0.2 JVM that was started on the remote server with
> the -XrunpiAgent:server=enabled option. I am able to successfully attach
to
> the remote Java Profiling Agent from my client machine within the Eclipse
> IDE, but when I click the icon to "Start Monitoring", the following error
> dialog box pops up:
>
> "IWAT0003E Launch Java Process Error
>
> IWAT0004W Problems occurred while launching the Java process.
>
> Reason:
> Profiler unable to establish connection with RAC. Possible fix: Add more
> memory or reduce dataChannelSize in serviceconfig.xml."
>
> I reduced the dataChannelSize incrementally down to 128K, but I continue
to
> get the error. I verified that the RAServer was using the correct
> dataChannelSize by looking at the servicelog.log file. I have also
> increased the heap size for the JBoss JVM to 1024M and I still continue to
> get the same error.
>
> I have looked through the archives and have not found a similar problem
> reported. Does anyone have any ideas?
>
> Thanks,
> Vince
>
>
|
|
|
| Re: Profiler unable to establish connection with RAC [message #20391 is a reply to message #20283] |
Tue, 28 June 2005 19:06 |
| Eclipse User |
|
|
|
Originally posted by: vadamo.netefficiency.com
Ali,
I have narrowed the problem down to the situation where the agent controller
is running as a service. When I run the agent controller in a command
prompt I am succesful in connecting and profiling the application. I have
attached two log files, one captured while the controller was running as a
service (servicelog.as.service.log) and the second captured while the
controller was run from the command prompt (servicelog.not.as.service.log).
I should also note that I switched to TPTP 3.3.0 while diagnosing this
problem. While it did not seem to have any effect on the problem stated
above, I am not succesful in importing the servicelog files into the
workbench. I get the following error: "An error occurred during the
execution of the remote log parser
" org.eclipse.hyades.logging.adapter.config.StaticParserWrappe r ": IWAT0373E
The adapter configuration file C:\...\GLA20914.dapter cannot be saved due to
the following reason: java.lang.NullPointerException".
Thanks for your help.
Vince
"Ali Mehregani" <microbold@hotmail.com> wrote in message
news:d9g0vu$a25$1@news.eclipse.org...
> Hi Vince,
>
> Just out of curiosity, are you able to launch the Java application
> remotely
> as opposed to attaching to it?
>
> Please follow the step below to see if you observe any odd behaviour:
>
> - Rename servicelog.log to servicelog.log.back under your
> <AC-HOME>\config directory
> - Open the serviceconfig.xml file and change the value of the
> loggingLevel attribute from "INFORMATION" to "DEBUG".
> - Restart the Agent Controller (keep in mind that you need to restart
> the agent controller everytime that there is a change made to
> serviceconfig.xml) and redo the steps that you have outlined below.
>
> Please attach your log file to this message or import your log file into
> the
> workbench to see if you observe any odd message. You can import the log
> file in the workbench by selecting File > Import > Log File > Next > Add >
> Common Base Event XML log > Details > specify the path to servicelog.log >
> OK > Finish
>
> If you can't narrow down the problem, contact me at amehrega@ca.ibm.com
> and
> I'll try and follow upon the problem.
>
> "Vince Adamo" <vadamo@netefficiency.com> wrote in message
> news:d99s0a$77p$1@news.eclipse.org...
>> I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client
>> machine
>> running Eclipse SDK 3.0.2. I have also installed the Remote Agent
>> controller (Release 3.0.2) on a remote server running Microsoft Windows
>> Server 2003. I am attempting to monitor, from the client machine, a
>> JBoss
>> 4.0.2 JVM that was started on the remote server with
>> the -XrunpiAgent:server=enabled option. I am able to successfully attach
> to
>> the remote Java Profiling Agent from my client machine within the Eclipse
>> IDE, but when I click the icon to "Start Monitoring", the following error
>> dialog box pops up:
>>
>> "IWAT0003E Launch Java Process Error
>>
>> IWAT0004W Problems occurred while launching the Java process.
>>
>> Reason:
>> Profiler unable to establish connection with RAC. Possible fix: Add
>> more
>> memory or reduce dataChannelSize in serviceconfig.xml."
>>
>> I reduced the dataChannelSize incrementally down to 128K, but I continue
> to
>> get the error. I verified that the RAServer was using the correct
>> dataChannelSize by looking at the servicelog.log file. I have also
>> increased the heap size for the JBoss JVM to 1024M and I still continue
>> to
>> get the same error.
>>
>> I have looked through the archives and have not found a similar problem
>> reported. Does anyone have any ideas?
>>
>> Thanks,
>> Vince
>>
>>
>
>
|
|
|
| Re: Profiler unable to establish connection with RAC [message #20423 is a reply to message #20391] |
Wed, 29 June 2005 06:00 |
No real name
Messages: 11
Registered: July 2009 |
Junior Member |
|
|
Hi Vince,
After importing both log files in the workbench (using a 4.0 driver), I
noticed that the last two sequences of commands were different. Assuming
that your steps were identical under both scenarios (command and service),
then I suspects the processed commands should be the same.
The last two commands of the service mode log are 37 and 26 whereas the last
two commands of the command mode log are 26 and 27.
When you run the agent controller in service mode, do you have the
<AgentController-HOME>\bin directory under your system path?
There is a problem with the Eclipse site, and I can't download the agent
controller code to determine what command these tags correspond to. I will
follow upon this tomorrow. In the mean while, can you make sure that you
have the bin directory of the agent controller in your system path before
running the agent controller in service mode.
Thanks,
Ali M.
"Vince Adamo" <vadamo@netefficiency.com> wrote in message
news:d9s73n$aem$1@news.eclipse.org...
> Ali,
>
> I have narrowed the problem down to the situation where the agent
controller
> is running as a service. When I run the agent controller in a command
> prompt I am succesful in connecting and profiling the application. I have
> attached two log files, one captured while the controller was running as a
> service (servicelog.as.service.log) and the second captured while the
> controller was run from the command prompt
(servicelog.not.as.service.log).
>
> I should also note that I switched to TPTP 3.3.0 while diagnosing this
> problem. While it did not seem to have any effect on the problem stated
> above, I am not succesful in importing the servicelog files into the
> workbench. I get the following error: "An error occurred during the
> execution of the remote log parser
> " org.eclipse.hyades.logging.adapter.config.StaticParserWrappe r ": IWAT0373E
> The adapter configuration file C:\...\GLA20914.dapter cannot be saved due
to
> the following reason: java.lang.NullPointerException".
>
> Thanks for your help.
>
> Vince
>
> "Ali Mehregani" <microbold@hotmail.com> wrote in message
> news:d9g0vu$a25$1@news.eclipse.org...
> > Hi Vince,
> >
> > Just out of curiosity, are you able to launch the Java application
> > remotely
> > as opposed to attaching to it?
> >
> > Please follow the step below to see if you observe any odd behaviour:
> >
> > - Rename servicelog.log to servicelog.log.back under your
> > <AC-HOME>\config directory
> > - Open the serviceconfig.xml file and change the value of the
> > loggingLevel attribute from "INFORMATION" to "DEBUG".
> > - Restart the Agent Controller (keep in mind that you need to restart
> > the agent controller everytime that there is a change made to
> > serviceconfig.xml) and redo the steps that you have outlined below.
> >
> > Please attach your log file to this message or import your log file into
> > the
> > workbench to see if you observe any odd message. You can import the log
> > file in the workbench by selecting File > Import > Log File > Next > Add
>
> > Common Base Event XML log > Details > specify the path to servicelog.log
>
> > OK > Finish
> >
> > If you can't narrow down the problem, contact me at amehrega@ca.ibm.com
> > and
> > I'll try and follow upon the problem.
> >
> > "Vince Adamo" <vadamo@netefficiency.com> wrote in message
> > news:d99s0a$77p$1@news.eclipse.org...
> >> I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client
> >> machine
> >> running Eclipse SDK 3.0.2. I have also installed the Remote Agent
> >> controller (Release 3.0.2) on a remote server running Microsoft Windows
> >> Server 2003. I am attempting to monitor, from the client machine, a
> >> JBoss
> >> 4.0.2 JVM that was started on the remote server with
> >> the -XrunpiAgent:server=enabled option. I am able to successfully
attach
> > to
> >> the remote Java Profiling Agent from my client machine within the
Eclipse
> >> IDE, but when I click the icon to "Start Monitoring", the following
error
> >> dialog box pops up:
> >>
> >> "IWAT0003E Launch Java Process Error
> >>
> >> IWAT0004W Problems occurred while launching the Java process.
> >>
> >> Reason:
> >> Profiler unable to establish connection with RAC. Possible fix: Add
> >> more
> >> memory or reduce dataChannelSize in serviceconfig.xml."
> >>
> >> I reduced the dataChannelSize incrementally down to 128K, but I
continue
> > to
> >> get the error. I verified that the RAServer was using the correct
> >> dataChannelSize by looking at the servicelog.log file. I have also
> >> increased the heap size for the JBoss JVM to 1024M and I still continue
> >> to
> >> get the same error.
> >>
> >> I have looked through the archives and have not found a similar problem
> >> reported. Does anyone have any ideas?
> >>
> >> Thanks,
> >> Vince
> >>
> >>
> >
> >
>
>
>
|
|
|
| Re: Profiler unable to establish connection with RAC [message #35068 is a reply to message #20423] |
Wed, 12 October 2005 23:35 |
Kelvin Chu
Messages: 12
Registered: July 2009 |
Junior Member |
|
|
Hi Mehregani and Vince,
I am seeing the error message. And I am using the setup as Vince. What
was your solution? Thanks.
Kelvin
Ali Mehregani wrote:
> Hi Vince,
>
>
>
> After importing both log files in the workbench (using a 4.0 driver), I
> noticed that the last two sequences of commands were different. Assuming
> that your steps were identical under both scenarios (command and service),
> then I suspects the processed commands should be the same.
>
> The last two commands of the service mode log are 37 and 26 whereas the last
> two commands of the command mode log are 26 and 27.
>
> When you run the agent controller in service mode, do you have the
> <AgentController-HOME>\bin directory under your system path?
>
>
>
> There is a problem with the Eclipse site, and I can't download the agent
> controller code to determine what command these tags correspond to. I will
> follow upon this tomorrow. In the mean while, can you make sure that you
> have the bin directory of the agent controller in your system path before
> running the agent controller in service mode.
>
>
>
> Thanks,
>
>
>
> Ali M.
>
>
>
> "Vince Adamo" <vadamo@netefficiency.com> wrote in message
> news:d9s73n$aem$1@news.eclipse.org...
>
>>Ali,
>>
>>I have narrowed the problem down to the situation where the agent
>
> controller
>
>>is running as a service. When I run the agent controller in a command
>>prompt I am succesful in connecting and profiling the application. I have
>>attached two log files, one captured while the controller was running as a
>>service (servicelog.as.service.log) and the second captured while the
>>controller was run from the command prompt
>
> (servicelog.not.as.service.log).
>
>>I should also note that I switched to TPTP 3.3.0 while diagnosing this
>>problem. While it did not seem to have any effect on the problem stated
>>above, I am not succesful in importing the servicelog files into the
>>workbench. I get the following error: "An error occurred during the
>>execution of the remote log parser
>>" org.eclipse.hyades.logging.adapter.config.StaticParserWrappe r ": IWAT0373E
>>The adapter configuration file C:\...\GLA20914.dapter cannot be saved due
>
> to
>
>>the following reason: java.lang.NullPointerException".
>>
>>Thanks for your help.
>>
>>Vince
>>
>>"Ali Mehregani" <microbold@hotmail.com> wrote in message
>>news:d9g0vu$a25$1@news.eclipse.org...
>>
>>>Hi Vince,
>>>
>>>Just out of curiosity, are you able to launch the Java application
>>>remotely
>>>as opposed to attaching to it?
>>>
>>>Please follow the step below to see if you observe any odd behaviour:
>>>
>>> - Rename servicelog.log to servicelog.log.back under your
>>><AC-HOME>\config directory
>>> - Open the serviceconfig.xml file and change the value of the
>>>loggingLevel attribute from "INFORMATION" to "DEBUG".
>>> - Restart the Agent Controller (keep in mind that you need to restart
>>>the agent controller everytime that there is a change made to
>>>serviceconfig.xml) and redo the steps that you have outlined below.
>>>
>>>Please attach your log file to this message or import your log file into
>>>the
>>>workbench to see if you observe any odd message. You can import the log
>>>file in the workbench by selecting File > Import > Log File > Next > Add
>>
>>>Common Base Event XML log > Details > specify the path to servicelog.log
>>
>>>OK > Finish
>>>
>>>If you can't narrow down the problem, contact me at amehrega@ca.ibm.com
>>>and
>>>I'll try and follow upon the problem.
>>>
>>>"Vince Adamo" <vadamo@netefficiency.com> wrote in message
>>>news:d99s0a$77p$1@news.eclipse.org...
>>>
>>>>I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client
>>>>machine
>>>>running Eclipse SDK 3.0.2. I have also installed the Remote Agent
>>>>controller (Release 3.0.2) on a remote server running Microsoft Windows
>>>>Server 2003. I am attempting to monitor, from the client machine, a
>>>>JBoss
>>>>4.0.2 JVM that was started on the remote server with
>>>>the -XrunpiAgent:server=enabled option. I am able to successfully
>
> attach
>
>>>to
>>>
>>>>the remote Java Profiling Agent from my client machine within the
>
> Eclipse
>
>>>>IDE, but when I click the icon to "Start Monitoring", the following
>
> error
>
>>>>dialog box pops up:
>>>>
>>>>"IWAT0003E Launch Java Process Error
>>>>
>>>>IWAT0004W Problems occurred while launching the Java process.
>>>>
>>>>Reason:
>>>> Profiler unable to establish connection with RAC. Possible fix: Add
>>>>more
>>>>memory or reduce dataChannelSize in serviceconfig.xml."
>>>>
>>>>I reduced the dataChannelSize incrementally down to 128K, but I
>
> continue
>
>>>to
>>>
>>>>get the error. I verified that the RAServer was using the correct
>>>>dataChannelSize by looking at the servicelog.log file. I have also
>>>>increased the heap size for the JBoss JVM to 1024M and I still continue
>>>>to
>>>>get the same error.
>>>>
>>>>I have looked through the archives and have not found a similar problem
>>>>reported. Does anyone have any ideas?
>>>>
>>>>Thanks,
>>>>Vince
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
| Re: Profiler unable to establish connection with RAC [message #35107 is a reply to message #35068] |
Thu, 13 October 2005 03:57 |
No real name
Messages: 404
Registered: July 2009 |
Senior Member |
|
|
Hi Kelvin,
Please open a defect against this (http://www.eclipse.org/tptp/ > Click on
Submit Enhancements & Bugs > Report a new bug > TPTP > Select the
Platform.Execution component for the defect). Mention in your defect if the
problem is only reproducible in Windows 2003 and if you were able to work
around it by running the agent controller in command mode.
"Kelvin Chu" <kchu@actuate.com> wrote in message
news:dik6k8$5vc$1@news.eclipse.org...
> Hi Mehregani and Vince,
>
> I am seeing the error message. And I am using the setup as Vince. What
> was your solution? Thanks.
>
> Kelvin
>
> Ali Mehregani wrote:
> > Hi Vince,
> >
> >
> >
> > After importing both log files in the workbench (using a 4.0 driver), I
> > noticed that the last two sequences of commands were different.
Assuming
> > that your steps were identical under both scenarios (command and
service),
> > then I suspects the processed commands should be the same.
> >
> > The last two commands of the service mode log are 37 and 26 whereas the
last
> > two commands of the command mode log are 26 and 27.
> >
> > When you run the agent controller in service mode, do you have the
> > <AgentController-HOME>\bin directory under your system path?
> >
> >
> >
> > There is a problem with the Eclipse site, and I can't download the agent
> > controller code to determine what command these tags correspond to. I
will
> > follow upon this tomorrow. In the mean while, can you make sure that
you
> > have the bin directory of the agent controller in your system path
before
> > running the agent controller in service mode.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Ali M.
> >
> >
> >
> > "Vince Adamo" <vadamo@netefficiency.com> wrote in message
> > news:d9s73n$aem$1@news.eclipse.org...
> >
> >>Ali,
> >>
> >>I have narrowed the problem down to the situation where the agent
> >
> > controller
> >
> >>is running as a service. When I run the agent controller in a command
> >>prompt I am succesful in connecting and profiling the application. I
have
> >>attached two log files, one captured while the controller was running as
a
> >>service (servicelog.as.service.log) and the second captured while the
> >>controller was run from the command prompt
> >
> > (servicelog.not.as.service.log).
> >
> >>I should also note that I switched to TPTP 3.3.0 while diagnosing this
> >>problem. While it did not seem to have any effect on the problem stated
> >>above, I am not succesful in importing the servicelog files into the
> >>workbench. I get the following error: "An error occurred during the
> >>execution of the remote log parser
> >>" org.eclipse.hyades.logging.adapter.config.StaticParserWrappe r ":
IWAT0373E
> >>The adapter configuration file C:\...\GLA20914.dapter cannot be saved
due
> >
> > to
> >
> >>the following reason: java.lang.NullPointerException".
> >>
> >>Thanks for your help.
> >>
> >>Vince
> >>
> >>"Ali Mehregani" <microbold@hotmail.com> wrote in message
> >>news:d9g0vu$a25$1@news.eclipse.org...
> >>
> >>>Hi Vince,
> >>>
> >>>Just out of curiosity, are you able to launch the Java application
> >>>remotely
> >>>as opposed to attaching to it?
> >>>
> >>>Please follow the step below to see if you observe any odd behaviour:
> >>>
> >>> - Rename servicelog.log to servicelog.log.back under your
> >>><AC-HOME>\config directory
> >>> - Open the serviceconfig.xml file and change the value of the
> >>>loggingLevel attribute from "INFORMATION" to "DEBUG".
> >>> - Restart the Agent Controller (keep in mind that you need to
restart
> >>>the agent controller everytime that there is a change made to
> >>>serviceconfig.xml) and redo the steps that you have outlined below.
> >>>
> >>>Please attach your log file to this message or import your log file
into
> >>>the
> >>>workbench to see if you observe any odd message. You can import the
log
> >>>file in the workbench by selecting File > Import > Log File > Next >
Add
> >>
> >>>Common Base Event XML log > Details > specify the path to
servicelog.log
> >>
> >>>OK > Finish
> >>>
> >>>If you can't narrow down the problem, contact me at amehrega@ca.ibm.com
> >>>and
> >>>I'll try and follow upon the problem.
> >>>
> >>>"Vince Adamo" <vadamo@netefficiency.com> wrote in message
> >>>news:d99s0a$77p$1@news.eclipse.org...
> >>>
> >>>>I have installed Eclipse TPTP Release 3.0.2 on a Windows XP client
> >>>>machine
> >>>>running Eclipse SDK 3.0.2. I have also installed the Remote Agent
> >>>>controller (Release 3.0.2) on a remote server running Microsoft
Windows
> >>>>Server 2003. I am attempting to monitor, from the client machine, a
> >>>>JBoss
> >>>>4.0.2 JVM that was started on the remote server with
> >>>>the -XrunpiAgent:server=enabled option. I am able to successfully
> >
> > attach
> >
> >>>to
> >>>
> >>>>the remote Java Profiling Agent from my client machine within the
> >
> > Eclipse
> >
> >>>>IDE, but when I click the icon to "Start Monitoring", the following
> >
> > error
> >
> >>>>dialog box pops up:
> >>>>
> >>>>"IWAT0003E Launch Java Process Error
> >>>>
> >>>>IWAT0004W Problems occurred while launching the Java process.
> >>>>
> >>>>Reason:
> >>>> Profiler unable to establish connection with RAC. Possible fix: Add
> >>>>more
> >>>>memory or reduce dataChannelSize in serviceconfig.xml."
> >>>>
> >>>>I reduced the dataChannelSize incrementally down to 128K, but I
> >
> > continue
> >
> >>>to
> >>>
> >>>>get the error. I verified that the RAServer was using the correct
> >>>>dataChannelSize by looking at the servicelog.log file. I have also
> >>>>increased the heap size for the JBoss JVM to 1024M and I still
continue
> >>>>to
> >>>>get the same error.
> >>>>
> >>>>I have looked through the archives and have not found a similar
problem
> >>>>reported. Does anyone have any ideas?
> >>>>
> >>>>Thanks,
> >>>>Vince
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
|
|
|
Goto Forum:
Current Time: Thu Apr 25 11:03:22 GMT 2024
Powered by FUDForum. Page generated in 0.02946 seconds |
] 
Search
Help
Register
Login
Home
