Network error handling in Java
Hi All,
I want to get notification when other end is not reachable due to removal of LAN cable or so. I am not getting any notification in Java. I have also enabled KeepAlive but still no notification. I get notification when app gets killed but not when its unreachable.How can I get any notification as soon as other end is unreachable ?
Thanks in advance
I want to get notification when other end is not reachable due to removal of LAN cable or so.You can't. The best you can get is a SocketTimeoutException when reading after you set a read timeout, or an IOException when writing.
I have also enabled KeepAlive but still no notification.Did you wait two hours? That's how long it takes.
Similar Messages
-
Bursting with JAVA APIs / MultiThreading / Errors Handling
We are trying to use the bursting JAVA APIs 10.1.3.3.1 Standalone) to burst huge XML files and generate PDF Files from RTF templates. Here are a list of our issues with this feature:
1. We have some problems catching the errors when bursting. We have tried to use the "oracle.apps.xdo.common.log.Logger" class, but it is not always reacting like we think it should. Could you please give us an exemple of a clean bursting error catching or a brief description of how we could do it. We have a lot of difficulties to find information about using the JAVA APIs of BIP.
2. Is it a clean way of catching the bursting errors to use the "oracle.apps.xdo.common.log.Logger" class?
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?1. Check tim d. blog, you can use the bursting listners to get the errors. It's also in the documentation.
First, on every exception, the Bursting APIs are dumping the error in the Logger. So I can't see how we can use the listeners to catch these. We can check the hasExceptions on the Logger but still, we have some problems with this. When we deploy our application as a MDB (Message driven bean), it seems that once the hasException flag has been raised, if we call the MDB again, it is still up. Is there documentation about that Logger class? Also, I'm worried that we won't be able to call our MDB twice to run simultaneously 2 different bursting process since it seems the Logger is something static, keeping every exception in memory... That's bad.. And show me where you have found documentation about this. All I see in documentation is how to call the DocumentProcessor in a couple of lines. I don't see anything about a clean way to catch errors.
2. Yes/No/Depends. I think it's fine. If your changing the logger options in your program that could come back to haunt you.
I guess so, I'm not changing anything and its already haunting me...
3. When using the 10.1.3.3.1 DocumentProcessor JAVA API, the process gets killed when the RTF template is not where the control file specified it. Even when using a finally clause containing the document processor, we can't fetch the error from the "oracle.apps.xdo.common.log.Logger" class. We did not find a way to catch this error which make our program crash.
Even worst, when we deploy the component has an MDB, when the error happens, it kills the whole oc4j container... please correct this quick.
4. How can we enable multi-threading that is included in the DocumentProcessor JAVA APIs so it can take advantage of the multi-processors environnements?
We got an answer from the dev team which is to add two properties to the document processor, something like:
enable-multithreading: true
thread-count: >2
We did that and what we got is that the process started and it got stuck in a dead lock at the first document processing. How nice! :)
We got a milestone in March and I'm really worried about all those problems... Not enough documentation, a pretty bad error handling, errors making crash the whole oc4j container, Logger seems not to be handling simultaneous calls/ threads, not even handling two subsequent calls... etc.
If anyone has the magic answer, it would be pretty welcomed!
Thanks -
Error handle request; Root exception is: java.lang.NoSuchMethodError
Hello Guys,
I am running EBS 11i, rdbms 10g on OEL4. After applying a bunch of patches to resolve some IE issues I ran into an error:
"FRM-41072: Cannot create group ACTION_REC_GROUP" when trying to cancel a PO.
An SR directed me to apply patch 8286920 which indeed fixed the FRM-41072 error. After this patch "Logon to Oracle Applications Manager" is not possible as the page gives me :
Error handle request; Root exception is: java.lang.NoSuchMethodError: oracle.apps.fnd.security.AolSecurity.userPwdHash(Ljava/lang/String;)Ljava/lang/String;
MOS thinks that patch 8286920 didn't break OAM but I don't think so since this is only happening on my DEV and TEST systems on which I have applied the patch. PROD, wihtout the patch, is accessible through OAM just as usual?
Any thouths?
Thank you
MathiasDid you apply all patches mentioned in the following docs?
FRM-41072 - Unable to Cancel Purchase Order or Purchase Order Line or Release [ID 947402.1]
Change Tax Code in the Purchase Order Gets Error - Could not reserve record (2 tries) Keep trying [ID 956047.1]
Autocreate Process Does Not Default Purchase Order Form As The Active Window After PO Is Created - Does Not Come To The Front [ID 1055623.1]
Did you bounce all the services and see if you ca reproduce the issue?
What about clearing the server cache files? -- How To Clear Caches (Apache/iAS, Cabo, Modplsql, Browser, Jinitiator, Java, Portal, WebADI) for E-Business Suite? [ID 742107.1]
Can you find any errors in the database/apache log files? Any invalid objects?
If you have verified all the above please update the SR with the error you have after applying that patch.
Thanks,
Hussein -
Java.sql.SQLException: Network error IOException: Connection refused:
hi...i am tryin to connect to sqlserver2000 ....i wanted a dsnless connection...i have downloaded jtds driver...set the classpath..no joy..i'm connecting to sqlserver's default port 1433..i also confirmed that sqlserver tcp is enabled...still gettin the same err:
java.sql.SQLException: Network error IOException: Connection refused: connect
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java
:385)
at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java
:50)
at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:182)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at SQLServerConnect.getConnection(SQLServerConnect.java:27)
at SQLServerConnect.displayDbProperties(SQLServerConnect.java:44)
at SQLServerConnect.main(SQLServerConnect.java:80)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:364)
at java.net.Socket.connect(Socket.java:507)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at net.sourceforge.jtds.jdbc.SharedSocket.createSocketForJDBC3(SharedSoc
ket.java:304)
at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:255)
at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java
:310)
... 7 more
Error Trace in getConnection() : Network error IOException: Connection refused:
connect
Error: No active Connection
i even tried connecting to the port 1433 thru telnet...err:Could not open connection to the host, on port 1433:connection failed...
i thought it cud b a firewall issue...disabled my windows firewall..no joy..
can ne body help me with this....need to solve this desparately
thanks in advance
judeOld, but still coming up in google searches. Here's the solution that worked for me:
Dynamic Port Allocation explained:
http://support.microsoft.com/kb/823938
How to: Configure a Server to Listen on a Specific TCP Port (SQL Server Configuration Manager)
http://support.microsoft.com/kb/823938
In case that dissappears:
To assign a TCP/IP port number to the SQL Server Database Engine
1. In SQL Server Configuration Manager, in the console pane, expand SQL Server 2005 Network Configuration, expand Protocols for <instance name>, and then double-click TCP/IP.
2. In the TCP/IP Properties dialog box, on the IP Addresses tab, several IP addresses appear, in the format IP1, IP2, up to IPAll. One of these are for the IP address of the loopback adapter, 127.0.0.1. Additional IP addresses appear for each IP Address on the computer. Right-click each address, and then click Properties to identify the IP address that you wish to configure.
3. If the TCP Dynamic Ports dialog box contains 0, indicating the Database Engine is listening on dynamic ports, delete the 0.
4. In the IPn Properties area box, in the TCP Port box, type the port number you wish this IP address to listen on, and then click OK.
5. In the console pane, click SQL Server 2005 Services.
6. In the details pane, right-click SQL Server (<instance name>) and then click restart, to stop and restart SQL Server. -
Error handling notification type=Platform,Domain=java.lang,subType=GC
I'm seeing this error over and over. Odd that 17 and 18 are not listed as members.
-Andrew
MemberId|ServiceVersion|ServiceJoined|MemberState
2|3.7.1|2012-03-28 08:59:53.744|JOINED,
4|3.7.1|2012-03-28 04:42:03.799|JOINED,
6|3.7.1|2012-03-28 05:22:21.955|JOINED,
7|3.7.1|2012-03-28 05:55:56.571|JOINED,
8|3.7.1|2012-03-28 05:55:56.584|JOINED,
9|3.7.1|2012-03-28 06:42:46.461|JOINED,
10|3.7.1|2012-03-28 06:00:00.698|JOINED,
11|3.7.1|2012-03-28 08:20:01.535|JOINED,
12|3.7.1|2012-03-28 08:20:02.32|JOINED,
13|3.7.1|2012-03-28 08:21:12.046|JOINED,
14|3.7.1|2012-03-21 09:10:59.991|JOINED,
16|3.7.1|2012-03-21 09:11:03.034|JOINED,
20|3.7.1|2012-03-21 09:10:59.236|JOINED,
22|3.7.1|2012-03-21 09:11:00.273|JOINED,
23|3.7.1|2012-03-21 09:11:02.329|JOINED
RecycleMillis=1200000
RecycleSet=MemberSet(Size=0
TcpRing{Connections=[23]}
IpMonitor{AddressListSize=1}
2012-03-28 09:00:04.395/11.378 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Service Managemen
t joined the cluster with senior service member 14
2012-03-28 09:00:04.659/11.642 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
2012-03-28 09:00:04.677/11.660 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
2012-03-28 09:00:04.693/11.676 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18
2012-03-28 09:00:04.706/11.689 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=17
Map (?):
2012-03-28 09:00:04.875/11.858 Oracle Coherence GE 3.7.1.1 <D5> (thread=Invocation:Management, member=2): Error handling no
tification type=Platform,Domain=java.lang,subType=GarbageCollector,name=ParNew,nodeId=18No ideas on a cause or solution for this? I only saw it once and I don't know how to reproduce it.
-Andrew -
Database Constraint Error Handling on create/edit (Struts ADF)
Hi,
In our project we use Struts ADF (JDeveloper 10.1.3) technology. And we're facing the following trouble with it.
If we try to create a record that violates say Unique constraint in the database, then during commit procedure of the AppModule's Transaction an exception occurs.
We handle this exception with our extension of DCErrorHandlerImpl. And we have to do the rollback action because the Transaction became invalid and we cannot do the commit since there was an error.
But unfortunately appModule.getTransaction().rollback(); forces ViewObj to loose all of the newly created rows. Because of this, after pressing submit with the same (violating) data once more our edit form shows the first row in a rowset.
Are there any ideas about what we may be doing wrong?
Any standard approaches on database constraint error handling?
The "before/after commit/rollback" approach is very effort-consuming because we have a lot of views in our app and tracking all of them may become a nightmare in future.
Thanks in advance.
Regards,
LarryHi Steve!
I'm using Postgree.
Here is StackTrace
06/06/27 09:52:24 Commit
oracle.jbo.DMLException: JBO-26041: Failed to post data to database during "Insert": SQL Statement "INSERT INTO public.test_tb(id,name,org_code) VALUES (?,?,?)".
at oracle.jbo.server.BaseSQLBuilderImpl.doEntityDML(BaseSQLBuilderImpl.java:481)
at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:5731)
at com.yukon.adf.postgre.entities.PostgreEntityImpl.doDML(PostgreEntityImpl.java:22)
at com.yukon.adf.postgre.entities.PostgreSequenceEntityImpl.doDML(PostgreSequenceEntityImpl.java:58)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:4531)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:2993)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2804)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1968)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2170)
at view.actions.ListTestPageController.onCommit(ListTestPageController.java:32)
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)
at oracle.adf.controller.v2.lifecycle.PageController.invokeEventMethod(PageController.java:110)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.handleEvent(PageLifecycleImpl.java:950)
at oracle.adf.controller.v2.struts.lifecycle.StrutsPageLifecycle.handleEvent(StrutsPageLifecycle.java:238)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.processComponentEvents(PageLifecycleImpl.java:322)
at oracle.adf.controller.v2.lifecycle.PageController.processComponentEvents(PageController.java:54)
at oracle.adf.controller.v2.lifecycle.Lifecycle$3.execute(Lifecycle.java:275)
at oracle.adf.controller.v2.lifecycle.Lifecycle.executePhase(Lifecycle.java:116)
at oracle.adf.controller.v2.lifecycle.LifecycleProcessor.execute(LifecycleProcessor.java:100)
at oracle.adf.controller.v2.struts.actions.DataAction.execute(DataAction.java:123)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1485)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:527)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:332)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
## Detail 0 ##
java.sql.SQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:330)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:282)
at oracle.jbo.server.BaseSQLBuilderImpl.doEntityDML(BaseSQLBuilderImpl.java:352)
at oracle.jbo.server.EntityImpl.doDML(EntityImpl.java:5731)
at com.yukon.adf.postgre.entities.PostgreEntityImpl.doDML(PostgreEntityImpl.java:22)
at com.yukon.adf.postgre.entities.PostgreSequenceEntityImpl.doDML(PostgreSequenceEntityImpl.java:58)
at oracle.jbo.server.EntityImpl.postChanges(EntityImpl.java:4531)
at oracle.jbo.server.DBTransactionImpl.doPostTransactionListeners(DBTransactionImpl.java:2993)
at oracle.jbo.server.DBTransactionImpl.postChanges(DBTransactionImpl.java:2804)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:1968)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2170)
at view.actions.ListTestPageController.onCommit(ListTestPageController.java:32)
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)
at oracle.adf.controller.v2.lifecycle.PageController.invokeEventMethod(PageController.java:110)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.handleEvent(PageLifecycleImpl.java:950)
at oracle.adf.controller.v2.struts.lifecycle.StrutsPageLifecycle.handleEvent(StrutsPageLifecycle.java:238)
at oracle.adf.controller.v2.lifecycle.PageLifecycleImpl.processComponentEvents(PageLifecycleImpl.java:322)
at oracle.adf.controller.v2.lifecycle.PageController.processComponentEvents(PageController.java:54)
at oracle.adf.controller.v2.lifecycle.Lifecycle$3.execute(Lifecycle.java:275)
at oracle.adf.controller.v2.lifecycle.Lifecycle.executePhase(Lifecycle.java:116)
at oracle.adf.controller.v2.lifecycle.LifecycleProcessor.execute(LifecycleProcessor.java:100)
at oracle.adf.controller.v2.struts.actions.DataAction.execute(DataAction.java:123)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1485)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:527)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:332)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:629)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:376)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:870)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:218)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:119)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:112)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595) -
Error in deployment:java.lang.NullPointerException:sdu name can not be null
HI Everyone!
I try to deploy my web dynpro project to SAP J2EE engine. Configuration about SAP J2EE Engine is OK, but there is an error during the deployment. Here is the deployment trace:
2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] INFO: deployment trace
14:56:24.207 [info #300] [#4]: Trying to connect to 'secude-vmcn0001:50004' as 'administrator'
14:56:24.207 [debug #100] [#4]: Session::getContext.[ B E G I N ].timerId=16
14:56:25.161 [debug #100] [#4]: Session::getContext.[ E N D ].timerId=[id:#16, elapsed: 954 ms.]
14:56:25.161 [info #300] [#4]: Connected to 'secude-vmcn0001:50004' as 'administrator'
14:56:25.161 [debug #100] [#4]: DeployProcessor::ctor:New deploy processor created.deployerId=4
14:56:25.161 [info #300] [#4]: +++++ Starting D E P L O Y action +++++
14:56:25.161 [info #300] [#4]: Selected archives for deployment
14:56:25.161 [info #300] [#4]: D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear
14:56:25.536 [debug #100] [#4]: DeployProcessor::deploy:going to generate Session id, deployerId=4
14:56:25.755 [debug #100] [#4]: DeployProcessor::deploy:got Session id='14',time:[id:#17, elapsed: 594 ms.], deployerId=4
14:56:25.974 [info #300] [#4]: Upload archives to the server.Remote upload path is 'C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14'
14:56:25.974 [debug #300] [#4]: DeployProcessor::uploadItemsToServer:Going to upload 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' on the server.deployerId=4
14:56:26.427 [info #300] [#4]: File 'D:\NetWeaverWorkspace\Workspace\Dashboard\Dashboard.ear' uploaded successfully as 'C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear'. Time:[id:#18, elapsed: 453 ms.]
14:56:26.427 [info #300] [#4]: Archives uploaded.time:[#18: 0.453 sec]
14:56:26.427 [debug #100] [#4]: DeployProcessor::deployItems:enter.timerId=19, deployerId=4
14:56:26.427 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:get deployer from server, deployerId=4
14:56:26.427 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer get successfully:[id:#20, elapsed: 0 ms.], deployerId=4
14:56:26.630 [info #300] [#4]: component version handling rule is UpdateAllVersions
14:56:26.849 [info #300] [#4]: Error strategies:
14:56:26.849 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:deployer initialized sucessfully:[id:#20, elapsed: 422 ms.], deployerId=4
14:56:26.849 [debug #100] [#4]: DeployProcessor::internalCreateAndInitDeployer:total time:[#20: 0.422 sec], deployerId=4
14:56:26.849 [info #300] [#4]: Starting deployment
14:56:27.177 [debug #100] [#4]: DeployProcessor::internalMapSdus:sduMapperVisitor.setCompositeDeploymentItem(null),remoteSdu=name: 'null', vendor: 'null', location: 'LOKAL', version: '0.2007.06.28.14.28.59', software type: 'J2EE', dependencies: '[]'
14:56:27.177 [debug #300] [#4]: DeployProcessor::deployItems:finally.Total Time:[#19: 0.75 sec], deployerId=4
14:56:27.177 [info #300] [#4]: +++++ End D E P L O Y action +++++
And here is the exception detail:
2007-6-28 14:56:27 /userOut/daView_category (com.sap.ide.eclipse.deployer.DVBaseLog) [Thread[Deploy Thread,6,main]] ERROR: java.lang.NullPointerException: sdu name can not be null.
at com.sap.engine.services.dc.api.model.impl.SduImpl.<init>(SduImpl.java:39)
at com.sap.engine.services.dc.api.model.impl.SdaImpl.<init>(SdaImpl.java:51)
at com.sap.engine.services.dc.api.model.impl.ModelFactoryImpl.createSda(ModelFactoryImpl.java:43)
at com.sap.engine.services.dc.api.model.SduMapperVisitor.createSda(SduMapperVisitor.java:52)
at com.sap.engine.services.dc.api.model.SduMapperVisitor.visit(SduMapperVisitor.java:64)
at com.sap.engine.services.dc.repo.impl.SdaImpl.accept(SdaImpl.java:136)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.internalMapSdus(DeployProcessorImpl.java:704)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:487)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:155)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:185)
at com.sap.ide.eclipse.sdm.threading.DCDeployThread.run(DCDeployThread.java:115)
It seems that there is something wrong about 'SDU', but i don't know what is it, and i can not find the answer both in sdn.sap.com and here.
Anyone can help me on this?
Thanks in Advance,
MKHi Sumit,
Thank you for your concern.
Below is a trace file on my server:
C:\SAP\JP1\JC00\j2ee\cluster\server0\log\defaultTrace.0.trc
#1.5 #000C296B3F6A000D0000000200000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The session id 14 is associated with correlator id 67431500000169001. Use this correlator id to filter the trace and log messages.#
#1.5 #000C296B3F6A000D0000000300000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###++++++++++++++ Starting deployment ++++++++++++++#
#1.5 #000C296B3F6A000D0000000400000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives specified for deployment are: #
#1.5 #000C296B3F6A000D0000000500000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###C:/SAP/JP1/JC00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/14/Dashboard.ear#
#1.5 #000C296B3F6A000D0000000600000A3000EF90978C2E8C29#1183013784131#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Start loading archives ...#
#1.5 #000C296B3F6A000D0000000700000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Archives are loaded.#
#1.5 #000C296B3F6A000D0000000800000A3000EF90978C2E8C29#1183013784147#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Error Handling Action: 'UndeploymentAction', Error Handling Strategy: 'OnErrorStop'.
Error Handling Action: 'DeploymentAction', Error Handling Strategy: 'OnErrorStop'.
Error Handling Action: 'PrerequisitesCheckAction', Error Handling Strategy: 'OnErrorStop'.
Version Handling Rule: 'UpdateAllVersions'.
Deployment Strategy: 'normal deploy strategy'.
Life Cycle Deployment Strategy: 'bulk deploy strategy'.
There are no batch filters specified.#
#1.5 #000C296B3F6A000D0000000900000A3000EF90978C2E8C29#1183013784194#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###The batch for session id 14 will be executed with normal parallelism strategy.#
#1.5 #000C296B3F6A000D0000000A00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name sap.com/tcwddispwda doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000B00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicruntime doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000C00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.rb doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000D00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.xml doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000E00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.proxy.framework doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000000F00000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tc~cmi doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001000000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:com.sap.aii.util.misc doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001100000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcddicddicservices doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001200000A3000EF90978C2E8C29#1183013784272#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###A component loader with name library:tcgraphicsigs doesn't exist, because is stopped or not deployed.#
#1.5 #000C296B3F6A000D0000001300000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Warning#1#com.sap.engine.services.deploy#Plain###JLinEE validation of application local/Dashboard returned result
WARNINGS:
References Test: Count of deploy time references (described in META-INF/SAP_MANIFEST.MF) and runtime references (described in META-INF/application-j2ee-engine.xml) does not match., file: Dashboard.ear, column 0, line 0, severity: warning
References Test: There are no matching deploy time references (described in META-INF/SAP_MANIFEST.MF) for the following runtime references [sap.com/tcwddispwda, sap.com/com.sap.mw.jco, sap.com/tcddicddicruntime, sap.com/com.sap.aii.util.rb, sap.com/com.sap.aii.util.xml, sap.com/webservices_lib, sap.com/com.sap.aii.proxy.framework, sap.com/sapxmltoolkit, sap.com/tccmi, sap.com/com.sap.security.api.sda, sap.com/com.sap.util.monitor.jarm, sap.com/com.sap.aii.util.misc, sap.com/tcddicddicservices, sap.com/com.sap.lcr.api.cimclient, sap.com/tcgraphics~igs, sap.com/sld] (described in the META-INF/application-j2ee-engine.xml)., file: Dashboard.ear, column 0, line 0, severity: warning
#1.5 #000C296B3F6A000D0000001400000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000001700000A3000EF90978C2E8C29#1183013784366#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception in operation deploy with application local/Dashboard.###
#1.5 #000C296B3F6A000D0000001B00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: connector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#connector#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000001D00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: servlet_jsp. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#servlet_jsp#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000001F00000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: appclient. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#appclient#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002100000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: dbpool. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#dbpool#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002300000A3000EF90978C2E8C29#1183013784397#/System/Server##java.lang.Package#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#java.lang.Package#Java#error.action.filter#com/sap/engine/services/mngt_model/localization.properties#Exception thrown by Action Filter: com.sap.engine.services.mngt_model.spi.ActionFilteringException: com.sap.engine.services.deploy.server.utils.DSRemoteException: Application local/Dashboard is not deployed..Action will not be delivered to domain: jmsconnector. Action is: APPLICATION_DEPLOYED#3#com.sap.engine.services.mngt_model.plugins.ApplicationActionFilter@d46ed0#jmsconnector#APPLICATION_DEPLOYED#
#1.5 #000C296B3F6A000D0000002500000A3000EF90978C2E8C29#1183013784397#/System/Server/Services/Deploy##com.sap.engine.services.deploy#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.deploy#Plain#Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000002800000A3000EF90978C2E8C29#1183013784397#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.###
#1.5 #000C296B3F6A000D0000002B00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Unlocking the Deploy.#
#1.5 #000C296B3F6A000D0000002C00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Error#1#com.sap.engine.services.tcxblxdeploy_controller#Plain#An error occurred while deploying the deployment item 'local_Dashboard'.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.dc.gd.DeliveryException: An error occurred during deployment of sdu id: local_Dashboard
sdu file path: C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear
version status: NEW
deployment status: Admitted
description:
1. Error:
Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
Reason: Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.
. Cannot deploy it.; nested exception is:
java.rmi.RemoteException: class com.sap.engine.services.deploy.server.utils.DSRemoteException: Error occurred while deploying ear file C:\SAP\JP1\JC00\j2ee\cluster\server0\temp\tcbldeploy_controller\archives\14\Dashboard.ear.
Reason: Exception while validating application local/Dashboard.
No one of the [] containers, which processed it, returned deployed component names.
The registered containers in this moment were [com.sap.security.ume, app_libraries_container, Cache Configuration Upload, servlet_jsp, dbcontentcontainer, connector, Cluster File System, JMSConnector, appclient, dbschemacontainer, orpersistence, JDBCConnector, EJBContainer, webservices_container, scheduler~container].
Possible reasons :
1.An AS Java service, which is providing a container, is stopped or not deployed.
2.The containers, which processed it, are not implemented correct. They deployed or started initially the application, but didn't return deployed components in the application deployment info.###
#1.5 #000C296B3F6A000D0000002F00000A3000EF90978C2E8C29#1183013784428#/System/Server/Deployment##com.sap.engine.services.tcxblxdeploy_controller#Administrator#4#####Thread[RMI/IIOP Worker [3],5,Dedicated_Application_Thread]##0#0#Info#1#com.sap.engine.services.tcxblxdeploy_controller#Plain###Deployment has finished#
Thanks,
MK -
Error in deployment JAva Module : deployment aborted
Hi,
yesterday i posted a message (cfr java.lang.NoSuchMethodError
Posted: Aug 28, 2007 10:54 AM )
There was some advice that i don't have to watch out the error. Some told me it was concerning a anti-virus programme (which doesn't run in this environment)
so i deploy it with this error :
could someone guide me thru the solution?
thx in advance , points will be given for good answers , i don't gave points at earlier post because it wasn't helpfull
Gwen
error message :
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sideshow-mel
SDM port : 50018
URL to deploy : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Result
=> deployment aborted : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication.. Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
additional information:
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[001]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\XID\DVEBMGS00\SDM\program\log\sdmcl20070829125021.log]/>
<!PATTERN[sdmcl20070829125021.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Aug 29, 2007 2:50:21 PM Info: -
Starting deployment -
Aug 29, 2007 2:50:21 PM Info: Error handling strategy: OnErrorStop
Aug 29, 2007 2:50:21 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 29, 2007 2:50:21 PM Info: Update strategy: UpdateAllVersions
Aug 29, 2007 2:50:21 PM Info: Starting deployment prerequisites:
Aug 29, 2007 2:50:24 PM Info: Loading selected archives...
Aug 29, 2007 2:50:24 PM Info: Loading archive 'C:\usr\sap\XID\DVEBMGS00\SDM\program\temp\temp13798ExcelFileAdapterModuleApplication.ear'
Aug 29, 2007 2:50:25 PM Info: Selected archives successfully loaded.
Aug 29, 2007 2:50:25 PM Info: Actions per selected component:
Aug 29, 2007 2:50:25 PM Info: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: Ending deployment prerequisites. All items are correct.
Aug 29, 2007 2:50:25 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:25 PM Info: Saved current Engine state.
Aug 29, 2007 2:50:25 PM Info: Starting: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: SDA to be deployed: C:\usr\sap\XID\DVEBMGS00\SDM\root\origin\sap.com\ExcelFileAdapterModuleApplication\localhost\0\2007.07.25.10.07.01\temp13798ExcelFileAdapterModuleApplication.ear
Aug 29, 2007 2:50:25 PM Info: Software type of SDA: J2EE
Aug 29, 2007 2:50:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:28 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:31 PM Info: Begin of log messages of the target system:
07/08/29 14:50:28 - ***********************************************************
07/08/29 14:50:29 - Start updating EAR file...
07/08/29 14:50:29 - start-up mode is lazy
07/08/29 14:50:29 - EAR file updated successfully for 125ms.
07/08/29 14:50:29 - Start deploying ...
07/08/29 14:50:29 - EAR file uploaded to server for 94ms.
07/08/29 14:50:31 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 10 more
Caused by: java.lang.NoClassDefFoundError: com/sap/aii/af/mp/module/Module
Loader Info -
ClassLoader name: [Deployment:Runtime:sap.com/ExcelFileAdapterModuleApplication]
Parent loader name: [Frame ClassLoader]
References:
common:service:http;service:servlet_jsp
service:ejb
common:service:iiop;service:naming;service:p4;service:ts
service:jmsconnector
library:jsse
library:servlet
common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
library:ejb20
library:j2eeca
library:jms
library:opensql
common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
interface:resourcecontext_api
interface:webservices
interface:cross
interface:ejbserialization
library:com.sap.aii.ai.lib
service:com.sap.aii.adapter.xi.svc
service:com.sap.aii.af.svc
service:com.sap.aii.af.cpa.svc
Resources:
C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231
C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231\ExcelFileAdapterModule.jar
Loading model: {parent,references,local}
The error occurred while trying to load "com.kk.ExcelModule.GetExcelFileBean".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 16 more
For detailed information see the log file of the Deploy Service.
07/08/29 14:50:31 - ***********************************************************
Aug 29, 2007 2:50:31 PM Info: End of log messages of the target system.
Aug 29, 2007 2:50:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:31 PM Error: Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Aug 29, 2007 2:50:31 PM Info: Starting to save the repository
Aug 29, 2007 2:50:32 PM Info: Finished saving the repository
Aug 29, 2007 2:50:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Aug 29, 2007 2:50:32 PM Error: -
At least one of the Deployments failed -
Message was edited by:
Gwen BaertHi,
yesterday i posted a message (cfr java.lang.NoSuchMethodError
Posted: Aug 28, 2007 10:54 AM )
There was some advice that i don't have to watch out the error. Some told me it was concerning a anti-virus programme (which doesn't run in this environment)
so i deploy it with this error :
could someone guide me thru the solution?
thx in advance , points will be given for good answers , i don't gave points at earlier post because it wasn't helpfull
Gwen
error message :
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : sideshow-mel
SDM port : 50018
URL to deploy : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Result
=> deployment aborted : file:/C:/Users/Admin/AppData/Local/Temp/temp13798ExcelFileAdapterModuleApplication.ear
Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication.. Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
additional information:
29-aug-2007 12:50:32 /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] INFO:
[001]Additional log information about the deployment
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\XID\DVEBMGS00\SDM\program\log\sdmcl20070829125021.log]/>
<!PATTERN[sdmcl20070829125021.log]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%24d %s: %m)]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
Aug 29, 2007 2:50:21 PM Info: -
Starting deployment -
Aug 29, 2007 2:50:21 PM Info: Error handling strategy: OnErrorStop
Aug 29, 2007 2:50:21 PM Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Aug 29, 2007 2:50:21 PM Info: Update strategy: UpdateAllVersions
Aug 29, 2007 2:50:21 PM Info: Starting deployment prerequisites:
Aug 29, 2007 2:50:24 PM Info: Loading selected archives...
Aug 29, 2007 2:50:24 PM Info: Loading archive 'C:\usr\sap\XID\DVEBMGS00\SDM\program\temp\temp13798ExcelFileAdapterModuleApplication.ear'
Aug 29, 2007 2:50:25 PM Info: Selected archives successfully loaded.
Aug 29, 2007 2:50:25 PM Info: Actions per selected component:
Aug 29, 2007 2:50:25 PM Info: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: Ending deployment prerequisites. All items are correct.
Aug 29, 2007 2:50:25 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:25 PM Info: Saved current Engine state.
Aug 29, 2007 2:50:25 PM Info: Starting: Initial deployment: Selected development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0' will be deployed.
Aug 29, 2007 2:50:25 PM Info: SDA to be deployed: C:\usr\sap\XID\DVEBMGS00\SDM\root\origin\sap.com\ExcelFileAdapterModuleApplication\localhost\0\2007.07.25.10.07.01\temp13798ExcelFileAdapterModuleApplication.ear
Aug 29, 2007 2:50:25 PM Info: Software type of SDA: J2EE
Aug 29, 2007 2:50:27 PM Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:28 PM Error: Unable to compare host[sideshow-mel] and host[PC4D] Throwable: java.net.UnknownHostException Throwable message: PC4D
Aug 29, 2007 2:50:31 PM Info: Begin of log messages of the target system:
07/08/29 14:50:28 - ***********************************************************
07/08/29 14:50:29 - Start updating EAR file...
07/08/29 14:50:29 - start-up mode is lazy
07/08/29 14:50:29 - EAR file updated successfully for 125ms.
07/08/29 14:50:29 - Start deploying ...
07/08/29 14:50:29 - EAR file uploaded to server for 94ms.
07/08/29 14:50:31 - ERROR: Not deployed. Deploy Service returned ERROR:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
... 10 more
Caused by: java.lang.NoClassDefFoundError: com/sap/aii/af/mp/module/Module
Loader Info -
ClassLoader name: [Deployment:Runtime:sap.com/ExcelFileAdapterModuleApplication]
Parent loader name: [Frame ClassLoader]
References:
common:service:http;service:servlet_jsp
service:ejb
common:service:iiop;service:naming;service:p4;service:ts
service:jmsconnector
library:jsse
library:servlet
common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
library:ejb20
library:j2eeca
library:jms
library:opensql
common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
interface:resourcecontext_api
interface:webservices
interface:cross
interface:ejbserialization
library:com.sap.aii.ai.lib
service:com.sap.aii.adapter.xi.svc
service:com.sap.aii.af.svc
service:com.sap.aii.af.cpa.svc
Resources:
C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231
C:\usr\sap\XID\DVEBMGS00\j2ee\cluster\server0\temp\deploy\1188391830231\ExcelFileAdapterModule.jar
Loading model: {parent,references,local}
The error occurred while trying to load "com.kk.ExcelModule.GetExcelFileBean".
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:401)
at com.sap.engine.services.ejb.deploy.verifier.CheckUtils.loadClass(CheckUtils.java:25)
at com.sap.engine.services.ejb.deploy.verifier.session.SessionBeanCheck.check(SessionBeanCheck.java:42)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.checkBean(Verifier.java:82)
at com.sap.engine.services.ejb.deploy.verifier.Verifier.check(Verifier.java:46)
at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:254)
at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2161)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
... 16 more
For detailed information see the log file of the Deploy Service.
07/08/29 14:50:31 - ***********************************************************
Aug 29, 2007 2:50:31 PM Info: End of log messages of the target system.
Aug 29, 2007 2:50:31 PM Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Aug 29, 2007 2:50:31 PM Error: Aborted: development component 'ExcelFileAdapterModuleApplication'/'sap.com'/'localhost'/'2007.07.25.10.07.01'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/ExcelFileAdapterModuleApplication..
Reason: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.; nested exception is:
com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application sap.com/ExcelFileAdapterModuleApplication in container EJBContainer.
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Aug 29, 2007 2:50:31 PM Info: Starting to save the repository
Aug 29, 2007 2:50:32 PM Info: Finished saving the repository
Aug 29, 2007 2:50:32 PM Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Aug 29, 2007 2:50:32 PM Error: -
At least one of the Deployments failed -
Message was edited by:
Gwen Baert -
Report and Alert don't executed in the error handler with a JMS proxy service
Hi,
I'm working with OSB 11.1.1.4.0 and I'm facing a problem with the error handler of my JMS proxy service.
My error handler contains two main elements :
- a Report action
- an Alert with a JMS destination defined
When the business service failed the message remain in the queue. It's the expected behavior.
The problem is :
- the report is missing
- the alert is raised but missing in the JMS destination defined in the Alert setting.
I've noticed if I add a Reply with Failure or Success, Report and Alert are successfully executed.
Unfortunately the message don't remain in the JMS queue.
What can I do in order to have my report/alert done and the JMS transaction rollback in order to keep the message in the queue ?
I've already met this problem in the past with alsb v3 and my solution was to add Service Callout in the error handler in order to externalize these actions.
This solution is not convenient and I hope another solution is possible.Inventorying workgroups can be difficult, especially when it comes to remote access and network security. Because workgroups are not centrally managed, some of the items discussed in this
wiki article on preparing your workgroup environment may require you to visit each machine individually.
For non-domain credentials, you do not use the <systemname>\<user> format, you simply enter the user name. Regarding how to enter the credentials, if you have an account that uses the same username and password on all machines and is an administrator
on all of those machines, then you can enter that in the All computers credentials page of the wizard. You can also do this if they are different user names. However, if some machines have an account with the same user name, such as Administrator,
but different passwords on each machine, you will need to use the Manually enter computer names discovery method, and then enter the information for each group or each machine.
As you can tell, workgroup environments can quickly negate any benefit that the agentless inventory nature of MAP provides.
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread. -
Interface Mapping run time error...java.lang.nullpointerException thrown
Hi,
I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
Interface Mapping run time error...java.lang.nullpointerException thrown during application mapping.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>CAMEL_BS_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>Camel_BService_01</SAP:Service>
<SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
<SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
</SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
<SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info />
</SAP:Hop>
- <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
<SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20070108</SAP:Date>
<SAP:Time>224350</SAP:Time>
<SAP:Host>gbdci550</SAP:Host>
<SAP:SystemId>PI7</SAP:SystemId>
<SAP:SystemNr>03</SAP:SystemNr>
<SAP:OS>AIX</SAP:OS>
<SAP:DB>DB6</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>014</SAP:ProcStatus>
<SAP:AdapterStatus>000</SAP:AdapterStatus>
<SAP:User>PIAFUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>002</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
<SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
<SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
<SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="TID" />
<SAP:MessageSizePayload>168</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>67</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
<SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
<SAP:Serialize_Children>X</SAP:Serialize_Children>
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
<SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="1" type="T">Sender scheme external = XIParty</Trace>
<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
<Trace level="1" type="T">Sender party external =</Trace>
<Trace level="1" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Party normalization: receiver</Trace>
<Trace level="1" type="T">Receiver scheme external =</Trace>
<Trace level="1" type="T">Receiver agency external =</Trace>
<Trace level="1" type="T">Receiver party external =</Trace>
<Trace level="1" type="T">Receiver party normalized =</Trace>
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- <!-- ************************************
-->
<Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
<Trace level="1" type="T">Queue name : XBTI0008</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
- <!-- ************************************
-->
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="1" type="T">number of receivers: 1</Trace>
<Trace level="1" type="T">Single-receiver split case</Trace>
<Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Persisting single message for post-split handling</Trace>
<Trace level="1" type="T" />
<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!-- ************************************
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
<Trace level="1" type="T">system-ID = PI7</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = PIAFUSER</Trace>
<Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!-- ************************************
-->
<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
<Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- <!-- ************************************
-->
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
- <!-- ************************************
-->
<Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:[email protected]">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Please I request to give me some hint how to troubleshoot this issue.
Thanks a lot,
SrujanHi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
Here is the Java exception
Mappage d'interface
Can someone be helpful for that ?
Regards
Laurent
Message was edited by:
Laurent Gitton -
[LV 7.1 Pro on WinXP for Tablet PC's]
I recently let a rather large LV app of mine run in the development environment while I was out for a couple of days. Upon returning I found that the app had hung for ~22 hours waiting for an answer to an Automatic Error Handling (AEH) dialog proclaiming an Error 7 in New File without any indication of the VI hierarchy that called New File. I set about ensuring that AEH dialogs would not pop up and have not been able to discover how I could have possibly received one in the first place.
Subsequent investigation revealed:
Neither AEH option in Options>Block Diagrams were checked.
Network problems had occurred around the time that the app had hung. All file paths are network paths when running in the development environment, so the cause of the error was most likely valid, even if the AEH dialog appearance wasn't.
My app has only one instance where the New File primitive is used by me. That subVI and all others above it in the hierarchy DO NOT have the AEH property enabled. The error out cluster of New File in my subvi is wired.
My app has three instances where New File is called from a vi.lib vi (Open/Create/Replace File.vi, Open Config Data.vi, and Prompt Web Browser Path.vi), none of which have the AEH property enabled. Nor does any of their calling VI's. All three instances also have their error out cluster wired.
A utility to examine the AEH property of all VI's (with all top level and dynamic VI's loaded) in memory reported that only 1 of 308 vi's ( RGT Does File Exists.vi from the Report Generation Toolkit) had that property true. That vi has no subVI's other than the File/Directory Info primitive and no calling VI's in common with any of the vi's that call New File, except a top level VI.
As long as 'Enable automatic error handling dialogs' remains unselected in options>block diagram, I am unable to get an AEH dialog for either the New File or File/Directory Info primitives in a test VI with AEH property enabled and their error out clusters unwired no matter what invalid path I pass to the functions. As soon as the options>block diagram>Enable AEH dialogs' is selected, both primitives fire AEH dialogs with no error out wired and don't when wired. i.e. works as advertised.
In other words I can find no reason why I should have gotten the problem AEH dialog...
I cannot afford for this app to hang because of a network problem, other portions of the app that were running concurrently correctly handled the error and, had the AEH dialog not appeared, the app would have made corrections or shutdown in an orderly fashion.
Any ideas?Very good.
Write Characters to File.vi>Open/Create/Replace File.vi>New File
New File throws the error. Open/Create/Replace strips the hierarchy from the source of the error. Write Characters passes it to the General Error Handler. I never looked above O/C/R file in the hierarchy except for enable automatic error handling property. The tip-off should have been to realize that O/C/R file was stripping the hierarchy from the error and look above that.
The real irony is that Write Characters was being used to log error cluster data to an error log file...
Save as... Copy without updating... the OEM 'Write Characters to File' is gone from this app.
Thanx (a bunch) -
Error while calling Java Web Dynpro
Dear Experts,
We have succecfully implemeneted our java stack but when i click on Web dynpro link i receieve following error on my browser, please help me. Thanks.
The error is:
java.lang.StringIndexOutOfBoundsException: String index out of range: 21
at java.lang.String.substring(String.java:1441)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.fillStaticTemplateContext(HtmlClient.java:516)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.sendResponse(HtmlClient.java:1213)
at com.sap.tc.webdynpro.clientimpl.html.client.HtmlClient.retrieveData(HtmlClient.java:252)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doRetrieveData(WindowPhaseModel.java:595)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:156)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
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)Dear ganga,
we haven't done any development yet, we only install the java stack and access webdynpro through web but when i try to click the link of webdynpro it gives me the error which i mentioned in my message. Furthermore, visual administrator and config tool are working fine even when i access web services menu through browser it shows me the info without any error. Please guide me and help me to solve this problem.
thanks,
basis team -
JSF error handling when the bean is not correctly loaded
Hi,
I am doing some error handling in JSF and I want to do it in an elegant way. I have the following scenario for error handling.
When the bean is initialized I load the bean with values from DAO which give SQL Exceptions.
Since the bean is not loaded I properly I have to send the user to an error page showing the error message why I am sending the user to this page.
I can do it by [ FacesContext.getCurrentInstance.redirect("/error.jsf") ] doing so I will loose all the FacesMessages that are added by the exceptions.
Instead I want to use the [ FacesContext.getCurrentInstance.dispatch("url") ] which will allow the transfer of the user but I get the following
16:59:39,341 WARN [lifecycle] executePhase(RESTORE_VIEW 1,com.sun.faces.context.FacesContextImpl@8537f9) threw exception
java.lang.ClassCastException: javax.faces.component.UIViewRoot
and the method that I am calling is
public static void programErrorEnd() {
logger.info("in the prgmErrorEnd mehod");
//intializing the contex object
FacesContext ctx = FacesContext.getCurrentInstance();
try {
//ready to dispatch the url.
//ctx.getExternalContext().redirect("app/error/prgmerror.jsf");
ctx.getExternalContext().dispatch("error/prgmerror.jsf");
} catch (IOException e) {
//TODO what to do when there is an error at this stage.
finally {
ctx.responseComplete();
}Thanks and Regarding
Edited by: sgatl2 on Aug 28, 2008 2:32 PM
Edited by: sgatl2 on Aug 28, 2008 2:45 PMJust let it throw the exception and define an error-page entry in the web.xml which catches the specified exception (or a superclass of it or a HTTP status code) and displays the error.jsf page accordingly.
-
Best practice of OSB logging Report handling or java code using publish
Hi all,
I want to do common error handling of OSB I did two implementations as below just want to know which one is the best practice.
1. By using the custom report handler --> When ever we want to log we will use the report action of OSB which will call the Custom java class which
Will log the data in to DB.
2. By using plain java class --> creating a java class publish to the proxy which will call this java class and do the logging.
Which is the best practice and pros and cons.
Thanks
PhaniHi Anuj,
Thanks for the links, they have been helpful.
I understand now that OSR is only meant to contain only Proxy services. The synch facility is between OSR and OSB so that in case when you are not using OER, you can publish Proxy services to OSR from OSB. What I didn't understand was why there was a option to publish a Proxy service back to OSB and why it ended up as a Business service. From the link you provided, it mentioned that this case is for multi-domain OSBs, where one OSB wants to use the other OSB's service. It is clear now.
Some more questions:
1) In the design-time, in OER no Endpoints are generated for Proxy services. Then how do we publish our design-time services to OSR for testing purposes? What is the correct way of doing this?
Thanks,
Umar -
Error Handling in WebUtil CLIENT_OLE2.get_obj_property
Hello,
we have a problem with the error handling in WebUtil's CLIENT_OLE2.get_obj_property function. The WebUtil version is 1.0.2 and the problem can be reproduced on the 9iAS, 9iDS and 10gAS as well.
Problem description:
The get_obj_property function does not throw a PL/SQL exception when it is given an invalid object as first argument (i.e. an object handle to an application that has intermittently been closed by the user). Instead, the function returns a NULL value and the control flow of our application code continues as if the function had succeeded. So the problem is that the get_obj_property function neither throws an exception nor can the failure be caught by calling WEBUTIL_CORE.IsError as this returns that no error occurred.
Example:
PACKAGE BODY word IS
OBJ_HND CLIENT_OLE2.OBJ_TYPE := NULL;
mydocs CLIENT_ole2.obj_type;
-- Start Word97
PROCEDURE wordopen is
BEGIN
obj_hnd := null;
obj_hnd := CLIENT_OLE2.create_obj ('Word.Application');
CLIENT_OLE2.Set_property(obj_hnd,'Visible',1);
END;
PROCEDURE test is
BEGIN
IF obj_hnd IS NULL THEN
wordopen;
END IF;
BEGIN
mydocs := CLIENT_OLE2.get_obj_property(obj_hnd,'Documents');
EXCEPTION WHEN OTHERS THEN
-- Word has probably been closed by the user
-- so just start it again and retry...
wordopen;
mydocs := CLIENT_OLE2.get_obj_property(obj_hnd,'Documents');
END;
END;
END;
If the procedure test is called once then the Word application is started and the procedure performs some work. The procedure could be called several times on the same Word instance but fails in case the user closes the Word application because the procedure does not get an exception or error from WebUtil's get_obj_property function. Only a JACOB Java exception is logged in the Java console of the user's computer - the PL/SQL code has no way of knowing that an error has occurred.
Possible solution / patch for webutil.pll:
The webutil.pll can be patched to throw an exception if it is given an invalid object handle. In webutil.pll version 1.0.2 in get_object_property, line 1205, just add the condition "(v_javaHandle IS NULL) or " at the beginning of the if-statement in that line so that an OLE_ERROR will be raised if v_javaHandle is NULL:
if (v_javaHandle IS NULL) or (v_javaHandle = 0) or (v_javaHandle='') or (v_javaHandle=-1) then
raise OLE_ERROR;
end if;
Can you confirm the error and re-release a patched webutil.pll at a later time?
Regards,
Andreas Leidner
infoteam GmbH BerlinHi
It is mentioned in webutil doc that, you must regenerate webutil.pll before using it; otherwise you’ll encounter error ORA-06508 when running a form with the attached library.
Hope this helps...
Regards,
Amatu Allah
Maybe you are looking for
-
my itunes keeps telling me to contact support when i try to connect a visa card and will not let me buy music. any ideas why?
-
Deploying TCS v2 in a Managed Environment
I wondered if anyone had successfully deployed TCS in a Managed Enterprise Environment using an Enterprise Management Tool such as SCCM or Radia? In our environment all Applications should be packaged for deployment so that they can be fully managed
-
Hi Please give the oracle support document or link with instructions for installing Oracle 11g client (latest version) on windows server 2008 64 bit. Please also give the link for downloading the oracle 11g client too. Many thanks
-
Why did you increase the space between bookmarks in the bookmark bar
It use to be smaller, so I could get more bookmarks on the browser bookmark bar. There is too much white space between them IMHO.
-
I keep getting this message when I launch PP "Premiere Pro cannot find any capable video play modules". I've read through a few threads and made the recommended changes but still no luck, it crashes everytime. I have a Mac Pro 2010 with a Nivdia Quad