web access to NetWeaver Server

[Former Member]

Dear All

I need to have a web access to the SAP system. When I go to the URL below (IP is internal)

http://10.100.150.30:50100/index.html

I got following option

First Column

SAP Library

System Information

User Management

SAP NetWeaver Administrator

Second Column

Web Services Navigator

UDDI Client

Web Dynpro

J2EE Engine Examples

When I click on User Management it goes to url http://10.100.150.30:50100/nwa and

When I click on NetWeaver Administrator it goes to url http://10.100.150.30:50100/useradmin

In both case it display following error

**************************************************************************************************

503 Service Unavailable

SAP J2EE Engine/7.00

Application cannot be started.

Details:

com.sap.engine.services.deploy.container.ExceptionInfo: JMS error.

**************************************************************************************************

Looking forward for your replies.

Thanks & Regards

Syed Saifuddin

[Former Member]

Please check that all the services are started in the system or not.Please print the logs of std_server.out from the work directory.

Also check the note Note 1303507 - JMS Adapter throws NullPointerException at channel start

Thanks

Rishi Abrol

[Former Member]

Dear Rishi Abrol

Thank you for your support and sorry for the misuse of your support but I have no option then sending you full log.

Please review and reply.

To reduce the length of log I am deleting the line saying service started.

Thank You

Syed Saifuddin

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 1189 ms.

Loading: PoolManager ... 6 ms.

Loading: ApplicationThreadManager ... 469 ms.

Loading: ThreadManager ... 408 ms.

Loading: IpVerificationManager ... 23 ms.

Loading: ClassLoaderManager ... 18 ms.

Loading: ClusterManager ... 284 ms.

Loading: LockingManager ... 155 ms.

Loading: ConfigurationManager ... 4082 ms.

Loading: LicensingManager ... 32 ms.

Loading: CacheManager ... 221 ms.

Loading: ServiceManager ...

<AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>

<AF[1]: managing allocation failure, action=0 (953274968/1073740288)>

<GC(1): GC cycle started Sat Aug 1 02:13:48 2009

<GC(1): freed 74830816 bytes, 95% free (1028105784/1073740288), in 69 ms>

<GC(1): mark: 60 ms, sweep: 9 ms, compact: 0 ms>

<GC(1): refs: soft 0 (age >= 32), weak 0, final 469, phantom 0>

<AF[1]: completed in 81 ms>

Loading services.:

Service memory started. (21 ms).

Service com.adobe~XMLFormService started. (3316 ms).

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

ServiceManager started for 68136 ms.

Framework started for 76613 ms.

SAP J2EE Engine Version 7.00 PatchLevel is running!

PatchLevel March 04, 2006 16:23 GMT

>

<AF[2]: Allocation Failure. need 64024 bytes, 91515 ms since last AF>

<AF[2]: managing allocation failure, action=1 (30296/1020053272) (53687016/53687016)>

<GC(2): GC cycle started Sat Aug 1 02:15:20 2009

<GC(2): freed 730530528 bytes, 73% free (784247840/1073740288), in 393 ms>

<GC(2): mark: 364 ms, sweep: 29 ms, compact: 0 ms>

<GC(2): refs: soft 0 (age >= 32), weak 19, final 9627, phantom 0>

<AF[2]: completed in 412 ms>

Aug 1, 2009 2:15:24 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:15:24 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:15:50 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:15:50 AM ...services.webdynpro.WebDynproContainer [SAPEngine_System_Thread[impl:5]_10] Fatal: Error occured during preparation of application startup.

Aug 1, 2009 2:16:15 AM ...services.webdynpro.WebDynproContainer [SAPEngine_System_Thread[impl:5]_10] Fatal: Error occured during preparation of application startup.

Aug 1, 2009 2:16:15 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:16:16 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:16:21 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:16:22 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:16:22 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

Aug 1, 2009 2:16:26 AM ...n.ConnectionFactory.checkForException [SAPEngine_System_Thread[impl:5]_10] Fatal: Failed to create connection! Reason: Cannot create connection. User

<AF[3]: Allocation Failure. need 8192 bytes, 65929 ms since last AF>

<AF[3]: managing allocation failure, action=1 (0/1020053272) (53687016/53687016)>

<GC(3): GC cycle started Sat Aug 1 02:16:26 2009

<GC(3): freed 614782976 bytes, 62% free (668469992/1073740288), in 180 ms>

<GC(3): mark: 146 ms, sweep: 33 ms, compact: 1 ms>

<GC(3): refs: soft 0 (age >= 32), weak 45, final 3760, phantom 0>

<AF[3]: completed in 182 ms>

<AF[4]: Allocation Failure. need 42168 bytes, 35353599 ms since last AF>

<AF[4]: managing allocation failure, action=1 (177792/1020053272) (53558864/53687016)>

<GC(4): GC cycle started Sat Aug 1 12:08:21 2009

<GC(4): freed 817200264 bytes, 81% free (870936920/1073740288), in 160638 ms>

<GC(4): mark: 158070 ms, sweep: 2564 ms, compact: 4 ms>

<GC(4): refs: soft 0 (age >= 32), weak 26, final 1221, phantom 0>

<GC(4): stop threads time: 331, start threads time: 0>

<AF[4]: completed in 161091 ms>

<AF[5]: Allocation Failure. need 536 bytes, 75085719 ms since last AF>

<AF[5]: managing allocation failure, action=1 (0/1020053272) (53558864/53687016)>

<GC(5): mark stack overflow[1]>

<GC(5): GC cycle started Sun Aug 2 09:03:28 2009

<GC(5): freed 800972960 bytes, 79% free (854531824/1073740288), in 220431 ms>

<GC(5): mark: 217696 ms, sweep: 2723 ms, compact: 12 ms>

<GC(5): refs: soft 0 (age >= 32), weak 46, final 404, phantom 0>

<GC(5): stop threads time: 449, start threads time: 1>

<AF[5]: completed in 221082 ms>

<AF[6]: Allocation Failure. need 15728 bytes, 73385970 ms since last AF>

<AF[6]: managing allocation failure, action=1 (482344/1020053272) (53687016/53687016)>

<GC(6): GC cycle started Mon Aug 3 05:29:11 2009

<GC(6): freed 800512760 bytes, 79% free (854682120/1073740288), in 156341 ms>

<GC(6): mark: 150786 ms, sweep: 5543 ms, compact: 12 ms>

<GC(6): refs: soft 0 (age >= 32), weak 44, final 394, phantom 0>

<GC(6): stop threads time: 457, start threads time: 12>

<AF[6]: completed in 156970 ms>

Thanks & Regards

[Former Member]

Hi ,

Goto configtool and try to increase the Application threads for the server and the dispatcher both.

What i can analise by rading the logs there are not enough threads .Please rember to take the backup of the Configtool setting before changing..

Please also let me know the JVM parameters Value in Configtool.

Thanks

Rishi Abrol

[Former Member]

Hello Syed,

I hope you have webdispatcher setup.

http://help.sap.com/saphelp_nw70/helpdata/en/f5/51c7d170bc4a98b1b5a0339213af57/content.htm

Check the above URL which can help you on setting up your Web based access to NW system.

Regards

Vivek

[Former Member]

Dear Rishi

When I try to run configtool.sh I got following exception. I am accessing the AIX machind through putty.

blade6:dvbadm 14> ./configtool.sh

java.lang.reflect.InvocationTargetException

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

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

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

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

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

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable

.

at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)

at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:175)

at java.lang.Class.forName1(Native Method)

at java.lang.Class.forName(Class.java:180)

at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:91)

at java.awt.Window.init(Window.java:268)

at java.awt.Window.<init>(Window.java:312)

at java.awt.Frame.<init>(Frame.java:431)

at javax.swing.JFrame.<init>(JFrame.java:229)

at com.sap.engine.configtool.visual.ConfigToolView.<init>(ConfigToolView.java:77)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:69)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:960)

... 6 more

Thanks & Regards

[Former Member]

Please set the Display Variable then run the configtool.

Thanks

Rishi Abrol

[Former Member]

Rishi

As I mention that I am using putty. I think GUI or any display will not change the Exception.

I am thinking if there is any command line argument to run configtool in text mode, It will be helpful to me.

eg. ./configtool.sh mode=silent or something like that.

I really appreciate your commitment.

Thank You

[Former Member]

No i dont thinks so you need to login in to Configtool.

Thanks

Rishi Abrol

[Former Member]

Hi Rishi

Before you wrote the following

"Goto configtool and try to increase the Application threads for the server and the dispatcher both."

Now if no need to login to configtool then what to do. I think you understand our issue closely.

Please help me in this task.

Regards,

Syed Saifuddin