java corba easerver msmq powerbuilder
Rob
We have java and powerbuilder components on a Jaguar server 4.0 using
JDK 1.3 Our business logic and processing code is written in
PowerBuilder and our service components are written in Java. Our
server has a dual Pentium 3 processor with half a gig of RAM and fast
SCSII hard discs with several gigs in capacity. Our service components
check a Microsoft Message Queue for incoming messages and dispatch
them to the appropriate business component for processing. I have one
shared java component which caches each components configuration data,
such as trace levels and other propoperties ( coming from the database
). One of our service components is a refresh component for this
shared component, ie. it sleeps for 15mins and then calls the
'of_refresh' method of the shared component. This tells the shared
component to re-load it's cached data from the database.
All up we have more than 20 service components, most of which are
listening to message queues. We communicate with the message queues
using a COM-CORBA bridge called Jacob to interface with the MSMQ API.
Now the problem is that memory is creeping up. I am wondering if this
could be due to Jaguar not having enough 'breathing' time to garbage
collect everything?
Also does anyone know of issues with loading data from the database in
a shared component using JDBC-ODBC and MSSQL 2000? Once loaded I store
the data in a java.util.Properties object referenced by an instance
variable in the shared component. I am closing database connections
and assigning the connection to null.
Also is there anyone out there with a similar environment that could
share some of their issues and resolutions? Anyone using Jaguar as a
processing server for messages coming form a Microsoft Message Queue?
Preferrably with high volume of messages, like 5000 per 24 hours. Any
architectual tips?
There are no Java Beans in our environment, as most of our components
are PowerBuilder and Java is used for service components and one
shared component.
I am not using ThreadManager, because our EAServer is a Small Business
edition and ThreadManager was creating new IIOP connections and pretty
soon I ran out of IIOP connections as there is a limit on this version
of EAServer.
Thank you for sharing any information.
Regards,
Rob.