Problem with instantiating

I'm having a bit of a problem understanding instantiating objects. The way I understand it, an object needs to be declared, instantiated and initialised befoore it can be used.
For example, I have a class Point.
So I can have a statement like :
Point P1 = new Point(0,0);
The way I understand it, Point P1+ is the declaration, new+ is the instantiation and Point(0,0)+ is the initialisation.
If my understanding is correct, there are two cases that confuse me.
Case 1:_
I already have a previously declared, instantiated and initialised object PArg of class Point.
then I can state:
Point p0 = PArg;
Now in this case I dont use the new +keyword. I can see where I decare the Object p0 and where I initialise it, but I don't see any instantiation. But the program still works. I don't understand how.
Case 2:+
Point PIn[] = new Point[5];
In this case I am declaring the array of objects and instantiating then with the new +keyword. But I still cannot initialse any elements of my array without intantiating them again. I need to have something like:
PIn[i] = new Point(x,y);
where it is instantiated again with the new +keyword and initialised. I on't understand why it is required or even possible to instantiate the objects in the array twice.
I hope my questions are appropriate for this forum. I would greatly appreciate any answers or links to answers.
Thanks.
Edited by: JulianPatel on Aug 29, 2008 1:13 PM

I have a follow-up question to the ones that have been answered here.
In your example, you assign the value of variable PArg (i.e. the value of the reference) to p0. After the assignment, p0 has the same value as PArg, meaning it refers to the same object as PArg (or both are null).
So if I'm understanding correctly, both p0 and PArg now point to the same physical object, that is to say the same memory location correct? Does that mean if I now change the value of some element in p0, it will also be changed in PArg? What about the other way around?
Eg In my class Point, store two integer values x and y. So suppose I decalre and initialise:
Point PArg = new Point(3,4);This will set PArg.x = 3 and PArg.y =4
Now if I have:
Point p0 = PArg;and then I change the value of p0.x and p0.y using :
p0.reset(1,2);This will change p0.x from 3 to 1. But will PArg.x also change from 3 to 1?
Similarly if it set :
PArg.reset(1,2);will this change the values of p0.x and p0.y?
The relevant potions of code for my class is:
class Point
int x,y;
Point(int xIn, int yIn)
x = xIn;
y = yIn;
void reset(int xIn, int yIn)
x = xIn;
y = yIn;
}And what if the object is created from a method ? Suppose I have a class Geometry containing methods like:
static double sqr(double d)
//Returns the square of the argument
return(d*d);
static double distance(Point p1, Point p2)
//Returns the distance between two Points and/or Floating Points
double d,x1,x2,y1,y2;
x1 = p1.x; x2 = p2.x;
y1 = p1.y; y2 = p2.y;
d = sqrt(sqr(x1-x2) + sqr(y1-y2));
return (d);
static Point integerAltitudeFoot(Point p0,Point pLine1,Point pLine2)
//Returns the Point of intersection of a perpendicular from p0 onto the line passing through pLine1 and pLine2
double d01,d02,d12,d1,d2;
int midX,midY;
d01 = distance(p0,pLine1);
d02 = distance(p0,pLine2);
d12 = distance(pLine2,pLine1);
d1 = (sqr(d12) + sqr(d01) - sqr(d02))/(2*d12);
d2 = (sqr(d12) + sqr(d02) - sqr(d01))/(2*d12);
midX = (int)((pLine1.x*d2 + pLine2.x*d1)/d12);
midY = (int)((pLine1.y*d2 + pLine2.y*d1)/d12);
Point footPrint = new Point(midX,midY);
return(footPrint);
}and then I have:
Point p = Geometry.altitudeFoot(p0,pLine1,pLine2);In this case the object is created by the line:
Point footPrint = new Point(midX,midY);within the altitude function, and then its reference is passed outside through the line:
return(footPrint);and passed onto p by
Point p = Geometry.altitudeFoot(p0,pLine1,pLine2);correct?
But wouldn't the life cycle of Point footPrint be terminated as soon as the method execution is complete? But Point p persists beyond the life cycle of footPrint.
I hope I have expressed my questions properly. As always, thanks in advance for the answers.
Edited by: JulianPatel on Aug 31, 2008 6:10 PM

Similar Messages

  • Problem with instantiation in static function

    I have a problem with instatiation of objects in a static function. When I do something like this,
    public static void test1() {
    String s = new String();
    everything works fine, but when I try to do the same with a internally defined class, I get the error "non-static variable this cannot be referenced from a static context".
    My code looks roughly like this:
    public static void test2() {
    Edge e = new Edge();
    class Edge {
    public int y_top;
    public double x_int;
    public int delta_y;
    public double delta_x;
    The compiler complains with the mentioned error message over the creation of a new Edge object and I don't have the slightest clue why... :| When I put the class Edge into an external file, it works.
    Can anyone help me out there?

    Your class Edge is a member of the instance of the current class. You don't have an implicit instance of the current class (the "this" reference) in a static context, therefore you get the error.
    You need to either declare Edge as static, move it outside your class, or create an explicit instance of the outer class which you use to create instances of Edge ("Edge e = new YourMainClass().new Edge()")

  • Problem with instantiating array

    Hi, so my problem is 2 fold :)
    First off, here are my constructors:
    public class ArrayBag implements BagADT<Object> {
        public Object[] bag;
        private int bagSize = size();
        public ArrayBag() {
            bag = new Object[100];
        public ArrayBag(int c) {
            if (c >= 0) {
                bag = new Object[c];
        }For some reason, netbeans doesnt recognize that the bag has been instantiated unless i change it to Object arrayBag[] = new Object[100] all on the same line.. I wrote a tester program which so far consists of arrayBag(100); and yeah...i get a null pointer error which poitns at the following method:
    public int size() {
            int count = 0;
            while (count < bag.length && bag[count] != null) {
                count++;
            }//end while
            return count;
        } The error directly points at the line containing the while statment...But if i DO change the instantiation to a single line, then this error doesnt happen. Im sure that these errors are interconnected with one and other...just unsure how to fix them.
    Thanks!
    Paul
    Edited by: Toadums on Jan 20, 2009 6:07 PM

    ah of course! Thanks!
    I do have another question though.
    So what my teacher did...he sent the part of the code which he wrote as a class file...we had to import it into the library and all that jazz...when i try to run my program i get some lines of errors:
    Exception in thread "main" java.lang.ClassCastException: [Ljava.lang.Object;
            at MemoryGame.init(MemoryGame.java:128)
            at MemoryGame.<init>(MemoryGame.java:57)
            at MemoryGame.main(MemoryGame.java:47)
    Java Result: 1like that....and im just wondering, since i cant look at the code that he gave us...how am i supposed to test, cause im not sure where the error is O.o

  • Problem with setContentPane() in JFrame class

    I recently discovered a problem with the setContentPane method in the JFrame class. When I use setContentPane(Container ..), the previously existing contentPane remains in the stack. I have tried nullifying getContentPane(), and all manner of things, but, each time I use setContentPane, I have another instance of a JPanel in the stack.
    I'm using code similar to setContentPane(new CustomJPanel()); and each time the user changes screens, and a similar call to that is made, the old CustomJPanel instance remains in the stack. Can anyone suggest a way around this? On their own the panels do not take up very much memory, but after several hours of usage, they will build up.

    I tried what you suggested; it only resulted in a huge performance decrease. The problem with memory allocation is still there.
    Here is the method I use to switch screens in my app:
    public static void changeScreen (JPanel panel){
              try{
                   appFrame.setTitle("Wordinary : \""+getTitle()+"\"");
                   appFrame.setContentPane(panel);
                   appFrame.setSize(appFrame.getContentPane().getPreferredSize());     
                   appFrame.getContentPane().setBackground(backColour);
                   for (int i = 0; i < appFrame.getContentPane().getComponents().length; i++)
                        appFrame.getContentPane().getComponents().setForeground(textColour);
                   //System.out.println("Background colour set to "+backColour+" text colour set to "+textColour);
                   appFrame.validate();
              catch (Exception e){
                   //System.out.println("change");
                   e.printStackTrace();
    And it is called like this:
    changeScreen(new AddWordPanel());The instantiation of the new instance is what is causing the memory problems, but I can't think of a way around it.

  • Problem with Dynamically accessing EJB Class objects in WL 7.0 SP1

    I am trying to build a component which has the ability to instantiate and execute
    an known EJB method on the fly.
    I have managed to build the component but when I try and execute it I get a ClassNotFoundException.
    I know that the EJB I am trying to invoke is deployed and available on the server,
    as I can see it in the console, I also seen to have been able to get the remote
    interface of the object, my problem occurs when I try and access the class object
    so I can perform a create on the object and then execute my method
    The code I have written is below:
    private Object getRemoteObject(Context pCtx, String pJNDIName, String pHomeBean)
    throws Exception {
         String homeCreate = "create";
         Class []homeCreateParam = { };
         Object []homeCreateParamValues = {};           
    try {  
    //This call seems to work and doesn't throw an exception     
    Object home = pCtx.lookup(pJNDIName);
    //However this call throws a java.lang.ClassNotFoundException
    Class homeBean = Class.forName(pHomeBean);
    Method homeCreateMethod = homeBean.getMethod(homeCreate,homeCreateParam);
    return homeCreateMethod.invoke(home, homeCreateParamValues);
    } catch (NamingException ne) {             
    logStandardErrorMessage("The client was unable to lookup the EJBHome.
    Please make sure ");
    logStandardErrorMessage("that you have deployed the ejb with the JNDI
    name "+pJNDIName+" on the WebLogic server ");
    throw ne;
    } catch (Exception e) {
    logStandardErrorMessage(e.toString());
    throw e;     
    Any advice would be really appreciated, I'm fast running out of ideas, I suspect
    it has something to do with the class loader but I'm not sure how to resolve it
    Regards
    Jo Corless

    Hello Joanne,
    Congratulations! I'm very happy that you've managed to fix your problem. It's
    always essential to understand how to package applications when deploying on BEA
    WebLogic. Usually, by throwing everything into an EAR file solves just about all
    the class loader problems. :-) Let us know if you have any further problems that
    we can assist you with.
    Best regards,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    "Joanne Corless" <[email protected]> wrote:
    >
    >
    I've fixed it!!!!!!!!
    Thanks to everyone who gave me help!!!!
    The class loader was the culprit which is what I suspected all along.
    As soon
    as I put the 2 jar files I was using into an EAR file the problem went
    away!!!!!
    Thanks again
    Jo Corless
    "Ryan LeCompte" <[email protected]> wrote:
    Hello Joanne,
    As Mr. Woollen mentioned, I also believe it's a problem with the class
    loader.
    You need to be careful how you arrange your EJBs, because WebLogic has
    a specific
    method in which it loads classes in an EAR, JAR, and WAR file(s). Please
    refer
    to http://dev2dev.bea.com/articles/musser.jsp for more information about
    BEA WebLogic
    class loading mechanisms and caveats. Also, try printing out the various
    methods
    that are available on the object that was returned to you via reflection.
    For
    example, use the getMethods() method, which returns an array of Method
    objects
    that you can subsequently cycle through and print out the various method
    names.
    This way you can discover if the class found/returned to you is indeed
    the one
    you intend to locate.
    Hope this helps,
    Ryan LeCompte
    [email protected]
    http://www.louisiana.edu/~rml7669
    Rob Woollen <[email protected]> wrote:
    I believe the issue is the home interface class for this EJB is not
    available in the class loader which is doing the reflection.
    If you do:
    getClass().getClassLoader().loadClass(homeInterfaceClassName)
    I suspect it will fail. Reflection still requires that the class be
    loadable.
    -- Rob
    Joanne Corless wrote:
    Hi Slava,
    If I make my code look like you describe below I get a compliationerror telling
    me that
    home.getMethod() is not recognised (no such method)
    If I change it slightly and use
    Method homeCreateMethod =
    home.getClass().getMethod(homeCreate,homeCreateParam);
    The code will compile OK but when executed it still throws a NoSuchMethodException
    Any ideas ?
    Thanks for your help so far
    Regards
    Jo Corless
    Your code should look like
    Object home = pCtx.lookup(pJNDIName);
    Method homeCreateMethod =
    home.getMethod(homeCreate,homeCreateParam);
    return homeCreateMethod.invoke(home, homeCreateParamValues);
    Regards,
    Slava Imeshev
    "Joanne Corless" <[email protected]> wrote in message
    news:[email protected]...
    Hi Ryan,
    I also wanted to mention that if you do a "header search" in this
    particular
    newsgroup
    with the search query as "reflection", you will see many previousmessages
    regarding
    reflection and EJBs. I believe you could learn a lot from thedifficulties
    that
    others have faced and solved.I tried that and although there was a number of similar cases noneof them
    actually
    seem to fix my issue. Thanks for the suggestion though
    Are the EJBs that you are trying to access accessible via your
    system
    classpath?
    Try to avoid having them accessible via the main system classpath,and
    only bundle
    them in your appropriate EJB jar files (contained in an EAR file,for
    example).Maybe I should have laid the problem out a little clearer.
    I have a number of EJB's bundled up in a JAR file which is hot deployedto
    the
    server. Within this first JAR file is an EJB (SSB) component that
    needs
    to
    be
    able to invoke a known method on another EJB. This second EJB may
    or
    may
    not be
    within the first JAR file but it also will be hot deployed.
    The component trying to invoke the method on the 2nd EJB has to
    be
    able to
    create
    an instance of the 2nd EJB without actually knowing anything bar
    a
    JNDI
    Name which
    is passed in at runtime.
    I can get as far as doing the
    Object home = pCtx.lookup(pJNDIName);
    This returned a class with the name
    "com.csc.edc.projects.allders.httppostoffice.postman.PostmanBean_mp8qy2_Home
    Impl_WLStub"
    My problem seems to occur when I try and invoke the create method
    Method homeCreate = home.getClass().getMethod("create", new Class[0]);
    My code throws a java.lang.NoSuchMethodException at this point so
    I
    am
    unable
    to progress to the next step of :
    Object bean = homeCreate.invoke(home, null);
    So I can return the instantiated bean back to the calling client.
    Why am I getting the NoSuchMethodException, is is because I am gettinga
    stub
    back rather than the home interface and if so how do I get the truehome
    interface
    from the bean
    Thanks in advance
    Jo Corless

  • Problem with ClassCastException in web application

    Hello,
              I'm trying to deploy a web application in WLS 5.1 and I'm getting the
              "dreaded" ClassCastException every time when JSP tries to read a bean
              from the request or session. Under my architecture (actually it's just
              the regular "model 2" ) bean is populated by a servlet, set on the
              request and then retrieved by JSP (servlet forwards to JSP). Everything
              work fine when I register servlets in weblogic.properties, but
              ClassCastException is thrown on any attempt to read from the request if
              the same JSPs and servlets are deployed as web application.
              Has anybody come across the same problem?
              Thanks in advance for help.
              Alexander
              

    Hello,
              This is all well and good as a temporary bug, but it's totally unrealistic for
              the future. Two points:
              * The ClassLoader doesn't need to be discarded, it just needs to be cleared.
              * Other servlet engines seem to be able to handle this.
              Hope it's on its way to resolution!
              TDoan wrote:
              > Alexander:
              >
              > I had some problem with ClassCastException, and recently I found out what it
              > was that causing it. I'm sure if this is the same problem you are having,
              > but please read the following paragraph.
              >
              > I cutted this from http://www.weblogic.com/docs51/classdocs/API_servlet.html
              > ClassCastException and HTTP Sessions
              >
              > You might encounter a ClassCastException while developing servlets that use
              > HTTP sessions. This could happen as a result of the following set of events:
              >
              > a.. You store a reference to a custom class, myFoo, in an HTTP session.
              >
              > b.. While in mid-session, you change your servlet (or JSP or JHTML),
              > causing it to be reloaded. In fact, it is necessary for it to be reloaded by
              > a completely new class loader, and the old class loader that had previously
              > loaded it must be discarded.
              >
              > c.. Because your custom class myFoo is also located under the servlet
              > classpath, it too is reloaded by the new class loader.
              >
              > d.. Now, when you retrieve myFoo from the HTTP session, you cast it to the
              > expected type, but you recieve a ClassCastException. The exception is thrown
              > even if class myFoo has not changed. Because it has been loaded by a
              > different class loader, it is regarded by the JVM as incompatible.
              > Note: If you are using session persistence, the class contents must be
              > serialized, and you will not encounter this exception.
              >
              > Here are some suggested work-arounds to this problem:
              >
              > a.. Do not place your class myFoo in the servlet classpath. Instead, place
              > it in the system classpath or the weblogic.class.path, which are accessible
              > by WebLogic Server. The class will not be reloaded when the servlet is
              > modified. This drawback to this solution is that you cannot prototype the
              > myFoo class, because you must restart the server in order to reload the
              > class after it is modified.
              >
              > b.. If you need to prototype the class, you can write a wrapper method
              > within it to store and retrieve its contents to and from the session. You do
              > not access the class directly from the session, but instead call it is
              > wrapper methods to store or populate it is contents from the session. As
              > long as you use standard Java class types to store the class contents, they
              > will not be reloaded when the servlet is reloaded. This approach has
              > performance drawbacks because your wrapper methods would need to set or get
              > multiple name=value pairs for each class's attributes.
              >
              > c.. Another work-around is to catch the ClassCastException, and replace
              > the old class that is stored in the session with a newly instantiated class,
              > or remove it from the session. Unfortunately, you lose the session data that
              > was previously stored in the class, so you must write your application to
              > handle this scenario. This is the easiest solution to the problem-remember
              > that you should not be storing critical information in an HTTP session, but
              > rather storing it in a database.
              > Note: The ClassCastException generally occurs while you are developing
              > your servlets, and should not be an issue in a stable production system. If
              > you are upgrading your system online, you might wish to warn your customer
              > base.
              >
              > Hope it helps,
              > Tin
              >
              > "Alexander Ananiev" <[email protected]> wrote in message
              > news:[email protected]...
              > > Hello,
              > >
              > > I'm trying to deploy a web application in WLS 5.1 and I'm getting the
              > > "dreaded" ClassCastException every time when JSP tries to read a bean
              > > from the request or session. Under my architecture (actually it's just
              > > the regular "model 2" ) bean is populated by a servlet, set on the
              > > request and then retrieved by JSP (servlet forwards to JSP). Everything
              > > work fine when I register servlets in weblogic.properties, but
              > > ClassCastException is thrown on any attempt to read from the request if
              > > the same JSPs and servlets are deployed as web application.
              > > Has anybody come across the same problem?
              > >
              > > Thanks in advance for help.
              > > Alexander
              > >
              

  • Problem with a BAPI collecting dunning levels

    Hello all experts,
    I am having a problem with BAPI “DebtorCreditAccount” (called from a VB program), collecting dunning levels.
    The BAPIs is called like follows (only the essential code is shown):
    The first function (GetCustomerCurrentBalance) works fine but the second (GetCustomerHighestDunningLevel) doesn’t work.
        Public Function GetCustomerCurrentBalance(ByVal strCustomerID As String) As Decimal
            Dim objARAccount, objReturn, objActualBalance As Object
            Try
                objARAccount = Me.p_sapBapi.GetSAPObject("ARAccount", "1000", Me.ConvertCustomerID(strCustomerID))
                objARAccount.GetCurrentBalance(Return:=objReturn, ActualBalance:=objActualBalance)
                Return CType(objActualBalance.Value("TOTAL_BAL"), Decimal)
            Catch ex As Exception
                Return 0
            Finally
                objARAccount = Nothing : objReturn = Nothing : objActualBalance = Nothing
            End Try
        End Function
        Public Function GetCustomerHighestDunningLevel(ByVal strCustomerID As String) As Integer
            Dim objDebtorCreditAccount, objReturn, objHighestDunningLevelD As Object
            Dim objTEST1 As Object
            Try
                objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount", Me.ConvertCustomerID(strCustomerID), "0001")
                objDebtorCreditAccount.GetHighestDunningLevel(Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD)
                Return CType(objHighestDunningLevelD.Value("DUNN_LEVEL"), Integer)
            Catch ex As Exception
                Return 0
            Finally
                objDebtorCreditAccount = Nothing : objReturn = Nothing : objHighestDunningLevelD = Nothing
            End Try
        End Function
    The error message I get is:
    Message: The runtime object of type DebtorCreditAccount with the persistent key 00000480060001 could not be created in the Business Object Repository.
    Message-Nr: 826
    Workarea: OL
    R/3 error message: Object does not exist
    Please give me some input on how to proceed!
    Best Regards,
    Niklas

    Thanks Vijaya for your fast reply. The parameters that I am giving as input are however correct.
    I have investigated the problem a bit further and tried some other calls.
    If I just chose to create an object of the type “DebtorCreditAccount” (without submitting any parameters) and then use the same method call as before (se code in topic above) I get the following error: “Mandatory parameter HIGHESTDUNNINGLEVELA missing.” This must mean that it knows that something is missing.
    objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount")
    objDebtorCreditAccount.GetHighestDunningLevel(Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD) 
    If if add the mandatory parameter “HIGHESTDUNNINGLEVELA” I get the error message "The persistent key for an business object instance of type DebtorCreditAccount has not been set. Cannot invoke method GETHIGHESTDUNNINGLEVEL”. This I interpret as the object has not been right instantiated. This brings me back to square one.
    objDebtorCreditAccount = Me.p_sapBapi.GetSAPObject("DebtorCreditAccount")
    objDebtorCreditAccount.GetHighestDunningLevel(HIGHESTDUNNINGLEVELA:="0", Return:=objReturn, HighestDunningLevelD:=objHighestDunningLevelD)
    Grateful for a response!
    Regards,
    Niklas

  • Problem with the NodeManager in Weblogic 10.0 MP1

    Hi,
    I have a problem starting the Nodemanager successfully. I have currently installed BEA Weblogic 10.0 MP1. The admin server is getting started successfully. When, I start the Nodemanager with the command:
    startnodemanager -machine <hostname>, it neither gives the success message nor the error message. It comes to a stand still. Please see the below text, which appears on the Command prompt, when I run the nodemanager command.
    Machine PUNITP128166D.ad.infosys.com
    Listen Address: PUNITP128166D.ad.infosys.com
    Listen Port: 8097
    PID for D:\Ariba9r1\shared/bin/startNodeManager.cmd: 5980
    D:\Ariba9r1\BuyerDev9r1\Server\bin>
    D:\Ariba9r1\BuyerDev9r1\Server>set CLASSPATH=D:\BEA10\wlserver_10.0\server\lib\A
    ribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib\tools.jar;D:\BEA10\wlserver_1
    0.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;
    D:\Ariba9r1\BuyerDev9r1\Server>chdir /d "D:\Ariba9r1\shared\nodemanager"
    D:\Ariba9r1\shared\nodemanager>"D:\BEA10\jdk150_11\bin\java.exe" -client -Xms32m
    -Xmx200m -XX:MaxPermSize=128m -XX:+UseSpinning -Xverify:none -classpath "D:\BE
    A10\wlserver_10.0\server\lib\AribaWebLogic81Patches.jar;.;D:\BEA10\jdk150_11\lib
    \tools.jar;D:\BEA10\wlserver_10.0\server\lib\weblogic_sp.jar;D:\BEA10\wlserver_1
    0.0\server\lib\weblogic.jar;" -Dbea.home=D:\BEA10 -Djava.security.policy=D:\BEA1
    0\wlserver_10.0\server\lib\weblogic.policy -DSavedLogsDirectory=D:\Ariba9r1\shar
    ed\nodemanager\logs -DJavaHome=D:\BEA10\jdk150_11 -DTrustedHosts=D:\BEA10\wlserv
    er_10.0\common\nodemanager\config\nodemanager.hosts -DListenAddress=PUNITP128166
    D.ad.infosys.com -DListenPort=8097 -DReverseDnsEnabled=true -DLogToStderr=true -
    DLogFile=D:\Ariba9r1\shared\nodemanager\nodemanager.log -DNodeManagerHome=D:\Ari
    ba9r1\shared\nodemanager weblogic.NodeManager
    After this, when I check the nodemanager status in Console, then the status appears as REACHABLE. Assuming, this to be the successfully message, I try to start the managed servers associated with the Machine/Server. But, it fails and there appears a message on the console with the status as 'Force Shutting Down' for this server.
    When I check the logs, there seems to be some problem with the Nulll exception. Please see the below logs as it appears, its only a part of the logs
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory" with its JNDI name "weblogic.jms.XAConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "QueueConnectionFactory" with its JNDI name "javax.jms.QueueConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory2" with its JNDI name "weblogic.jms.XAConnectionFactory2" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "MessageDrivenBeanConnectionFactory" with its JNDI name "weblogic.jms.MessageDrivenBeanConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultXAConnectionFactory0" with its JNDI name "weblogic.jms.XAConnectionFactory0" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "DefaultConnectionFactory" with its JNDI name "weblogic.jms.ConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040407> <Default connection factory "TopicConnectionFactory" with its JNDI name "javax.jms.TopicConnectionFactory" is started.>
    ####<Jun 28, 2010 4:20:25 PM IST> <Info> <JMS> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722225995> <BEA-040306> <JMS service is active now.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281003> <SAF Service has been initialized.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <SAFService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226041> <BEA-281002> <SAF Service has been started.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226120> <BEA-101128> <Initializing HTTP services.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101135> <buyerserver1 is the default Web server.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101052> <[HttpServer (defaultWebserver) name: buyerserver1] Initialized>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226135> <BEA-101129> <Initializing the Web application container.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226198> <BEA-180046> <INFO: Logging service enabled.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC license service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Configuration Helper instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Task Manager instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC security service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Outbound routing service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Debug> <WTC> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226213> <BEA-180046> <INFO: TC Transaction service instantiated!>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220031> <The server does not support reliable SOAP messaging.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebService> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226229> <BEA-220027> <Web Service reliable agents are started on the server.>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <JMX> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226604> <BEA-149512> <JMX Connector Server started at service:jmx:iiop://PUNITP128166D.ad.infosys.com:8050/jndi/weblogic.management.mbeanservers.runtime .>
    ####<Jun 28, 2010 4:20:26 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722226651> <BEA-000287> <Invoking startup class: ariba.j2ee.appserver.weblogic.Startup.startup(directory=D:\Ariba9r1\BuyerDev9r1\Server)>
    ####<Jun 28, 2010 4:20:27 PM IST> <Info> <WebLogicServer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227229> <BEA-000288> <ariba.j2ee.appserver.weblogic.Startup reports: Changed directory to D:\Ariba9r1\BuyerDev9r1\Server>
    ####<Jun 28, 2010 4:20:27 PM IST> <Info> <Management> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722227244> <BEA-141187> <Java system properties are defined as follows:
    ariba.server.home = D:\Ariba9r1\BuyerDev9r1\Server
    awt.toolkit = sun.awt.windows.WToolkit
    bea.home = D:\BEA10
    file.encoding = Cp1252
    file.encoding.pkg = sun.io
    file.separator = \
    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
    java.awt.headless = true
    java.awt.printerjob = sun.awt.windows.WPrinterJob
    java.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBOracleJDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBDB2JDBC.zip;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions\aribaDBMssqlJDBC.zip;D:\BEA10\wlserver_10.0\server\lib\weblogic.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes;D:\Ariba9r1\BuyerDev9r1\Server\classes\AribaJ2EE.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\extensions;D:\BEA10\wlserver_10.0\server\lib\wls-api.jar
    java.class.version = 49.0
    java.endorsed.dirs = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed
    java.ext.dirs = D:\BEA10\jdk150_11\jre\lib\ext
    java.home = D:\BEA10\jdk150_11\jre
    java.io.tmpdir = C:\DOCUME~1\suram_vishal\Local Settings\Temp\
    java.library.path = D:\BEA10\jdk150_11\bin;.;C:\SYSROOT\system32;C:\SYSROOT;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\jdk150_11\bin;D:\BEA10\patch_wlw1001\profiles\default\native;D:\BEA10\patch_wls1001\profiles\default\native;D:\BEA10\wlserver_10.0\server\native\win\32;D:\BEA10\wlserver_10.0\server\bin;D:\BEA10\modules\org.apache.ant_1.6.5\bin;D:\BEA10\jdk150_11\jre\bin;D:\BEA10\jdk150_11\bin;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:/Ariba9r1/BuyerDev9r1/Server/bin/Win32;D:/Ariba9r1/BuyerDev9r1/Server/bin;C:\SYSROOT\system32;C:\SYSROOT;C:\SYSROOT\System32\Wbem;C:\Program Files\Java\jre1.5.0_06;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\Program Files\CA\eTrustITM;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;D:\BEA10\wlserver_10.0\server\native\win\32\oci920_8;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\bin;D:\Ariba9r1\BuyerDev9r1\Server;D:\Ariba9r1\BuyerDev9r1\Server\lib\Win32;D:\Ariba9r1\BuyerDev9r1\Server\internal\lib\Win32
    java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
    java.naming.factory.url.pkgs = weblogic.jndi.factories:weblogic.corba.j2ee.naming.url:weblogic.jndi.factories:weblogic.corba.j2ee.naming.url
    java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.utils|weblogic.net
    java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition
    java.runtime.version = 1.5.0_11-b03
    java.security.policy = D:\BEA10\wlserver_10.0\server\lib\weblogic.policy
    java.specification.name = Java Platform API Specification
    java.specification.vendor = Sun Microsystems Inc.
    java.specification.version = 1.5
    java.vendor = Sun Microsystems Inc.
    java.vendor.url = http://java.sun.com/
    java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
    java.version = 1.5.0_11
    java.vm.info = mixed mode
    java.vm.name = Java HotSpot(TM) Client VM
    java.vm.specification.name = Java Virtual Machine Specification
    java.vm.specification.vendor = Sun Microsystems Inc.
    java.vm.specification.version = 1.0
    java.vm.vendor = Sun Microsystems Inc.
    java.vm.version = 1.5.0_11-b03
    javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
    javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
    javax.xml.rpc.ServiceFactory = weblogic.webservice.core.rpc.ServiceFactoryImpl
    javax.xml.soap.MessageFactory = weblogic.webservice.core.soap.MessageFactoryImpl
    org.omg.CORBA.ORBClass = weblogic.corba.orb.ORB
    org.omg.CORBA.ORBSingletonClass = weblogic.corba.orb.ORB
    org.xml.sax.driver = weblogic.apache.xerces.parsers.SAXParser
    org.xml.sax.parser = weblogic.xml.jaxp.RegistryParser
    os.arch = x86
    os.name = Windows 2003
    os.version = 5.2
    path.separator = ;
    sun.arch.data.model = 32
    sun.boot.class.path = D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\serializer.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xalan.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xercesImpl.jar;D:\Ariba9r1\BuyerDev9r1\Server\classes\endorsed\xml-apis.jar;D:\BEA10\jdk150_11\jre\lib\rt.jar;D:\BEA10\jdk150_11\jre\lib\i18n.jar;D:\BEA10\jdk150_11\jre\lib\sunrsasign.jar;D:\BEA10\jdk150_11\jre\lib\jsse.jar;D:\BEA10\jdk150_11\jre\lib\jce.jar;D:\BEA10\jdk150_11\jre\lib\charsets.jar;D:\BEA10\jdk150_11\jre\classes
    sun.boot.library.path = D:\BEA10\jdk150_11\jre\bin
    sun.cpu.endian = little
    sun.desktop = windows
    sun.io.unicode.encoding = UnicodeLittle
    sun.java.launcher = SUN_STANDARD
    sun.jnu.encoding = Cp1252
    sun.management.compiler = HotSpot Client Compiler
    sun.os.patch.level = Service Pack 2
    user.country = US
    user.dir = D:\Ariba9r1\BuyerDev9r1\Server
    user.home = C:\Documents and Settings\suram_vishal
    user.language = en
    user.name = suram_vishal
    user.timezone = Asia/Calcutta
    vde.home = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\ldap
    weblogic.Name = buyerserver1
    weblogic.ReverseDNSAllowed = false
    weblogic.classloader.preprocessor = weblogic.diagnostics.instrumentation.DiagnosticClassPreProcessor
    weblogic.management.server = http://PUNITP128166D.ad.infosys.com:8099
    weblogic.net.http.URLStreamHandlerFactory = ariba.util.net.URLStreamHandlerFactory
    weblogic.nodemanager.ServiceEnabled = true
    weblogic.security.SSL.ignoreHostnameVerification = true
    weblogic.security.TrustKeyStore = DemoTrust
    weblogic.system.BootIdentityFile = D:\BEA10\user_projects\VanillaBuyer\servers\buyerserver1\data\nodemanager\boot.properties
    >
    ####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229510> <BEA-000365> <Server state changed to STANDBY>
    ####<Jun 28, 2010 4:20:29 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <main> <<WLS Kernel>> <> <> <1277722229525> <BEA-000365> <Server state changed to STARTING>
    ####<Jun 28, 2010 4:20:29 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722229572> <BEA-149209> <Resuming.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230182> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_NEW to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_NEW to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
    ####<Jun 28, 2010 4:20:30 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722230728> <BEA-149060> <Module Buyer of application Buyer successfully transitioned from STATE_PREPARED to STATE_ADMIN on server buyerserver1.>
    ####<Jun 28, 2010 4:20:35 PM IST> <Warning> <HTTP> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-101162> <User defined listener ariba.server.ormsserver.ServletContextListener failed: java.lang.NullPointerException.
    java.lang.NullPointerException
         at java.util.Hashtable.put(Hashtable.java:396)
         at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)
         at ariba.j2ee.core.J2EEServer.initialize(J2EEServer.java:77)
         at ariba.j2ee.core.AribaServletContextListener.contextInitialized(AribaServletContextListener.java:25)
         at ariba.server.ormsserver.ServletContextListener.contextInitialized(ServletContextListener.java:26)
         at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Unknown Source)
         at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:168)
         at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1744)
         at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
         at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
         at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
         at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
         at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
         at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
         at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
         at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
         at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
         at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
         at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
         at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
         at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
         at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
         at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
         at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
    >
    ####<Jun 28, 2010 4:20:35 PM IST> <Info> <Deployer> <punitp128166d> <buyerserver1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1277722235212> <BEA-149059> <Module Buyer of application Buyer is transitioning from STATE_ADMIN to STATE_PREPARED on server buyerserver1.>
    ####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000388> <JVM called WLS shutdown hook. The server will force shutdown now>
    ####<Jun 28, 2010 4:20:35 PM IST> <Alert> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000396> <Server shutdown has been requested by <WLS Kernel>>
    ####<Jun 28, 2010 4:20:35 PM IST> <Notice> <WebLogicServer> <punitp128166d> <buyerserver1> <Thread-1> <<WLS Kernel>> <> <> <1277722235212> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    Kindly help me in getting this resolved.
    Thanks,
    Vishal.

    The error appears to come from the ariba code. I suggest asking them.
    java.lang.NullPointerException
    at java.util.Hashtable.put(Hashtable.java:396)
    at ariba.j2ee.weblogic.Properties.initialize(Properties.java:53)

  • Problem With Business Object and printing job

    Hello,
    We are encountering a problem with the application "Business Objects FINANCE", and we would need your help quickly.
    In the application , itu2019s impossible to print Consolidated Subsidiaries nor the Securities Held. If we try so, the application freezes and we can't do anything but killing the application via the task manager.
    Though, other states can be printed without problem.
    We tried on several different PCs, and the problem occured equally on each one.
    The version installed is 10.5, and we can do any tests that you think would be useful to diagnose problem.
    Our society is AUBAY SA, and our credential to enter in your support website are : S0005386617
    In attachment youu2019ll find a screenshot of the event viewer from the server where the application is install.
    Thanks in advance for your answer,
    best regards.

    check the export parameters of the event triggering workflow.
    If there is a problem, try instantiating the object in your wf based on the key.
    Also check if the wf is able to import the data.
    regards,
    Sandeep Josyula

  • Weblogic 10.0 Problems with stripes/struts

    When trying to deploy the sample application for the stripes framework on weblogic 10.0 I get the following error when deploying.
    <Dec 3, 2009 12:16:51 PM CET> <Error> <HTTP> <BEA-101165>
    <Could not load user defined filter in web.xml:
    net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
    Problem instantiating default configuration objects.I actually had to switch to using the Sun JDK to get this error. JRockit does not report it, and just fails when I try to use the application. The problem appear to be weblogic 10.0 specific. No problems with jetty or tomcat, and I've heard reports that it is resolved in weblogic 10.3. Have ayone come accross similar problems when using stripes/struts on weblogic 10.0, and found a solution to this? Is there a patch available for 10.0 than fix this?
    Regards
    Morten
    PS: I have ommited the complete stack trace, since it is monstrously huge.

    Guess I was wrong in thinking that this was an isolated weblogic 10.0 problem. I just downloaded weblogic 10.3 and tried to deploy the same application there, and the same error happened.
    <03.des.2009 kl 15.12 CET> <Error> <HTTP> <BEA-101165>
    <Could not load user defined filter in web.xml:
    net.sourceforge.stripes.controller.StripesFilter.net.sourceforge.stripes.exception.StripesRuntimeException:
    Problem instantiating default configuration objects.
            at net.sourceforge.stripes.config.DefaultConfiguration.init(DefaultConfiguration.java:220)
            at net.sourceforge.stripes.config.RuntimeConfiguration.init(RuntimeConfiguration.java:272)
            at net.sourceforge.stripes.controller.StripesFilter.init(StripesFilter.java:125)
            at weblogic.servlet.internal.FilterManager$FilterInitAction.run(FilterManager.java:329)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
            Truncated. see log file for complete stacktrace
    java.lang.NullPointerException
            at java.io.FilterInputStream.read(FilterInputStream.java:116)
            at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
            at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
            at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
            at java.io.InputStreamReader.read(InputStreamReader.java:167)
            Truncated. see log file for complete stacktraceSo is there anyone out there with experience with struts/stripes, that can tell why this does not work? If you need to try this yourself, you can download the stripes sample application here:
    http://sourceforge.net/projects/stripes/files/stripes/Stripes%201.5.2/stripes-1.5.2.zip/download
    There is an example WAR called "stripes-examples.war" in the zip that is ready to be deployed.
    Regards
    Morten
    PS: you still need to start weblogic with Sun JDK rather than JRockit to get the error. With JRockit the application simply fails when used.

  • Problem with reading PNG metadata due to unicode strings

    Being new to the XMP SDK I have problems trying to dump the XMP data from a .png file because the data contains UTF-8 data.
    I have searched the forum for answers, but the answers I found do not help.
    The answer I found was to replace std::string with std::wstring. but that causes problems with the compile - btw, I am using MSVC 2010 C++ Express
    and XMP SDK-CC201306
    Changing the std:: line to:
    #define TXMP_STRING_TYPE std::wstring
    and all string definitions in my code to wstring, gives me a bunch of compile errors, such as:
    f:\pkg\c++\xmp-toolkit-sdk-cc201306\public\include\client-glue/TXMPMeta.incl_cpp(74): error C2664: 'std::basic_string<_Elem,_Traits,_Ax> &std::basic_string<_Elem,_Traits,_Ax>::assign(const _Elem *,unsigned int)' : cannot convert parameter 1 from 'XMP_StringPtr' to 'const wchar_t *'
    1>          with
    1>          [
    1>              _Elem=wchar_t,
    1>              _Traits=std::char_traits<wchar_t>,
    1>              _Ax=std::allocator<wchar_t>
    1>          ]
    1>          Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast
    1>          f:\pkg\c++\xmp-toolkit-sdk-cc201306\public\include\client-glue/TXMPMeta.incl_cpp(72) : while compiling class template member function 'void TXMPMeta<tStringObj>::SetClientString(void *,XMP_StringPtr,XMP_StringLen)'
    1>          with
    1>          [
    1>              tStringObj=std::wstring
    1>          ]
    1>          f:\pkg\c++\XMP-Toolkit-SDK-cc201306\public\include\XMP.incl_cpp(55) : see reference to class template instantiation 'TXMPMeta<tStringObj>' being compiled
    1>          with
    1>          [
    1>              tStringObj=std::wstring
    1>          ]
    Any help or pointers will be most welcome.
    TIA,
    DayWalker

    OK, I now understand the point you were driving at.
    To check out this idea, I have modified the code in the routine which dumps the output from the callback to a file as follows:
    (Though if you were to dump the file using the std:: stream - .i.e. using the utility as supplied, you should see the same problem - it is not at all dependent on my using the wxWidgets toolkit)
    XMP_Status DumpXMPToFile(void * WXUNUSED(refCon), XMP_StringPtr buffer, XMP_StringLen bufferSize )
        XMP_Status status = 0;
        wxString wsT;
        try
        wxString wsText( buffer, wxConvUTF8 );
        if( g_wfDumpFile.IsOpened() )
          wsT.Printf( _T("<%s> size(%d)"), wsText, bufferSize );
          g_wfDumpFile.SeekEnd();
          g_wfDumpFile.Write( wsT, wsT.Length() );
        else
          return -1;
        catch(XMP_Error & e)
    The output for the one line in question:
    <Iptc4xmpCore:CiAdrExtadr> size(24)< = "> size(4)<Leo-Saurer-Straße> size(15)<> size(1)<C3> size(2)<> size(1)<9F> size(2)<>> size(1)<e> size(1)<"> size(1)<
    > size(1)<   > size(3)<   > size(3)<   > size(3)
    The hex contents of the buffer I get in the callback is
    0x003908D0  4c 65 6f 2d 53 61 75 72 65 72 2d 53 74 72 61 c3 9f 65 00 cd cd cd cd  Leo-Saurer-Straße.ÍÍÍÍ
    0x003908E7  cd cd cd cd cd cd cd cd cd fd fd fd fd ab ab ab ab ab ab ab ab ee fe  ÍÍÍÍÍÍÍÍÍýýýý««««««««îþ
    As you can see, my conversion routines takes all the buffer contains and converts it to the appropriate UTF-8 string, even though the count passed to me is short and represents only the count up to the first non-ASCII character and all of the subsequent strings  - interpreted as hex values by the caller of the call back would not give me the correct characters, athough they are passed to me for display.
    The two fragments of one byte length are the ones I could not find in the actual output.
    The call stack at that point:
    >
    wxMeta.exe!DumpXMPToFile(void * __formal, const char * buffer, unsigned long bufferSize)  Line 110
    C++
    wxMeta.exe!TextOutputProcWrapper(void * refCon, const char * buffer, unsigned long bufferSize)  Line 60 + 0x18 bytes
    C++
    wxMeta.exe!DumpClearString(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > & value, long (void *, const char *, unsigned long)* outProc, void * refCon)  Line 409 + 0x1c bytes
    C++
    wxMeta.exe!DumpPropertyTree(const XMP_Node * currNode, int indent, unsigned int itemIndex, long (void *, const char *, unsigned long)* outProc, void * refCon)  Line 161 + 0x14 bytes
    C++
    wxMeta.exe!DumpPropertyTree(const XMP_Node * currNode, int indent, unsigned int itemIndex, long (void *, const char *, unsigned long)* outProc, void * refCon)  Line 222 + 0x1f bytes
    C++
    wxMeta.exe!XMPMeta::DumpObject(long (void *, const char *, unsigned long)* outProc, void * refCon)  Line 1100 + 0x23 bytes
    C++
    wxMeta.exe!WXMPMeta_DumpObject_1(__XMPMeta__ * xmpObjRef, long (void *, const char *, unsigned long)* outProc, void * refCon, WXMP_Result * wResult)  Line 968
    C++
    wxMeta.exe!TXMPMeta<std::basic_string<char,std::char_traits<char>,std::allocator<char> > >::DumpObject(long (void *, const char *, unsigned long)* outProc, void * refCon)  Line 833 + 0x21 bytes
    C++
    wxMeta.exe!MyFrame::DisplayMetaData(wxString & wsrFilePathAndName)  Line 484
    C++
    Hoping this will help resolve the issue :-)

  • Problems in Instantiating the Model Node

    Hi All,
    I Have a problem with creating the instance of a Model Node  which needs an urgent solution, This is the Scenario:
    I Have created a WebDynpro Project using NetWeaver CE Environment and Java EE 5.0 where i am using an Adaptive WebService Model. I have successfully created the model using the WSDL files and have also added to the Controller,
    But when I try to create an Instance of the Request Node in my controller ie after writing this line:
    Request_MI_Nwce007_AS_SOAPReq objReq = null;
    objReq = new Request_MI_Nwce007_AS_SOAPReq();
    This is the Request Structure from the WSDL - Request_MI_Nwce007_AS_SOAPReq
    it gives me an Error saying The constructor Request_MI_Nwce007_AS_SOAPReq() is undefined.
    Please let me know the exact problem and also the way to overcome this problem.
    Its Quite URGENT!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Points Rewarded for helpful answers.
    Regards,
    Poojith MV

    Hi Poojitha,
    If your imported Webservice has any structure like  this Request_MI_Nwce007_AS_SOAPReq_Input then instantiate the input structure.
    else
    Try instantiating along with the package name, for example if your package name is: com.sdn then try this:
    "com.sdn.*Request_MI_Nwce007_AS_SOAPReq objReq = null;
    objReq = new com.sdn.Request_MI_Nwce007_AS_SOAPReq();
    Hope this solves your problem.
    Thanks n Regards,
    Jhansi Miryala

  • 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)

  • Problem with database functions after disposing frames.....

    Hello,
    I have some problems with hangups with my app after disposing some frames...
    My scenario is something like this:
    - i have a login frame which instantiates some other application module and it disposes itself with some code like:
    this.dispose();
    this.finalize();
    System.runFinalization();
    System.gc();
    - after that the new instantiated module frame can return to the login frame by disposing itself and instantiating again the login frame with the same code like above
    my problem is that after some 2-3 tryes to login to a module - retun to login - login to module - return to module my app hangs on some code like:
    combobox.setSelectedIndex(0);
    or
    queryDataSet.executeQuery();
    i have to mention that i use a DataModule.
    do u have any ideas?
    thanks in advance.
    adrian

    >
    - i have a login frame which instantiates some other
    application module and it disposes itself with some
    code like:
    this.dispose();
    this.finalize();
    System.runFinalization();
    System.gc();
    Sounds like a bad idea all around.
    Finalize is supposed to be called by the gc - not by you.
    Almost always using finalize is either pointless or will cause memory leaks.
    do u have any ideas?
    I would guess it has nothing to do with JDBC.
    Are you catching SQLException and printing them out? If not then do so.
    If you are do you see any exceptions? If not then it isn't JDBC.

  • Performance problem with synchronized singleton

    I'm using the singleton pattern to cache incoming JMS Message data from a 3rd party. I'm seeing terrible performance though, and I think it's because I've misunderstood something.
    My singleton class stores incoming JMS messages in a HashMap, so that successive messages can be checked to see if they are a new piece of data, or an update to an earlier one.
    I followed the traditional examples of a private constructor and a public getInstance method, and applied the double-checked locking to the latter. However, a colleague then suggested that all my other methods in the same class should also be synchronized - is this the case or am I creating an unnecessary performance bottleneck? Or have I unwittingly created that bottleneck elsewhere?
    package com.mycode;
    import java.util.HashMap;
    import java.util.Iterator;
    public class DataCache {
        private volatile static DataCache uniqueInstance;
        private HashMap<String, DataCacheElement> dataCache;
        private DataCache() {
            if (dataCache == null) {
                dataCache = new HashMap<String, DataCacheElement>();
        public static DataCache getInstance() {
             if (uniqueInstance == null) {
                synchronized  (DataCache.class) {
                    if (uniqueInstance == null) {
                        uniqueInstance = new DataCache();
            return uniqueInstance;
        public synchronized void put(String uniqueID, DataCacheElement dataCacheElement) {
            dataCache.put(uniqueID, dataCacheElement);
        public synchronized DataCacheElement get(String uniqueID) {
            DataCacheElement dataCacheElement = (DataCacheElement) dataCache.get(uniqueID);
            return dataCacheElement;
        public synchronized void remove(String uniqueID) {
            dataCache.remove(uniqueID);
        public synchronized int getCacheSize() {
         return dataCache.keySet().size();
         * Flushes all objects from the cache that are older than the
         * expiry time.
         * @param expiryTime (long milliseconds)
        public synchronized void flush(long expiryTime) {
            String uniqueID;
            long currentDate = System.currentTimeMillis();
            long compareDate = currentDate - (expiryTime);
            Iterator<String> iterator = dataCache.keySet().iterator();
            while( iterator.hasNext() ){
                // Get element by unique key
                uniqueID = (String) iterator.next();
                DataCacheElement dataCacheElement = (DataCacheElement) get(uniqueID);
                // get time from element
                long lastUpdatedDate = dataCacheElement.getUpdatedDate();
                // if time is greater than 1 day, remove element from cache
                if (lastUpdatedDate <  compareDate) {
                    remove(uniqueID);
        public synchronized void empty() {
            dataCache.clear();
    }

    m0thr4 wrote:
    SunFred wrote:
    m0thr4 wrote:
    I [...] applied the double-checked locking
    Which is broken. http://www.ibm.com/developerworks/java/library/j-dcl.html
    from the link:
    The theory behind double-checked locking is perfect. Unfortunately, reality is entirely different. The problem with double-checked locking is that there is no guarantee it will work on single or multi-processor machines.
    The issue of the failure of double-checked locking is not due to implementation bugs in JVMs but to the current Java platform memory model. The memory model allows what is known as "out-of-order writes" and is a prime reason why this idiom fails[b].
    I had a read of that article and have a couple of questions about it:
    1. The article was written way back in May 2002 - is the issue they describe relevant to Java 6's memory model? DCL will work starting with 1.4 or 1.5, if you make the variable you're testing volatile. However, there's no reason to do it.
    Lazy instantiation is almost never appropriate, and for those rare times when it is, use a nested class to hold your instance reference. (There are examples if you search for them.) I'd be willing to be lazy instantiation is no appropriate in your case, so you don't need to muck with syncing or DCL or any of that nonsense.

Maybe you are looking for

  • Error creating OIM schema with RCU 11.1.1.3.3 (RCU-6135)

    Hello! I'm trying to install Oracle Access & Identity Management 11g on Windows Server 2003 32bit machine As main guide I use the article from onlineappsdba.com ( [this one|http://onlineappsdba.com/index.php/2010/08/05/oracleidm-11g-step-by-installat

  • How can I EXCLUDE particular folders/files from being included in the Lightroom 5 catalog?

    How can I EXCLUDE particular folders/files from being included in the Lightroom 5 catalog? I want to be able to specify paths and/or filename patterns that should NEVER be indexed in the catalog: not that they don't show up under certain circumstance

  • Invoking crystal reports using weblogic

              hi ,           We are invoking crystal reports using it's CGI component           ie wcscgi.exe.we have placed the exe in cgi-bin directory           created in public_html directory.During the runtime           the following error occurs:

  • Error when upgrading from 10.4 to 10.5

    Hi, I am getting an error message when I attempt to upgrade my macbook from 10.4.11 to 10.5. Before the installation begins I receive a message that states "You need 10.4 before upgrading. I thought it may have been a HD problem so I used disk utilit

  • How do I uninstall 10.4.5

    Hey, I recently updated to tiger 10.4.5 WHAT A MISTAKE!! Now the computer cannot recognize any of my video cameras. I need to do work tonight for uni!!! So how do I revert back to using 10.4.4?? PS. why do apple screw us around so much? The idea of a