I'm not sure what is going on but one good way to diagnose these problems is to 
turn on the debug logging on the client and server.  In this case, since it 
seems to be a problem with the basic connections, you should use the 
"Endpoint.*" target on the server.  In WEB-INF/flex/services-config.xml, find 
level=  change that to Debug and make sure Endpoint.* is in the targets below. 

 

On the client, I'd also turn on <mx:TraceTarget/>.  

 

The other thing I find that is helpful is to look at the configuration which is 
getting compiled into your SWF.  When you compile your app, you point it at the 
server's configuration and it copies a subset of that config into the variable:

 

mx.messaging.config.ServerConfig.xml

 

you can print that out at startup (actually, this is done automatically by 
mx:TraceTarget).

 

The last thing I'll mention quickly just to be sure you is that if you are 
using HTTP based channels, the player is using the same HTTP session on the 
server as any jsp files running in that same web application.  It sounds like 
things may work when you are dealing with a pre-authenticated session but fail 
when the session is not in place.  It is relatively common that people will put 
a security filter into the web.xml file to enforce security.  If one of these 
filters runs before the MessageBrokerServlet (also in web.xml) it may prevent 
flex from contacting the server in the case where the filter aborts or 
redirects the request because the authentication has failed. 

 

Jeff

 

________________________________

From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Greg 
Morphis
Sent: Wednesday, October 17, 2007 9:43 AM
To: [email protected]
Subject: Re: [flexcoders] Re: Unknown destination 'EmployeeServiceRO

 

Still havent found anything with this. One thing I didnt mention yesterday is 
that there is a folder with a security check.. 
Just a simple check...


<p>security test for app</p>
<%
  if ( request.getUserPrincipal() != null) {
%>
    Your user principal name is
    <b><%= request.getUserPrincipal().getName() %></b><br><br>
<%
  } else {
%>
    No user principal could be identified.<br><br> 
<%
  }
%>
<%
    if (request.isUserInRole("AOPScheduler-BASICINQ")) {
%>
      You have been granted role AOPScheduler-BASICINQ<br><br>
<%    
    }
    if ( request.isUserInRole("AOPScheduler-BASICAM"))    { 
%>
    You have been granted role AOPScheduler-BASICAM<br><br>
<%
    }   
%>

I can hit the url which is protected, I'm prompted to log in. I log in and it 
works... 

security test for app 

Your user principal name is 1234567

You have been granted role AOPScheduler-BASICAM


So the roles seem to be working.. If I take change the url and take off the 
/security/ (to the root folder) I get the same error..
Anything else anyone can throw out there to check? Please? I'm getting 
frustrated with this 








On 10/16/07, Greg Morphis <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:

So I copied the folder down from dev to my local machine. 
I was able to run the app from there.. But I cannot build my copy in Eclipse 
and run it. WTF?!?!?!
This is pissing me off.... 

 

On 10/16/07, Greg Morphis <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote:

I copied the tomcat folder from our dev server down to my local machine, since 
both of the installations are in the same place 
C:\Tomcat5.5
The server started fine, I cleaned and rebuilt the app.. same error. I don't 
think it's a tomcat config issue.. 

 

On 10/16/07, Greg Morphis < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > 
wrote:

I'll give that a try in a little bit, I'll have to modify the main view and 
security login page to ignore the current way of loading. I think the answer 
will be "no, no destination is being found"

Thanks

 

On 10/16/07, Anatole Tartakovsky < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
> wrote:

Is it the only destination not being found? Can you create another destination, 
 and debug in something like this:

 

mb = MessageBroker.getMessageBroker(null);
srv = 
(RemotingService)mb.getServiceByType("flex.messaging.services.RemotingService");
RemotingDestination remotingDestination = 
(RemotingDestination)srv.getDestination(destinationName);// debug in 
 

Regards,
Anatole


 

On 10/16/07, Dimitrios Gianninas < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
> wrote: 

Hmm not sure if this is the problem but dont create roles names with any 
special characters, dashes ( - ) in your case. I know Weblogic has a problem 
with this when we named our roles with underscores in them. In WL we also need 
to define them in the WEB-NF/weblogic.xml, not sure if this is the case for 
Tomcat. 

 

As for not being able to connect, hmmm..is there any more errors before this 
one?

 

Dimitrios Gianninas

Development Team Lead

Optimal Payments Inc.

 

 

________________________________

From: [email protected] <http://ups.com/>  [mailto: flexcoders@ 
<mailto:flexcoders@> yahoogroups.com <http://yahoogroups.com> ] On Behalf Of 
Greg Morphis
Sent: Tuesday, October 16, 2007 9:53 AM 
To: [EMAIL PROTECTED] ups.com <http://ups.com/> 


Subject: [flexcoders] Re: Unknown destination 'EmployeeServiceRO


 

Anyone? Has no one seen this error before? Does everything look correct?
This is with Flex 2 / LCDS on Tomcat with Java middleware.

Thanks

On 10/15/07, Greg Morphis < [EMAIL PROTECTED] <mailto:gmorphis%40gmail.com> > 
wrote:
> I'm condensing my previous posts..
> ----------------------------------------------------
> getting this error on a flex app..
>
> [FaultEvent fault=[RPC Fault faultString="[MessagingError 
> message='Unknown destination 'EmployeeServiceRO'.']"
> faultCode="InvokeFailed" faultDetail="Couldn't establish a connection
> to 'EmployeeServiceRO'"] 
> messageId="47E7A8FA-EB41-1E60-A96D-A474ECC048D1"
> type="fault"
> bubbles=false
> cancelable=true eventPhase=2]
>
> I've checked the remoting-config.xml
> 
> <destination id="EmployeeServiceRO">
> <properties>
> <source>com.alltel.rapid.aopscheduler.business.EmployeeDelegate</source>
> <scope>application</scope> 
> </properties>
> <security>
> <security-constraint>
> <auth-method>Basic</auth-method>
> <roles>
> <role>AOPScheduler-BASICAM</role>
> <role>AOPScheduler-BASICINQ</role>
>
> </roles>
> </security-constraint>
> </security>
>
> </destination>
>
> I installed log4j and I see this when I log in.. 
> 2007-10-15 11:59:48,812 [http-8080-Processor24] DEBUG
> org.apache.catalina.realm.RealmBase - Username e0087890 has role
> AOPScheduler-BASICINQ
> 2007-10-15 11:59:48,812 [http-8080-Processor24] DEBUG 
> org.apache.catalina.realm.RealmBase - No role found:
> AOPScheduler-BASICINQ
>
> But I have the roles defined:
> In the web.xml file
> <auth-constraint>
> <role-name>AOPScheduler-BASICAM</role-name> 
> <role-name>AOPScheduler-BASICINQ</role-name>
> </auth-constraint>
> </security-constraint>
>
> and
> <security-role>
> <description>
> The role that is required to log in to the Manager Application 
> </description>
> <role-name>AOPScheduler-BASICAM</role-name>
> </security-role>
> <security-role>
> <description>
> The role that is required to log in to the Reader Application 
> </description>
> <role-name>AOPScheduler-BASICINQ</role-name>
> </security-role>
>
>
> So to me everything looks okay, what am I missing?
> The odd thing is that we store the code in CVS, I've checked out a 
> fresh copy of the code and everything looks good. The only thing I can
> think of is something not configured right in Tomcat?
>

AVIS IMPORTANT

WARNING

Ce message électronique et ses pièces jointes peuvent contenir des 
renseignements confidentiels, exclusifs ou légalement privilégiés destinés au 
seul usage du destinataire visé. L'expéditeur original ne renonce à aucun 
privilège ou à aucun autre droit si le présent message a été transmis 
involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes 
pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, 
veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses 
pièces jointes, de votre système. La lecture, la distribution, la copie ou tout 
autre usage du présent message ou de ses pièces jointes par des personnes 
autres que le destinataire visé ne sont pas autorisés et pourraient être 
illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en 
aviser l'expéditeur. 

This electronic message and its attachments may contain confidential, 
proprietary or legally privileged information, which is solely for the use of 
the intended recipient. No privilege or other rights are waived by any 
unintended transmission or unauthorized retransmission of this message. If you 
are not the intended recipient of this message, or if you have received it in 
error, you should immediately stop reading this message and delete it and all 
attachments from your system. The reading, distribution, copying or other use 
of this message or its attachments by unintended recipients is unauthorized and 
may be unlawful. If you have received this e-mail in error, please notify the 
sender. 





 

 





 

 

Reply via email to