Invalid ticket lifetime in default trace
Hi,
I keep getting the following invalid lifetime error messages. What can I do to get rid of the messages?
Br,
Johan
#2.0 #2011 01 26 10:37:14:441#+0100#Error#com.sap.engine.services.security.authentication.loginmodule.ticket#
#BC-JAS-SEC#security#1CC1DE05B10C02660000000000001890#6538650000000004#sap.com/me~ear#com.sap.engine.services.security.authentication.loginmodule.ticket#Guest#0##DB806784292F11E0B15700000063C59A#c2379401292f11e08c4400000063c59a#c2379401292f11e08c4400000063c59a#0#Thread[HTTP Worker [@1590167589],5,Dedicated_Application_Thread]#Plain##
Parsing UME property: Invalid ticket lifetime in hours: ''. '8' hours will be used.
[EXCEPTION]
java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:468)
at java.lang.Integer.parseInt(Integer.java:497)
at com.sap.security.core.server.jaas.UMEAdapter.<init>(UMEAdapter.java:160)
at com.sap.security.core.server.jaas.UMEAdapter.<init>(UMEAdapter.java:76)
at com.sap.security.core.server.jaas.EvaluateTicketLoginModule.initialize(EvaluateTicketLoginModule.java:179)
at com.sap.engine.services.security.login.LoginModuleLoggingWrapperImpl.initialize(LoginModuleLoggingWrapperImpl.java:170)
at com.sap.engine.services.security.login.LoginContextFactory.initializeLoginContext(LoginContextFactory.java:196)
at com.sap.engine.services.security.login.FastLoginContext.login(FastLoginContext.java:208)
at com.sap.engine.services.servlets_jsp.server.servlet.AuthenticationFilter.doFilter(AuthenticationFilter.java:109)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Hi Johan,
property 'login.ticket_lifetime' may have been destroyed somehow. You may try to set it back to 8 hours (default) manually and avoid exceptions.
To check the property and reset it to default if necessary, go to configtool, switch to the Configuration Editor mode, then go to cluster_config -> system ->
custom_global -> cfg -> services -> com.sap.security.core.ume.service, switch to Edit mode, open Propertysheet properties and find the property 'login.ticket_lifetime'.
Check if 'custom' checkbox is checked, also check custom value and if empty, set it to default (8). Save your changes, restart will be required.
Regards,
Anton
Edited by: Anton Shabinskyi on Jan 26, 2011 1:22 PM
Similar Messages
-
How can we change the lifetime of an assertion ticket?
The default lifetime is set to 120 seconds.
We need to extend the tickets lifetime. Where can we define this?
Edited by: Urs Hürlimann on Jun 30, 2008 8:52 AMtrc file: "/var/log/suva/espresso/wlss1/sso_log.txt", trc level: 3, release: "640"
"Thr 14393" Thu Jul 3 11:20:46 2008
"Thr 14393" MySapEvalLogonTicketEx was called.
"Thr 14393" Unconverted Ticket is the following: AjExMDAgAA9wb3J0YWw6RTAwMDA0MDCIAAdkZWZhdWx0EAADV0xTDwADMDAxCAABAQEACEUwMDAwNDAwAgADMDAwAwADUzUwBAAMMjAwODA3MDMwOTE4BwAEAAAAAgoACEUwMDAwNDAw%2FwEFMIIBAQYJKoZIhvcNAQcCoIHzMIHwAgEBMQswCQYFKw4DAhoFADALBgkqhkiG9w0BBwExgdAwgc0CAQEwIjAdMQwwCgYDVQQDEwNTNTAxDTALBgNVBAsTBEoyRUUCAQAwCQYFKw4DAhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MDcwMzA5MTg1MlowIwYJKoZIhvcNAQkEMRYEFPoQw28O4qu98dOGLjvU6FAdQ81DMAkGByqGSM44BAMELzAtAhQ5z0e6BOwCc9A9nDYayvSqun5PtgIVAIf1F7g1mpGZ1mHWse0c19HAgS3s
."Thr 14393" Initialized variables...
"Thr 14393" Preparing InContext...
"Thr 14393" *** ERROR => SAP Codepage is invalid! Uses UTF8 for output. "ssoxxext_mt. 331"
"Thr 14393" Ticket is the following: AjExMDAgAA9wb3J0YWw6RTAwMDA0MDCIAAdkZWZhdWx0EAADV0xTDwADMDAxCAABAQEACEUwMDAwNDAwAgADMDAwAwADUzUwBAAMMjAwODA3MDMwOTE4BwAEAAAAAgoACEUwMDAwNDAw%2FwEFMIIBAQYJKoZIhvcNAQcCoIHzMIHwAgEBMQswCQYFKw4DAhoFADALBgkqhkiG9w0BBwExgdAwgc0CAQEwIjAdMQwwCgYDVQQDEwNTNTAxDTALBgNVBAsTBEoyRUUCAQAwCQYFKw4DAhoFAKBdMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA4MDcwMzA5MTg1MlowIwYJKoZIhvcNAQkEMRYEFPoQw28O4qu98dOGLjvU6FAdQ81DMAkGByqGSM44BAMELzAtAhQ5z0e6BOwCc9A9nDYayvSqun5PtgIVAIf1F7g1mpGZ1mHWse0c19HAgS3s
."Thr 14393" Profile is the following: /usr/espresso/config/wlss1/sapcerts/h50a090.pse
."Thr 14393" Password is the following: (NULL)
"Thr 14393" Just before Validation...
"Thr 14393" Dump of InContext "ssoxxapi_mt.c 156"
"Thr 14393" 00000000 34 31 31 30 78 44 04 10 f2 1a 2c e8 78 44 06 68 4110xD..ò.,èxD.h
"Thr 14393" 00000010 00 00 01 ec 00 00 00 00 00 00 00 00 ...ì........
"Thr 14393" Copies from InContext->Format: PKCS7 "ssoxxapi_mt.c 163"
"Thr 14393" Copies from InContext->pzcsProName: /usr/espresso/config/wlss1/sapcerts/h50a090.pse "ssoxxapi_mt.c 166"
"Thr 14393" DecodeB64Len returns 0. iDecLength=369
"Thr 14393" Dump of Decoded ticket: "ssoxxapi_mt.c 188"
"Thr 14393" 00000000 02 31 31 30 30 20 00 0f 70 6f 72 74 61 6c 3a 45 .1100 ..portal:E
"Thr 14393" 00000010 30 30 30 30 34 30 30 88 00 07 64 65 66 61 75 6c 0000400...defaul
"Thr 14393" 00000020 74 10 00 03 57 4c 53 0f 00 03 30 30 31 08 00 01 t...WLS...001...
"Thr 14393" 00000030 01 01 00 08 45 30 30 30 30 34 30 30 02 00 03 30 ....E0000400...0
"Thr 14393" 00000040 30 30 03 00 03 53 35 30 04 00 0c 32 30 30 38 30 00...S50...20080
"Thr 14393" 00000050 37 30 33 30 39 31 38 07 00 04 00 00 00 02 0a 00 7030918.........
"Thr 14393" 00000060 08 45 30 30 30 30 34 30 30 ff 01 05 30 82 01 01 .E0000400ÿ..0...
"Thr 14393" 00000070 06 09 2a 86 48 86 f7 0d 01 07 02 a0 81 f3 30 81 ..*.H.÷.... .ó0.
"Thr 14393" 00000080 f0 02 01 01 31 0b 30 09 06 05 2b 0e 03 02 1a 05 ð...1.0...+.....
"Thr 14393" 00000090 00 30 0b 06 09 2a 86 48 86 f7 0d 01 07 01 31 81 .0...*.H.÷....1.
"Thr 14393" 000000A0 d0 30 81 cd 02 01 01 30 22 30 1d 31 0c 30 0a 06 Ð0.Í...0"0.1.0..
"Thr 14393" 000000B0 03 55 04 03 13 03 53 35 30 31 0d 30 0b 06 03 55 .U....S501.0...U
"Thr 14393" 000000C0 04 0b 13 04 4a 32 45 45 02 01 00 30 09 06 05 2b ....J2EE...0...+
"Thr 14393" 000000D0 0e 03 02 1a 05 00 a0 5d 30 18 06 09 2a 86 48 86 ...... "0...*.H.
"Thr 14393" 000000E0 f7 0d 01 09 03 31 0b 06 09 2a 86 48 86 f7 0d 01 ÷....1...*.H.÷..
"Thr 14393" 000000F0 07 01 30 1c 06 09 2a 86 48 86 f7 0d 01 09 05 31 ..0...*.H.÷....1
"Thr 14393" 00000100 0f 17 0d 30 38 30 37 30 33 30 39 31 38 35 32 5a ...080703091852Z
"Thr 14393" 00000110 30 23 06 09 2a 86 48 86 f7 0d 01 09 04 31 16 04 0#..*.H.÷....1..
"Thr 14393" 00000120 14 fa 10 c3 6f 0e e2 ab bd f1 d3 86 2e 3b d4 e8 .ú.Ão.⫽ñÓ..;Ôè
"Thr 14393" 00000130 50 1d 43 cd 43 30 09 06 07 2a 86 48 ce 38 04 03 P.CÍC0...*.HÎ8..
"Thr 14393" 00000140 04 2f 30 2d 02 14 39 cf 47 ba 04 ec 02 73 d0 3d ./0-..9ÏGº.ì.sÐ=
"Thr 14393" 00000150 9c 36 1a ca f4 aa ba 7e 4f b6 02 15 00 87 f5 17 .6.Êôªº~O¶....õ.
"Thr 14393" 00000160 b8 35 9a 91 99 d6 61 d6 b1 ed 1c d7 d1 c0 81 2d ¸5...ÖaÖ±í.×ÑÀ.-
"Thr 14393" 00000170 ec ì
"Thr 14393" Read version.
"Thr 14393" Read Codepage.
"Thr 14393" Read InfoUnit (0x20).
"Thr 14393" Read length (15).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x88).
"Thr 14393" Read length (7).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x10).
"Thr 14393" Read length (3).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x0F).
"Thr 14393" Read length (3).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x08).
"Thr 14393" Read length (1).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x01).
"Thr 14393" Read length (8).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x02).
"Thr 14393" Read length (3).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x03).
"Thr 14393" Read length (3).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x04).
"Thr 14393" Read length (12).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x07).
"Thr 14393" Read length (4).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0x0A).
"Thr 14393" Read length (8).
"Thr 14393" Read contents.
"Thr 14393" Read InfoUnit (0xFF).
"Thr 14393" ParseTicket returns 0. "ssoxxapi_mt.c 200"
"Thr 14393" Bytes processed: 106 "ssoxxapi_mt.c 203"
"Thr 14393" Argument Dump for ticket verification:
"Thr 14393" Content byte stream:
"Thr 14393" 00000000 02 31 31 30 30 20 00 0f 70 6f 72 74 61 6c 3a 45 .1100 ..portal:E
"Thr 14393" 00000010 30 30 30 30 34 30 30 88 00 07 64 65 66 61 75 6c 0000400...defaul
"Thr 14393" 00000020 74 10 00 03 57 4c 53 0f 00 03 30 30 31 08 00 01 t...WLS...001...
"Thr 14393" 00000030 01 01 00 08 45 30 30 30 30 34 30 30 02 00 03 30 ....E0000400...0
"Thr 14393" 00000040 30 30 03 00 03 53 35 30 04 00 0c 32 30 30 38 30 00...S50...20080
"Thr 14393" 00000050 37 30 33 30 39 31 38 07 00 04 00 00 00 02 0a 00 7030918.........
"Thr 14393" 00000060 08 45 30 30 30 30 34 30 30 .E0000400
"Thr 14393"
Signature byte stream:
"Thr 14393" 00000000 30 82 01 01 06 09 2a 86 48 86 f7 0d 01 07 02 a0 0.....*.H.÷....
"Thr 14393" 00000010 81 f3 30 81 f0 02 01 01 31 0b 30 09 06 05 2b 0e .ó0.ð...1.0...+.
"Thr 14393" 00000020 03 02 1a 05 00 30 0b 06 09 2a 86 48 86 f7 0d 01 .....0...*.H.÷..
"Thr 14393" 00000030 07 01 31 81 d0 30 81 cd 02 01 01 30 22 30 1d 31 ..1.Ð0.Í...0"0.1
"Thr 14393" 00000040 0c 30 0a 06 03 55 04 03 13 03 53 35 30 31 0d 30 .0...U....S501.0
"Thr 14393" 00000050 0b 06 03 55 04 0b 13 04 4a 32 45 45 02 01 00 30 ...U....J2EE...0
"Thr 14393" 00000060 09 06 05 2b 0e 03 02 1a 05 00 a0 5d 30 18 06 09 ...+...... "0...
"Thr 14393" 00000070 2a 86 48 86 f7 0d 01 09 03 31 0b 06 09 2a 86 48 .H.÷....1....H
"Thr 14393" 00000080 86 f7 0d 01 07 01 30 1c 06 09 2a 86 48 86 f7 0d .÷....0...*.H.÷.
"Thr 14393" 00000090 01 09 05 31 0f 17 0d 30 38 30 37 30 33 30 39 31 ...1...080703091
"Thr 14393" 000000A0 38 35 32 5a 30 23 06 09 2a 86 48 86 f7 0d 01 09 852Z0#..*.H.÷...
"Thr 14393" 000000B0 04 31 16 04 14 fa 10 c3 6f 0e e2 ab bd f1 d3 86 .1...ú.Ão.⫽ñÓ.
"Thr 14393" 000000C0 2e 3b d4 e8 50 1d 43 cd 43 30 09 06 07 2a 86 48 .;ÔèP.CÍC0...*.H
"Thr 14393" 000000D0 ce 38 04 03 04 2f 30 2d 02 14 39 cf 47 ba 04 ec Î8.../0-..9ÏGº.ì
"Thr 14393" 000000E0 02 73 d0 3d 9c 36 1a ca f4 aa ba 7e 4f b6 02 15 .sÐ=.6.Êôªº~O¶..
"Thr 14393" 000000F0 00 87 f5 17 b8 35 9a 91 99 d6 61 d6 b1 ed 1c d7 ..õ.¸5...ÖaÖ±í.×
"Thr 14393" 00000100 d1 c0 81 2d ec ÑÀ.-ì
"Thr 14393" Encoded content byte stream:
"Thr 14393" 00000000 30 78 06 09 2a 86 48 86 f7 0d 01 07 01 a0 6b 04 0x..*.H.÷.... k.
"Thr 14393" 00000010 69 02 31 31 30 30 20 00 0f 70 6f 72 74 61 6c 3a i.1100 ..portal:
"Thr 14393" 00000020 45 30 30 30 30 34 30 30 88 00 07 64 65 66 61 75 E0000400...defau
"Thr 14393" 00000030 6c 74 10 00 03 57 4c 53 0f 00 03 30 30 31 08 00 lt...WLS...001..
"Thr 14393" 00000040 01 01 01 00 08 45 30 30 30 30 34 30 30 02 00 03 .....E0000400...
"Thr 14393" 00000050 30 30 30 03 00 03 53 35 30 04 00 0c 32 30 30 38 000...S50...2008
"Thr 14393" 00000060 30 37 30 33 30 39 31 38 07 00 04 00 00 00 02 0a 07030918........
"Thr 14393" 00000070 00 08 45 30 30 30 30 34 30 30 ..E0000400
"Thr 14393" Verify returns 0 "ssoxxsgn_mt.c 189"
"Thr 14393" Certificate is:
"Thr 14393" 00000000 30 82 02 3b 30 82 02 26 02 01 00 30 09 06 07 2a 0..;0..&...0...*
"Thr 14393" 00000010 86 48 ce 38 04 03 30 1d 31 0c 30 0a 06 03 55 04 .HÎ8..0.1.0...U.
"Thr 14393" 00000020 03 13 03 53 35 30 31 0d 30 0b 06 03 55 04 0b 13 ...S501.0...U...
"Thr 14393" 00000030 04 4a 32 45 45 30 1e 17 0d 30 37 30 37 30 32 31 .J2EE0...0707021
"Thr 14393" 00000040 31 34 32 33 34 5a 17 0d 32 37 30 37 30 32 31 31 14234Z..27070211
"Thr 14393" 00000050 34 32 33 34 5a 30 1d 31 0c 30 0a 06 03 55 04 03 4234Z0.1.0...U..
"Thr 14393" 00000060 13 03 53 35 30 31 0d 30 0b 06 03 55 04 0b 13 04 ..S501.0...U....
"Thr 14393" 00000070 4a 32 45 45 30 82 01 b6 30 82 01 2b 06 07 2a 86 J2EE0..¶0..+..*.
"Thr 14393" 00000080 48 ce 38 04 01 30 82 01 1e 02 81 81 00 82 7d d4 HÎ8..0........}Ô
"Thr 14393" 00000090 9c a2 05 69 84 e9 83 71 b1 34 0d 5d 71 83 92 85 .¢.i.é.q±4."q...
"Thr 14393" 000000A0 b2 5a ca a3 82 d7 ac 38 6e 94 40 84 3f 0a 46 7a ²ZÊ£.׬8n.@.?.Fz
"Thr 14393" 000000B0 a8 75 a8 c1 ca 3b 70 ba 6a 97 07 12 f6 b1 99 ed ¨u¨ÁÊ;pºj...ö±.í
"Thr 14393" 000000C0 3e ec 53 13 f3 94 0a 67 bb d6 9f 38 72 29 61 ab >ìS.ó..g»Ö.8r)a«
"Thr 14393" 000000D0 02 3d 17 a1 33 3c 52 23 5d 9f b7 d1 0e 95 e3 a5 .=.¡3<R#".·Ñ..ã¥
"Thr 14393" 000000E0 5e f9 b0 4f c7 c9 20 c5 72 da 7a c3 d5 0f 24 0d ^ù°OÇÉ ÅrÚzÃÕ.$.
"Thr 14393" 000000F0 bb 8e 54 da 9e bb 70 21 11 c5 35 82 e5 35 85 2e ».TÚ.»p!.Å5.å5..
"Thr 14393" 00000100 9f 59 39 79 b3 32 50 c8 86 83 96 19 17 02 15 00 .Y9y³2PÈ........
"Thr 14393" 00000110 fa 50 79 da fa 3f 3a b1 e8 0a 6d f5 bd 16 f2 24 úPyÚú?:±è.mõ½.ò$
"Thr 14393" 00000120 d8 f8 d7 1b 02 81 80 4f bd f5 2e 33 04 f0 51 c1 Øø×....O½õ.3.ðQÁ
"Thr 14393" 00000130 7c a5 5c 93 81 b5 c1 7d 4c 20 50 76 85 34 50 cf |¥..µÁ}L Pv.4PÏ
"Thr 14393" 00000140 d9 fc 72 b2 e1 b2 b1 6f a0 10 48 b8 ff 17 e7 a9 Ùür²á²±o .H¸ÿ.ç©
"Thr 14393" 00000150 0a e1 e0 18 05 3e 34 d9 d5 61 df 71 4c c8 dc 92 .áà..>4ÙÕaßqLÈÜ.
"Thr 14393" 00000160 b1 51 b5 df 66 59 70 6b 5e 57 c3 19 a2 d6 58 3b ±QµßfYpk^WÃ.¢ÖX;
"Thr 14393" 00000170 7d 32 d2 e9 e1 f1 66 3e aa ac 46 0d cd 4e 67 70 }2Òéáñf>ª¬F.ÍNgp
"Thr 14393" 00000180 36 f7 f9 be 0b 2e 16 a0 5d 69 5d 5b 81 13 a9 03 6÷ù¾... "i""..©.
"Thr 14393" 00000190 cb 38 63 56 1a bd 36 4a 5d 6c 15 66 17 fa 10 a3 Ë8cV.½6J"l.f.ú.£
"Thr 14393" 000001A0 20 99 e1 d2 34 77 13 03 81 84 00 02 81 80 5c a5 .áÒ4w........\u00A5
"Thr 14393" 000001B0 41 c8 31 99 f2 ff a7 20 be 01 2d 80 4b 7e e9 45 AÈ1.òÿ§ ¾.-.K~éE
"Thr 14393" 000001C0 80 72 c9 59 52 28 af 76 57 0b 08 ae ec 75 db 19 .rÉYR(¯vW..®ìuÛ.
"Thr 14393" 000001D0 dc 06 db e8 2a 2e 0b 55 11 09 76 ff a9 ad f3 5c Ü.Ûè*..U..vÿ©ó
"Thr 14393" 000001E0 f3 c5 bf 23 db 6e fd ea 85 81 78 ad 2a 05 2d 83 óÅ¿#Ûnýê..x*.-.
"Thr 14393" 000001F0 12 91 ff f0 a0 bb 79 c3 0e cb 37 f8 dc 05 31 38 ..ÿð »yÃ.Ë7øÜ.18
"Thr 14393" 00000200 c3 1b 5b 61 64 19 4e b1 60 d2 7e b7 a8 51 d6 6e Ã."ad.N±`Ò~·¨QÖn
"Thr 14393" 00000210 36 1e fc ce 6a 78 20 c3 e6 54 1f 0d 68 c0 db 61 6.üÎjx ÃæT..hÀÛa
"Thr 14393" 00000220 c5 84 63 15 d4 19 36 94 56 03 2f 2e 3b 89 30 0c Å.c.Ô.6.V./.;.0.
"Thr 14393" 00000230 06 08 2a 86 48 86 f7 0d 02 05 05 00 03 01 00 ..*.H.÷........
"Thr 14393" ValidateTicket returns 0. "ssoxxapi_mt.c 226"
"Thr 14393" Validation succeeded...
"Thr 14393" Got date 200807030918 from ticket.
"Thr 14393" Cur time = 200807030920.
"Thr 14393" Computing validity in hours.
"Thr 14393" Computing validity in minutes.
"Thr 14393" CurTime_t = 1215163200, CreTime_t = 1215163080
"Thr 14393" validity: 120, difference: 120.000.
"Thr 14393" Evaluating user...
"Thr 14393" Evaluating Client ...
"Thr 14393" Evaluating Sysid ...
"Thr 14393" Evaluating Portal User...
"Thr 14393" Evaluating AuthSchema...
"Thr 14393" Evaluating creation time...
"Thr 14393" Computing validity in minutes.
"Thr 14393" validity: 120, difference: 3720.000.
"Thr 14393" *** ERROR => MySapEvalLogonTicketEx returns 4. "ssoxxext_mt. 665"
"Thr 14393" End of function MySapEvalLogonTicketEx. -
PI 7.11 - confusing error messages in the Default Trace
Hello,
Every day, I see these error messages pop up in the default trace ( all with location System.err ):
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:57)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:977)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:41)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:67)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:355)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:60)
at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
.... and many others.
It all seems to start with this error:
java.util.regex.PatternSyntaxException: Unexpected internal error near index 16 number_of_nodes\
They all appear just once a day and all at the same time.
I already looked for possible causes or background jobs, but nothing...
Can anybody give me a suggestion?
Thanks a lot.Hi Kevin,
indeed....You need to apply the following SAP Notes:
1749574 - Checking for the latest Configuration Wizard patch
1927916 - Registration of Mbean:ConfigurationExportKMC DefaultTrace
Afterwards restart J2EE engine. This helped in my case.
Best Regards
Harald -
Error Logs in the Default Trace
Hi All,
Iam getting following eror for every second in the Default Trace log but no users are effected with this log. Can anybody tell me what this error is about .
Date : 12/20/2006
Time : 11:18:43:702
Message : Exception in method: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
[EXCEPTION]
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
at java.lang.Thread.run(Thread.java:534)
Severity : Error
Category :
Location : com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()
Application : sap.com/irj
Thread : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Datasource : 34368150:/usr/sap/PP1/JC03/j2ee/cluster/server0/log/defaultTrace.trc
Message ID : 0003BA4DBF04001100003473000012530004250B918DE14E
Source Name : com.sap.ip.collaboration.rtc
Argument Objs : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
at java.lang.Thread.run(Thread.java:534)
Arguments : com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfactory/default/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1093)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
at java.lang.Thread.run(Thread.java:534)
Dsr Component :
Dsr Transaction :
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.ip.collaboration.rtc
ThreadObject : Thread[Thread-37,5,SAPEngine_Application_Thread[impl:3]_Group]
Transaction :
User : j2ee_guest
Thanks,
MasterI am having this same issue as well. I upgraded our BI and BI Portal to SP12. Everything worked fine. Then I started the BI integration as outlined in OSS note 917950 -> Setting up BEx Web - Problem analysis.doc and restarted the J2EE engine and now I have this same error in the default trace and I can't log into the visual admin as the j2ee_admin user. I get "error while connecting". But I can connect to the visual admin as myself. If I login to the BI portal as my self and click on user administration I get this error "A required service for the identity management user interface is not available. Contact your system administrator"
Here's the error as seen in the default trace file that keeps repeating.
#1.#0003BA21A6F5005C000000590000595B000439DE957600B4#1189528059902#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration
.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#J2EE_GUEST#0####d71a1250608111dcbcf70
003ba21a6f5#Thread[Thread-57,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: com.sap.engine.se
rvices.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the whole lookup name is jmsfa
ctory/default/QueueConnectionFactory.
[EXCEPTION]
#1#com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at jmsfactory, the wh
ole lookup name is jmsfactory/default/QueueConnectionFactory.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:261)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:624)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1238)
at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1182)
at java.lang.Thread.run(Thread.java:534)
Also, at the very beginning of the default trace file I see this error:
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null
##0#0#Error##Java###A SecurityException was caught while attempting to retrieve user with Administrator rights in the fallback attem
pt. The performed attempt was userCtx.getUserInfo(role.getRunAsIdentity(true)) but it ended with the following security exception :
[EXCEPTION]
#1#com.sap.security.core.server.userstore.UserstoreException: Could not get user null -
Deleting default trace file in java
Hello all,
Whats the best way to automatically delete default trace file in java instance? I want to delete these files lets say every week or 2 wkkds,Is there any type of configuration that can be done through NWA or OS...? or do i have to write some scripts? Please advice.Perfect.
When set to 10, 0 -->9 are cyclic files. Regarding archiving, yes this is possible. Apart from defaulttrace files you can also archive other java log files (system, network,security etc). The configuration procedure is explained :-
http://help.sap.com/saphelp_nw04/helpdata/en/48/2edfd5bd3e0d4a81b90325fe195a70/frameset.htm
Once the 10th trace file(i.e.defaultrace9) is full, all the trace files (from defaulttrace0-defaultrace9) are zipped to a single file. The file compression ratio is extremely good.
Unfortunately there is no automated mechanism to clear off the archived files. This needs manual intervention(regular cleanup, script etc).
The archived log files may also be viewed for analysis from NWA.
While estimating the size for each defaulttrace consider three factors i) System load ii) Number of defaulttrace files.
iii) Retention days(without archiving)
Ex: System load as observed :
Say the trace file size is 10MB and 6 trace files get written in 4 hours of peak time and 1 trace files is written for 4 hours during non-peak time .Assuming 8 hours of peak business hours and rest all non-working hours.
No of files generated is 62 + 14 = 16 files of 10 MB each are generated per week day
If the defaulttrace file count is set to 16, you can retain one days' logs . Say you wish to retain the same with less number of files (i.e. 8) you would have to increase the file size to 20 MB. Also will have to look at file system space availability.
CAUTION: For a file system occupancy estimate, you will have to also consider as to how many Server nodes are
configured as each node has its own log area !
For this you need to observe the pattern as to how many files are being written then estimate the size and count
cheers !
PRADi -
Moving Default Trace File in SQL Server
How can I move the default trace file in SQL server?
SQL Server 2012?
Thanks in advance
ebroPlease have a look at these links:
Change path for default SQL Server trace
Steps to change the default location of SQL Server /SQL Server Agent - Error log files
DETERMINING DEFAULT TRACE LOCATION
Collecting the Information in the Default Trace
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog -
Write logs in different location instead of default trace
I need to write a logs in different location other than default trace. I don't want to write logs in default trace. what setting i need to do in portal so that i can able to write at other location instead of default trace.
Hi,
Check this thread.
Log for J2EE Web Services?
Regards,
Harini S -
Webdynpro Exception in Default Trace File
Hello ,
We are on EP7.0 ECC6.0 ESS1.0 and kepp on getting the following error in the Default Trace file for ESS Travel Webdynpro :
#1.5^H#00145EC6B0AC001200000072000740EC00045AF21F04ABB9#1225895855827#com.sap.engine.services.servlets_jsp.client.RequestInfo
Server#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#JSS0WHZ#4383##goxsa664_PP1_7622452
#JSS0WHZ#36d947e0ab4711ddb54c00145ec6b0ac#SAPEngine_Application_Thread[impl:3]_10##0#0#Error##Plain###application [webdynpro/
dispatcher] Processing HTTP request to servlet [dispatcher] finished with error. The error is: com.sap.tc.webdynpro.services.
sal.core.DispatcherException: Wrong Web Dynpro URL: "../WebDynpro/Servlet/<deployableObject>/<application>/xx?..". xx is not
allowed without exchange key. Retrieved URI path: /sap.com/esstratri/TripForm/~wd_key115_1225895826865/background.gif.
at com.sap.tc.webdynpro.serverimpl.wdc.adapter.HttpRequestAdapter.checkApplicationUri(HttpRequestAdapter.java:111)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.checkApplicationUri(RequestManager.java:665)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:141)
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:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessio
nMessageListener.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(AccessController.java:215)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
If anybody has encountered such situation ....please let me know.
Thanks in advance.
ShikhilHi Shikhil,
We are running into this exact same issue. Can you please tell me if you were able to resolve this and how it was done?
Thank you so much,
-Kevin -
Time stamp information in default trace file
How to check the time stamp in defaulttrace.trc or application.trc files for logs in XI server.
I have seen following timestamp in above mentioned trace files. But seem to me, during the shutdown time of server, system put the timestamp in trace file.
ERROR gateway shutdown
TIME Fri Jun 20 11:01:08 2008
Except for shutdown time, how the system put the timestamp for other activity of system in the default trace and application trace file??
Sometime, i need to check the timestamp to get some specific information in default trace file for some system activities.
is timestamp mentioned in coded form as per following log:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException#
#1.#36CC34C00F02009B000001B500001FF40004510B33EAB76C#1215008464352#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS #4869A1FC78690A8DE10000000A2C0AC7#SAPEngine_Application_Thread[impl:3]_51##0#0#Error##P
lain###java.lang.reflect.InvocationTargetException
Thanks
AmarHi Amarjit
The timestamp is noted in unix epoch time (java does use this as well). It is this field:
#1.#36CC34C00F02009B000001B400001FF40004510B33EAB6D3# 1215008464352 #com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.RFCDefaultRequestHand
ler.handleRequest()#J2EE_GUEST#0##XQA#SAPSYS
The first 10 digits are seconds since epoch. The last 3 digits are milisecondes. Converted in human readable format: 07/02/2008 16:21:04.352
[Unix Time|http://en.wikipedia.org/wiki/Unix_time]
Damn, i remeber having answered this already here in the forums, but i cannot find the thread anymore myself :-(((
Best regards
Michael -
Details missing in default trace file of XI
Hi Experts,
I am doing RFC to RFC scenario. I am getting checkered flag in SXMB_MONI. But for some reason i am not getting the details of my scenario in the default trace of XI. I'm not sure if the detiails of scenarios involving RFC's will be updated in the trace files. If yes, please help me in finding the reasons as to why it is not heppening in my case.
Thanks and Regards,
Hari.Hi,
Increase your logging/ Tracing levels in the Integration engine configuration to see the synchronous message in the SXMB_MONI.
1.Execute SXMB_ADM in the ABAP stack of XI
2.Navigate to Configuration --> Integration Engine Configuration --> Change Specific Configuration Data
Set the following:
Category : Runtime
Parameter : LOGGING_SYNC
value : 1 (activated)
Parameter : TRACE_LEVEL 3
value : 3 (activated)
For information on how to activate and deactivate traces, see the following SAP Note: 532918 (RFC Trace Generation)
also go with below links
Configuring the Trace File
http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
Enqueue Trace Analysis
http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
Enqueue Trace Records
http://help.sap.com/saphelp_nw04/helpdata/en/3d/93532ad37011d194ba00a0c94260a5/frameset.htm
Please let me know if this helps you or do you need any more info. -
Hi Friends,
usr/sap/<sid>/DVEBMGS<nn>/j2ee/cluster/server0/log/archive
In the above folder the default trace files of XI are getting archived, which is zip format and in hidden mode.These files have occupied huge amount of space.
What is the importance of these files?
Are these files necessary?
Will it cause any problem if we delete these file?
Pls help !!
Regards,
Bharath.Hai,
Check the below link.....
http://help.sap.com/saphelp_nwce10/helpdata/en/ac/e9d8a51c732e42bd0e7de54b9ff4e2/frameset.htm
You can delete the old archives if you really dont see any issue.
Regards,
Yoganand.V -
Logging Format like in default trace
Hi all,
When using log-viewer service in visual admin I want my logs to be formatted as it is in default trace (defaultTrace.trc)
The message is separately displayed in its own column whereas location/severity/date etc. is shown in its own column, but not contained in the message itself.
When I use my own location, destination(file) and formatter(trace) I cannot achieve the same. I get date and time in the right columns, but in the message column I get all the stuff that is in the file: date, severity, location. Let's say its not getting filtered.
Any idea what's so special about default trace?
regards
stefan
Edited by: Stefan Bungert on Apr 21, 2008 4:16 PMHi,
I think you change the format as you using TraceFormatter class.
According to the pattern you give in the constructor your format will change.
It is that pattern that determines.
Regards,
Srinivasan Subbiah -
Unable to view latest default trace in log viewer
Hello all,
We have NW 7.0 J2EE production server. We have a CI and two application servers.
Our SP level is SP18.
The DB is oracle and the operating system in RHEL 4.
I have a problem in viewing the default trace files in log viewer using the visual administrator.
I am able to view the old default trace but unable to view the latest trace data generated.
I am facing this problem when i try to view the logs of a particular application server.
Able to view the latest default trace properly for CI and the other application server. Problem lies only with a single application server.
I have also check the permissions in OS level for the trace files. Everything looks fine.
Could some one give me a clue on how to solve this issue.
Regards,
ChandruHello Joey,
The trace file isnt too big....
We have set the file size as 10 MB.
We have some 15 to 16 default trace files for each of the server process and we have 3 server process in that application server.
The ForceSingleTraceFile parameter is set as YES in visual admin.
So the logs will be displayed in visual admin as a single default trace file.
Hope I had provided the inputs you have asked...
Regards,
Chandru -
Visual admin error on default trace on server0
HI,
We have a recurrent error log which occurs all 5 minutes in the default trace in our Was Java (server0 node).
ACCESS.ERROR: Authorization check for caller assignment to J2EE security role [SAP-J2EE-Engine : administrators].
The user that throw this error is PIRWBUSER.
please, can you help us ?
Thanks.Hi Stephane,
The following thread will help to resolve the problem.
please check it.
Error in SP13; Authorization check for caller assignment
Re: Too many exception"ACCESS.ERROR: Authorization check"
regards
mahesh. -
NWA logs and trace does not show the content of Default trace
Hi All,
The content which i see in /usr/sap/SID/DV*/j2ee/cluster/server0/log/default trace
i am unable to see the same in default trace in NWA logs and traces,
It is a 7.0 system..
Coudl you please suggest.
Rgds
SHello,
Is it newly built system? Please compare log and trace levels with other java systems in your landscape.
You can give a try as following..
1. Goto NWA and click on Log Configurator service.
2. Switch to advanced mode.
3. Select the Location tab page.
4. Choose the location of default.trc file.
5. Save the configuration
6. Restart JAVA and see.
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Jan 12, 2012 3:36 PM
Maybe you are looking for
-
Eraser tool won't reverse when swapping fore and background colors
When using the eraser tool to blend layers I often want to "unerase" a bit so hit "X" to paint with white and it still erases to layer below just as it had before switching the foreground "W" and background "B" colors. Makes no sense to me as I thoug
-
Powerbook does not start in 10.5.4
I have a G4 Powerbook 1.5 with 10.4.11 on the mainhard drive. Since I have a lot of graphic apps I could not install 10.5.4 on the same drive because of limited space. The 10.5.4 installer allowed me to install it on one of my Firewire drives. Once t
-
Group Policy Pref - Mapped Drives Not Applying to One User
Hi All, I’m new to this list, so please excuse any etiquette slip ups. I have three users at a site. All their machines are running Windows XP Service Pack 3 and have client side extensions installed. I created a group policy to map their default
-
Illustrator CS5 random thin lines in shape of a circle with an off-centred middle
Hi there! I need to create random thin lines in shape of a circle (similar to a dandelion), but with an off-centred middle. I hope this makes sense... Here is a quick scribble of what I need: I just can't figure it out, does anybody have any ideas? C
-
Acrobat Reader cannot be installed??? Version 4-9
Hi, can anybody help me? My son messed with the registry in XP Pro SP3 and deleted my Acrobat Reader. I tried to reinstall it using everything I read but no luck. Here are the two Errors I get: Error 1401.Could not create key \.fdf\AcroExch.FDFDoc\Sh