Re-login problem with WLS 5.1 sp8

Hi,
I have a re-login problem with a war servlet: user called reader does not have
viewing access to all views of a web interface. When she tries to access those
views a new login dialog comes up as should. The problem is that this new dialog
does not accept power user login as I would like it to! Any ideas how to change
the configuration in either web.xml or weblogic.properties file to make it work?
In Tomcat environment it works.
BR Jukka

Similar Messages

Servlet reloading not working with WLS 5.1 sp8

          I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
          problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
          work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
          the servler reloading works fine.
          Does anybody experience similar problem or have I forgot to do something?
          WLS properties/env vars setting:
          - weblogic.httpd.servlet.reloadCheckSecs=0
          - WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
          - JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
          Thanks in advance for any help.


          I've experienced the same problem with both sp6 and sp8. In both cases I performed several test, including
          - varied the value of weblogic.httpd.servlet.reloadCheckSecs
          - changes to the package depth the servlet belonged to
          - changes to the string length of the package names the servlet belonged to
          At best, the servlet would reload sometimes. I've moved back to sp5 and the problem has subsided.
          Note: I did not try registering the servlet to see how that would effect the dynamic reloading.
          Hope this helps
          - Dave
          "Michel Dinh" <[email protected]> wrote:
          >
          >I downloaded and installed WLS 5.1's sp8 to fix the "java.net.SocketException: Connection aborted by peer: socket write error"
          >problem. Although that problem is fixed, I have found that, however, the servlet (automatic) reloading does not
          >work anymore. If I remove the sp8 from my Java system classpath and WL classpath (i.e. not using sp8), then
          >the servler reloading works fine.
          >
          >
          >Does anybody experience similar problem or have I forgot to do something?
          >
          >WLS properties/env vars setting:
          >
          >- weblogic.httpd.servlet.reloadCheckSecs=0
          >- WEBLOGIC_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8.jar;...
          >- JAVA_CLASSPATH=%WEBLOGIC_HOME%\lib\weblogic510sp8boot.jar;...
          >
          >Thanks in advance for any help.

General install and deployment problem with WLS clustering on two boxes

Hi,
I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
Any help appriecated.
Surfbum.

Hi I think I've found the answer. You can build a managed server template using the pack command.
http://e-docs.bea.com/common/docs90/pack/tasks.html

Apache-soap Problem with WLS 5.1sp9

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

I have problem with WLS 5.1sp9.
My environment is the following :
jaf-1.0.1
javamail-1.2
soap-2.2
xerces-1.4.4
and I want to call EJB.
So, I write some EJB and deploy it.
And rpcrouter work!!
Success to deploy the Service.
But I run into problem with calling this ejb.
This error is the following.
SOAP-ENV:Server.BadTargetObjectURI
Unable to resolve target object: BC2_BoardSync
please, help me.
here's my example..
ps.
sorry for my poor English..T_T
[ws5.10.zip]
[vb.zip]

Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

We are using simplified chinese, after swith to bea jdriver, it messed up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince except webservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error. Is
there a way to turn off isolation level in workshop? I tried manually edit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

I did try to change the value in this config file as well, but did not help.
In fact, the installation default setting is with
'<transaction-isolation-level>' commented out.
And when I use bea oracle jdriver, it somehow messed up with database
character set encoding, so our Chinese characters could not be retrieved
correctly. And I try to set the encoding of jdriver to 'GBK', it did not
work.
"Anurag Pareek" <[email protected]> Ð´ÈëÏûÏ¢ÐÂÎÅ
:[email protected]..
Hello Ma,
The transaction isolation level value for EJBs backing the JWS files is
specified in the <transaction-isolation-level> tag in the
WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
manipulate this value to serve your purpose.
Please do let me know how it goes.
Regards,
Anurag
Workshop Support
"Ma Jie" <[email protected]> wrote in message
news:[email protected]..
We are using simplified chinese, after swith to bea jdriver, it messed
up
all the encoding. So we cannot display Chinese character correctly.
We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
environment, BEA supplied JDK 1.3.1_03.
We have many diffrent problems with oracle drivers:
1. We want to use XA driver to support distributed transaction, However:
* bea jdriver xa messes up with encoding
* when using oracle 901 driver, everything works fince exceptwebservices.
Workshop application access the ejb, then the workshp application sets
isolation level, but oracle driver does not support it and gives error.Is
there a way to turn off isolation level in workshop? I tried manuallyedit
weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
2. When not using XA, oracle thin driver works fine. But we lost XA
capability.
Any work around?

AD account Login problem with MAC 10.6.8

Hi All,
We have around 50 odd MAC that are connected to windows server 2008 R2. the user were logining in to these MACs using their AD account. Recently few of the random MAC did not allow the user to login using their AD account.When analyzed though the MAC shows that it has connected to the Domain and the server is active with green button it has unbind itself from the server.I had to login in as local user bind the MAC back to get this resolved.
Now the same has started happeneing for most of the MAC that we have and every morning I have login as local Admin and unbind / bind the MAC with the server. this gets reset once the user reboots or shutsdown.
Have tried with few of the below solution but nothing helped:
Solution 1:
<key>mdns_timeout</key>
<integer>2</integer>
The integer value is in seconds; changing it to at least 5 should allow the Mac OS X client to reconnect to the Active Directory domain after a network interruption. In some configurations, a larger timeout value may be required.
You can change this value by using the sudo command and a text editor to edit the preference file directly. Or you can use the Terminal command below, making sure to enter it all on a single line:
sudo /usr/libexec/PlistBuddy -c 'Set :mdns_timeout 5' /System/Library/SystemConfiguration/IPMonitor.bundle/Contents/Info.plist
Solution 2:
I have seen all of the probable solutions and tried everything and still I am getting issues with 10.6.6 and after rebooting the Mac gets unbind. Or the Mac gets Network Accounts Available even when not accessing the list of users from AD. But the thing that I have done that has solved all my issues with AD on the Macs is to uncheck the box to search on all domains. For some reason I am seeing that when the Macs have this option checked, it searches through out the forest on the same domain controller more than once, so AD stops the handshaking of the authentication.
I hope this helps like it did on our Network, since then I have not seen the Macs lose the binding or slow SMB.
If you've tried this please let us know.
TIP: Uncheck Allow Authentication from any domain for Mac AD problems
Wednesday, April 20, 2011
Steven Wells sent a fix and an explanation of problems with Macs losing their binding to Active Diretory:
Unchecking "Allow authentication from any domain in the forest" is working at our college. We have been beating our heads on this for about 2 terms, with no understanding of why it works in some places and not in others. When we found this working, our IT guy said that the Security SID is being duplicated, when it looks in other domain forest, and that is what is causing the problem. This is the first time I have found an explanation for the problem.
If you've tried this approach please let us know.
Solution 3:
Solved it. Create a file in Textedit with the name 'auto_master' (no file extension) with the following contents:
# Automounter master map
+auto_master # Use directory service
/net -hosts -nobrowse,hidefromfinder,nosuid
/home auto_home -nobrowse,hidefromfinder
#/Network/Servers -fstab
/- -static
Place this in /etc/ folder
Hope this helps
solution 4:
TIP: a Kerberos fix for OS X 10.5 and 10.6 binding to Active directory
Friday, November 11, 2011
Mehdi Mafi forwarded a fix he found for problems with Leopard and Snow Leopard binding to Active Directory:
This was taken from Dane Riley's imaging building for DeployStudio.
With Mac OS X Leopard every Mac is now running a KDC (Kerberos Distribution Center). Basically each imaged machine is using the same security certificate and hash. Deploying a single image will deploy the same KDC to every system. This [Apple] article covers how to reset the local KDC so that each system is unique. Basically, do the following:
Launch Keychain Access
Search for com.apple.kerberos.kdc and delete all 3 items
Using Terminal type sudo rm -fr /var/db/krb5kdc
After deployment, perhaps using Apple Remote Desktop to all systems, re- establish the KDC by typing sudo /usr/libexec/configureLocalKDC
If you've tried this approach with Mac OS X 10.5, 10.6, or even Lion, please let us know. .
TIP: More on a kerberos fix for AD binding problems
Monday, November 14, 2011
Mehdi Mafi updated his Friday report about Mac OS X 10.6 problems binding to Active Directory:
You may want to add this. If the Mac keeps unbinding from AD (people can't log in to a Mac), here is how to fix it:
Unbind it from Domain
Launch Keychain Access
Search for com.apple.kerberos.kdc and delete all 3 items
Using Terminal type sudo rm -fr /var/db/krb5kdc
Re-establish the KDC by typing sudo /usr/libexec/configureLocalKDC
Bind it to domain again ( When you bind, uncheck allow authentication from any domain in the forest in: Directory Utilitiy-> Advanced Options\Administrative ) this fix the issue that sometimes it can' find AD under search space.
If you tried this please let us know.
Solution 5:
For Snow Leopard AD login issues, use upper case domain
Solution 6: for .local
To create this StartupItem, create the following directory as root:
/Library/StartupItems/FixADAuth
Then chown it to root:wheel and chmod it to 755. These must also be the owner/permissions on the two files it will contain, below:
Contents of our /Library/StartupItems/FixADAuth/FixADAuth:
#!/bin/bash
. /etc/rc.common
date > /var/log/FixADAuth.log
n=0
AuthSuccess=0
while [ $AuthSuccess != 1 ]
do
id Administrator && AuthSuccess=1 || networksetup -setsearchdomains Ethernet "Empty"; networksetup -setsearchdomains Ethernet middlewich.local; n=$(($n+1))
done
echo Authentication successful: $AuthSuccess >> /var/log/FixADAuth.log echo Operation count: $n >> /var/log/FixADAuth.log
date >> /var/log/FixADAuth.log
Contents of our /Library/StartupItems/FixADAuth/StartupParameters.plist:
Description = "Fixes Active Directory authentication issue";
Uses = ("Disks");
Obviously you'll need to change "middlewich.local" to your own domain name (and the network interface name if your connection is wireless). The script checks to see if it can see the user "Administrator" on the domain, as he's a fairly common bloke, but if you've renamed yours for security reasons then pick another one. I've also included some logging functionality for debug purposes, so you can verify how well the script is working if you need to and time it in your environment before telling the users how long to wait. The /var/log/FixADAuth.log file will contain the date/time the process started, the success variable set to 1 (just to verify), how many DNS operations were required to fix the problem, and the date/time it ended. For us the time difference is normally about +30-40 seconds with around 120-180 operations taking place. Once you're happy with the script, you can strip it down to its bare functionality if you like, like so for us:
#!/bin/bash
. /etc/rc.common
AuthSuccess=0
while [ $AuthSuccess != 1 ]
do
id Administrator && AuthSuccess=1 || networksetup -setsearchdomains Ethernet "Empty"; networksetup -setsearchdomains Ethernet middlewich.local
done
I hope this helps someone!
Regards

You are welcome.
But the question is 10.6 mac just like 10.6.8 , as long as its the same and works.
Yes. You can save some updates by using the combo update.
10.6.8 Combo Updater

Problems with WLS 4.5.1 and F5 Big IP HA+ Switch

Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
          4.5.1 servers (two in the pool currently). At seemly random intervals the
          Big IP believes the one or both of the servers are not responding, so they
          are removed from the pool. We have a growing body of anecdotal evidence to
          suggest that the servers are actually on-line and available during the
          event. Either the switch is confused or the WLS servers aren't always
          responding correctly to the HTTP requests sent by the switch for polling.
          We're having problems catching the problem with the right diagnostics.
          Has anyone out there observed similar behavior with these components?
          Thanks.
          - Sean McRae


Sort of,
          I use iplanet between the 2, so I havent had this problem, but I have had
          several problems with clustering, here is what I recomend doing:
          write a simple java program (or whatever your prefered language) to do a HTTP
          ping on your distinct weblogic servers every X seconds/minutes where X is less
          than Big IPs death tolerance. Time how long/or if ever each of your pings take.
          turn on verbose gc.
          My guess is its one of 3 things:
          1.) your have a big gc going on and your server isnt responding quick enough
          and big ip is marking it dead
          2.) you have thread contention that is causing your server not to respond quick
          enough
          3.) your network has some issues and the packets arent making it there, or not
          quick enough.
          the ping program will prove/disprove #2 and lead you to or away from 3. Verbose
          gc will prove/disprove #1.
          hope this helps
          -Joel
          Sean wrote:
          > Hello. We're having problems with our F5 Big IP HA+ switch and pool of WLS
          > 4.5.1 servers (two in the pool currently). At seemly random intervals the
          > Big IP believes the one or both of the servers are not responding, so they
          > are removed from the pool. We have a growing body of anecdotal evidence to
          > suggest that the servers are actually on-line and available during the
          > event. Either the switch is confused or the WLS servers aren't always
          > responding correctly to the HTTP requests sent by the switch for polling.
          > We're having problems catching the problem with the right diagnostics.
          >
          > Has anyone out there observed similar behavior with these components?
          >
          > Thanks.
          >
          > - Sean McRae

ConnectionPool problems with WLS 7.0 and Oracle 9.2

Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
application on the productive system (and only there) we constantly encounter
a whole set of SQLExceptions which have all in common that the Connection from
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSet
- Connection has already been closed
- Closed Statement
- Transaction is no longer active - status committing
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()
There are no special Statements which create these errors. They are spread at
random across practically every query the application creates, and the same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSets are
closed immediately after use. As an example, I attached a code snippet and a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrent usern,
since in the approval tests on an almost identical test system these errors never
occurred.
I also followed the advice from Oracle and installed the latest Oracle JDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in the application
classpath (via a reference in the Manifest file of the application jar), not in
the system classpath? There has never been a problem with that, but in a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script creates for the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath? If
it is possible, why is it necessary?
Best regards,
Andreas Zehrt
[CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

Andreas Zehrt wrote:
Hi Joe,
Your hint that there is a threading problem was right:
On further investigation of the code I found out that the class that passes the
Connection to the DAO not only stores it as a member at some point (which is not
a good idea anyway) but is also a singleton - then, of course, it's no surprise
that the Connection gets invalid in a incalculable way when concurrent threads
share it.
The singleton instantiation was not so obvious because the way of instantiation
is controlled by a configuration parameter that can be overridden at different
levels.
I changed it and the productive logfiles indicate that the SQLExceptions related
to that class have disappeared.I am happy to have helped.
So, thanks a lot for the advice.
But I am still wondering why this code has worked for so long a time with WLS
5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
it was multi-user environment.Mo idea.
I still believe that there is a difference between WLS 5.1 and 7.0 in the way
it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
a little more explicit about those changes and possible version incompatabilities
beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
effect in this case, I will certainly do what I can to see that our documentation
is explicit about changes.
Joe
Best regards, Andreas
Joe Weinstein <[email protected]> wrote:
Hi Andreas.
Andreas Zehrt wrote:
Hi,
We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
application on the productive system (and only there) we constantlyencounter
a whole set of SQLExceptions which have all in common that the Connectionfrom
the pool is not valid any more when the application tries to use it.
Typical, recurring error messages are:
- Exhausted ResultSetThat is typically if the statement that created it is either re-executed
or closed.
- Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
would show
where it was originally closed.
- Closed Statementsame as above.
- Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
datasource,
and then later trying to use it after the transaction which it was associated
with,
is finished.
- NullPointerException at
weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
There are no special Statements which create these errors. They arespread at
random across practically every query the application creates, andthe same queries
sometimes succeed and sometimes fail.
I double and triple checked that all Connections, Statements and ResultSetsare
closed immediately after use. As an example, I attached a code snippetand a resulting
StackTrace which.
The problem also seems to occur only with an (unknown) minimum of concurrentusern,
since in the approval tests on an almost identical test system theseerrors never
occurred.
I also followed the advice from Oracle and installed the latest OracleJDBC driver
(Oracle 10g) - to no avail.
What else can I do?
Another question: Is it correct that my Oracle JDBC driver is in theapplication
classpath (via a reference in the Manifest file of the applicationjar), not in
the system classpath? There has never been a problem with that, butin a Newsgroup
answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
suggested to "get it listed at the
front of the -classpath argument that the startWebLogic script createsfor the
java line that starts the server".
I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
Is it possible and safe to add a jar located there to the system classpath?If
it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
We also ship
an oracle thin driver, which becomes obsolete soon...
I am concerned that your code creates pool connections to be used later.
The problems
can arise if more than one thread ever gets the same connection, or if
the connection
is used in the same thread, spanning transactions. It does also seem
that there may
be a threading issue, because if two threads each call the code to create
a connection,
and two connections are made, but one over-writes the other, the two
threads can
end up using the same connection, and closing it. The over-written one
never gets closed,
resulting in that leak message you got...
Joe
The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
several classes in the business layer, but not used, until the DAOtakes it to make the query.
So, the Connection is closed where it was opened, not in the DAO class.
public class ConcernDAOImpl extends BaseDAO {
     public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
throws DataAccessException, ConstraintException, ComaParseException{>
sqlMessage.append(")");
String sqlStmt = sqlMessage.toString();
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
pstmt = conn.prepareStatement(sqlStmt);
rs = pstmt.executeQuery();
while (rs != null && rs.next()) {
final Concern concern =
new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
return concerns;
} catch (SQLException sqle) {
// Wrapps real SQL exception
String[] message = new String[]{sqle.getMessage(), sqlStmt};
throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
sqle);
} finally {
closeAll(rs, pstmt);
_logger.exitDebug(method);
Here, the Connection is acquired and finally closed
public class ComaServiceProviderClassicImpl {
     public void updateComplaint(
final Request updateRequest,
final ResponseSingleElement response,
final Principal principal)
throws SystemException {
try {
logger.info("updateComplaint", "store incident");
// store the incident in the database
incidentManager.storeIncident(getConnection(), updateIncident);
// reload the incident from Cache and / or the databaseto get the ContactReferences.
Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
getConnection(), updateIncident.getOID());
} catch (RemoteException rex) {
// remote exceptions
rollbackIfNecessary();
CoreUtils.unwrapRemoteException(rex, logger);
} catch (SystemException e) {
// all other exceptions --> rollback if necessary and rethrow
rollbackIfNecessary();
throw e;
} finally {
removeConnection();
logger.exitDebug("updateComplaint");
This is the resulting StackTrace:
sql exception: [Closed Statement: next] - sql statement: [select *
     at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
     at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
     at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
     at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
was detected. A Connection leak occurs when a connection obtained from
the pool was not closed explicitly by calling close() and then was disposed
by the garbage collector and returned to the connection pool. The following
stack trace at create shows where the leaked connection was created.
Stack trace at connection create:
     at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
     at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
     at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
     at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
     at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
     at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
     at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
     at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
     at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
     at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
     at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
     at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
     at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
     at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
     at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
     at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
     at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
     at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
     at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
     at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
     at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
     at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
     at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

There are two separate login problems, with different solutions

I have just spent a couple of hours fixing a 24in iMac that kept rejecting the account login after installing Leopard. (login with correct password goes to blue screen then back to loginscreen)
I went through the Apple tech doc that had you logging in as a single user (Cmd-s) and it did not work.
What did work for me was an archive and install of Leopard.
It seems that anyone with a new iMac that installed the recent imac update is having this problem. For those people, archive and install seems to work.
http://discussions.apple.com/thread.jspa?threadID=1214059&tstart=0
For other people, the single-user instructions seem to work.
http://discussions.apple.com/thread.jspa?threadID=1202129&tstart=0
hope this helps
cheers
bruce

> When working with word, documents or emails in the middle of a sequence
> the picture or window suddenly is yanked off the screen to the right.
Microsoft Word? What version and service pack?
Microsoft Office 2011 SP2 includes Word version 14.2.2. Some Office 2011 updates addressed problems with Lion.

MobileMe login problem with aperture3

Hello all,
I'm experiencing the following problem. I cannot login to mobileMe via Aperture 3, because MobileMe didn't recognize the stored password for "xxxxx's" MobileMe account; the username/password combination is not recognized. I've tried the following (in all possible orders):
1. Close Aperture3
2. Logout of MobileMe account
3. In Keychain delete settings for MobileMe
4. Login to MobileMe again
5. Open Aperture3
Anybody any suggestions?
Thanks for the help,
Casper
Message was edited by: Casper Stoutjesdijk
Changed subject title

I have the same problem with iPhoto.

Login problem with LinkedIn

I cannot login to LinkedIn with Firefox but there is no such problem with IE8. The trouble started about 2 months ago when I had version 3.6.15 and continues with the present version 4.0.1. I have been in correspondence with LinkedIn ever since but nothing they suggest works. I like Firefox and it is my default browser, so it is annoying to have to use IE8 just for this task. I would therefore very much appreciate any solutions that anyone can offer.

Clear cookies for that site. Access via Firefox button, Options | Options | Privacy and then click the "Show Cookies" button.
See http://www.linkedin.com/answers/using-linkedIn/ULI/648039-4236346

Login problems with Vista

I have a 10.4.11 OSX server as an OD Master.
All my OSX and WinXP clients can authenticate without problem.
I received a new computer with Windows Vista Ultimate x64 SP1. I was able to make it join my domain without problem but when I try to log in, I get the following error " Procedure number out of range".
IMHO, I believe the problem is with a default config in Vista x64 more that a problem with my server.
Has anyone seen this kind of error before?

I have a 10.4.11 OSX server as an OD Master.
All my OSX and WinXP clients can authenticate without problem.
I received a new computer with Windows Vista Ultimate x64 SP1. I was able to make it join my domain without problem but when I try to log in, I get the following error " Procedure number out of range".
IMHO, I believe the problem is with a default config in Vista x64 more that a problem with my server.
Has anyone seen this kind of error before?

Problems with WLS 7.0 and NES plug-in

Hi,
I am not able to configure NES with weblogic 7.0. I created a domain
with an admin server and 3 clustered servers. When I tried to configure
NES it is giving me these errors.
[06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
/data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
ml, line 32, column 15: Error processing obj.conf line 1: init functions
are not allowed in this objset
Also below are the lines copied from obj.conf that I added.
Init fn="load-modules" funcs="wl_proxy,wl_init"\
shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
Init fn="wl_init"
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy \
WebLogicCluster="localhost:7001,localhost:7002,\
localhost:7003" PathTrim="/weblogic"
</Object>
Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
is 6.0 and I am on Solaris 8.
Shiva.

Hi,
I am not able to configure NES with weblogic 7.0. I created a domain
with an admin server and 3 clustered servers. When I tried to configure
NES it is giving me these errors.
[06/May/2002:18:41:26] failure ( 1530): Invalid configuration: File
/data/iasuser2/webserver/https-ias02.mygazoo.com/config/server.x
ml, line 32, column 15: Error processing obj.conf line 1: init functions
are not allowed in this objset
Also below are the lines copied from obj.conf that I added.
Init fn="load-modules" funcs="wl_proxy,wl_init"\
shlib=/data/iasuser2/webserver/https-ias02.mygazoo.com/libproxy.so
Init fn="wl_init"
<Object name="weblogic" ppath="*/weblogic/*">
Service fn=wl_proxy \
WebLogicCluster="localhost:7001,localhost:7002,\
localhost:7003" PathTrim="/weblogic"
</Object>
Is NES plug-in supported with WLS 7.0. My version of iPlanet webserver
is 6.0 and I am on Solaris 8.
Shiva.

Login problems with facetime and Imessage

I have IPAD 2 upgraded to IOS 6.0. I am living at Alexandria EGYPT.
I didn't face any problem with both apps until the 2nd of October 2012. Since then and both apps telling me that Apple ID doesn't match with the entered password. The same password is used for app store and working with no problem, the password have been used even to log in to the support as well as Icloud.
I have tried the following actions with no result:
1- Soft reset the IPAD.
2- Time is set to automatic.
3- Set the time to USA.
4- Time set back to auto.
5- Connect using different WiFi networks.
I hope I can find a solution, I am using both apps to keep in touch with my family.

I did a total reset and start the IPAD as a new one before restore...same problem exist
after restore try again and with the same problem...
Finally I have created a new apple ID and used it only for facetime and imessages...and it works....
I can't really understand the problem....
It is not a problem with communication or IPAD settings because it worked with another apple ID
it is not a problem with server or account because I am still using my old ID with my macbook
strange

Multiple user login problem with ADF

Hi All,
I am using Jdev 11g. I have an ADF application which is running inside JDev enbedded WLS. I implemented "Authentication Only" security into the application and created a few users. If I try to login/logout/re-login with individual user, all of users work perfectly. However, when I have one user already logged in, I open another browser and try to login with another user (or the same user), I always get an "Error 403--Forbidden" error. Basically I have an application which can only work for one user at one time. Does anyone know how to fix this problem so that I can have multiple users logged in at the same time?
Thank you very much in advance,
John

Chris,
Thank you for your response.
I am using Firefox version 2.0.0.20. When I add the security component into my ADF application, I just take whatever it has by default without any customization. That includes default login.html and error.html. Here is my experience,
1) Execute my starting task flow activity inside the JDeveloper. This will invoke a new login page in my default browser Firefox.
2) Login the application with user "abc" and do something. Keep this session open.
3) Open another Firefox browser and enter login URL. and then Login the application with user "xyz" (or even "abc"). I got the error page.
To me, it should be basic web application behavior. I can do things like this in other J2EE application. This one doesn't make sense at all. I am not sure if this is the behavior I would see when I deploy it to a standalone WLS.
Any ideas?
Thanks,
John

Re-login problem with WLS 5.1 sp8

Similar Messages

Maybe you are looking for