Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

EAS35 remote debugging from PoweJ

4 posts in General Discussion (old) Last posting was on 2000-02-17 21:22:19.0Z
<=one way=> Posted on 2000-02-17 05:55:24.0Z
Newsgroups: sybase.public.easerver
From: "<=one way=>" <oneway_111@yahoo.com>
Subject: EAS35 remote debugging from PoweJ
Date: Thu, 17 Feb 2000 00:55:24 -0500
Lines: 71
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01BF78E1.AC61F9A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host: oppenheimer163.oppenheimerfunds.com 216.44.5.163
Message-ID: <347_dsMybyQe$GA.332@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28526
Article PK: 160675

The following message is raised in PowerJ while attempting to debug a component running in EAS on a remote machine.
 
The task was not loaded. The application cannot be debugged. The remote Sun VM may not be started, or you may have mistyped the name of the remote machine, or you may have mistyped the Agent password.
 
This is strange because:
1) sometimes it actually works though most of the time the above message is shown
1) the remote Sun VM 1.1.x in EAS is running (debug version of EAS is used)
2) when connection to EAS is tested from PJ Deploy and Run options window, the test is successful
3) com.sybase.jaguar.component.debug = true for that component.
 
TIA
 


Dave Wolf [Sybase] Posted on 2000-02-17 14:53:09.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: EAS35 remote debugging from PoweJ
Date: Thu, 17 Feb 2000 09:53:09 -0500
Lines: 95
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0023_01BF792C.CC1DA500"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: dwolf-nt.sybase.com 157.133.41.127
Message-ID: <347_YgVW0cVe$GA.223@forums.sybase.com>
References: <347_dsMybyQe$GA.332@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28515
Article PK: 160671

Can you please open a tech support case.  I keep hearing reports of this but cannot reproduce it myself.

Dave Wolf
Internet Applications Division
 
<=one way=> <oneway_111@yahoo.com> wrote in message news:dsMybyQe$GA.332@forums.sybase.com...
The following message is raised in PowerJ while attempting to debug a component running in EAS on a remote machine.
 
The task was not loaded. The application cannot be debugged. The remote Sun VM may not be started, or you may have mistyped the name of the remote machine, or you may have mistyped the Agent password.
 
This is strange because:
1) sometimes it actually works though most of the time the above message is shown
1) the remote Sun VM 1.1.x in EAS is running (debug version of EAS is used)
2) when connection to EAS is tested from PJ Deploy and Run options window, the test is successful
3) com.sybase.jaguar.component.debug = true for that component.
 
TIA
 


<=one way=> Posted on 2000-02-17 21:22:19.0Z
Newsgroups: sybase.public.easerver
From: "<=one way=>" <oneway_111@yahoo.com>
Subject: Re: EAS35 remote debugging from PoweJ
Date: Thu, 17 Feb 2000 16:22:19 -0500
Lines: 117
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BF7963.29DAC6B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host: oppenheimer163.oppenheimerfunds.com 216.44.5.163
Message-ID: <347_bhlhb4Ye$GA.324@forums.sybase.com>
References: <347_dsMybyQe$GA.332@forums.sybase.com> <347_YgVW0cVe$GA.223@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28448
Article PK: 154670

props.put("com.sybase.ejb.socketReuseLimit","1") and etc does not seem to help.
 
TIA
Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message news:YgVW0cVe$GA.223@forums.sybase.com...
Can you please open a tech support case.  I keep hearing reports of this but cannot reproduce it myself.

Dave Wolf
Internet Applications Division
 
<=one way=> <oneway_111@yahoo.com> wrote in message news:dsMybyQe$GA.332@forums.sybase.com...
The following message is raised in PowerJ while attempting to debug a component running in EAS on a remote machine.
 
The task was not loaded. The application cannot be debugged. The remote Sun VM may not be started, or you may have mistyped the name of the remote machine, or you may have mistyped the Agent password.
 
This is strange because:
1) sometimes it actually works though most of the time the above message is shown
1) the remote Sun VM 1.1.x in EAS is running (debug version of EAS is used)
2) when connection to EAS is tested from PJ Deploy and Run options window, the test is successful
3) com.sybase.jaguar.component.debug = true for that component.
 
TIA
 


<=one way=> Posted on 2000-02-17 21:04:41.0Z
Newsgroups: sybase.public.easerver
From: "<=one way=>" <oneway_111@yahoo.com>
Subject: Re: EAS35 remote debugging from PoweJ
Date: Thu, 17 Feb 2000 16:04:41 -0500
Lines: 130
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0009_01BF7960.B30D2E30"
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host: oppenheimer163.oppenheimerfunds.com 216.44.5.163
Message-ID: <347_WK5ZkuYe$GA.332@forums.sybase.com>
References: <347_dsMybyQe$GA.332@forums.sybase.com> <347_YgVW0cVe$GA.223@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28453
Article PK: 160613

We'll open a case though I have not heard anything of use from support for a long time.
 
The following message is shown in the PJ's console.
Internal Debugger Error: StartDebugger() failed: java.net.ConnectException: Connection refused.
 
The monitor shows only 3 sessions open.
Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message news:YgVW0cVe$GA.223@forums.sybase.com...
Can you please open a tech support case.  I keep hearing reports of this but cannot reproduce it myself.

Dave Wolf
Internet Applications Division
 
<=one way=> <oneway_111@yahoo.com> wrote in message news:dsMybyQe$GA.332@forums.sybase.com...
The following message is raised in PowerJ while attempting to debug a component running in EAS on a remote machine.
 
The task was not loaded. The application cannot be debugged. The remote Sun VM may not be started, or you may have mistyped the name of the remote machine, or you may have mistyped the Agent password.
 
This is strange because:
1) sometimes it actually works though most of the time the above message is shown
1) the remote Sun VM 1.1.x in EAS is running (debug version of EAS is used)
2) when connection to EAS is tested from PJ Deploy and Run options window, the test is successful
3) com.sybase.jaguar.component.debug = true for that component.
 
TIA