Error when connecting local tomcar-server

[tbehrends]

Hi!

I was trying to profile my local application-server (tomcat 5) which was started from Eclipse 3.0 using a tomcat-pluging.

Starting the server works fine (with the profiler-dll). But when connecting the server from the profiler frontend (server: localhost, port: 10000) an error dialog with following message opens:

"Assertion failed: ourJVMPI, fileDumper.cpp, line 1624"

Greetings,
tom

[tbehrends]

BTW, this stopped my Application-Server. Could the error-popup was raised by the server.

[Vladimir Kondratyev]

This is _very_ interesting issue. Definitely it's a bug in profiler agent. Couldn't you please provide us with URL where we can download the same Tomcat plugin.

[tbehrends]

Hi!

This won't be neccessary - I've got the same phenomen when starting tomcat manually (with startup.bat).

I tried both Java 1.4.2 and 1.5 - with the same error. My System:

- Windows XP Professional
- 512 MB Memory
- Pentium M 1.3 GHz
- LAN connection (fixed IP)

Also, I've problems setting the port for the listener (I thought changing the port may help). When setting the port with the port - parameter, the system ignores this and always uses 10000. But there is no error message saying the parameter was misspelled.

Maybe it's the Tomcat-version. I'll try Tomcat 4.1 tomorrow.

Greeting,
tom

[Anton Katilin]

Could you please sent your modified startup.bat at [email protected].

[tbehrends]

Hi!

I tested my windows-client with my linux-server and this is okay. I must be the windows-DLL.

tom

[Vladimir Kondratyev]

I'm afraid I didn't understand your latest message. Do you still experience the problem?

[tbehrends]

Yes (only with windows applications). But I didnt install the latest release. Did you change anything the the yjpagent.dll?

[Vladimir Kondratyev]

Did you change anything the the yjpagent.dll?

we are changing code constantly. BTW, it seems that you are the one who has this problem. Please send us your startup.bat script you are using to launch Tomcat.

[tbehrends]

Hello,

I sent my startup to [email protected] last week. Maybe I should send it to another address?

[Anton Katilin]

Could you please:

1. Try Tools | Integrate with J2EE Server... action in the latest build 425.
2. If it doesn't help, could you please replace your Tomcat startup script with original one (from Tomcat distribution archive) and try Tools | Integrate with J2EE Server... again. If it still doesn't work please send us both original and modified scripts at [email protected]
3. Probably you have obsolete versions of yjpagent.dll. Please search your disks for yjpagent.dll and remove all found except for one from build 425.

[tbehrends]

I installed the build 425 and it works now! Thx

[adelhaj]

Hi,

I have the following setup. Tomcat 4.1.24 and j2sdk1.4.2_05. We have a servlet and us the following batch file to start the application ( this one has been modified using the "Integ with J2EE Server" option.

File details below:
rem Generated with YourKit Java Profiler 4.0.10

set PATH=D:\Program Files\YourKit Java Profiler 4.0.10\bin\win32;%PATH%
set JAVA_TOOL_OPTIONS=-agentlib:yjpagent=sessionname=Tomcat %JAVA_TOOL_OPTIONS%
set CATALINA_BASE=.
set CATALINA_HOME=d:\dev\tomcat\v4.1.24
set CATALINA_TMPDIR=d:\temp
set JAVA_OPTS=-server -Xmx256M

rem to perform remote debugging, change the JPDA
rem transport to dt_socket and set the JPDA_ADDRESS
rem to a port like 53002. Then, in karmira, connect
rem via socket.
set JPDA_TRANSPORT=dt_socket
set JPDA_ADDRESS=53000
set DEBUG=
if not ""%1"" == ""-debug"" goto doStart

set DEBUG=jpda
echo %DEBUG%

:doStart
%CATALINA_HOME%\bin\catalina %DEBUG% start -config %CATALINA_BASE%\conf\server.xml
goto end

:end

_______________________________________________

I've tried everything and I still am not able to connect to my local app or any remote app. I've tried both options and its not working. My issue is figuring out which port to use for the profiler. I ran netstat -ano to try and find the port put still having NO LUCK. Here is the netstat details:

netstat details
------------
D:\Projects\siemens>netstat -ano

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1640
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:1042 0.0.0.0:0 LISTENING 1256
TCP 0.0.0.0:1521 0.0.0.0:0 LISTENING 2264
TCP 0.0.0.0:3017 0.0.0.0:0 LISTENING 3584
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1532
TCP 0.0.0.0:5001 0.0.0.0:0 LISTENING 2676
TCP 0.0.0.0:8009 0.0.0.0:0 LISTENING 2676
TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING 2676
TCP 127.0.0.1:1060 0.0.0.0:0 LISTENING 3408
TCP 127.0.0.1:2095 127.0.0.1:2096 ESTABLISHED 628
TCP 127.0.0.1:2096 127.0.0.1:2095 ESTABLISHED 628
TCP 127.0.0.1:2259 127.0.0.1:2260 ESTABLISHED 2280
TCP 127.0.0.1:2260 127.0.0.1:2259 ESTABLISHED 384
TCP 127.0.0.1:3039 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3040 127.0.0.1:3041 ESTABLISHED 2280
TCP 127.0.0.1:3041 127.0.0.1:3040 ESTABLISHED 2676
TCP 127.0.0.1:3042 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3043 127.0.0.1:3044 ESTABLISHED 2280
TCP 127.0.0.1:3044 127.0.0.1:3043 ESTABLISHED 2676
TCP 127.0.0.1:3045 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3046 127.0.0.1:3047 ESTABLISHED 2280
TCP 127.0.0.1:3047 127.0.0.1:3046 ESTABLISHED 2676
TCP 127.0.0.1:3048 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3049 127.0.0.1:3050 ESTABLISHED 2280
TCP 127.0.0.1:3050 127.0.0.1:3049 ESTABLISHED 2676
TCP 127.0.0.1:3051 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3052 127.0.0.1:3053 ESTABLISHED 2280
TCP 127.0.0.1:3053 127.0.0.1:3052 ESTABLISHED 2676
TCP 127.0.0.1:3054 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3055 127.0.0.1:3056 ESTABLISHED 2280
TCP 127.0.0.1:3056 127.0.0.1:3055 ESTABLISHED 2676
TCP 127.0.0.1:3057 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3058 127.0.0.1:3059 ESTABLISHED 2280
TCP 127.0.0.1:3059 127.0.0.1:3058 ESTABLISHED 2676
TCP 127.0.0.1:3060 127.0.0.1:1521 TIME_WAIT 0
TCP 127.0.0.1:3061 127.0.0.1:3062 ESTABLISHED 2280
TCP 127.0.0.1:3062 127.0.0.1:3061 ESTABLISHED 2676
TCP 127.0.0.1:8005 0.0.0.0:0 LISTENING 2676
TCP 192.168.2.230:139 0.0.0.0:0 LISTENING 4
TCP 192.168.2.230:1061 192.168.2.230:1521 ESTABLISHED 2280
TCP 192.168.2.230:1097 10.1.0.93:1026 ESTABLISHED 3708
TCP 192.168.2.230:1100 10.1.0.96:1329 ESTABLISHED 3708
TCP 192.168.2.230:1148 207.46.106.166:1863 ESTABLISHED 3568
TCP 192.168.2.230:1521 192.168.2.230:1061 ESTABLISHED 2264
TCP 192.168.2.230:1808 0.0.0.0:0 LISTENING 2252
TCP 192.168.2.230:1809 0.0.0.0:0 LISTENING 2252
TCP 192.168.2.230:2356 207.68.178.16:80 CLOSE_WAIT 3568
TCP 192.168.2.230:2506 192.168.2.149:139 ESTABLISHED 4
TCP 192.168.2.230:2922 192.168.2.31:445 ESTABLISHED 4

----------------------------------

The onlytime I was able to bring this up was using the eclipse plugin and that will not be an option in my current scenario. I'm thinking of buying this tool since I really like it but the setup has been harsh on me.

my e-mail is [email protected], so you can also contact me if you need more detail on things I missed.

THANKS

[Vladimir Kondratyev]

Please check Tomcat's log file to find which port is used by profiler

[adelhaj]

Please check Tomcat's log file to find which port is used by profiler

Thanks for the reply? I'd read that here as well, but I look inside the logs and I don't see anything. Which log file are you refering too?? Is there a specific one I should be looking at.

And if you could explain in short about "the port used by the profiler"? Is this different than the port used by tomcat??

Thanks