Eclipse Community Forums: Eclipse Scout » Derby DB with ClientDriver

Home » Eclipse Projects » Eclipse Scout » Derby DB with ClientDriver

Derby DB with ClientDriver [message #1058299]

Mon, 13 May 2013 09:44

Eclipse User

Hi

I am a beginner with Eclipse scout ( and new within this forum ). i have started to learn with the minicrm example. This example is fine and it's run also after the deployment on Tomcat as a Server Web application. Now my problem is the derby DB.
i would like to integrate the DB not as Embebed (...jdbc.EmbeddedDriver).

i have connected with the example SimpleApp.jave (from derby.zip ) the derby BD
driver = "org.apache.derby.jdbc.ClientDriver";
protocol = "jdbc:derby://localhost:1527/";
connection and results are as expected.

now, i have changed simple the file "DerbySqlService.jave" with
>"org.apache.derby.jdbc.ClientDriver";
>jdbc:derby://localhost:1527/c:/DerbyDB";
deployed on Tomcat- webapps as before, start Tomcat, download the zip, start Derby Server and try the example.
the result is

Fehler

Die ursprüngliche Fehlermeldung ist:
Verarbeitungsfehler

ProcessingException[ProcessingStatus[ERROR code=0 Calling IStandardOutlineService.getCompanyTableData() / Verarbeitungsfehler]]
at org.eclipse.scout.rt.client.servicetunnel.AbstractServiceTunnel.invokeService(AbstractServiceTunnel.java:167)
at org.eclipse.scout.rt.client.servicetunnel.http.internal.InternalHttpServiceTunnel.invokeService(InternalHttpServiceTunnel.java:175)
at org.eclipse.scout.rt.client.servicetunnel.http.HttpServiceTunnel.invokeService(HttpServiceTunnel.java:115)
at org.eclipse.scout.rt.client.servicetunnel.ServiceTunnelInvocationHandler.invoke(ServiceTunnelInvocationHandler.java:47)
at $Proxy16.getCompanyTableData(Unknown Source)
at eclipse.prg.minicrm.client.ui.desktop.outlines.pages.CompanyTablePage.execLoadTableData(CompanyTablePage.java:38)
at org.eclipse.scout.rt.client.ui.desktop.outline.pages.AbstractPageWithTable.execPopulateTable(AbstractPageWithTable.java:242)
at org.eclipse.scout.rt.client.ui.desktop.outline.pages.AbstractPageWithTable.loadTableDataImpl(AbstractPageWithTable.java:652)
at org.eclipse.scout.rt.client.ui.desktop.outline.pages.AbstractPageWithTable.loadChildren(AbstractPageWithTable.java:715)
at org.eclipse.scout.rt.client.ui.basic.tree.AbstractTreeNode.ensureChildrenLoaded(AbstractTreeNode.java:909)
at org.eclipse.scout.rt.client.ui.desktop.outline.DefaultPageChangeStrategy.pageChanged(DefaultPageChangeStrategy.java:43)
at org.eclipse.scout.rt.client.ui.desktop.outline.AbstractOutline.handleActivePageChanged(AbstractOutline.java:429)
at org.eclipse.scout.rt.client.ui.desktop.outline.AbstractOutline.access$0(AbstractOutline.java:422)
at org.eclipse.scout.rt.client.ui.desktop.outline.AbstractOutline$P_OutlineListener.treeChanged(AbstractOutline.java:465)
at org.eclipse.scout.rt.client.ui.basic.tree.AbstractTree.fireTreeEventInternal(AbstractTree.java:2177)
at org.eclipse.scout.rt.client.ui.basic.tree.AbstractTree.fireNodesSelected(AbstractTree.java:2014)
at org.eclipse.scout.rt.client.ui.basic.tree.AbstractTree.selectNodes(AbstractTree.java:1659)
at org.eclipse.scout.rt.client.ui.basic.tree.AbstractTree.selectNode(AbstractTree.java:1619)
at org.eclipse.scout.rt.client.ui.desktop.AbstractDesktop.setOutline(AbstractDesktop.java:896)
at eclipse.prg.minicrm.client.ui.desktop.Desktop.execOpened(Desktop.java:71)
at org.eclipse.scout.rt.client.ui.desktop.AbstractDesktop$P_LocalDesktopExtension.desktopOpenedDelegate(AbstractDesktop.java:1730)
at org.eclipse.scout.rt.client.ui.desktop.AbstractDesktop$P_UIFacade.fireDesktopOpenedFromUI(AbstractDesktop.java:1814)
at org.eclipse.scout.rt.ui.swt.AbstractSwtEnvironment$2.run(AbstractSwtEnvironment.java:461)
at org.eclipse.scout.rt.ui.swt.concurrency.SwtScoutSynchronizer$1.runVoid(SwtScoutSynchronizer.java:60)
at org.eclipse.scout.rt.client.ClientJob.runStatus(ClientJob.java:189)
at org.eclipse.scout.rt.client.ClientJob.runTransactionWrapper(ClientJob.java:172)
at org.eclipse.scout.rt.client.ClientJob.run(ClientJob.java:159)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

how can i use thet derby-DB as a DB server?
rudolf

Re: Derby DB with ClientDriver [message #1058301 is a reply to message #1058299]

Mon, 13 May 2013 09:53

Eclipse User

I'm not sure about the Derby problem. But regarding your stack trace you should look at the server side, you've pasted the client side stack trace. If you are running your application from within Eclipse you can look at the Console view and there change to the server side output (screen like icon on the top right of the Console view).

EDIT: Screenshot:
index.php/fa/14767/0/

Attachment: ConsoleView.png
(Size: 25.89KB, Downloaded 8586 times)

[Updated on: Mon, 13 May 2013 10:02] by Moderator

Re: Derby DB with ClientDriver [message #1058310 is a reply to message #1058299]

Mon, 13 May 2013 10:19

Eclipse User

thanks for the short replay.

I have run the example without eclipe.
attached the log's

best regards
Rudolf

Attachment: localhost_access_log.2013-05-13.txt
(Size: 0.25KB, Downloaded 229 times)

Re: Derby DB with ClientDriver [message #1058311 is a reply to message #1058310]

Mon, 13 May 2013 10:24

Eclipse User

another two Log's

Attachment: catalina.2013-05-13.log
(Size: 2.69KB, Downloaded 194 times)
Attachment: localhost.2013-05-13.log
(Size: 0.65KB, Downloaded 241 times)

Re: Derby DB with ClientDriver [message #1058321 is a reply to message #1058311]

Mon, 13 May 2013 10:46

Eclipse User

Ah, those unfortunately aren't the log files we're looking for... There should also be a stack trace and some reference to
StandardOutlineService.getCompanyTableData()
where the client side log file indicated that something went wrong. I can't check right now for the default logging setup of a Scout server application. But probably you find a log file named something like <yourprojectname>.out or catalina.out. The location and naming of the log files is highly dependant on your configuration. Sad

[Updated on: Mon, 13 May 2013 10:47] by Moderator

Re: Derby DB with ClientDriver [message #1058355 is a reply to message #1058321]

Mon, 13 May 2013 12:07

Eclipse User

hi

i have searched the two files ( minicrm.out* and catalina.out* ) within my compl-PC, ( tomcat and DerbyDB is installed local) but i don't find this files. And i have no idee how i can construct the log's.

a question for my understanding
is the way to connect the DerbyDB with org.apache.derby.jdbc.ClientDriver
within a -scout Server Web application- correct or due i need a different driver pkg ?
best regards
Rudolf

Re: Derby DB with ClientDriver [message #1058360 is a reply to message #1058355]

Mon, 13 May 2013 13:10

Eclipse User

I think the driver class used as driver is defined in the "JdbcDriverName" property.

You can control it, by overriding getConfiguredJdbcDriverName in your Sql service class. (current value -- overriden in AbstractDerbySqlService):

  @Override
  protected String getConfiguredJdbcDriverName(){
    return "org.apache.derby.jdbc.EmbeddedDriver";
  }

I have no experience with org.apache.derby.jdbc.ClientDriver, I never try it. In my opinion it will work. Just add:

  @Override
  protected String getConfiguredJdbcDriverName(){
    return "org.apache.derby.jdbc.ClientDriver";
  }

[Updated on: Mon, 13 May 2013 13:11] by Moderator

Re: Derby DB with ClientDriver [message #1058364 is a reply to message #1058360]

Mon, 13 May 2013 13:47

Eclipse User

hi
thanks for the answer

getConfiguredJdbcDriverName() is overwrite and derbyDB server is running

@Override
protected String getConfiguredJdbcDriverName() {
//return "org.apache.derby.jdbc.EmbeddedDriver";
return "org.apache.derby.jdbc.ClientDriver";
}

@Override
protected String getConfiguredJdbcMappingName() {
return "jdbc:derby:localhost:1527/c:/DerbyDB";
}

due i need a different url ?

with example simpleAPP.source ( form derby.zip install)
driver = "org.apache.derby.jdbc.ClientDriver";
protocol = "jdbc:derby://localhost:1527/";
is a connection possible without any problems.

best regards
Rudolf

Re: Derby DB with ClientDriver [message #1058368 is a reply to message #1058364]

Mon, 13 May 2013 14:07

Eclipse User

I am not really not an expert in jdbc mapping name, but if your database server is running on a specific port as a service, are you sure your need "c:/DerbyDB" at the end of the name?

Maybe you need nothing, or a database identifier. With MySQL you specify the database name (db_name in this example):

  @Override
  protected String getConfiguredJdbcMappingName() {
    return "jdbc:mysql://localhost:3306/db_name";
  }

As Arthur said, it would also be usefull to see the server stacktrace. When deployed in a tomcat, if you didn't change anything it will be located in

<tomcat folder>/work/Catalina/localhost/<war name>/eclipse/configuration

Re: Derby DB with ClientDriver [message #1058374 is a reply to message #1058368]

Mon, 13 May 2013 14:32

Eclipse User

hi

i have tested with following:

scout override
@Override
protected String getConfiguredJdbcDriverName() {
//return "org.apache.derby.jdbc.EmbeddedDriver";
return "org.apache.derby.jdbc.ClientDriver";
}

@Override
protected String getConfiguredJdbcMappingName() {
String q = "jdbc:derby://localhost:1527/DerbyDB";
System.out.println(q);
return q;
}

install path
c:apache
tomcat
bin -> startNetworkServer.bat
db-derby
derbyDB -> existing derby DB

trace
!SESSION 2013-05-13 20:23:36.984 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

!ENTRY org.eclipse.scout.service 4 0 2013-05-13 20:23:36.984
!MESSAGE org.eclipse.scout.service.internal.ServicesExtensionManager.added(ServicesExtensionManager.java:195) register service: bundle=eclipse.prg.minicrm.server, service=eclipse.prg.minicrm.server.services.common.sql.Derby1SqlService
!STACK 0
java.lang.ClassNotFoundException: eclipse.prg.minicrm.server.services.common.sql.Derby1SqlService
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:340)
at org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:229)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1212)
at org.eclipse.scout.service.internal.ServicesExtensionManager.added(ServicesExtensionManager.java:105)
at org.eclipse.scout.commons.runtime.ExtensionPointTracker.open(ExtensionPointTracker.java:112)
at org.eclipse.scout.service.internal.ServicesExtensionPointTracker.access$0(ServicesExtensionPointTracker.java:1)
at org.eclipse.scout.service.internal.ServicesExtensionPointTracker$1.run(ServicesExtensionPointTracker.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

!ENTRY org.eclipse.scout.commons 2 0 2013-05-13 20:24:40.669
!MESSAGE org.eclipse.scout.commons.serialization.SerializationUtility.getBundleOrderPrefixes(SerializationUtility.java:123) bundle order prefixes are neither defined in config.ini nor as a system property. Using default value: org.eclipse.scout.commons.serialization.bundleOrderPrefixes=eclipse.prg.minicrm.,org.eclipse.scout

!ENTRY org.eclipse.scout.commons 2 0 2013-05-13 20:24:40.669
!MESSAGE org.eclipse.scout.commons.serialization.SerializationUtility.getBundleOrderPrefixes(SerializationUtility.java:123) bundle order prefixes are neither defined in config.ini nor as a system property. Using default value: org.eclipse.scout.commons.serialization.bundleOrderPrefixes=eclipse.prg.minicrm.,org.eclipse.scout

!ENTRY org.eclipse.scout.rt.shared 4 0 2013-05-13 20:24:42.169
!MESSAGE org.eclipse.scout.rt.shared.services.common.exceptionhandler.LogExceptionHandlerService.differentiatedLog(LogExceptionHandlerService.java:76) ProcessingStatus[ERROR code=0 invoking eclipse.prg.minicrm.shared.services.outline.IStandardOutlineService:getCompanyTableData / jdbcDriverName=org.apache.derby.jdbc.ClientDriver, jdbcMappingName=jdbc:derby://localhost:1527/DerbyDB / unexpected exception java.lang.ClassNotFoundException: org.apache.derby.jdbc.ClientDriver]
!STACK 0
ProcessingException[ProcessingStatus[ERROR code=0 invoking eclipse.prg.minicrm.shared.services.outline.IStandardOutlineService:getCompanyTableData / jdbcDriverName=org.apache.derby.jdbc.ClientDriver, jdbcMappingName=jdbc:derby://localhost:1527/DerbyDB / unexpected exception java.lang.ClassNotFoundException: org.apache.derby.jdbc.ClientDriver]]
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.leaseConnectionInternal(AbstractSqlService.java:637)
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.execCreateConnection(AbstractSqlService.java:288)
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.leaseConnection(AbstractSqlService.java:613)
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.getTransaction(AbstractSqlService.java:689)
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.select(AbstractSqlService.java:727)
at org.eclipse.scout.rt.server.services.common.jdbc.SQL.select(SQL.java:101)
at eclipse.prg.minicrm.server.services.outline.StandardOutlineService.getCompanyTableData(StandardOutlineService.java:28)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.scout.service.ServiceUtility.invoke(ServiceUtility.java:172)
at org.eclipse.scout.rt.server.DefaultTransactionDelegate.invokeImpl(DefaultTransactionDelegate.java:218)
at org.eclipse.scout.rt.server.DefaultTransactionDelegate.invoke(DefaultTransactionDelegate.java:92)
at org.eclipse.scout.rt.server.ServiceTunnelServlet.runServerJobTransactionWithDelegate(ServiceTunnelServlet.java:392)
at org.eclipse.scout.rt.server.ServiceTunnelServlet.runServerJobTransaction(ServiceTunnelServlet.java:388)
at org.eclipse.scout.rt.server.ServiceTunnelServlet$RemoteServiceJob.runTransaction(ServiceTunnelServlet.java:416)
at org.eclipse.scout.rt.server.ServerJob.runTransactionWrapper(ServerJob.java:202)
at org.eclipse.scout.rt.server.ServerJob.access$0(ServerJob.java:190)
at org.eclipse.scout.rt.server.ServerJob$1.run(ServerJob.java:161)
at org.eclipse.scout.rt.server.ServerJob$1.run(ServerJob.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.eclipse.scout.rt.server.ServerJob.run(ServerJob.java:156)
at org.eclipse.scout.commons.job.JobEx.runNow(JobEx.java:50)
at org.eclipse.scout.rt.server.ServerJob.runNow(ServerJob.java:148)
at org.eclipse.scout.rt.server.ServiceTunnelServlet.doPost(ServiceTunnelServlet.java:297)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.eclipse.scout.http.servletfilter.HttpServletEx.access$0(HttpServletEx.java:1)
at org.eclipse.scout.http.servletfilter.HttpServletEx$1.service(HttpServletEx.java:38)
at org.eclipse.scout.http.servletfilter.internal.FilterChainImpl.doFilter(FilterChainImpl.java:44)
at org.eclipse.scout.http.servletfilter.helper.HttpAuthJaasFilter.doFilter(HttpAuthJaasFilter.java:62)
at org.eclipse.scout.http.servletfilter.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
at org.eclipse.scout.http.servletfilter.helper.DevelopmentAuthFilter.doFilter(DevelopmentAuthFilter.java:61)
at org.eclipse.scout.http.servletfilter.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
at org.eclipse.scout.http.servletfilter.security.AbstractChainableSecurityFilter.doFilterInternal(AbstractChainableSecurityFilter.java:220)
at org.eclipse.scout.http.servletfilter.security.AbstractChainableSecurityFilter.access$0(AbstractChainableSecurityFilter.java:219)
at org.eclipse.scout.http.servletfilter.security.AbstractChainableSecurityFilter$1.run(AbstractChainableSecurityFilter.java:157)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.eclipse.scout.http.servletfilter.security.AbstractChainableSecurityFilter.doFilter(AbstractChainableSecurityFilter.java:149)
at org.eclipse.scout.http.servletfilter.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
at org.eclipse.scout.http.servletfilter.security.AbstractChainableSecurityFilter.doFilter(AbstractChainableSecurityFilter.java:103)
at org.eclipse.scout.http.servletfilter.internal.FilterChainImpl.doFilter(FilterChainImpl.java:41)
at org.eclipse.scout.http.servletfilter.ServletFilterDelegate.delegateServiceMethod(ServletFilterDelegate.java:57)
at org.eclipse.scout.http.servletfilter.HttpServletEx.service(HttpServletEx.java:35)
at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:947)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1009)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassNotFoundException: org.apache.derby.jdbc.ClientDriver
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:169)
at org.eclipse.scout.rt.server.services.common.jdbc.internal.pool.SqlConnectionBuilder.createJdbcConnection(SqlConnectionBuilder.java:35)
at org.eclipse.scout.rt.server.services.common.jdbc.internal.pool.SqlConnectionPool.leaseConnection(SqlConnectionPool.java:102)
at org.eclipse.scout.rt.server.services.common.jdbc.AbstractSqlService.leaseConnectionInternal(AbstractSqlService.java:621)
... 69 more

Re: Derby DB with ClientDriver [message #1058432 is a reply to message #1058374]

Tue, 14 May 2013 01:46

Eclipse User

Caused by: java.lang.ClassNotFoundException: org.apache.derby.jdbc.ClientDriver
is the interesting line of your stack trace. Either you have a problem with the setup of your MANIFEST.MFs and/or libraries or this isn't the correct class at all. I unfortunately don't have time to look into this and I have never used the Derby ClientDriver class.

Re: Derby DB with ClientDriver [message #1058433 is a reply to message #1058432]

Tue, 14 May 2013 01:55

Eclipse User

Sorry for the wrong advice I gave yesterday. I had a better look at apache derby. According to this stackoverflow question, there are 2 different jars:

* derby.jar (the one included in scout with the bundle org.apache.derby.jdbc_1091.fragment)
* derbyclient.jar

The second one contains the driver you are looking for. You need to include it at runtime (be aware that you are in an OSGi Application). I am not sure if there is an OSGi bundle containing this derbyclient.jar out of the box.

In a nutshell, the derby support from scout uses the EmbeddedDriver. Setting up the scout server to use the derby ClientDriver not so complicated. Do not hesitate to ask question here if you are blocked.
This page might also help: how to write a jdbc connection bundle.

Re: Derby DB with ClientDriver [message #1058479 is a reply to message #1058433]

Tue, 14 May 2013 06:25

Eclipse User

hi

Many thanks for your help and spending time for my problem.

org.apache.derby.jdbc.ClientDriver is ok. minicrm test is running within Eclipse-Scout and on Tomcat.

best regards
Rudolf

Previous Topic:	Any plans to improve the CalendarField component
Next Topic:	ThreadContext.get() / put()

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 03 12:57:56 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter