Re: java RemoteException issue

2007-04-17 Thread Axton

Flashboards (not the part on the mid-tier server) also uses rmi.  If
you run a servlet container (jboss, tomcat, websphere, etc.), they
will listen on a port for rmi as well.

Axton Grams

On 4/17/07, Halstead, Robert <[EMAIL PROTECTED]> wrote:

Axton,

Thanks for the quick reply.  We had to roll back the switch to the
server group as we had issues with the licenses we got from BMC.  As the
licenses went into Remedy with out problems,  when we brought Remedy up,
the server wouldn't hand out "write" licenses only read.  We're not sure
what is going on there.

With the Java error, we only get this if we enable the server group.  As
soon as we rolled back to a non-server group state, we do not get that
error.  If it does have to deal with the Email Engine, why would this
error out only when we enable the server group and not all the time?
The next time we attempt this I will take a look at netstat and see if
the port is in use.  In all reason, this could be our issue for the java
error.  Is there any other part of the Remedy system that may produce an
RMI error?

Bob Halstead
Bresnan Communications

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Tuesday, April 17, 2007 6:45 AM
To: arslist@ARSLIST.ORG
Subject: Re: java RemoteException issue

The email engine uses RMI for the Admin interface.  In the
EmailDaemon.Properties file, you can specify the port RMI should listen
on.

com.remedy.arsys.emaildaemon.RMIPort=1100

I believe 1100 is the default

Chances are something else is already using this port?

Stop Remedy and use the following to see if anything is using this port:

$ netstat -na |grep 1100
  *.1100   *.*0  0 49152  0
LISTEN

or

# lsof |grep IP |grep 1100
java   1154 remedy7u  IPv4 0x3000d0dac400t0   TCP
*:1100 (LISTEN)

The 1154 is the pid:
$ ps -ef |grep 1154
 remedy  1154   895  0   Apr 15 ?   10:06 /usr/java/bin/java
-Djava.library.path=/xxx/AREmail -cp /xxx

Axton Grams

On 4/17/07, Halstead, Robert <[EMAIL PROTECTED]> wrote:
> **
>
> Hey guys, we've just enabled our server group, however we're seeing
> this error pop up when we start remedy.  It's a java RemoteException
> error.  Is this crucial for Remedy, or something to ignore?  the
> RemoteException usually has to do with RMI.. I've added our
> ar_instal_dir/bin and java_dir/bin to the PATH variable in arsystem
> file, but this doesn't seem to solve the problem.
>
> Remedy is up and running, I would like to find out why I only get this

> when we enable server group though.  I'm guessing remedy is trying to
> communicate with the other server for some reason via RMI.  Just a
guess though.
>
> Any ideas?
>
> Here is the PATH variable in the arsystem file:
>
> INSTALL_DIR=/opt/remedy/remprd
>
JAVADIR=:/usr/jdk/j2sdk1.4.2_08/jre:/usr/jdk/j2sdk1.4.2_08/jre/lib/sparc
/server
> #installer will add the ":" in front of this val ue since it might

> be blank
> PATH=/sbin:/usr/sbin:/usr/bin:/bin:$INSTALL_DIR/bin:/usr/jdk/j2sdk1.4.
> 2_08/jre/bin:$PATH;
> export PATH
>
>  I've posted the log below.
>
> Action Request System initializing.
> Starting AR System Server
>
>  (ARNOTE 0)
>AR Monitor version 6.03.00 patch 020 started.
>
>  (ARNOTE 0)
>AR Monitor started.
>
> Action Request System(R) Approval Server   Version 6.03.00.00
> Remedy, a BMC Software company.  Copyright (c) 1999 - 2004 BMC
> Software, Inc.  All rights reserved.
>
> AR System Reconciliation Engine Version  1.00.00 patch 005 Remedy, a
> BMC Software company.
> Copyright (c) 2004 - 2005 BMC Software, Inc.
> All rights reserved.
>
> Action Request System(R)  Server   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 1991 - 2005 BMC Software, Inc.
> All rights reserved.
>
> 390600 : A floating license specification was ignored because it
> requires a server group tag (ARERR 3329)
>
> Action Request System(R)  Fork Daemon   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 2000 - 2005 BMC Software, Inc.
> All rights reserved.
>
>  (ARNOTE 0)
>Server indicates that it's up.
>
>
> Action Request System  AR System Application Command Dispatcher
Version
> 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 1998 - 2005 BMC Software, Inc.
> All rights reserved.
>
> Action Request System(R)  Plug-In Server   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 2001 - 2005 BMC Software, Inc.
> All rights reserved.
>
>
> RemoteException
> java.rmi.ConnectException: Connection refused to host: localhost;
> nested exception is:
>  

Re: java RemoteException issue

2007-04-17 Thread Halstead, Robert
Axton,

Thanks for the quick reply.  We had to roll back the switch to the
server group as we had issues with the licenses we got from BMC.  As the
licenses went into Remedy with out problems,  when we brought Remedy up,
the server wouldn't hand out "write" licenses only read.  We're not sure
what is going on there.

With the Java error, we only get this if we enable the server group.  As
soon as we rolled back to a non-server group state, we do not get that
error.  If it does have to deal with the Email Engine, why would this
error out only when we enable the server group and not all the time?
The next time we attempt this I will take a look at netstat and see if
the port is in use.  In all reason, this could be our issue for the java
error.  Is there any other part of the Remedy system that may produce an
RMI error?

Bob Halstead
Bresnan Communications 

-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Tuesday, April 17, 2007 6:45 AM
To: arslist@ARSLIST.ORG
Subject: Re: java RemoteException issue

The email engine uses RMI for the Admin interface.  In the
EmailDaemon.Properties file, you can specify the port RMI should listen
on.

com.remedy.arsys.emaildaemon.RMIPort=1100

I believe 1100 is the default

Chances are something else is already using this port?

Stop Remedy and use the following to see if anything is using this port:

$ netstat -na |grep 1100
  *.1100   *.*0  0 49152  0
LISTEN

or

# lsof |grep IP |grep 1100
java   1154 remedy7u  IPv4 0x3000d0dac400t0   TCP
*:1100 (LISTEN)

The 1154 is the pid:
$ ps -ef |grep 1154
 remedy  1154   895  0   Apr 15 ?   10:06 /usr/java/bin/java
-Djava.library.path=/xxx/AREmail -cp /xxx

Axton Grams

On 4/17/07, Halstead, Robert <[EMAIL PROTECTED]> wrote:
> **
>
> Hey guys, we've just enabled our server group, however we're seeing 
> this error pop up when we start remedy.  It's a java RemoteException 
> error.  Is this crucial for Remedy, or something to ignore?  the 
> RemoteException usually has to do with RMI.. I've added our 
> ar_instal_dir/bin and java_dir/bin to the PATH variable in arsystem 
> file, but this doesn't seem to solve the problem.
>
> Remedy is up and running, I would like to find out why I only get this

> when we enable server group though.  I'm guessing remedy is trying to 
> communicate with the other server for some reason via RMI.  Just a
guess though.
>
> Any ideas?
>
> Here is the PATH variable in the arsystem file:
>
> INSTALL_DIR=/opt/remedy/remprd
>
JAVADIR=:/usr/jdk/j2sdk1.4.2_08/jre:/usr/jdk/j2sdk1.4.2_08/jre/lib/sparc
/server
> #installer will add the ":" in front of this val ue since it might

> be blank 
> PATH=/sbin:/usr/sbin:/usr/bin:/bin:$INSTALL_DIR/bin:/usr/jdk/j2sdk1.4.
> 2_08/jre/bin:$PATH;
> export PATH
>
>  I've posted the log below.
>
> Action Request System initializing.
> Starting AR System Server
>
>  (ARNOTE 0)
>AR Monitor version 6.03.00 patch 020 started.
>
>  (ARNOTE 0)
>AR Monitor started.
>
> Action Request System(R) Approval Server   Version 6.03.00.00
> Remedy, a BMC Software company.  Copyright (c) 1999 - 2004 BMC 
> Software, Inc.  All rights reserved.
>
> AR System Reconciliation Engine Version  1.00.00 patch 005 Remedy, a 
> BMC Software company.
> Copyright (c) 2004 - 2005 BMC Software, Inc.
> All rights reserved.
>
> Action Request System(R)  Server   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 1991 - 2005 BMC Software, Inc.
> All rights reserved.
>
> 390600 : A floating license specification was ignored because it 
> requires a server group tag (ARERR 3329)
>
> Action Request System(R)  Fork Daemon   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 2000 - 2005 BMC Software, Inc.
> All rights reserved.
>
>  (ARNOTE 0)
>Server indicates that it's up.
>
>
> Action Request System  AR System Application Command Dispatcher
Version
> 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 1998 - 2005 BMC Software, Inc.
> All rights reserved.
>
> Action Request System(R)  Plug-In Server   Version 6.03.00 patch 020
> Remedy, a BMC Software company.
> Copyright (c) 2001 - 2005 BMC Software, Inc.
> All rights reserved.
>
>
> RemoteException
> java.rmi.ConnectException: Connection refused to host: localhost; 
> nested exception is:
> java.net.ConnectException: Connection refused AR System Email 
> Engine has started
>
> RemoteException
> java.rmi.ConnectException: Connection refused to host: localhost; 
> nested exception is:
> java.net.Conne

Re: java RemoteException issue

2007-04-17 Thread Axton

The email engine uses RMI for the Admin interface.  In the
EmailDaemon.Properties file, you can specify the port RMI should
listen on.

com.remedy.arsys.emaildaemon.RMIPort=1100

I believe 1100 is the default

Chances are something else is already using this port?

Stop Remedy and use the following to see if anything is using this port:

$ netstat -na |grep 1100
 *.1100   *.*0  0 49152  0 LISTEN

or

# lsof |grep IP |grep 1100
java   1154 remedy7u  IPv4 0x3000d0dac400t0   TCP
*:1100 (LISTEN)

The 1154 is the pid:
$ ps -ef |grep 1154
remedy  1154   895  0   Apr 15 ?   10:06 /usr/java/bin/java
-Djava.library.path=/xxx/AREmail -cp /xxx

Axton Grams

On 4/17/07, Halstead, Robert <[EMAIL PROTECTED]> wrote:

**

Hey guys, we've just enabled our server group, however we're seeing this
error pop up when we start remedy.  It's a java RemoteException error.  Is
this crucial for Remedy, or something to ignore?  the RemoteException
usually has to do with RMI.. I've added our ar_instal_dir/bin and
java_dir/bin to the PATH variable in arsystem file, but this doesn't seem to
solve the problem.

Remedy is up and running, I would like to find out why I only get this when
we enable server group though.  I'm guessing remedy is trying to communicate
with the other server for some reason via RMI.  Just a guess though.

Any ideas?

Here is the PATH variable in the arsystem file:

INSTALL_DIR=/opt/remedy/remprd
JAVADIR=:/usr/jdk/j2sdk1.4.2_08/jre:/usr/jdk/j2sdk1.4.2_08/jre/lib/sparc/server
#installer will add the ":" in front of this val
ue since it might be blank
PATH=/sbin:/usr/sbin:/usr/bin:/bin:$INSTALL_DIR/bin:/usr/jdk/j2sdk1.4.2_08/jre/bin:$PATH;
export PATH

 I've posted the log below.

Action Request System initializing.
Starting AR System Server

 (ARNOTE 0)
   AR Monitor version 6.03.00 patch 020 started.

 (ARNOTE 0)
   AR Monitor started.

Action Request System(R) Approval Server   Version 6.03.00.00
Remedy, a BMC Software company.  Copyright (c) 1999 - 2004 BMC Software,
Inc.  All rights reserved.

AR System Reconciliation Engine Version  1.00.00 patch 005
Remedy, a BMC Software company.
Copyright (c) 2004 - 2005 BMC Software, Inc.
All rights reserved.

Action Request System(R)  Server   Version 6.03.00 patch 020
Remedy, a BMC Software company.
Copyright (c) 1991 - 2005 BMC Software, Inc.
All rights reserved.

390600 : A floating license specification was ignored because it requires a
server group tag (ARERR 3329)

Action Request System(R)  Fork Daemon   Version 6.03.00 patch 020
Remedy, a BMC Software company.
Copyright (c) 2000 - 2005 BMC Software, Inc.
All rights reserved.

 (ARNOTE 0)
   Server indicates that it's up.


Action Request System  AR System Application Command Dispatcher   Version
6.03.00 patch 020
Remedy, a BMC Software company.
Copyright (c) 1998 - 2005 BMC Software, Inc.
All rights reserved.

Action Request System(R)  Plug-In Server   Version 6.03.00 patch 020
Remedy, a BMC Software company.
Copyright (c) 2001 - 2005 BMC Software, Inc.
All rights reserved.


RemoteException
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused
AR System Email Engine has started

RemoteException
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is:
java.net.ConnectException: Connection refused
Loaded Web Services plugin properly
Action Request System initialization is complete.
__20060125___This posting was submitted
with HTML in it___


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"


java RemoteException issue

2007-04-17 Thread Halstead, Robert
Hey guys, we've just enabled our server group, however we're seeing this
error pop up when we start remedy.  It's a java RemoteException error.
Is this crucial for Remedy, or something to ignore?  the RemoteException
usually has to do with RMI.. I've added our ar_instal_dir/bin and
java_dir/bin to the PATH variable in arsystem file, but this doesn't
seem to solve the problem.
 
Remedy is up and running, I would like to find out why I only get this
when we enable server group though.  I'm guessing remedy is trying to
communicate with the other server for some reason via RMI.  Just a guess
though.
 
Any ideas? 
 
Here is the PATH variable in the arsystem file:
 
INSTALL_DIR=/opt/remedy/remprd
JAVADIR=:/usr/jdk/j2sdk1.4.2_08/jre:/usr/jdk/j2sdk1.4.2_08/jre/lib/sparc
/server #installer will add the ":" in front of this val
ue since it might be blank
PATH=/sbin:/usr/sbin:/usr/bin:/bin:$INSTALL_DIR/bin:/usr/jdk/j2sdk1.4.2_
08/jre/bin:$PATH; export PATH
 
 I've posted the log below.
 
Action Request System initializing.
Starting AR System Server
 
 (ARNOTE 0)
   AR Monitor version 6.03.00 patch 020 started.
 
 (ARNOTE 0)
   AR Monitor started.
 
Action Request System(R) Approval Server   Version 6.03.00.00
Remedy, a BMC Software company.  Copyright (c) 1999 - 2004 BMC Software,
Inc.  All rights reserved.
 
AR System Reconciliation Engine Version  1.00.00 patch 005
Remedy, a BMC Software company.  
Copyright (c) 2004 - 2005 BMC Software, Inc.  
All rights reserved.
 
Action Request System(R)  Server   Version 6.03.00 patch 020
Remedy, a BMC Software company.  
Copyright (c) 1991 - 2005 BMC Software, Inc.  
All rights reserved.
 
390600 : A floating license specification was ignored because it
requires a server group tag (ARERR 3329)
 
Action Request System(R)  Fork Daemon   Version 6.03.00 patch 020
Remedy, a BMC Software company.  
Copyright (c) 2000 - 2005 BMC Software, Inc.  
All rights reserved.
 
 (ARNOTE 0)
   Server indicates that it's up.
 

Action Request System  AR System Application Command Dispatcher
Version 6.03.00 patch 020
Remedy, a BMC Software company.  
Copyright (c) 1998 - 2005 BMC Software, Inc.  
All rights reserved.
 
Action Request System(R)  Plug-In Server   Version 6.03.00 patch 020
Remedy, a BMC Software company.  
Copyright (c) 2001 - 2005 BMC Software, Inc.  
All rights reserved.
 
 
RemoteException
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is: 
java.net.ConnectException: Connection refused
AR System Email Engine has started
 
RemoteException
java.rmi.ConnectException: Connection refused to host: localhost; nested
exception is: 
java.net.ConnectException: Connection refused
Loaded Web Services plugin properly
Action Request System initialization is complete.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"