php-java-bridge-users Mailing List for PHP/Java Bridge

Hello,

Can someone please share the details on how to get PJB configured
successfully with Joomla? My requirement is as follows...

1) Have an existing J2EE application that is working under Tomcat
2) I would like to use Joomla as a front end to it for managing the CMS
functions..

I am trying to use PJB to bridge these two applications so that I manage the
sessions, single sign on etc...

I have dowloaded the PJB 5.5.4.1 followed the JavaBridge configuration steps
and placed the required libs under the tomcat app, and when I copied the
Joomla folder and accessed it is giving the following error..

*Database Error: Unable to connect to the database:The MySQL adapter "mysql"
is not available.*

Any ideas on how to resolve this? I greatly appreciate it..

Thanks
RS

Jetty still seems to not work without the 15 second delay. Promiscuous
is off and based on the Jetty output below I am sure that I am bound
to 127.0.0.1. In Java.inc I a have define ("JAVA_HOSTS",
"127.0.0.1:8080");

2010-02-14 12:35:32.466:INFO::Started SelectChannelConnector@127.0.0.1:8080
2010-02-14 12:35:46.904:INFO:/JavaBridge:PhpJavaServlet: PHP/Java
Bridge servlet D:\Programs\jetty-hightide-7.0.1.v20091125\webapps\JavaBridge
version 5.5.4.1 ready.

Do I need anything in the web.xml or properties to specifically enable
SocketContextServer?

Thanks,

McKinley

On Sun, Feb 14, 2010 at 5:49 PM,
<php...@li...> wrote:
> PHP/Java Bridge version 5.5.4 still contains  "ContextRunners" which
> will be used if(LOCAL_ADDR.equals(req.getRemoteAddr()) && contextServer!
> If you install jetty on
> the local host and do not switch off the SocketContextServer, the bridge
> will still work with Jetty.
>
> If you switch off promiscuous mode again and run jetty on localhost (ip:
> 127.0.0.1), it should work.

Thanks for explaining the other options. I'll try it out. I am using
Jetty 7.0.1 on Windows Server 2003 with IIS.

Thanks,

McKinley

On Sun, Feb 14, 2010 at 5:49 PM,
<php...@li...> wrote:

> We have tested this with Oracle/Bea WebLogic, Sun Application server,
> Glassfish, Tomcat.
>
> Servlet engines which do not flush their output immediately cannot use
> chunked encoding to implement a two-way connection.
>
> PHP/Java Bridge version 5.5.4 still contains  "ContextRunners" which
> will be used if(LOCAL_ADDR.equals(req.getRemoteAddr()) && contextServer!
> =null && contextServer.isAvailable(channel)). If you install jetty on
> the local host and do not switch off the SocketContextServer, the bridge
> will still work with Jetty.
>
> Which Jetty version and which operating system version do you use?

Hi,

PHP/Java Bridge version >= 5.5.4 uses HTTP/1.1 chunked connections to
communicate with the servlet. From the NEWS file:
-----

* If the Java environment doesn't allow java.lang.Threads, Sockets, or
  if the back end doesn't run on localhost
  ("127.0.0.1".equals(req.getRemoteAddr()), or if the promiscuous
  option is set, the bridge now uses a HTTP tunnel to communicate with
  the back end.  Example:

  --
  telnet YOURHOST.com 8080 
PUT /JavaBridge/foo.phpjavabridge HTTP/1.1
Host: YOURHOST.com:8080
Transfer-Encoding: chunked

22
<H p="1" v="java.lang.String"></H>
b
<F p="E" />
0

-----

We have tested this with Oracle/Bea WebLogic, Sun Application server,
Glassfish, Tomcat.

Servlet engines which do not flush their output immediately cannot use
chunked encoding to implement a two-way connection.

PHP/Java Bridge version 5.5.4 still contains  "ContextRunners" which
will be used if(LOCAL_ADDR.equals(req.getRemoteAddr()) && contextServer!
=null && contextServer.isAvailable(channel)). If you install jetty on
the local host and do not switch off the SocketContextServer, the bridge
will still work with Jetty.


> tried to properly set promiscuous mode

If you switch off promiscuous mode again and run jetty on localhost (ip:
127.0.0.1), it should work.


But I am currently preparing PHP/Java Bridge version 6.0.0, which will
not contain these ContextServers anymore; chunked connections will be
the only way to communicate with the servlet.

I will try to find a workaround. In the worst case we'll have flag Jetty
as unsupported.

Which Jetty version and which operating system version do you use?



Regards,
Jost Bökemeier

I am using the JavaBridge template war for version 5.5.4.1 on Jetty. I
am using PHP on a separate IIS server. Running test.php on IIS with
the Java.inc from the Jetty server has this behavior Jetty. The
request begins, exactly 15 seconds pass, and then the request
completes showing all the Java System properties. So, it works, but
only after exactly 15000 ms.

On Tomcat the same arrangement completes the request instantly. I have
tried various settings in the 'define' section of Java.inc. I have
tried to properly set promiscuous mode in the web.xml file.

The only other clue is that if I test with a telnet PUT the console
output of Jetty says:

2010-02-14 06:36:43.029:INFO:/JavaBridge:handleHttpConnection init failed

Any idea what I should do to diagnose the problem with Jetty?