Skip to Content
author's profile photo Former Member
Former Member

Problem with XI J2EE Stack

We are getting the following error when the XI stack starts up. It seems to point to a problem in the Exchange Profile. However, I am not sure whether it is complaining because of incorrect parameters or because it is unable to access it. This instance of XI has been running just fine for the last few months and we have had no problems with it. All the J2EE services are shut down as the exception shows. Any insight into what the problem might be is well appreciated.

FYI, We haven't added any patches for the last couple of months. It was working fine during that time.

Included is the output from the log.

-


stdout/stderr redirect

-


node name : server0

pid : 4500

system name : XID

system nr. : 00

started at : Thu Jan 20 14:57:26 2005

CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources

CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain

CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub

CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS

CompilerOracle: exclude iaik/security/md/SHA a

CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices

CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile

CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup

SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is starting...

Loading: LogManager ... 4687 ms.

Loading: PoolManager ... 16 ms.

Loading: ApplicationThreadManager ... 142 ms.

Loading: ThreadManager ... 158 ms.

Loading: IpVerificationManager ... 126 ms.

Loading: ClassLoaderManager ... 78 ms.

Loading: ClusterManager ... 1558 ms.

Loading: LockingManager ... 724 ms.

Loading: ConfigurationManager ... 5647 ms.

Loading: LicensingManager ... 47 ms.

Loading: ServiceManager ...

Loading services.:

Service cross started. (47 ms).

Service memory started. (47 ms).

Service file started. (173 ms).

Service timeout started. (126 ms).

Service userstore started. (31 ms).

Service runtimeinfo started. (31 ms).

Service tcsecvsi~service started. (362 ms).

Service p4 started. (1541 ms).

Service trex.service started. (692 ms).

Service jmx_notification started. (865 ms).

Service classpath_resolver started. (126 ms).

Service tcsecwssec~service started. (661 ms).

Service deploy started. (10662 ms).

Service log_configurator started. (11997 ms).

Service locking started. (16 ms).

Service apptracing started. (424 ms).

Service http started. (533 ms).

Service naming started. (816 ms).

Service ts started. (203 ms).

Service javamail started. (298 ms).

Service failover started. (220 ms).

Service licensing started. (47 ms).

Service appclient started. (282 ms).

Service jmsconnector started. (455 ms).

Service connector started. (204 ms).

Service configuration started. (16 ms).

Service webservices started. (2887 ms).

Service dbpool started. (9428 ms).

Service com.sap.aii.af.svc started. (942 ms).

Service com.sap.security.core.ume.service started. (4048 ms).

Service security started. (5083 ms).

Service applocking started. (486 ms).

Service shell started. (675 ms).

Service tceCATTPingservice started. (189 ms).

Service classload started. (549 ms).

Service telnet started. (220 ms).

Service keystore started. (1789 ms).

Service ssl started. (156 ms).

Service ejb started. (2322 ms).

Service servlet_jsp started. (2400 ms).

Service tcsecsecurestorage~service started. (753 ms).

Service dsr started. (2150 ms).

Service jmx started. (2730 ms).

Service webdynpro started. (2526 ms).

Service tcsecdestinations~service started. (753 ms).

Service pmi started. (392 ms).

Service basicadmin started. (894 ms).

Service adminadapter started. (659 ms).

Service sld started. (2824 ms).

Service rfcengine started. (5098 ms).

Service monitor started. (4032 ms).

Service tc.monitoring.logviewer started. (7608 ms).

Service com.sap.aii.af.ms.svc started. (7640 ms).

Service jms_provider started. (11437 ms).

Service com.sap.aii.af.cpa.svc started. (11718 ms).

Service com.sap.aii.adapter.marketplace.svc started. (188 ms).

Service com.sap.aii.adapter.xi.svc started. (282 ms).

Service com.sap.aii.af.security.service started. (204 ms).

Service com.sap.aii.adapter.bc.svc started. (361 ms).

Service com.sap.aii.adapter.mail.svc started. (94 ms).

Service com.sap.aii.adapter.jms.svc started. (644 ms).

Service com.sap.aii.adapter.jdbc.svc started. (612 ms).

Service com.sap.aii.adapter.file.svc started. (659 ms).

Service com.sap.aii.af.ispeak.svc started. (706 ms).

Service com.sap.aii.adapter.rfc.svc started. (1882 ms).

ServiceManager started for 69917 ms.

Framework started for 84184 ms.

SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is running!

PatchLevel 87037.313 October 19, 2004 19:52 GMT

>### Excluding compile: iaik.security.md.SHA::a

Jan 22, 2005 3:03:51 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Jan 25, 2005 10:17:28... ...utilxi.prop.api.PropertySourceFactory [SAPEngine_Application_Thread[impl:3]_0] Fatal: XI properties could not be initialized. Check ExchangeProfile (or aii.properties).

Thrown:

java.lang.Throwable: dummy Throwable for stack trace

at com.sap.aii.utilxi.prop.api.PropertySourceFactory.getPropertySource(PropertySourceFactory.java:55)

at com.sap.aii.utilxi.misc.api.AIIProperties.sync(AIIProperties.java:528)

at com.sap.aii.utilxi.misc.api.AIIProperties.<init>(AIIProperties.java:301)

at com.sap.aii.utilxi.misc.api.AIIProperties.getInstance(AIIProperties.java:328)

at com.sap.aii.ib.server.util.perf.TimerFactory.<clinit>(TimerFactory.java:86)

at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:73)

at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)

at $Proxy30.processFunction(Unknown Source)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:95)

at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)

at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)

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:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Jan 29, 2005 7:37:28 AM com.sap.engine.core.configuration [SAPEngine_Application_Thread[impl:3]_23] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Jan 31, 2005 4:11:19 PM ...l.cache.WebResourceCache.startService [Thread[Thread-1140,5,SAPEngine_Application_Thread[impl:3]_Group]] Fatal: Tried to save: ~wd_key0_1107205757104

Feb 5, 2005 3:07:25 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Feb 5, 2005 3:02:56 PM com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_78] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Feb 6, 2005 3:03:13 PM com.sap.engine.core.configuration [SAPEngine_System_Thread[impl:5]_77] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

Feb 19, 2005 3:15:45 AM com.sap.engine.core.configuration [Thread[Timeout Service Internal Thread,5,SAPEngine_System_Thread[impl:5]_Group]] Fatal: Error event: java.sql.SQLException: Io exception: Connection reset by peer: socket write error

SAP J2EE Engine Version 6.40 PatchLevel 87037.313 is shutting down! PatchLevel 87037.313 October 19, 2004 19:52 GMT

Stopping services.

Service com.sap.aii.adapter.rfc.svc stopped. (439 ms)

Service com.sap.aii.af.ispeak.svc stopped. (78 ms)

Service com.sap.aii.adapter.marketplace.svc stopped. (15 ms)

Service com.sap.aii.adapter.jdbc.svc stopped. (79 ms)

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 21, 2005 at 04:41 AM

    Hi Sunit,

    Did you figure out what happened? We're seeing the same issue.

    Thanks,

    Jay

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.