Re: ARERR log

2013-07-12 Thread Rajiv Gopal
Hi,

I've gone through the ARThread log and it shows the Thread on Fast Queue
Died and Restarted.

 /* Fri Jul 12 2013 06:20:39.2670 */ Thread Id 12832 (thread number
106) on FAST queue restarted.
 /* Fri Jul 12 2013 06:21:36.2830 */ Thread Id 12832 (thread number
106) on FAST queue died.
 /* Fri Jul 12 2013 06:21:36.2830 */ Thread Id 6860 (thread number
106) on FAST queue restarted.
 /* Fri Jul 12 2013 06:21:47.1420 */ Thread Id 1084 (thread number
 42) on FAST queue died.
 /* Fri Jul 12 2013 06:21:47.1420 */ Thread Id 8388 (thread number
 42) on FAST queue restarted.



On Fri, Jul 12, 2013 at 3:30 PM, Hullule, Kiran wrote:

> This is AR Server crash or potentially Fast thread died . This happened
> due to webservice execution.  As you are running on 7.5 patch 03 , see the
> 7.5 p08 readme file if there is any defect fixed in this area.
>
> -Original Message-
> From: Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] On Behalf Of Rajiv Nakkana
> Sent: Friday, July 12, 2013 2:53 PM
> To: arslist@ARSLIST.ORG
> Subject: ARERR log
>
> Hi,
>
> I'm receiving the following error in one of our application server.
> However I'm able to access the server and see that there are 350 Users
> connected to the server.
>
> Fri Jul 12 05:19:09 2013  390620 : AR System server terminated when a
> signal/exception was received by the server (ARNOTE 20)
>
> Fri Jul 12 05:19:09 2013 0xc005
>
> Fri Jul 12 05:19:09 2013  390620 : AR System server terminated -- fatal
> error encountered (ARNOTE 21)
>
> Fri Jul 12 05:19:52 2013  390620 : AR System server terminated when a
> signal/exception was received by the server (ARNOTE 20)
>
> Fri Jul 12 05:19:52 2013
>
>Timestamp: 1373620792.6650
>
>Thread Id: 13840
>
>Version: 7.5.00 Patch 003 200909292346 Sep 30 2009 01:21:53
>
>ServerName: arsprod
>
>Database: SQL -- Oracle
>
>Hardware: Intel Pentium
>
>OS: Windows Server 2003
>
>RPC Id: 9690560
>
>RPC Call: 121 (XMLGE)
>
>RPC Queue: 390620
>
>Client: User BMCCTRLM from Webservice (protocol 14) at IP address
> 10.218.105.65
>
>Form:
>
>Logging On: Thread ServerGroup
>
>Code: c005
>
>Operation: write
>
>Access Addr: 0x230
>
>Stack Begin:
>
>   Addr: 00837272
>
>   Addr: 005159C1
>
>   Addr: 0052393C
>
>   Addr: 51DFCA38
>
>Stack End
>
> Any help would be appriciated.
>
> Thanks and Regards,
> Rajiv N
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"


Re: Really dumb question re Java.

2013-06-18 Thread Rajiv Gopal
Hi Lisa,

There is no question of compatibility, but we are encountering Encryption
issue after upgrading our Java. So would say just to check the same.

Regards,
Rajiv N


On Tue, Jun 18, 2013 at 1:34 PM, Lisa Singh  wrote:

> One of my bosses asked to ensure the rollout of Java 7.21 was
> "compatible" with Remedy. I personally can't think of any reason the
> Java VM would matter in the case of Remedy (with the exception of
> Analytics) - am I missing a portion of Remedy proper that uses *any*
> client-side Java?
>
> Surely the point of Tomcat is to do all the Java server side.
>
> Can anybody confirm?
>
> Kind Regards,
>
> Lisa
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"