Problem with delegation

Hi all,
I had delegated an object based on which I developed all m wfs. I had some problem with the delegation, i deleted and delegated it again, but none of my wfs works (there is a syntax error telling that one of the attribute component is not found),i understand that its a problem with the delegation. Is there a way out of this..
Regards,
Sathish.

Hi,
the synax error is probably related to the bindings from the event to the workflow. If you delete an attribute or rename it, then you should also check that the binding are still correct.
Kind regards, Rob Dielemans

Similar Messages

Problem with Delegated Adminstrator.

One hosted domain on my DA following problems:
Automatic appear a blank line in the top.
[http://img687.imageshack.us/img687/5368/69821783.png]
This hosted domain have 80 users, but there are two user display information about first name and display name on two lines ( user 1 and user 5) .
[http://img96.imageshack.us/img96/7421/78763072.png]
when I click on one of the two lines of user1 or user 5, i don't see anything about information of user ( blank page) so i can't edit user.
I have a group is [email protected], this group include all of user of this hosted domain, when click on this group to add or remove user but this page is blank.
Please help me!
./commadmin -V
Delegated Administrator 7.0-0.00 (B2009-03-31)

ergwertwrtfre wrote:
One hosted domain on my DA following problems:
Automatic appear a blank line in the top.
[http://img687.imageshack.us/img687/5368/69821783.png]
This hosted domain have 80 users, but there are two user display information about first name and display name on two lines ( user 1 and user 5) .
[http://img96.imageshack.us/img96/7421/78763072.png]
when I click on one of the two lines of user1 or user 5, i don't see anything about information of user ( blank page) so i can't edit user.
I have a group is [email protected], this group include all of user of this hosted domain, when click on this group to add or remove user but this page is blank.
I'm have not come across any of these problems with Delegated Administrator 7.
All I can suggest is to upgrade to DA7p1 (comes with comm-suite-7) and failing that log a Support request.
Regards,
Shane.

Problem with Delegated Administrator

Dear All
I am having probelm to get the JES2005/Q4 get working on my server,
installation goes okay with no error and installation log and events looks okay, after installation and configuration of Delegated administrator i can not login to DA with admin or amadmin username name and I keep getting invalid username msg. the funny thing is I can login to com express with admin username but not to DA. I tried almost everthing but I can not undrestand where is the problem
Any help is apperciated.
BR
Mo

DA is part of Sun Messaging Server deliveries and questions should be posted to the Sun Messaging Server forum.
Regards,
Ludovic.

Problem deleting users with delegated admin

Hello,
I seem to be having a problem deleting users with delegated administrator. I am using JES 2005Q4.
Here is what I do:
I set Inetuserstatus and mailuserstatus to deleted. Then run msuserpurge to delete the mail box. This seems to be working fine. Then I do a commadmin domain purge and it will actually delete the persons ldap record, but it does not delete the o=pab records or the o=PIserverDB records.
I am probably missing a step here, and would apprecidate it somebody could point me in the right direction.
Thanks,
Gary

DA patches:
119777-10 most current release for Solaris
119778 for X86
119779 for Linux
118540-23 Communication Express Solaris Sparc
118541 X86
118542 Linux
118207-42 Messaging core Solaris sparc
118208 X86
118209 Linux
116574-02 Veritas Vcsha (sparc only)
118242-03 and 118245-03 Dssetup sparc
118243 and 118246 X86
118247 Linux
122018-02 Outlook Connector
(all the currently released patches. Most have t-patches available from tech support post the above numbers)

Problem with configuring the application in websphere

Hi,
We have taken the back up of war file which was working and have deployed the same,We are using websphere as the application server due to some problem with the configuration we are getting the following error when we are trying to run the application.
Could any one please suggest on the same.
[7/22/08 5:04:30:766 EDT] 9f0473c WebGroup E SRVE0026E: [Servlet Error]-[GAServlet]: java.lang.NoClassDefFoundError: Error while defining class: com.xxrx.ga.al.GAServlet
This error indicates that the class: com.objectframe.servlet.OFServlet
could not be located while defining the class: com.xxrx.ga.al.GAServlet
This is often caused by having the class at a higher point in the classloader hierarchy
Dumping the current context classloader hierarchy:
==> indicates defining classloader
*** indicates classloader where the missing class could have been found
==>[0]
com.ibm.ws.classloader.CompoundClassLoader@1fec073f
Local ClassPath: C:\Documents and Settings\XG\Desktop\MyWorkspace\XG_Pilot\WebContent\WEB-INF\classes;C:\Documents and Settings\XG\Desktop\MyWorkspace\activation1;C:\Documents and Settings\XG\Desktop\MyWorkspace\classes121;C:\Documents and Settings\XG\Desktop\MyWorkspace\CLIENT-GDDRel40-QA.71;C:\Documents and Settings\XG\Desktop\MyWorkspace\cos1;C:\Documents and Settings\XG\Desktop\MyWorkspace\ejs1;C:\Documents and Settings\XG\Desktop\MyWorkspace\fscontext1;C:\Documents and Settings\XG\Desktop\MyWorkspace\jfoundations1;C:\Documents and Settings\XG\Desktop\MyWorkspace\JRAPI-GDDRel40-QA.71;C:\Documents and Settings\XG\Desktop\MyWorkspace\LOADER-GDDRel40-QA.71;C:\Documents and Settings\XG\Desktop\MyWorkspace\log4j1;C:\Documents and Settings\XG\Desktop\MyWorkspace\mail1;C:\Documents and Settings\XG\Desktop\MyWorkspace\MAILER-GDDRel40-QA.71;C:\Documents and Settings\XG\Desktop\MyWorkspace\mvcf-1.0.21;C:\Documents and Settings\XG\Desktop\MyWorkspace\providerutil1;C:\Documents and Settings\XG\Desktop\MyWorkspace\REPORT-GDDRel40-QA.71;C:\Documents and Settings\XG\Desktop\MyWorkspace\XG_Pilot\WebContent;
Delegation Mode: PARENT_FIRST
[1] com.ibm.ws.classloader.JarClassLoader@531728191 Local Classpath: Delegation mode: PARENT_FIRST
[2] com.ibm.ws.classloader.ExtJarClassLoader@1932756796 Local ClassPath: E:\XIP\IBM\WebSphere Studio\Application Developer IE\v5.1\runtimes\ee_v51\lib\app; Delegation Mode: PARENT_LAST
[3] com.ibm.ws.classloader.ProtectionClassLoader@723a473c
[4] com.ibm.ws.bootstrap.ExtClassLoader@3822873d
[5] sun.misc.Launcher$AppClassLoader@383fc73d
[6] sun.misc.Launcher$ExtClassLoader@3833c73d
---Original exception---
java.lang.NoClassDefFoundError: com/objectframe/servlet/OFServlet
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code))
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code))
at com.ibm.ws.classloader.CompoundClassLoader._defineClass(CompoundClassLoader.java:446)
at com.ibm.ws.classloader.CompoundClassLoader.findClass(CompoundClassLoader.java(Compiled Code))
at com.ibm.ws.classloader.CompoundClassLoader.loadClass(CompoundClassLoader.java:300)
at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code))
at java.beans.Beans.instantiate(Beans.java:201)
at java.beans.Beans.instantiate(Beans.java:62)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:188)
at com.ibm.ws.webcontainer.webapp.WebAppServletManager.getServletReference(WebAppServletManager.java:455)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletReference(WebApp.java:652)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcherInfo.calculateInfo(WebAppRequestDispatcherInfo.java:187)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcherInfo.<init>(WebAppRequestDispatcherInfo.java:68)
at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDispatcher(WebApp.java:1462)
at com.ibm.ws.webcontainer.webapp.WebApp.getRequestDispatcher(WebApp.java:1421)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:268)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:182)
at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:618)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:443)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
--- end Original exception----

Hi Guillaume,
I have been "playing" with section you mentioned since yesterday, but I could reach my goal :(
An example of the problem is as following:
Manager 1 is added to both “Project Managers” and “Resource Managers”. Accordingly he is added to “My Projects” category permission.
Manager2.TeamLead1 (not a descendent of Manager 1) is added to only “Project Managers” and accordingly he is added to “My Projects” category permission.
I want (Manager2.TeamLead1)’s projects to viewable only for his Manager 2 (and the Director), not for Manager 1, because the Manager1 is not responsible for managing his work
How can I achieve that ?? :)
Thanks,

Deleting users with Delegated Admin

Hope anyone can help with this:
When I delete a user with Delegated Admin (For Messaging 5.x) the user
seems to be deleted in iDA, but it is not deleted in LDAP.
Therefore, I cannot re-use it's attributes (like E-mail address) for
another (new) user.
This causes all kind of problems.
I can go into the Console and through away the user, then everything
works again. But I expected iDA also to delete the user if I use the
delete button.
Any ideas? Did I forget something?
Thanks in advance,
Niels de Troye

Hi..
the nda does not remove the user... is put it in suspend mode...
you have to run the imsimta purge command to remove the user.. or to wait
the server to do that
in a day or so....
take a look at the manual to see how you can do that...
"N. de Troye" wrote:
Hope anyone can help with this:
When I delete a user with Delegated Admin (For Messaging 5.x) the user
seems to be deleted in iDA, but it is not deleted in LDAP.
Therefore, I cannot re-use it's attributes (like E-mail address) for
another (new) user.
This causes all kind of problems.
I can go into the Console and through away the user, then everything
works again. But I expected iDA also to delete the user if I use the
delete button.
Any ideas? Did I forget something?
Thanks in advance,
Niels de Troye--
Over and Out
Giorgos Kiriakidis
Technical Department
NetSmart S.A.
Panepistimiou 58.
Athens 10678
Hellas
Tel +3013302608
Fax +3013302658
Email [email protected]
This message contains confidential information intended for a specific
individual and purpose,
is protective by law. If you are not the intended recipient, you should
delete this message.
Any disclosure, coping, distribution or taking any action based on this
message is strictly prohibited.

Problems with deleted domain

Someone created a domain and then deleted it. The domain purge did not work so I deleted the entries with the ldapdelete command on the directory server. The problem now is that when I try to create the domain again on the Delegated Administrator I still get the following error:
Status: CreateDomain
Failed:
This container is already in use.
When I run the ldapsearch I do not find this domain. What could be the problem??
I'm using this messaging server version:
iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)
libimta.so 5.2 Patch 1 (built 23:25:07, Aug 19 2002)
SunOS mail 5.9 Generic_112233-05 sun4u sparc SUNW,UltraAX-i2
with delegated administrator version .1.2

First, you NEED to upgrade to at least patch 2. Your code is years old.
You should also upgrade your DA, as 1.2p2 has long been available.
There must be something left of your domain entry, or DA wouldn't be choking on it. Examine your Access Log for when you try to add it, and see what search came back with results. Duplicate that search on the command line, and see what that data is.

Massive problems with BlackBerry ID/BIS/App World after provider switch

Hi,
I recently switched providers and got a bunch of different problems since then. The old provider deleted my BIS account, which of course also disabled the push mail functionality on my BlackBerry. I tried to register a new account with my new provider, which didn't work for unknown reasons. After several calls to my new providers hotline they finally suggested to reset my BB to factory default and try registering again. After the reset, pretty much the very first thing I was prompted with was the BlackBerry ID login. I used my old login and right after that, in the mail setup dialog, got the error again that there's a problem with the applications server and I can't create or login with a BIS account. I wondered how it could know my BIS account, so I did another factory reset and this time created a new BlackBerry ID. This time everything went fine, the new BIS account was created within seconds and a test mail was delivery to my device immediately. I was pretty happy, until I noticed that I couldn't restore all my data from BlackBerry Protect because of the new BlackBerry ID. Also all my apps were gone from App World, which is linked to the BlackBerry ID as well. So what I'm wondering now is
1) why is my BIS account linked to my BlackBerry ID,
2) how can I unlink it and use my new BIS account with my old BlackBerry ID and
3) if I can't, how do I get my BlackBerry Protect data and App World purchases back?
I'd prefer having the first two questions answered, because I'm sure switching providers and therefore BIS accounts is a pretty common thing, so there must be some do this right, right? I hope there's some way to fix it, because if I have to choose between "keep apps but live without email" and "have push mail and repurchase all apps", I'd probably choose Android instead.
PS: I also tried to find a way to contact RIM, so they could somehow unlink my old BIS account from my BlackBerry ID, but there's really not such a thing as "BlackBerry Support". The only thing I found was a button on the App World page for refunds etc, but even there the link was dead.
Solved!
Go to Solution.

I have no insight into if the carrier you are using should or should not be on that list. All I have is what you reported (that they can't escalate) coupled with that list...which leads me to conclude that they are not a fully authorized BB carrier. They would seem to be somehow affiliated though, since indeed you were able to set up BIS services with them. But, I do know of other carriers that are not listed...and as I recall they are something of a sub to a fully authorized carrier, and somehow provide services through that other carrier (who has the formal contract with RIM). I'm really guessing here as I have absolutely no insight into anything authoritative on this matter.
Regarding the contractually required formal support model...it works like this. You contract with a carrier for services. As part of that contract, you agree to a support model, and that support model starts with them (normally...as I said earlier, some models in some regions use service centers instead...you must review your specific documentation to know what the actual support model is for your specific contract). Consequently, all service-related support needs that you have must start with your carrier (or service center)...contractually, you are not allowed to bypass them and seek formal help direct from RIM. Hence the cost of the direct-to-RIM Incident Support system...you are electing to bypass your contract, and doing so is not "free". (There are also contracts between the carriers and RIM which further require that the carriers provide that front-line support to their end users, and provide the carriers with certain controls over some things that the end users are allowed access to...but that's just in support of the contract between you and your carrier.)
Now, in some situations (yours included, sadly), it gets even more complex. What I said above applies solely to the services you receive on your BB (voice, data, email, etc.). But, that has nothing to do with support for the device itself (e.g., warranty)...that's a separate contract, and was executed at the time of purchase between you and your place of purchase. That place of purchase (or assigned service center) is responsible for all support for the device itself (warranty, etc.). Again, this servicing (e.g., warranty) is delegated from RIM to the resellers...RIM provides zero front line support for devices, services, etc...none...all of that is contractually delegated down from RIM to various other entities (the carriers, resellers, service centers, etc.). RIM provides warranty and such, but the servicing of such is provided by others from a front line perspective...again, escalation into RIM is available to those front-line entities, but not to end users (save for the fee-based Incident Support model).
In your case, this could get quite messy. All too often, a service related issue is ignored by the carrier if they discover that they also did not originally sell the device to the end user (if they sold both the device and service, they would be responsible for all support for everything). They have a sad tendency to "blame the device" when it's really a service issue, and ignore the plea from the end user. Despicable, yes...but it happens all too often. And it get's worse...the device support entity will often likewise blame the service entity. The sad part of this bad scenario is that it's the end user who is left out in the cold with no service nor support from anyone that will actually aid their situation. Hopefully, this really poor outcome happens only rarely...but I know 100% (from reports on this forum) that it does happen more than 0%. I hope it does not come to pass for you, but I thought I'd warn you about it just in case so that you can be prepared for it.
All in all, I think what I'd suggest is that you press 1udn1 for support and escalation on this. Get them to tell you why they have no escalation path since, as far as you understand, they are 100% responsible for all of your service-related support, and that is exactly what this situation is, and they need to resolve it for you one way or another. Escalate with them to managers with them...the front line folks you reach likely won't have any authority to do anything "off script"...and you'll likely need that. Stress to them that you PAY THEM for your services and service-related support...and right now they are delivering neither to you, yet you continue to PAY THEM. Get them to reveal why they have no escalation capability...and see if they will reveal that they are sub to another carrier who does have that capability, and see if you can escalate that way.
You also may want to contact your former carrier...perhaps they did not fully release something related to your BB/BIS account, and that is what is preventing it from migrating to your new device? It is quite normal to migrate a BIS account from device to device (15 in one year, as I recall), so that one can retain their AW purchase records and such. This holds true crossing carriers...indeed, I've had one BIS account for years, and it started on one carrier and is now on a different one, and all my things are properly intact. Something is wrong "inside" preventing yours from doing so, and that needs attention "inside" to resolve for you.
Good luck!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Problems with iCal invitees 10.6.8

Hi
I have just upgraded fro 10.5 server to 10.6 server, Ialthough iCal is basically workign Ok I cannot work out what to do about a problem with attendees in iCal.
Whenever I try to add an attended i iCal, as I start typing it tries to autocomplete just as it used to in 10.5, However, whichever attendee i select, it always ends up with an exclamation mark next to it, and I get an error message:
The server responded:
“HTTP/1.1 403 Forbidden”
to operation CalDAVWriteEntityQueueableOperation.
I dont quite believe the error message, there is not a problem with my permissions as such, because I can create and edit and delete events in this calendar to my heart's content. This shared calendar was created with iCal Server Utility, and i used calendarserver_manage_principlas to give me write permission. I know i have write permission fr this calendar, because I *can* write i, and because I can see in my delegation settings that I have write permission.
As this is a shared calendar, so I just tried to add an attendee to an event in my own calendar. the behaviour is similar, I get the exclamation mark, but no error message.
Is it relevant that we are currently *not* runnign a mail srver
Can anyone suggest what I can do to breathje life into this feature please - attendees are pretty important for us.
May thanks for any help.

Put your install DVD into the optical drive (CD/DVD drive) and reboot. Be sure to either use the disc that came with your Mac, or, if you installed a later Mac OS X version from disc, use the newer disc. As soon as you hear the boot chime, hold down the "c" key on your keyboard (or the Option Key until the Install Disk shows up) until the apple shows up. That will force your MacBook to boot from the install DVD in the optical drive.
When it does start up, you'll see a panel asking you to choose your language. Choose your language and press the Return key on your keyboard once. It will then present you with an Installation window. Completely ignore this window and click on Utilities in the top menu and scroll down to Disk Utility and click it. When it comes up is your Hard Drive in the list on the left?
If it is, then click on the Mac OS partition of your hard drive in the left hand list. Then select the First Aid Tab and run Repair Disk. The Repair Disk button won't be available until you've clicked on the Mac OS partition on your hard drive. If that repairs any problems run it again until the green OK appears and then run Repair Permissions. After repairing use Startup Disk from the same menu to choose your hard drive for restarting from your hard drive.

J2ee agent 2.2 configuration problem with Websphere Portal 5.1

Hi,
I am trying to configure j2ee agent 2.2 with Websphere Portal server.
I have followed the document "Sun Java SystemAccess Manager
PolicyAgent 2.2 Guide for IBM WebSphere Portal Server 5.1.0.2"
Please see the thread "Problem with Sun's SSO system and Websphere Portal Server integration" for environment related information.
Also the security on app server has been enabled and is talking to LDAP.
My aim here is to enable application server (portal server) to autheticate requests.
I am getting following error when I log into the portal application.
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: now processing: SSO Task Handler
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
SSOTaskHandler: SSO Validation failed for null
07/03/2007 06:32:16:062 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: unknown certificate
     at com.ibm.jsse.bs.a(Unknown Source)
     at com.ibm.jsse.bs.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmFilter: result =>
FilterResult:
     Status      : FORBIDDEN
     RedirectURL     : null
     RequestHelper:
          null
     Data:
          null
07/03/2007 06:32:16:078 PM IST: Thread[Servlet.Engine.Transports : 1,5,main]
AmIdentityAsserter: result => TAIResult: status: 403, principal: null, subject: null
From whatever analysis I have done so far, I believe this issue is related to the personal certificate for sun one webserver (on which access manager & LDAP are installed) not registered with the application server (portal server).
I am not sure about the way I go by solving the issue.
Please can anybody help me out.
Thanks,
Yaseer
Message was edited by:
yazee
Message was edited by:
yazee

Ankush,
I am getting error as follows in the webserver error log:-
Error receiving request from 172.23.213.75 (SSL_ERROR_CERTIFICATE_UNKNOWN_ALERT: SSL peer had some unspecified issue with the certificate it received)
Although I can get into am console but with https://apollo.maxnewyorklife.com/amconsole
Tried the same thing, but couldnt resolve it. I will give it another go.
Generally I am getting same error again and again.
In my amWebsphere log file of j2ee agent (under root\am_wps_agent\agent_001\logs\debug) error I get.....
07/15/2007 04:19:11:656 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
AmFilter: now processing: SSO Task Handler
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTokenValidator.validate(): Exception caught
com.iplanet.sso.SSOException: Invalid sessionid formatjava.lang.IllegalArgumentException: Invalid server id in session id com.iplanet.services.naming.ServerEntryNotFoundException: Naming Service is not available.
     at com.iplanet.sso.providers.dpro.SSOProviderImpl.createSSOToken(SSOProviderImpl.java:205)
     at com.iplanet.sso.SSOTokenManager.createSSOToken(SSOTokenManager.java:325)
     at com.sun.identity.agents.common.SSOTokenValidator.validateInternal(SSOTokenValidator.java:252)
     at com.sun.identity.agents.common.SSOTokenValidator.validate(SSOTokenValidator.java:157)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:88)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
SSOTaskHandler: SSO Validation failed for AQIC5wM2LY4SfcwoaNKFd01DvjYeNPbR3wXaa9sMVjcKtwo=@AAJTSQACMDE=#
07/15/2007 04:19:11:766 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: Checking if https://apollo.maxnewyorklife.com:443/amserver/UI/Login is available
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
WARNING: URLFailoverHelper: the url https://apollo.maxnewyorklife.com:443/amserver/UI/Login is not available
javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.bw.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.v.a(Unknown Source)
     at com.ibm.jsse2.u.a(Unknown Source)
     at com.ibm.jsse2.bx.a(Unknown Source)
     at com.ibm.jsse2.bx.l(Unknown Source)
     at com.ibm.jsse2.bx.startHandshake(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)
     at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown Source)
     at com.ibm.net.ssl.internal.www.protocol.https.HttpsURLConnection.connect(Unknown Source)
     at com.sun.identity.agents.common.URLFailoverHelper.isAvailable(URLFailoverHelper.java:190)
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:129)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Caused by: com.ibm.jsse2.util.g: No trusted certificate found
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.f.b(Unknown Source)
     at com.ibm.jsse2.util.d.a(Unknown Source)
     at com.ibm.jsse2.bn.checkServerTrusted(Unknown Source)
     at com.ibm.jsse2.z.checkServerTrusted(Unknown Source)
     ... 39 more
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
URLFailoverHelper: disconnected the connection for availability check
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: URLFailoverHelper: No URL is available at this time
07/15/2007 04:19:11:797 PM IST: Thread[Servlet.Engine.Transports : 0,5,main]
ERROR: AmFilter: Error while delegating to inbound handler: SSO Task Handler, access will be denied
[AgentException Stack]
com.sun.identity.agents.arch.AgentException: No URL is available at this time
     at com.sun.identity.agents.common.URLFailoverHelper.getAvailableURL(URLFailoverHelper.java:133)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getLoginURL(AmFilterRequestContext.java:757)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:285)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectURL(AmFilterRequestContext.java:258)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:363)
     at com.sun.identity.agents.filter.AmFilterRequestContext.getAuthRedirectResult(AmFilterRequestContext.java:345)
     at com.sun.identity.agents.filter.SSOTaskHandler.doSSOLogin(SSOTaskHandler.java:210)
     at com.sun.identity.agents.filter.SSOTaskHandler.process(SSOTaskHandler.java:98)
     at com.sun.identity.agents.filter.AmFilter.processTaskHandlers(AmFilter.java:189)
     at com.sun.identity.agents.filter.AmFilter.isAccessAllowed(AmFilter.java:152)
     at com.sun.identity.agents.websphere.AmIdentityAsserterBase.processRequest(AmIdentityAsserterBase.java:195)
     at com.sun.identity.agents.websphere.AmTrustAssociationInterceptor.negotiateValidateandEstablishTrust(AmTrustAssociationInterceptor.java:91)
     at com.ibm.ws.security.web.TAIWrapper.negotiateAndValidateEstablishedTrust(TAIWrapper.java:101)
     at com.ibm.ws.security.web.WebAuthenticator.handleTrustAssociation(WebAuthenticator.java:191)
     at com.ibm.ws.security.web.WebAuthenticator.authenticate(WebAuthenticator.java:928)
     at com.ibm.ws.security.web.WebCollaborator.authorize(WebCollaborator.java:531)
     at com.ibm.ws.security.web.EJSWebCollaborator.preInvoke(EJSWebCollaborator.java:262)
     at com.ibm.ws.webcontainer.webapp.WebAppSecurityCollaborator.preInvoke(WebAppSecurityCollaborator.java:132)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:506)
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
     at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
     at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
     at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
     at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)
     at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)
     at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:652)
     at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
Thanks,
Yaseer

I like the new version of Firefox 4, but have slowest problem with the company bluecoat proxy. I have change different setting in the about:config. Any Ideas how to to fix the slowest.

I like the new version of Firefox 4, But have slowing problem with the bluecoat proxy. I have change different setting in the about:config with no luck. Any ideas why it's moving so slow would help?
network.automatic-ntlm-auth.trusted-uris = proxysg
network.negotiate-auth.delegation-uris=proxysg
network.negotiate-auth.trusted-uris=proxysg
network.negotiate-auth.allow-proxies = True
network.ntlm.send-lm-response = True
network.automatic-ntlm-auth.allow-proxies=True

You can also look at Tab Mix Plus.
Tab Mix Plus: https://addons.mozilla.org/firefox/addon/1122

A problem with threads

I am trying to implement some kind of a server listening for requests. The listener part of the app, is a daemon thread that listens for connections and instantiates a handling daemon thread once it gets some. However, my problem is that i must be able to kill the listening thread at the user's will (say via a sto button). I have done this via the Sun's proposed way, by testing a boolean flag in the loop, which is set to false when i wish to kill the thread. The problem with this thing is the following...
Once the thread starts excecuting, it will test the flag, find it true and enter the loop. At some point it will LOCK on the server socket waiting for connection. Unless some client actually connects, it will keep on listening indefinatelly whithought ever bothering to check for the flag again (no matter how many times you set the damn thing to false).
My question is this: Is there any real, non-theoretical, applied way to stop thread in java safely?
Thank you in advance,
Lefty

This was one solution from the socket programming forum, have you tried this??
public Thread MyThread extends Thread{
     boolean active = true;
     public void run(){
          ss.setSoTimeout(90);
          while (active){
               try{
                    serverSocket = ss.accept();
               catch (SocketTimeoutException ste){
               // do nothing
     // interrupt thread
     public void deactivate(){
          active = false;
          // you gotta sleep for a time longer than the
          // accept() timeout to make sure that timeout is finished.
          try{
               sleep(91);
          }catch (InterruptedException ie){
          interrupt();
}

Problem with Threads and a static variable

I have a problem with the code below. I am yet to make sure that I understand the problem. Correct me if I am wrong please.
Code functionality:
A timer calls SetState every second. It sets the state and sets boolean variable "changed" to true. Then notifies a main process thread to check if the state changed to send a message.
The problem as far I understand is:
Assume the timer Thread calls SetState twice before the main process Thread runs. As a result, "changed" is set to true twice. However, since the main process is blocked twice during the two calls to SetState, when it runs it would have the two SetState timer threads blocked on its synchronized body. It will pass the first one, send the message and set "changed" to false since it was true. Now, it will pass the second thread, but here is the problem, "changed" is already set to false. As a result, it won't send the message even though it is supposed to.
Would you please let me know if my understanding is correct? If so, what would you propose to resolve the problem? Should I call wait some other or should I notify in a different way?
Thanks,
B.D.
Code:
private static volatile boolean bChanged = false;
private static Thread objMainProcess;
   protected static void Init(){
        objMainProcess = new Thread() {
            public void run() {
                while( objMainProcess == Thread.currentThread() ) {
                   GetState();
        objMainProcess.setDaemon( true );
        objMainProcess.start();
    public static void initStatusTimer(){
        if(objTimer == null)
             objTimer = new javax.swing.Timer( 1000, new java.awt.event.ActionListener(){
                public void actionPerformed( java.awt.event.ActionEvent evt){
                          SetState();
    private static void SetState(){
        if( objMainProcess == null ) return;
        synchronized( objMainProcess ) {
            bChanged = true;
            try{
                objMainProcess.notify();
            }catch( IllegalMonitorStateException e ) {}
    private static boolean GetState() {
        if( objMainProcess == null ) return false;
        synchronized( objMainProcess ) {
            if( bChanged) {
                SendMessage();
                bChanged = false;
                return true;
            try {
                objMainProcess.wait();
            }catch( InterruptedException e ) {}
            return false;
    }

Thanks DrClap for your reply. Everything you said is right. It is not easy to make them alternate since SetState() could be called from different places where the state could be anything else but a status message. Like a GREETING message for example. It is a handshaking message but not a status message.
Again as you said, There is a reason I can't call sendMessage() inside setState().
The only way I was able to do it is by having a counter of the number of notifies that have been called. Every time notify() is called a counter is incremented. Now instead of just checking if "changed" flag is true, I also check if notify counter is greater than zero. If both true, I send the message. If "changed" flag is false, I check again if the notify counter is greater than zero, I send the message. This way it works, but it is kind of a patch than a good design fix. I am yet to find a good solution.
Thanks,
B.D.

Problem with threads running javaw

Hi,
Having a problem with multi thread programming using client server sockets. The program works find when starting the the application in a console using java muti.java , but when using javaw multi.java the program doesnt die and have to kill it in the task manager. The program doesnt display any of my gui error messages either when the server disconnect the client. all works find in a console. any advice on this as I havent been able to understand why this is happening? any comment would be appreciated.
troy.

troy,
Try and post a minimum code sample of your app which
does not work.
When using javaw, make sure you redirect the standard
error and standard output streams to file.
Graeme.Hi Graeme,
I dont understand what you mean by redirection to file? some of my code below.
The code works fine under a console, code is supposed to exit when the client (the other server )disconnects. the problem is that but the clientworker side of the code still works. which under console it doesnt.
public class Server{
ServerSocket aServerSocket;
Socket dianosticsSocket;
Socket nPortExpress;
ClientListener aClientListener;
LinkedList queue = new LinkedList();
int port = 0;
int clientPort = 0;
String clientName = null;
boolean serverAlive = true;
* Server constructor generates a server
* Socket and then starts a client threads.
* @param aPort      socket port of local machine.
public Server(int aPort, String aClientName, int aClientPort){
port = aPort;
clientName = aClientName;
clientPort = aClientPort;
try{
// create a new thread
aServerSocket = new ServerSocket(port) ;
// connect to the nPortExpress
aClientListener = new ClientListener(InetAddress.getByName(clientName), clientPort, queue,this);
// aClientListener.setDaemon(true);
aClientListener.start();
// start a dianostic port
DiagnosticsServer aDiagnosticsServer = new DiagnosticsServer(port,queue,aClientListener);
// System.out.println("Server is running on port " + port + "...");
// System.out.println("Connect to nPort");
catch(Exception e)
// System.out.println("ERROR: Server port " + port + " not available");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Server port " + port + " not available", JOptionPane.ERROR_MESSAGE);
serverAlive = false;
System.exit(1);
while(serverAlive&&aClientListener.hostSocket.isConnected()){
try{
// connect the client
Socket aClient = aServerSocket.accept();
//System.out.println("open client connection");
//System.out.println("client local: "+ aClient.getLocalAddress().toString());
// System.out.println("client localport: "+ aClient.getLocalPort());
// System.out.println("client : "+ aClient.getInetAddress().toString());
// System.out.println("client port: "+ aClient.getLocalPort());
// make a new client thread
ClientWorker clientThread = new ClientWorker(aClient, queue, aClientListener, false);
// start thread
clientThread.start();
catch(Exception e)
//System.out.println("ERROR: Client connection failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client connection failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end constructor Server
void serverExit(){
     JOptionPane.showMessageDialog(null, "Server ","ERROR: nPort Failure", JOptionPane.ERROR_MESSAGE);
     System.exit(1);
}// end class Server
*** connect to another server
public class ClientListener extends Thread{
InetAddress hostName;
int hostPort;
Socket hostSocket;
BufferedReader in;
PrintWriter out;
boolean loggedIn;
LinkedList queue;      // reference to Server queue
Server serverRef; // reference to main server
* ClientListener connects to the host server.
* @param aHostName is the name of the host eg server name or IP address.
* @param aHostPort is a port number of the host.
* @param aLoginName is the users login name.
public ClientListener(InetAddress aHostName, int aHostPort,LinkedList aQueue,Server aServer)      // reference to Server queue)
hostName = aHostName;
hostPort = aHostPort;
queue = aQueue;
serverRef = aServer;
// connect to the server
try{
hostSocket = new Socket(hostName, hostPort);
catch(IOException e){
//System.out.println("ERROR: Connection Host Failed");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort Failed", JOptionPane.ERROR_MESSAGE);
System.exit(0);
} // end constructor ClientListener
** multi client connection server
ClientWorker(Socket aSocket,LinkedList aQueue, ClientListener aClientListener, boolean diagnostics){
queue = aQueue;
addToQueue(this);
client = aSocket;
clientRef = aClientListener;
aDiagnostic = diagnostics;
} // end constructor ClientWorker
* run method is the main loop of the server program
* in change of handle new client connection as well
* as handle all messages and errors.
public void run(){
boolean alive = true;
String aSubString = "";
in = null;
out = null;
loginName = "";
loggedIn = false;
while (alive && client.isConnected()&& clientRef.hostSocket.isConnected()){
try{
in = new BufferedReader(new InputStreamReader(client.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(client.getOutputStream()));
if(aDiagnostic){
out.println("WELCOME to diagnostics");
broadCastDia("Connect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
out.println("WELCOME to Troy's Server");
broadCastDia("Connect : client "+client.getInetAddress().toString());
     out.flush();
String line;
while(((line = in.readLine())!= null)){
StringTokenizer aStringToken = new StringTokenizer(line, " ");
if(!aDiagnostic){
broadCastDia(line);
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
else{
if(line.equals("GETIPS"))
getIPs();
else{
clientRef.sendMessage(line); // send mesage out to netExpress
out.println(line);
out.flush();
} // end while
catch(Exception e){
// System.out.println("ERROR:Client Connection reset");
                         JOptionPane.showMessageDialog(null, (e.toString()),"ERROR:Client Connection reset", JOptionPane.ERROR_MESSAGE);
try{
if(aDiagnostic){
broadCastDia("Disconnect : diagnostics "+client.getInetAddress().toString());
out.flush();
else {
broadCastDia("Disconnect : client "+client.getInetAddress().toString());
     out.flush();
// close the buffers and connection;
in.close();
out.close();
client.close();
// System.out.println("out");
// remove from list
removeThreadQueue(this);
alive = false;
catch(Exception e){
// System.out.println("ERROR: Client Connection reset failure");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Client Connection reset failure", JOptionPane.ERROR_MESSAGE);
}// end while
} // end method run
* method run - Generates io stream for communicating with the server and
* starts the client gui. Run also parses the input commands from the server.
public void run(){
boolean alive = true;
try{
// begin to life the gui
// aGuiClient = new ClientGui(hostName.getHostName(), hostPort, loginName, this);
// aGuiClient.show();
in = new BufferedReader(new InputStreamReader(hostSocket.getInputStream()));
out = new PrintWriter(new OutputStreamWriter(hostSocket.getOutputStream()));
while (alive && hostSocket.isConnected()){
String line;
while(((line = in.readLine())!= null)){
System.out.println(line);
broadCast(line);
} // end while
} // end while
catch(Exception e){
//     System.out.println("ERRORa Connection to host reset");
JOptionPane.showMessageDialog(null, (e.toString()),"ERROR: Connection to nPort reset", JOptionPane.ERROR_MESSAGE);
try{
hostSocket.close();
     }catch(Exception a){
     JOptionPane.showMessageDialog(null, (a.toString()),"ERROR: Exception", JOptionPane.ERROR_MESSAGE);
alive = false;
System.exit(1);
} // end method run

Problem with threads and camera.

Hi everybody!
I've a problem with taking snapshot.
I would like to display a loading screen after it take snapshot ( sometimes i
have to wait few seconds after i took snapshot. Propably photo is being taken in time where i have to wait).
I was trying to use threads but i didn't succeed.
I made this code:
display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while((!performing.isShown()) && (backgroundCamera.isShown())){
                    Thread.yield();
                notifyAll();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    this.wait();
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();This code is sometimes showing performing screen but sometimes no.
I don't know why. In my opinion performing.isShown() method isn't working correctly.
Does anyone have some idea how to use threads here?

Hi,
I've finally managed to work this fine.
The code:
       Object o = new Object();
       display.setCurrent(perform);
        new Thread(new Runnable(){
            public void run() {
                while(!performing.isShown()){
                    Thread.yield();
               synchronized(o) {
                  o.notify();
        }).start();
        new Thread(new Runnable(){
            public void run() {
                try {
                    synchronized(o) {
                       o.wait(1);
                } catch(Exception e) {
                    exceptionHandler(e);
                photo = camera.snapshot();
                display.setCurrent(displayPhoto);
        }).start();

Problem with delegation

Similar Messages

Maybe you are looking for