[svn] 4171: Nested exception handlers in an instance method: fix arg0 ( the activation record).

Revision: 4171
Author: [email protected]
Date: 2008-11-23 18:09:10 -0800 (Sun, 23 Nov 2008)
Log Message:
Nested exception handlers in an instance method: fix arg0 (the activation record).
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/adobe/abc/GlobalOptimizer.java

Similar Messages

Verifier Error: Exception handlers not sorted in ascending order by the off

Hello,
Java Card 2.2 did not convert my Applet !
Java Card 2.2.1 & 2.1.2 do not report this Error and the Applet is working !
What's wrong here ?
D:\save\smsTest>C:\Programme\Java\jdk1.5.0_06\bin\java -classpath D:\java_card_kit-2_2\lib\converter.jar;D:\java_card_kit-2_2\lib\offcardverifier.jar com.sun.javacard.converter.Converter -config SMS_JCDK_2_2.opt
Java Card 2.2 Class File Converter (version 1.3)
Copyright 2002 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms.
warning: You did not supply export file for the previous minor version of the package
parsing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\IExceptionConstants.class
parsing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\ITestConsts.class
parsing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\InfoData.class
parsing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\SMS.class
parsing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\StringConsts.class
converting com.gieseckedevrient.jctt.smsTest.IExceptionConstants
converting com.gieseckedevrient.jctt.smsTest.ITestConsts
converting com.gieseckedevrient.jctt.smsTest.InfoData
parsing D:\java_card_kit-2_2\api_export_files\java\lang\javacard\lang.exp
converting com.gieseckedevrient.jctt.smsTest.SMS
parsing D:\java_card_kit-2_2\api_export_files\javacard\framework\javacard\framework.exp
parsing U:\_Tools\java\43019-560\Annex_B_Export_Files\sim\toolkit\javacard\toolkit.exp
converting com.gieseckedevrient.jctt.smsTest.StringConsts
writing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\javacard\smsTest.exp
writing D:\save\smsTest\com\gieseckedevrient\jctt\smsTest\javacard\smsTest.jca
Verifier Error: Exception handlers not sorted in ascending order by the offset of the handler
Verification failed

Hello again,
it seams this error only occurs when using javac from JDK 1.5/1.6 (1.4 not tested).
When I us jdk1.3.1_11 to compile the java sources this error never occurs during conversion !

How to call a instance method without creating the instance of a class

class ...EXCH_PRD_VERT_NN_MODEL definition
public section.
methods CONSTRUCTOR
    importing
      value(I_ALV_RECORDS) type ..../EXCH_VBEL_TT_ALV
      value(I_HEADER) type EDIDC .
methods QUERY
    importing
      I_IDEX type FLAG
      i_..........
    returning
      value(R_RESULTS) type .../EXCH_VBEL_TT_ALV .
Both methods are instance methods.
But in my program i cannot created instance of the class unless i get the results from Query.
I proposed that Query must be static, and once we get results we can create object of the class by pasing the result table which we get from method query.
But i must not change the method Query to a static method.
Is there any way out other than making method Query as static ?
Regards.

You can't execute any instance method without creating instance of the class.
In your scenario, if you don't want to process your method of your class, you can check the instance has been created or not.
Like:
IF IT_QUERY IS NOT INITIAL.
CRATE OBJECT O_QUERY EXPORTING......
ENDIF.
IF O_QUERY IS NOT INITIAL.
CALL METHOD O_QUERY->QUERY EXPORTING....
ENDIF.
Regards,
Naimesh Patel

Two questions: Scanner and exception handlers

Extreme Newbie Alert: I took a single college semester involving Java, almost five years ago, and haven't really touched it since until recently when I decided to try to get back into it. I am now working on building a program while reading the Java 5.0 Tutorial downloadable from Sun.
Okay, now that the faint of heart have left us, here are the two questions I want to ask:
1) I am trying to use the Scanner tool ( http://java.sun.com/j2se/1.5.0/docs/api/java/util/Scanner.html ) on a FileReader wrapped in a BufferedReader. I have installed JDK 5.0 and I am importing java.util.*, but when I try to compile I get this error:
Wishlist.java:71: cannot resolve symbol
symbol : class Scanner
location: class Wishlist
Scanner readFromMe = new Scanner(new BufferedReader(new FileReader("wishlist.txt")));
^
...and then another one pointing to the other appearance of "Scanner" in the same line, followed by six more in places where I use the readFromMe variable that line was supposed to declare and initialize. Any idea why the compiler doesn't recognize Scanner even though I'm importing its package?
2) Is there anything preventing you from nesting exception handlers? As you've seen, in this program I open a file...if that attempt produces a FileNotFoundException, I want the error handling to create a new, empty file to use in place of the one that should have been there. Since this could throw an IOException of its own, I would need to put a try | catch block into the other catch block. Is the compiler going to stand for that? Alternatively, is there any input stream that creates a file with the specified filename if there is none already? Probably not, since a newly created file will be empty and there's no point in having an input stream on it...

1) Are you sure you installed and are invoking jdk
1.5? Maybe you have an earlier version ahead of it
on your path.Hm. I did use 1.3 back in college...I checked the contents of PATH and the User Variables version of it was set correctly but the System Variables version of it was set to 1.3. I corrected the System Variables version of it and now the compiler doesn't complain about Scanner...but I'm still getting errors that it doesn't recognize readFromMe even after I initialized it. Odd...
2) yeah you can nest try/catch blocks like that.
However, in this case, exceptions sound like the
wrong way to go. A missing file sounds like a real,
regular possibility -- it's not that exceptional as
you describe it. A better thing would be to create
a File object, see if the file exists, and then if
it doesn't go ahead and immediately handle that
case. Don't even try to open the file that may not
exist.Okay, I'll try rewriting the file read like that, and hopefully the readFromMe errors will go away. If they don't I'll make a new post...probably with the entirety of the code because I can't even guess at what part of the code is causing that. Thanks for the help!

Javax.ejb.EJBException: Could not unmarshal method ID; nested exception is:

When i am calling a method getewebLevel() from the service layer getting this exception, in the view controller java file, but when i am calling this method from the Model layer, main file it's giving me correct result... but when extending to the view layer getting this :-- i have created the data controls and also added the bindings to the .jsff files
javax.ejb.EJBException: Could not unmarshal method ID; nested exception is:
java.rmi.UnmarshalException: Method not found: 'getewebLevel(Ljava.lang.String;)'; nested exception is: java.rmi.UnmarshalException: Method not found: 'getewebLevel(Ljava.lang.String;)'
java.rmi.UnmarshalException: Method not found: 'getewebLevel(Ljava.lang.String;)'
Edited by: 971944 on Dec 11, 2012 11:17 PM

Where is the method getewebLevel located - in Model or ViewController ?

Exception handlers and subscripts

Hi,
When I write a script, I specify a handlers for exceptions such as ContactInactive. When I call a subscript from my original script, I assume I have to reset the exception handlers to point to labels in the subscript, correct? If that is correct, my next question is do I have to set the exception handlers once again when I return from the subscript, or will the setting be retained from when I set it earlier in my original script?
Thanks in advance for any help.
Robert

Hi,
http://www.lc.leidenuniv.nl/awcourse/oracle/appdev.920/a96624/07_errs.htm#877
this will give u the information.
Regards
Bharath

Class methods vs. Instance methods

When shall we use class methods instead of instance methods , and vice versa?
By going through the Java Tutorial, it only says the following.
A common use for static methods is to access static fields....
I am definitely sure that class methods aren't just exist for accessing static fields of a class.
PS. I understand that instance methods belong to the object that is instantiated and class methods belong to the class itself.

Jay-K wrote:
JoachimSauer wrote:
P.S.: I wouldn't call them "class methods". They are called static methods in Java. It helps to stay with the common, widely-used terminology.Thanks, its good to know what the norms are.
but i wonder why the Java Tutorial states it clearly "Class Methods" over here [http://java.sun.com/docs/books/tutorial/java/javaOO/classvars.html|http://java.sun.com/docs/books/tutorial/java/javaOO/classvars.html]
Because strictly speaking that's what they are. They belong to classes, rather than instances of classes. The world-at-large, though, has found that term to be a bit ambiguous, especially when discussing fields - it's not uncommon to see instance variables referred to as "class variables" by newbies - so it's kind-of self-corrected.

Objects and instance methods for JSP?

I've been looking through the JSP 2.0 specification and, while I'm extremely impressed with the improvements in this version, I'm also disappointed to see that everything still boils down to statically bound methods.
What I mean by this is that the template part of a JSP is like an anonomously named static method associated with the JSP class. The new tag-files in JSP 2.0 are terrific, but they also have this same kind of static binding.
As far as I know, only JPlates (www.jplates.com) allows you to develop web applications using actual instances of classes that have instance methods for expressing the template parts. Are there any other template processing systems that support real object-oriented development of dynamic content-generation applications?

By an amazing coincidence, the domain name jplates.com is registered to a Daniel Jacobs and your user name is djacobs. What are the odds of that?
If you're going to plant commercials, you need to disguise them better than this.

Bapi - class method-instance method

can v tell from a given bapi, whether a particular bapi is a class method or an instance method by observing the code?

Priya Madhavi wrote:
> i mean the example in the code... with the syntax that u gave for both the types.
I didn't get your point about syntax?
May be check this link
http://www.sapmaterial.com/bapi_example.html
a®

JPA error with nested exception for more details

Hi All,
A strange thing is that when i can deploy javaee app successfully. But some time, it is failed and i have to wait for 10, 15 minutes then i can deploy again. When i got error, below is the error message:
I don't know if you can find a hint.
INFO: EclipseLink, version: Eclipse Persistence Services - 2.3.2.v20111125-r10461
SEVERE: Local Exception Stack:
Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 more
SEVERE: Exception while invoking class org.glassfish.persistence.jpa.JPADeployer prepare method
SEVERE: Exception while preparing the app
SEVERE: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
javax.persistence.PersistenceException: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:517)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                ... 40 more
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 more
SEVERE: Exception while preparing the app : Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
Local Exception Stack:
Exception [EclipseLink-4019] (Eclipse Persistence Services - 2.3.2.v20111125-r10461): org.eclipse.persistence.exceptions.DatabaseException
Exception Description: Error while obtaining information about the database. Refer to the nested exception for more details.
                at org.eclipse.persistence.exceptions.DatabaseException.errorRetrieveDbMetadataThroughJDBCConnection(DatabaseException.java:361)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:602)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryProvider.login(EntityManagerFactoryProvider.java:206)
                at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:488)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.getDatabaseSession(EntityManagerFactoryDelegate.java:188)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryDelegate.createEntityManagerImpl(EntityManagerFactoryDelegate.java:277)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:294)
                at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:272)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.loadPU(PersistenceUnitLoader.java:211)
                at org.glassfish.persistence.jpa.PersistenceUnitLoader.<init>(PersistenceUnitLoader.java:120)
                at org.glassfish.persistence.jpa.JPADeployer$1.visitPUD(JPADeployer.java:224)
                at org.glassfish.persistence.jpa.JPADeployer$PersistenceUnitDescriptorIterator.iteratePUDs(JPADeployer.java:495)
                at org.glassfish.persistence.jpa.JPADeployer.createEMFs(JPADeployer.java:233)
                at org.glassfish.persistence.jpa.JPADeployer.prepare(JPADeployer.java:168)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.prepareModule(ApplicationLifecycle.java:871)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:410)
                at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:240)
                at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:389)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:348)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:363)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1085)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$1200(CommandRunnerImpl.java:95)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1291)
                at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1259)
                at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:461)
                at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:212)
                at com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:179)
                at com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:117)
                at com.sun.enterprise.v3.services.impl.ContainerMapper$Hk2DispatcherCallable.call(ContainerMapper.java:354)
                at com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:195)
                at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:849)
                at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:746)
                at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:1045)
                at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:228)
                at com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:137)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:104)
                at com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
                at com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:79)
                at com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
                at com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:59)
                at com.sun.grizzly.ContextTask.run(ContextTask.java:71)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:532)
                at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:513)
                at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLRecoverableException: Closed Connection
                at oracle.jdbc.driver.PhysicalConnection.getMetaData(PhysicalConnection.java:4508)
                at com.sun.gjc.spi.base.ConnectionHolder.getMetaData(ConnectionHolder.java:345)
                at org.eclipse.persistence.internal.sessions.DatabaseSessionImpl.loginAndDetectDatasource(DatabaseSessionImpl.java:589)
                ... 42 morethanks,
-Hoang Long

r035198x wrote:
Yep, the appserver got hold of a usable connection but the connection was closed before the appserver had finished/committed with it. It could be that the connection was closed by the database or some firewall timeout setting.
A good start is to investigate options of configuring your appserver's connection eviction policies including forcing a validation SQL to be executed when a connection is acquired. Make sure that such a query doesn't impact on performance and have some performance and integration testing before rolling out.i found that if i close the computer which causes this issue, hence other dev computers can deploy normally.
"deploy" here i mean deploy to a running instance on each dev's machine.
From this, i would guess the common database server itself rejects connection from clients.
I will try to investigate more if i am missing something.
And here i found a link that possibly a first good attempt:
[http://www.eclipse.org/forums/index.php/m/505809/]
EclipseLink automatically recovers from communication failures, but there is little we can do to diagnose the failure. We basically execute a query and have to wait for the JDBC driver, or DataSource's response, if it hangs for 10minutes, then we are waiting. You could set the JDBC timeout hint on your query, but whether the JDBC driver honors this is up to the driver. You should see the SQLException in your logs, provided your log level is warning or lower.
If you cannot fix your firewall, they you could change your connection pool settings to use a min number of connections of 0, so there will never be idle connections. But then you will be reconnecting a lot.
You could also use a third party connection pool or DataSource that supports a timeout setting on the pooled connections, or spawn a thread in your application the clears the connection pool every 30minutes.regards,
-HL

Javax.ejb.EJBException: Nested Exception:javax.xml.ws.WebServiceException:

Hello Experts..,
I created a EJB session bean 3.0 (Remote and Local). I created a web service from this bean.
When I test the web service, I get following exception...
javax.ejb.EJBException: Exception raised from invocation of public java.lang.String com.<name>...doeHeader(java.lang.String) method on bean instance com.<name>...@714647bf for bean nested exception is: javax.xml.ws.WebServiceException: java.lang.ClassCastException: class ..jndi.persistent.UnsatisfiedReferenceImpl:service:[email protected]@4807ccf6@alive incompatible with interface
My ejb-jar.xml is almost empty:
<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd">
</ejb-jar>
Am I missing any properties in the ejb-jar.xml?
Server logs show
at $Proxy3060.salesOrderCreateOut(Unknown Source)
at com...doe.salesheader.DoeToPIBean.doeHeader(DoeToPIBean.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
What does these logs mean?
Thanks
Srinivas

Here is the DoeToPIBean
@WebService(targetNamespace="http://<name>.com/doe/salesheader/", endpointInterface="com...doe.salesheader.DoeToPIRemote", portName="DoeToPIBeanPort", serviceName="DoeToPIService")
@Stateless
public class DoeToPIBean implements DoeToPIRemote, DoeToPILocal {
     @WebServiceRef (name="SalesOrderCreateOutService")
     private SalesOrderCreateOutService service;
     public String doeHeader(String headerXml){
          SalesOrderCreateOut servicePort = service.getSalesOrderCreate_Out_Port();
          javax.xml.ws.BindingProvider bp = (javax.xml.ws.BindingProvider) servicePort;
          Map<String, Object> context = bp.getRequestContext();
          context.put(BindingProvider.USERNAME_PROPERTY, "<name>");
          context.put(BindingProvider.PASSWORD_PROPERTY, "<pwd>");
          SalesOrderResponse response = null;
          Project salesOrderCreateRequest = new Project();
          Header header = new Header();
          header.setTitle("EAST COAST SHEET METAL MOTOR WARRANTY");
          header.setBillToName("GLOBAL MECHANICAL SYSTEMS LTD");
          salesOrderCreateRequest.setHeader(header);
          try {
               response = servicePort.salesOrderCreateOut(salesOrderCreateRequest);
          } catch (SalesOrderError_Exception e) {
               // TODO Auto-generated catch block
               e.printStackTrace();
          TRETURN treturn = response.getTRETURN();
          Iterator ls = treturn.getItem().iterator();
          while(ls.hasNext()){
               TRETURN.Item tempItem = (TRETURN.Item)ls.next();
               headerXml = tempItem.getMESSAGE();
               break;
          return headerXml;
Exception occurs on the bold line above: (line 58)
When I "CTRL + click" on the method "salesOrderCreateOut" on this line, it goes to the interface declaration. So I don't see the implementation of this interface method anywhere in my workspace..,
I generated this client code using the wizard similar to wsimport..
Here is the full stack trace:
Error com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding # java.lang.ClassCastException: class com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl:service:[email protected]@75da931b@alive incompatible with interface com.sap.engine.services.webservices.espbase.xi.ESPXIMessageProcessor:library:[email protected]ssLoader@5892a78b@alive
[EXCEPTION]
javax.xml.ws.WebServiceException: java.lang.ClassCastException: class com.sap.engine.services.jndi.persistent.UnsatisfiedReferenceImpl:service:[email protected]@75da931b@alive incompatible with interface com.sap.engine.services.webservices.espbase.xi.ESPXIMessageProcessor:library:[email protected]ssLoader@5892a78b@alive
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_XI(SOAPTransportBinding.java:2067)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:812)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:759)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:167)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:120)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:83)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:64)
at $Proxy3060.salesOrderCreateOut(Unknown Source)
at com....doe.salesheader.DoeToPIBean.doeHeader(DoeToPIBean.java:58)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Here is the full stack trace, as this editor won't let me paste (limit is 7500 chars)...
http://www.yousendit.com/download/YWhPSkhRTXY3bUJjR0E9PQ

Regarding Nested exception message

Hi,
In my application, when i run the servlet it gives me following stack trace. I am settign the attribute of exception and passing exception to JSP page where after getting and checking the attribute value . I am setting the new error message.
Issue : My nested excpetion (as per the trace) gives a good explanation of error/exception.
"Nested exception:
Cannot use javahl nor command line svn client"
But when i display the message using e.getMessage or .getLocalizedMessage. I get the message as
org.leafcutter.core.TaskRunnerException: Unable to execute task 'svn'
Is there any way where i can set the nested exception message and send it to JSP page. I dot want the main exception message but nested exception message. Please let me know if it is possible
====================
org.leafcutter.core.TaskRunnerException: Unable to execute task 'svn' at org.leafcutter.core.AntObject.execute(Unknown Source)
at org.leafcutter.core.TaskRunner.run(Unknown Source)
at org.leafcutter.core.TaskRunner.run(Unknown Source)
at DiffServlet.doGet(DiffServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:284)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:204)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:257)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:245)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:199)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:184)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:164)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:156)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:20
6)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:833)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:732)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:619)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:534)
Nested exception:
Cannot use javahl nor command line svn client
at org.tigris.subversion.svnant.SvnTask.execute(SvnTask.java:269)
at org.leafcutter.core.AntObject.execute(Unknown Source)
at org.leafcutter.core.TaskRunner.run(Unknown Source)
at org.leafcutter.core.TaskRunner.run(Unknown Source)
at DiffServlet.doGet(DiffServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:284)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:204)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:257)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardContextValve.invokeInternal(Standard
ContextValve.java:245)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:199)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:184)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:164)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:149)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:156)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValv
eContext.java:151)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.jav
a:567)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:972)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:20
6)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:833)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ssConnection(Http11Protocol.java:732)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java
:619)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP
ool.java:688)
at java.lang.Thread.run(Thread.java:534)
==============================

let me rephrase the question.
I am using 3rd party API leafcutter, due to some reason it is throwing one exception (nested one). In the main flow this exception is coming along with main exception
I want the message of nested exception.
If it can be implemented with getCause. Please let me know how to set that.
or is there any other way to implement this

EJB 3.0 Application Client threw Remote nested exception

Hi All,
I came across the following EJBException message when trying to retrieve an Employee record (entity bean in EJB 3.0) after having successfully added it into EMPLOYEE table using stateless session bean:
*10/03/2009 8:53:14 PM com.sun.enterprise.appclient.MainWithModuleSupport <init>*
WARNING: ACC003: Application threw an exception.
javax.ejb.EJBException: nested exception is: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: null; nested exception is:
java.lang.NullPointerException
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: null; nested exception is:
java.lang.NullPointerException
at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:243)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)
at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)
at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)
at ejb.__EmployeeRemote_Remote_DynamicStub.findEmployee(ejb/__EmployeeRemote_Remote_DynamicStub.java)
at ejb._EmployeeRemote_Wrapper.findEmployee(ejb/_EmployeeRemote_Wrapper.java)
at client.EmployeeApplicationClient.printEmployee(EmployeeApplicationClient.java:608)
at client.EmployeeApplicationClient.main(EmployeeApplicationClient.java:55)
Below is the code snippets of EmployeeApplicationClient.java:
public class EmployeeApplicationClient {
    @EJB
    private static EmployeeRemote employeebean1;
    @EJB
    private static EmployeeRemote employeebean2;
    public EmployeeApplicationClient() {}
    public static void main(String[] args)
        EmployeeApplicationClient employee_application_client = new EmployeeApplicationClient();
        employee_application_client.addEmployee(1, John, Smith);
        employee_application_client.printEmployee(1);
    public void addEmployee(int id, String firstname, String surname)
        try {
            Employee employee1 = new Employee();
            employee1.setID(id);
            employee1.setfirstname(firstname);
            employee1.setsurname(surname);
            employeebean1.createEmployee(employee1);
        catch {.....}
    public void printEmployee(int employee_id)
       Employee employee2 = employeebean2.findEmployee(employee_id);
       System.out.println("employee Id: " + employeebean2.getId());
       System.out.println("employee firstname: " + employeebean2.getfirstname());
       System.out.println("employee surname: " + employeebean2.getsurname());
}Using employeebean1/employeebean2 in printEmployee() did not make any difference.
The error message appears to indicate that I have incorrectly structured these methods.
The deployment of EmployeeBean was successful and employee1 is in EMPLOYEE table via SQL query.
I am using JDK1.6.07, Glassfish v2 with MySQL 5.0 and Netbeans 6.1 on Windows XP platform.
Any assistance would be greatly appreciated.
Thanks,
Jack

Hi Ataraxisme,
Thank you for responding to this post.
This is a J2EE Application Client that was created and deployed along as an Netbeans EAR (both Application Client and EJB) project which uses resource injection as opposed to JNDI lookup.
I am trying to get employeeApplicationClient.java to work the same way as the following travelAgentApplicationClient.java example which has successfully retrieved its record record immediately after adding using resource injection:
public class TravelAgentClient {
    @EJB
    private static TravelAgentRemote travelagent;
    public TravelAgentClient() {
    public static void main(String[] args) {
        TravelAgentClient client = new TravelAgentClient();
        client.doTravelAgent();
    public void doTravelAgent() {
        try {
            Cabin cabin_1 = new Cabin();
            cabin_1.setId(1);
            cabin_1.setName("Master Suite");
            cabin_1.setDeckLevel(1);
            cabin_1.setShipId(1);
            cabin_1.setBedCount(3);
            travelagent.createCabin(cabin_1);
            Cabin cabin_2 = travelagent.findCabin(1);
            System.out.println(cabin_2.getName());
            System.out.println(cabin_2.getDeckLevel());
            System.out.println(cabin_2.getShipId());
            System.out.println(cabin_2.getBedCount());
         ......Thanks,
Jack

Error in PI mapping "nested exception is: java.lang.OutOfMemoryError "

Hi Experts ,
I encounter an error in the PI mapping while calling a Java Mapping (Mercator Map)
Error Message as ::-
java.lang.RuntimeException: RemoteException in setMercGeneral: Error occurred in server thread; nested exception is: java.lang.OutOfMemoryError at com.philips.xi.mercator.MercatorCall.execute(MercatorCall.java:90) at
Could anyone suggest , how we can overcome this error message
I have also tried to restart the RMI Server , but that was not not helpful.
Regards,
Shweta

Sweta,
Is this a java mapping or Graphical, If Java, you should not run into this issue as you dont load the nested XSD`s.
Also the error message indicates outofMemory in mercator side when posting your Large message.
java.lang.OutOfMemoryError at com.philips.xi.mercator.MercatorCall.execute(MercatorCall.java:90) at
Regards
Ravi Raman
Edited by: Ravi Raman on Jun 30, 2010 4:26 PM

Java.rmi.ServerError: A error occurred the server; nested exception is:

Hello Guys,
I'm getting the following error when calling a method of a normally
deployed facade session bean.
java.rmi.ServerError: A error occurred the server; nested exception is:
java.lang.AbstractMethodError
It's very confusing, it sometimes appear and sometimes the method is
invoked normally.
Thanks in advance for ur help.
Itani
[att1.html]

That error means your are not running xserver process. Or, your ssh connection is not set-up to forward X-11 data.

[svn] 4171: Nested exception handlers in an instance method: fix arg0 ( the activation record).

Similar Messages

Maybe you are looking for