JDBInsight 2.0 Released - True J2EE/JDBC Resource Transaction Analysis !!
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation of J2EE performance management products from JInspired.
Downloads: http://www.jinspired.com/products/jdbinsight/downloads/index.html
JDBInsight is the first product to effectively integrate Java profiling information with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived from its support of the Java VM Profiling Interface (JVMPI) such as Java call stack analysis, cpu, blocking and waiting measurements at the transaction path level. Clock measurements are adjusted for blocking, waiting and gc pauses. New features in this release
- New console user interface: Many new informative visualizations of J2EE transactions and performance execution profiles have been added. Including call stack graphs, entry point tree maps, sequence diagrams, call stack and transaction transcripts. Additional views included allow for navigation of the performance profile via database table or column, Java package, class, or method, technology classification, SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE server administrators can now better understand the interaction of various Java enterprise technologies with corporate databases. Classifications are available for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets, JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way to communicate with multiple servers without having to use a graphical user interface. This facilitates the streamlined connection, activation and deactivation of profiles on local or remote servers with the ability to control multiple servers from a single terminal. The terminal environment provides a powerful environment to create and schedule snapshot information, in order to monitor servers at regular intervals, with the ability to store and retrieve snapshots from any mounted drive, as well as providing a rich set of commands, that can be executed from saved scripts, to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management product to have the ability to detect and present resource transaction demarcations - allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for each JDBC interception point create a resource object. When a JDBC resource changes state the allocation site counters are updated. This helps to pinpoint source code locations where resource objects are created and not closed properly or freed from memory. Because an interception is a combination of call stack and SQL the view caters for generic J2EE application frameworks which create objects based on application parameters and callers.
- Xml expor: Various statistical measurements can be viewed in Xml format and copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying the performance tuning and testing of J2EE(tm) applications, which access data through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the access of enterprise data by J2EE(tm) client-, web-, and bean containers. The analysis can encompass transaction executions, from multiple J2EE(tm) containers. JDBInsight captures timing and execution information for enterprise data accessed by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an Entity Bean using a container's persistence engine. JDBInsight can also profile non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management tools on the market is that JDBInsight provides analysis from a sequence perspective instead of simply showing a call tree. Inefficiencies in J2EE applications occur mainly at the transaction level such as repeating the execution of a particular SQL locally and globally. JDBInsight facilitates the recognition of database interaction patterns that exhibit inefficiencies when viewed in terms of the sequential execution of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for Application Performance Tuning and Testing that focuses directly on early identification within the development and testing lifecycle. Jinspired offers sophisticated analytical tools, that capture transactional behaviour and performance timing information, across multiple containers in a single console, and presents this information intuitively to the user "Visualizing the Invisible".
any one
Similar Messages
-
JDBInsight 2.0 Released - True JDBC Transaction Analysis !!!
Check out the new product release and revised documentation at:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
PRESS RELEASE
=============
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
of J2EE performance management products from JInspired.
JDBInsight is the first product to effectively integrate Java profiling information
with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
analysis, cpu, blocking and waiting measurements at the transaction path level.
Clock measurements are adjusted for blocking, waiting and gc pauses. New features
in this release
- New console user interface: Many new informative visualizations of J2EE transactions
and performance execution profiles have been added. Including call stack graphs,
entry point tree maps, sequence diagrams, call stack and transaction transcripts.
Additional views included allow for navigation of the performance profile via
database table or column, Java package, class, or method, technology classification,
SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE
server administrators can now better understand the interaction of various Java
enterprise technologies with corporate databases. Classifications are available
for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way
to communicate with multiple servers without having to use a graphical user interface.
This facilitates the streamlined connection, activation and deactivation of profiles
on local or remote servers with the ability to control multiple servers from a
single terminal. The terminal environment provides a powerful environment to create
and schedule snapshot information, in order to monitor servers at regular intervals,
with the ability to store and retrieve snapshots from any mounted drive, as well
as providing a rich set of commands, that can be executed from saved scripts,
to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management
product to have the ability to detect and present resource transaction demarcations
- allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for
each JDBC interception point create a resource object. When a JDBC resource changes
state the allocation site counters are updated. This helps to pinpoint source
code locations where resource objects are created and not closed properly or freed
from memory. Because an interception is a combination of call stack and SQL the
view caters for generic J2EE application frameworks which create objects based
on application parameters and callers.
- Xml export: Various statistical measurements can be viewed in Xml format and
copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of
overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying
the performance tuning and testing of J2EE(tm) applications, which access data
through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
analysis can encompass transaction executions, from multiple J2EE(tm) containers.
JDBInsight captures timing and execution information for enterprise data accessed
by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
Entity Bean using a container's persistence engine. JDBInsight can also profile
non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management
tools on the market is that JDBInsight provides analysis from a sequence perspective
instead of simply showing a call tree. Inefficiencies in J2EE applications occur
mainly at the transaction level such as repeating the execution of a particular
SQL locally and globally. JDBInsight facilitates the recognition of database interaction
patterns that exhibit inefficiencies when viewed in terms of the sequential execution
of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
Application Performance Tuning and Testing that focuses directly on early identification
within the development and testing lifecycle. Jinspired offers sophisticated analytical
tools, that capture transactional behaviour and performance timing information,
across multiple containers in a single console, and presents this information
intuitively to the user "Visualizing the Invisible".Check out the new product release and revised documentation at:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
PRESS RELEASE
=============
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
of J2EE performance management products from JInspired.
JDBInsight is the first product to effectively integrate Java profiling information
with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
analysis, cpu, blocking and waiting measurements at the transaction path level.
Clock measurements are adjusted for blocking, waiting and gc pauses. New features
in this release
- New console user interface: Many new informative visualizations of J2EE transactions
and performance execution profiles have been added. Including call stack graphs,
entry point tree maps, sequence diagrams, call stack and transaction transcripts.
Additional views included allow for navigation of the performance profile via
database table or column, Java package, class, or method, technology classification,
SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE
server administrators can now better understand the interaction of various Java
enterprise technologies with corporate databases. Classifications are available
for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way
to communicate with multiple servers without having to use a graphical user interface.
This facilitates the streamlined connection, activation and deactivation of profiles
on local or remote servers with the ability to control multiple servers from a
single terminal. The terminal environment provides a powerful environment to create
and schedule snapshot information, in order to monitor servers at regular intervals,
with the ability to store and retrieve snapshots from any mounted drive, as well
as providing a rich set of commands, that can be executed from saved scripts,
to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management
product to have the ability to detect and present resource transaction demarcations
- allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for
each JDBC interception point create a resource object. When a JDBC resource changes
state the allocation site counters are updated. This helps to pinpoint source
code locations where resource objects are created and not closed properly or freed
from memory. Because an interception is a combination of call stack and SQL the
view caters for generic J2EE application frameworks which create objects based
on application parameters and callers.
- Xml export: Various statistical measurements can be viewed in Xml format and
copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of
overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying
the performance tuning and testing of J2EE(tm) applications, which access data
through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
analysis can encompass transaction executions, from multiple J2EE(tm) containers.
JDBInsight captures timing and execution information for enterprise data accessed
by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
Entity Bean using a container's persistence engine. JDBInsight can also profile
non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management
tools on the market is that JDBInsight provides analysis from a sequence perspective
instead of simply showing a call tree. Inefficiencies in J2EE applications occur
mainly at the transaction level such as repeating the execution of a particular
SQL locally and globally. JDBInsight facilitates the recognition of database interaction
patterns that exhibit inefficiencies when viewed in terms of the sequential execution
of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
Application Performance Tuning and Testing that focuses directly on early identification
within the development and testing lifecycle. Jinspired offers sophisticated analytical
tools, that capture transactional behaviour and performance timing information,
across multiple containers in a single console, and presents this information
intuitively to the user "Visualizing the Invisible". -
JDBInsight 2.0 Released - True Transaction Analysis !!!
Check out the product and revised documentation at:
http://www.jinspired.com/products/jdbinsight/downloads/index.html
PRESS RELEASE
=============
DUBLIN, IRELAND - 29th October, 2003 - JInspired (www.jinspired.com), a leader
in J2EE(tm) transaction analysis, today announced JDBInsight 2.0, the next generation
of J2EE performance management products from JInspired.
JDBInsight is the first product to effectively integrate Java profiling information
with JDBC/SQL transaction analysis. Version 2.0 has numerous features derived
from its support of the Java VM Profiling Interface(JVMPI) such as Java call stack
analysis, cpu, blocking and waiting measurements at the transaction path level.
Clock measurements are adjusted for blocking, waiting and gc pauses. New features
in this release
- New console user interface: Many new informative visualizations of J2EE transactions
and performance execution profiles have been added. Including call stack graphs,
entry point tree maps, sequence diagrams, call stack and transaction transcripts.
Additional views included allow for navigation of the performance profile via
database table or column, Java package, class, or method, technology classification,
SQL tokens, or transaction entry points.
- Java call stack classification engine: Developers, testers, database and J2EE
server administrators can now better understand the interaction of various Java
enterprise technologies with corporate databases. Classifications are available
for Java enterprise technologies such as EJB, Hibernate, JDO, JMS, JSP, Servlets,
JTS, JDBC, and Struts.
- Terminal services: The terminal services add-on provides a quick and easy way
to communicate with multiple servers without having to use a graphical user interface.
This facilitates the streamlined connection, activation and deactivation of profiles
on local or remote servers with the ability to control multiple servers from a
single terminal. The terminal environment provides a powerful environment to create
and schedule snapshot information, in order to monitor servers at regular intervals,
with the ability to store and retrieve snapshots from any mounted drive, as well
as providing a rich set of commands, that can be executed from saved scripts,
to assist in analysis of this highly detailed profile data.
- Transaction demarcations: JDBInsight 2.0 is the first performance management
product to have the ability to detect and present resource transaction demarcations
- allowing visual sub-transaction identification.
- Resource Management: JDBInsight keeps counters representing objects states for
each JDBC interception point create a resource object. When a JDBC resource changes
state the allocation site counters are updated. This helps to pinpoint source
code locations where resource objects are created and not closed properly or freed
from memory. Because an interception is a combination of call stack and SQL the
view caters for generic J2EE application frameworks which create objects based
on application parameters and callers.
- Xml export: Various statistical measurements can be viewed in Xml format and
copied into applications for custom report generation.
- Server options: Additional system properties to customize the small amount of
overhead added during runs.
About JDBInsight
JDBInsight is an innovative enterprise development product, aimed at simplifying
the performance tuning and testing of J2EE(tm) applications, which access data
through the Java Database Connectivity (JDBC(tm)) API. JDBInsight analyses the
access of enterprise data by J2EE(tm) client-, web-, and bean containers. The
analysis can encompass transaction executions, from multiple J2EE(tm) containers.
JDBInsight captures timing and execution information for enterprise data accessed
by Servlets, JavaServer Pages, Session- and Entity Beans using JDBC(tm) or an
Entity Bean using a container's persistence engine. JDBInsight can also profile
non-J2EE applications that access enterprise data through the JDBC(tm) API.
What distinguishes JDBInsight from other profiling and performance management
tools on the market is that JDBInsight provides analysis from a sequence perspective
instead of simply showing a call tree. Inefficiencies in J2EE applications occur
mainly at the transaction level such as repeating the execution of a particular
SQL locally and globally. JDBInsight facilitates the recognition of database interaction
patterns that exhibit inefficiencies when viewed in terms of the sequential execution
of a business and/or resource transaction.
About JInspired
JInspired located in Ireland, delivers JDBInsight, a comprehensive solution for
Application Performance Tuning and Testing that focuses directly on early identification
within the development and testing lifecycle. Jinspired offers sophisticated analytical
tools, that capture transactional behaviour and performance timing information,
across multiple containers in a single console, and presents this information
intuitively to the user "Visualizing the Invisible".Dear Friend...
ur error concerning...
"In default.properties, I changed {transaction/sessionbean}.timeout from 0 to 100. Sometime after this, error.log contained:
"SQL Exception: Table or view 'Entity1BeanTable' already exists in
schema 'APP'". "
Ur XML file contains
"<create-table-deploy>true</create-table-deploy>"
The first time u deploy ur bean,table is created with the query specified.once u shutdown the server
"<delete-table-undeploy>false</delete-table-undeploy>" property does not allow the app server to drop the table.
This leaves u with the above mentioned error/exception when u start the server for the second time as ur server tries to create the table again.Moreover this will not hinder the starting process of the server.
ganesh -
1) How do I add a new jdbc resource.
The tutorial
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/WebApp12.html#wp70019
does it behind the scene with asant.
2) What shall I do if I don't want to use a jdbc resource but a jndi resource which
accesses a OpenLDAP server?JDBC resource can be created using asadmin command.
Its a two step process.
First JDBC connection pool has to be created using following command.
asadmin create-jdbc-connection-pool user admin password adminadmin host fuyako port 7070 datasourceclassname XA restype jax.sql.DataSource
isolationlevel serializable isconnectvalidatereq=true validationmethod auto-commit description "XA Connection" --property DatabaseName="jdbc\:pointbase\:server\:\/\/local
host\/sample" :User=public:Password=public XA_connection_pool
Next JDBC resource has to be created using the following command.
asadmin create-jdbc-resource --user admin --password adminadmin --host fuyako --port 7070
--connectionpoolid XA_connection_pool --description
"creating a sample jdbc resource" sample_jdbc_resource
Please change the parameters as suitable to you.
The detailed description of these commands can be found as following URLs
http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1/create-connector-connection-pool.1.html
http://java.sun.com/j2ee/1.4/docs/relnotes/cliref/hman1/create-jdbc-resource.1.html -
I have the following configuration for a JDBC resource and i expected the connections to stay alive between web server restarts but i see from the oracle side that the sessions logon time keep changing every couple of hours. Should the logon time match the web server restart time at least for the minimum number of connections? Is there another parameter to make sure the connections stay alive and keep being reused instead of opening new ones?
<jdbc-resource>
<jndi-name>jdbc/pgmgrdb</jndi-name>
<datasource-class>oracle.jdbc.pool.OracleDataSource</datasource-class>
<max-connections>34</max-connections>
<isolation-level>serializable</isolation-level>
<property>
<name>password</name>
<value>passwrod</value>
<description/>
</property>
<property>
<name>user</name>
<value>username</value>
<description/>
</property>
<property>
<name>url</name>
<value>jdbc:oracle:thin:@xx.x.xx.xx:1521:DEV</value>
<description/>
</property>
<property>
<name>perf-monitor</name>
<value>true</value>
<description/>
</property>
<property>
<name>perf-monitor-interval</name>
<value>120</value>
<description/>
</property>
<description>PM Datasource</description>
</jdbc-resource>Thanks
JBRight, that part i understand but the part that i cannot get my head around is the logon time for these connections as seen from Oracle seems to change every 2-3 hours. It seems like the initial connections opened by the web server are closed and new sessions are created to replace them. I am not able to figure out why those connections are closed thereby defeating the purpose of a connection pooling.
It is not even that additional load is causing the connections to spike and then the pool is re-sized back to the initial level - the connection pool size stays steady but the new connections are established to replace the ones that are closed. The pool is being used by the code via spring. The reason we are looking into this because we noticed latency during getConnection and release connection and my theory is that there shouldn't be any latency because the pool has already established connection. We are using SJWS 7.0u5 / JDK 1.6_14 with Oracle 9i.
Thanks
JB -
WLST modified db uname/pwd verification for JDBC resource-No Restart Server
Hi,
I have created a WLST script for changing the db username and password for a particular jdbc resource.It is working fine.
But to verify whether the right username and password has been provided ,is there a way to test the db connection for the changed user name and password without restarting the server.
I also understand that there would be the cached connections of the previous user name and password for the jdbc resource.
Please let me know if I can do this using any API's in WLST or any other way.
Idea is to execute the change db user name and password and verification in one go.
Cheers,
MohanYou could try something like
servers = domainRuntimeService.getServerRuntimes();
# this return an array, for example array(weblogic.management.runtime.ServerRuntimeMBean,[[MBeanServerInvocationHandler]com.bea:Name=AdminServer,Location=AdminServer,Type=ServerRuntime])
# we obtain the server to which the datasource is targetted
admin = servers[0];
jdbcruntime = admin.getJDBCServiceRuntime();
datasources = jdbcruntime.getJDBCDataSourceRuntimeMBeans();
# this returns an array of the active datasources on the server, for example array(weblogic.management.runtime.JDBCDataSourceRuntimeMBean,
# [[MBeanServerInvocationHandler]com.bea:ServerRuntime=AdminServer,Name=ExampleDataSource,Location=AdminServer,Type=JDBCDataSourceRuntime])
datasource = datasources[0];
# Reset the connection pool in the data source by shutting down and recreating all available database connections in the pool.
datasource.reset();
# Test the connection pool in the data source by reserving and releasing a connection from it.
test = datasource.testPool();
# Print out information about all the connections in the connection pool in the data source, if there are any.
datasource.dumpPool(); -
JDBC Resource require a Application Server Reboot?
I am running Sun Application server and using netbeans to access a Postgresql database in a J2EE application.
When i change the values in a JDBC Resource Connection pool (ether via a deploy deploy from Netbeans or manually on the server), they don't seem to take effect until the server is restarted?
Is there a way to get these values used by the server wthout a reboot?
BryonHi Bryon,
Which version of App. Server are you using?
This behaviour was there until App Server v 7.
I tried setting (changing) the connection pool properties (max pool size, initial pool size, pool-resize quantity) with new version using GUI and able to see the refreshed values using asadmin "get" command.
Can you specify the properties that you are trying to change?
-Jagadish -
How to access JDBC Resource registered in Sun Java System App Server ?
I want to create a stand-alone JDBC application with Java SE using Swing technologies and JNDI technology. The purpose of using JNDI technology is to avoid change of Java Source Code every time I move the database to different location. This Java application will be used in a standalone PC installed with Windows XP Professional with no LAN / WAN connection. Of course, Internet connection is available with the PC.
I use JavaDB to store the data tables and the location of the database is D:\E-DRIVE\SAPDEV. Tomorrow, if I move this database to C:\SAPDEV or any network drive, I do not want to change the Java Source code. I want to use JNDI which, if I am not wrong, helps developers to avoid manual change of Java source code whenever the database location is changed. Changes have to be made only in the JNDI Name which contains all relevant information about the database in order to get connection no matter where the database SAPDEV is stored; it can be placed under D:\E-DRIVE directory or C:\ directory of the hard disk. To implement my intention, I started developing Java application as per the steps mentioned below:
Step 1:
To proceed, first, I sought the help of Sun Java System Application Server Admin Console. I created JNDI object for Connection Pool using the menu path Common Tasks->Resources->JDBC->Connection Pools.
JNDI Name : ABAPRPY
Resource Type : javax.sql.DataSource
Datasource class : org.apache.derby.jdbc.ClientDataSource
Description : ABAP Program Repository
The Connection Pool creation has options for General, Advanced and Additional Settings tabs and I made all the settings relevant to the database I created in D:\E-DRIVE\SAPDEV.
To confirm whether the above settings are correct, I pressed the Ping push button which is available in the General tab of the connection pool creation screen. The system responded with the message Ping Succeeded.
Step 2:
I created a JDBC Resource using the menu path Common Tasks->Resources->JDBC->JDBC Resources.
JNDI Name : jdbc/SAPDEV
Pool Name : ABAPRPY
Description : Database Connection for SAPDEV database
Status : Enabled
I can see all the above settings recorded in the domain.xml which is placed in the folder
C:\Sun\AppServer\domains\domain1\config
Step 3:
I have made sure that Sun Java System Application Server is up and running in the background with JavaDB server. I created a Java Program making sure the following JAR files are included in the classpath:
appserv-admin.jar
appserv-ee.jar
appserv-rt.jar
javaee.jar
fscontext.jar
Plus, the lib directory of JDK 1.6 & C:\Sun\AppServer\domains\domain1\config
Source code of the program is as follows: I used NetBeans IDE to create my project file.
import java.util.logging.Level;
import java.util.logging.Logger;
import javax.naming.*;
import javax.activation.DataSource;
public class JNDILookup {
public static void main(String[] args) {
try {
InitialContext initCtx = new InitialContext();
DataSource ds = (DataSource) initCtx.lookup("java:comp/env/jdbc/sapdev>");
} catch (NamingException ex) {
Logger.getLogger(JNDILookup.class.getName()).log(Level.SEVERE, null, ex);
When I attempted to compile the above program in NetBeans IDE ,no compilation error reported. But while executing the program, I got the following run-time error message:
SEVERE: null
javax.naming.NameNotFoundException: No object bound for java:comp/env/jdbc/sapdev> [Root exception is java.lang.NullPointerException]
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:224)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:396)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at SAPConnect.JNDILookup.main(JNDILookup.java:21)
Caused by: java.lang.NullPointerException
at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173)
... 3 more
Now, I want to come out of this situation; at the same time, I want to preserve the settings I have made in the Sun Java System Application Server Admin Console. That is, I want to programmatically access the data source using Connection Pool created in Sun Java System Application Server Admin Console.
I request dear forum members to provide me an appropriate solution.
Thanks and regards,
K. Rangarajan.jay44 wrote:
Bare in mind I am attempting the context.lookup() from inside the container (my code is in a session bean). I have accessed the server and have my bean "say hello" first to verify the bean works OK, then I call a method with this rather standard code:
String jndiDataSourceName ="Second_EJB_Module_DataBase";
Logger.getLogger(DynamicPU.class.getName()).log(Level.INFO,"Programatically acquiring JNDI DataDource: "+ jndiDataSourceName);
InitialContext ctx;
try {
ctx = new InitialContext();
ds =(DataSource)ctx.lookup("java:comp/env/jdbc/"+jndiDataSourceName);
} catch (NamingException ex) {
Logger.getLogger(DynamicPU.class.getName()).log(Level.SEVERE, null, ex);
return "Exception generated trying to preform JDBC DataSource lookup. \n"+ex.toString();
But when I run the code the server log shows the initial context is created Ok, but an exception is thrown becasue the resource name is not found:
(and i have tried vriations of ctx.lookup("jdbc/"+jndiDataSourceName) etc etc
You are fine here. It works in container because the InitialContext properties have been supplied already. That was the link I forwarded earlier. The InitialContext you create locally needs to locate the container JNDI. That is what the properties specify.
Where I am confused is where you indicate the stack below is from the server log. So, you initiate a standalone (java main method) application, create an InitialContext, and you see the results in your app server log?
LDR5010: All ejb(s) of [EJB_Module_1] loaded successfully!
Programatically acquiring JNDI DataDource: Second_EJB_Module_DataBase
The log message is null.
javax.naming.NameNotFoundException: Second_EJB_Module_DataBase not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:216)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:188)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:192)...
at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
This is strange since I can see this resource (a JDBC connection named Second_EJB_Module_DataBase) is configured on the server from the server's admin console.
That is why you can obtain a lookup from within the container (app server).
For this lookup to work it may be that one must map the name inside an ejb-jar.xml deployed with the application, but I have also read some resources like jdbc connection should have a default name. Does anyone know if my lookup() should work without using an ejb-jar.xml mfile to explcitly map the reource for my application?
Both EBJ's and data sources can be referenced via JNDI. It's a remote lookup (that is normally optimized if it is running in the same JVM). You should not have any dependencies on a JDBC data source being set-up on ejb-jar.xml. That file can of course impact your EJB's. However, data sources are normally set-up on a container-specific basis (e.g., you probably did it through a console, but there is a spec somewhere about how to set up a data source via a resource the app server looks for; it varies from app server to app server). However, once you have that container-specific data source set-up, JNDI operates vendor-neutral. You should be able to take the code above and move it to JBoss or Weblogic or Tomcat or whatever (this is an ideal, in practice, the vendors sometimes put a data source in a name you would not expect, but again, you can use their JMX console to see what the JNDI name is).
(As I stated above if I have to use a deployment discriptor to get at this JNDI datasource, then solution is not "programmatic" as newly configured datasources could not be accessed without redeploying the entire application).
As JSchell alluded to, you will always have at least something vendor-specific. JNDI itself (the code you wrote) is totally portable. However, you have to set the various JNDI environment properties to a given vendor's spec. Ideally, you should not need a vendor's actual InitialContext application, but it's a possibility. Once you can safely cast to Context, you should be vendor-neutral (if not, demand your money back).
So that is exactly where I am stuck, trying to get the lookup to work and wondering if it should work without and xml file mapping the resource for my app.
What we ended up doing for standalone was to provide our own JNDI. If you look at the open source project JOTM, there are examples on how to use that with XBean (if integrating with Spring, as we did), you can easily set up a data source that runs standalone exactly as you get in the container. Another benefit is you get full JTA/JTS support and the ability to run XA transactions. (This might all be alphabet soup, but the app server gives it to you, and this is the way we ended up doing the same: JNDI + JTA + JTS + XA). It ends up the same application code uses a "vanilla" InitialContext and all we have to do is write one or two xml files (one for our app server, a couple for JOTM), and our actual code works the same.
I still think you have a shot at getting to the container's JNDI, just not using their full-blown app server JAR.
I think there must be a simple way to do this with an ejb-jar.xml, I am no expert in JNDI, I could be missing something simple, I will keep at it and post an answer here if I come up with it.
Thanks, jayIt is simple to code. Getting it to integrate with your app server, yes, that can be challenging. But it has nothing to do with EJB's. Write a simple test. Using nothing but DataSource and InitialContext. Let us know where you get stuck.
- Saish -
How do I use a JDBC Resource set-up in Sun Java System Appliation Server?
How do I use a JDBC Resource set-up in Sun Java System Appliation Server 8.2?
I created a JDBC Resource labeled "jdbc/__PetroPool" that is backed by a Connection Pool labeled "PetroPool".
Since this is set-up in Sun Java System Appliation Server 8.2, I am looking for suggestions, examples or guides on how I can use this connection.
I've been browsing the developer's guide for Sun Java System Appliation Server 8.2 without much luck.
Googling really doesn't provide a lot of useful information either...
Any suggestions, examples or guides on how I can use this connection is greatly appreciated.
Thanks,
--ToddHow do I use a JDBC Resource set-up in Sun Java System Appliation Server 8.2?
I created a JDBC Resource labeled "jdbc/__PetroPool" that is backed by a Connection Pool labeled "PetroPool".
Since this is set-up in Sun Java System Appliation Server 8.2, I am looking for suggestions, examples or guides on how I can use this connection.
I've been browsing the developer's guide for Sun Java System Appliation Server 8.2 without much luck.
Googling really doesn't provide a lot of useful information either...
Any suggestions, examples or guides on how I can use this connection is greatly appreciated.
Thanks,
--Todd -
Cannot access to JDBC Resource from application client
Hello!
I have created a Connection Pool to my PostgreSQL database and a JDBC Resource via Admin Console in SJSAS 9.1_02. I can ping the connection pool ok.
I can get a Connection from a Stateless session Bean:
Context ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("jdbc/pgDS");
Connection c = ds.getConnection();
//working with c
c.close();It works fine.
But when I try to do the same from client application (created with netbeans template "Enterprise Application Client"), I get an exception on this line: Connection c = ds.getConnection();
The Exception:
28.10.2008 20:09:10 com.sun.gjc.common.DataSourceObjectBuilder getDataSourceObject
SEVERE: RAR5099 : Wrong class name or classpath for Datasource Object
java.lang.ClassNotFoundException: org.postgresql.ds.PGSimpleDataSource
at com.sun.enterprise.loader.EJBClassLoader.findClassData(EJBClassLoader.java:741)
at com.sun.enterprise.loader.EJBClassLoader.findClass(EJBClassLoader.java:631)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at com.sun.gjc.common.DataSourceObjectBuilder.getDataSourceObject(DataSourceObjectBuilder.java:251)
at com.sun.gjc.common.DataSourceObjectBuilder.constructDataSourceObject(DataSourceObjectBuilder.java:106)
at com.sun.gjc.spi.ManagedConnectionFactory.getDataSource(ManagedConnectionFactory.java:970)
at com.sun.gjc.spi.DSManagedConnectionFactory.getDataSource(DSManagedConnectionFactory.java:139)
at com.sun.gjc.spi.DSManagedConnectionFactory.createManagedConnection(DSManagedConnectionFactory.java:93)
at com.sun.enterprise.resource.LocalTxConnectorAllocator.createResource(LocalTxConnectorAllocator.java:68)
at com.sun.enterprise.resource.AbstractResourcePool.createSingleResource(AbstractResourcePool.java:891)
at com.sun.enterprise.resource.AbstractResourcePool.createResourceAndAddToPool(AbstractResourcePool.java:1752)
at com.sun.enterprise.resource.AbstractResourcePool.createResources(AbstractResourcePool.java:917)
at com.sun.enterprise.resource.AbstractResourcePool.initPool(AbstractResourcePool.java:225)
at com.sun.enterprise.resource.AbstractResourcePool.internalGetResource(AbstractResourcePool.java:516)
at com.sun.enterprise.resource.AbstractResourcePool.getResource(AbstractResourcePool.java:443)
at com.sun.enterprise.resource.PoolManagerImpl.getResourceFromPool(PoolManagerImpl.java:248)
at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:176)
at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:327)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:189)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:165)
at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:158)
at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:108)
at converter.Main.doConversion(Main.java:56)
at converter.Main.main(Main.java:29)
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:266)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:449)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:259)
at com.sun.enterprise.appclient.Main.main(Main.java:200)
28.10.2008 20:09:10 com.sun.enterprise.resource.LocalTxConnectorAllocator createResource
WARNING: RAR5038:Unexpected exception while creating resource for pool vlkvPostgresPool. Exception : Class name is wrong or classpath is not set for : org.postgresql.ds.PGSimpleDataSource
28.10.2008 20:09:10 com.sun.enterprise.connectors.ConnectionManagerImpl internalGetConnection
WARNING: RAR5117 : Failed to obtain/create connection from connection pool [ vlkvPostgresPool ]. Reason : Class name is wrong or classpath is not set for : org.postgresql.ds.PGSimpleDataSource
28.10.2008 20:09:10 com.sun.gjc.spi.base.DataSource getConnection
WARNING: RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : org.postgresql.ds.PGSimpleDataSource]
Caught an unexpected exception!
java.sql.SQLException: Error in allocating a connection. Cause: Class name is wrong or classpath is not set for : org.postgresql.ds.PGSimpleDataSource
at com.sun.gjc.spi.base.DataSource.getConnection(DataSource.java:115)
at converter.Main.doConversion(Main.java:56)
at converter.Main.main(Main.java:29)
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:597)
at com.sun.enterprise.util.Utility.invokeApplicationMain(Utility.java:266)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:449)
at com.sun.enterprise.appclient.MainWithModuleSupport.<init>(MainWithModuleSupport.java:259)
at com.sun.enterprise.appclient.Main.main(Main.java:200)
Please help me, I'm trying to solve it all day long...the issue is right in the exception trace. obviously, your client code does not have the "org.postgresql.ds.PGSimpleDataSource" class in its classpath.
note, generally DataSources are not something you would access from a remote client.
Edited by: jtahlborn on Oct 28, 2008 4:18 PM -
Hi there,
I am using S1 AS7....
1. Can i define a JDBC Resource at the Application level (so that all the beans have access to the Resouce) rather than defining the <resource-ref > tag to all the beans that uses the JDBC Resource.
How can i do this in S1AS7.0.
2. In S1AS7.0, can i lookup the JDBC Resource from any business classes which has no corresponding JDBC resource mapping.
Any idea,
Thanks & Regards,
Dinesh.Probably a plugin class loading problem ... if you google for some
combination of eclipse plugin hibernate, you should see many messages on
the subject.
Later,
PW
P.S. I always prefix my googles with "site:dev.eclipse.org news.eclipse"
to help narrow them down. -
SAP J2EE Engine JTA Transaction Xml for table TABLE could not be ana
I'm having a weird case. I created 3 entity bean. In my R/3 will call this JCO.Function to do the insert to database. But out of 3 entity bean, only 1 entity bean got error where it unable to insert to database and have this error in the log.
The case is quite weird where i created the same entity but only 1 entity is not working as expected. Wondering what cause this problem.
Thanks.
org.xml.sax.SAXException: Fatal Error: URI=:main: Line=1: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Name expected: 0x20(:main:, row:1, col:218)#
at com.sap.dictionary.database.dbs.XmlExtractor$XMLErrorHandler.fatalError(XmlExtractor.java:279)#
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)#
at com.sap.dictionary.database.dbs.XmlExtractor.map(XmlExtractor.java:130)#
at com.sap.dictionary.database.catalog.DbGeneralStructure.<init>(DbGeneralStructure.java:86)#
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:90)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)#
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)#
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)#
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)#
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)#
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)#
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)#
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)#
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)#
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)#
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)#
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)#
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)#
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)#
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)#
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)#
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)#
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)#
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:324)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)#
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)#
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)#
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#
at java.security.AccessController.doPrivileged(Native Method)#
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)#
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)#
##0#0#Error##Java###{0}.commit(), Cannot commit due to unexpected exception in beforeCompletion():
[EXCEPTION]
{1}#2#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5 #001A6467CDF400590000004E000018D8000459BB785F496C#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Server#Java#ts_0004##Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).#1#SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b]#
#1.5 #001A6467CDF400590000004F000018D8000459BB785F4BC5#1224561620123#com.sap.engine.services.ts#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ts#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error#1#/System/Audit#Java###Exception {0}#1#com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000050000018D8000459BB785F4E8F#1224561620123#com.sap.engine.services.ejb.entity.Container#sap.com/ESolutionsEGatewayEAR#com.sap.engine.services.ejb.entity.Container#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Java###null
[EXCEPTION]
{0}#1#com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
#1.5 #001A6467CDF4005900000051000018D8000459BB785F5FA9#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###RemoteException insertOk=false#
#1.5 #001A6467CDF4005900000052000018D8000459BB785F6094#1224561620123#System.err#sap.com/ESolutionsEGatewayEAR#System.err#J2EE_GUEST#0####95b74d409f2411dd86c4001a6467cdf4#SAPEngine_Application_Thread[impl:3]_20##0#0#Error##Plain###Tue Oct 21 12:00:20 SGT 2008 java.rmi.RemoteException: com.sap.engine.services.ejb.exceptions.BaseRemoteException: Transaction system failure in method net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(net.tnb.model.ReasonCodeBean).
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:573)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
... 15 more
Caused by: java.lang.IllegalStateException: Xml for table <TABLE> could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 more
; nested exception is:
javax.transaction.RollbackException: com.sap.engine.services.ts.exceptions.BaseRollbackException: Exception in beforeCompletition of ( SAP J2EE Engine JTA Transaction : [031fffffff3ffffffb2005b] ).
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:236)
at net.tnb.model.ReasonCodeEntityHomeImpl3_0.create(ReasonCodeEntityHomeImpl3_0.java:546)
at net.tnb.model.ReasonCodeEntityHome_Stub.create(ReasonCodeEntityHome_Stub.java:57)
at net.tnb.model.EToGatewayBean.insertIntoTable(EToGatewayBean.java:223)
at net.tnb.model.EToGatewayBean.processFunction(EToGatewayBean.java:166)
at net.tnb.model.EToGatewayLocalLocalObjectImpl3_0.processFunction(EToGatewayLocalLocalObjectImpl3_0.java:175)
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:324)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277)
at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219)
at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.IllegalStateException: Xml for table ZREASON_CODE could not be analysed
at com.sap.dictionary.database.catalog.XmlCatalogReader.getTable(XmlCatalogReader.java:100)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:124)
at com.sap.sql.catalog.impl.BufferedCatalogReader.getTable(BufferedCatalogReader.java:87)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.checkTables(CheckColAndTabVisitor.java:299)
at com.sap.sql.sqlparser.CheckColAndTabVisitor.performCatalogChecks(CheckColAndTabVisitor.java:176)
at com.sap.sql.sqlparser.CommonSQLStatement.checkSemantics(CommonSQLStatement.java:169)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.check(StatementAnalyzerImpl.java:35)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:101)
at com.sap.sql.jdbc.common.StatementAnalyzerImpl.preprepareStatement(StatementAnalyzerImpl.java:87)
at com.sap.sql.jdbc.common.AbstractCommonStatement.parseStatement(AbstractCommonStatement.java:472)
at com.sap.sql.jdbc.common.CommonConnectionImpl.prepareStatement(CommonConnectionImpl.java:375)
at com.sap.engine.services.dbpool.cci.ConnectionHandle.prepareStatement(ConnectionHandle.java:81)
at net.tnb.model.ReasonCodeEntityBean3_0Persistent.ejb_iInsert(ReasonCodeEntityBean3_0Persistent.java:306)
at com.sap.engine.services.ejb.entity.pm.UpdatablePersistent.ejbFlush(UpdatablePersistent.java:92)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flushAll(TransactionContext.java:429)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.flush(TransactionContext.java:378)
at com.sap.engine.services.ejb.entity.pm.TransactionContext.beforeCompletion(TransactionContext.java:506)
at com.sap.engine.services.ejb.entity.SynchronizationList.beforeCompletion(SynchronizationList.java:136)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:226)
... 16 moreHi Stefan and Everyone,
I have solved my problem. Just want to let everyone know if u have to install the SP's for WEB AS 6.30/6.40.
You start from the installation from CD 6.30/6.40. Everything will be working at this point. You can login to Visual Admin, Config tool and SDM.
Before you apply any SP's, do the following:
a) Create an emergency user with the Administrator rights: Ref OSS Note:669848
Try to follow this route for SP's:
From CD 6.30/6.40 -> SP04 -> SP07
Apply SP04 first before applying SP07 (Recommended Approach).
Refer the installation guide: SAP Web AS Support Package Guide 630SP2 to 640SP4.
Use JDK1.4.2_05 to install SP04. You must reference the following OSS Notes and apply to your system accordingly, this is the key to an error free installation:
a) OSS Note: 697535
b) OSS Note: 709140
c) OSS Note: 716604
d) OSS Note: 706378
You have to be really careful with SP04 installation, because it changes the version from 6.30 -> 6.40.
Once you are able to install SP04 without any problems, you can directly apply SP07 or the highest 6.40 SP.
Kind Regards,
Buddha. -
Performing resource transaction at the work order completion in Oracle
Hello Guru's
Is there any way to have Oracle 11g to perform the resource transaction at the work order completion? Currently a resource transaction is performed when work order is scanned in a scan point. What we want to see is resources transactions at the end of life of work orders most likely a wip assy completion transaction. We are seeing that this happens only for bill of material with just one level. We would like see this behavior on BOMs set up using phatom as supply type for the subassemblies (with more than 1 level structure).
Regards,I am using SAP ECC 6.0.
SAP Basis Component and Cross-Application Component: release 700, level 013
Is there any other information you need?
Could I still use this OSS note with this version?
Also, the issue is not about the response time like mentioned in the OSS note. -
Error when releasing the WS using the transaction WSCONFIG
Hello Colleagues,
Following error message is recieved when i try to release the webservice using the transaction WSCONFIG.
Error when creating Web service (Method call of IF_SRT_REGISTRY_ENTRY~CREATE_NEW failed; the class does not exist)
Can you please let me know if anyone of you have faced the similar error and have been successful in solving.
Thanks & Best regards,
AjayHi Ajay,
Check if the thread below resolves your issue:
[Re: web service - How activate host ?;
Regards, Trevor -
Orders stuck in "Released to Warehouse" in Shipping transaction screen
Hi,
we used the RO to transfer inventory between different org, 1 order was stucked in shipping transaction screen:
Line status: Released to warehouse
Next step: Transact Move Order
But I can see move order number in shipping transaction screen, the item also reserved, the order line showing allocate.
In Transact Move Order, I can not find any record.
In pending transaction screen, I can find those records, but no error message, can not submit there.
Can anyone please advice what is the next step i need to do to process to the Pick Released status.
Thanks,If your shipping delivery details are at 'Released to Warehouse' then the pick release has already taken place. Depending on your setups, you may also find that you have generated pick slips for these orders.
If it's correct that those 300 orders should have been released, then you need to take the following steps to pick confirm. You don't mention if you are using mobile apps so we'll assume you're using the forms in which case you'd go to the Transact Move Orders form in Inventory and using either the pick slip or the move order (printed on the pick slip and visible in the Shipping Txns Form) or the order number (Pick Wave tab), query back the pick release suggestions/allocations and either confirm or amend as appropriate. If you're using lot or serial control then you will need to supply this information also. This will change the status for the confirmed lines to 'Staged/Pick Confirmed' in the STF.
If you didn't intend to release some or all of those orders then you will still need to query back the move orders in the Transact Move Orders form but you should then either backorder or cancel the allocation for each line as appropriate (Tools menu).
If you expected your lines to be automatically pick confirmed on release, then your problem lies in not having used a pick release rule with Auto Pick Confirm = Yes.
Regards,
Jon
Maybe you are looking for
-
Just bought an ipad mini I have synced it with my itunes but when I go to play my music it just flashes threw all the songs or albums or artists like it is on super fast shuffle until it finds a song it would like to play. need help please
-
I have yet to be able to update to 5.1.1. It will not down load to my iTunes either. My iPad comes back with an undesignated error, saying it cannot update.
-
Why do we allocate space for a new object???
When we create a new object, we instantiate it. Why do we do this. I read that we are allocating space for it. What is allocating space and why is it necessary??
-
Images added to my layout surrounded by gray box!
Hi, I'm very new to all this but I have what seems to be a simple question! When I try to add a graphic to my layout it's surrounded by a gray box...I downloaded the graphic from a scrapbooking website, but on the website when it shows the tutorials
-
I have a question. I accidenlty formatted al my files on my camera and I need them. Can I bring them into a best buy and have them repair it for me and get the lost files back. How much would it cost too to get it fixed also I dont c this as impossib