Thread: Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

Brought to you by: andremachado, gromwe, jon_koerber, jost_boekemeier, kai_londenberg

php-java-bridge-users

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-03-27 09:25:09

Hi Jost,

I see this in my java.ini (which was autoinstalled):
-------
;; If you want to start the default JVM automatically when the HTTP
;; server starts, disable java.hosts, java.servlet and
;; java.socketname, set java.java_home=<VM_HOME> and
;; java.java=<VM_EXE>, for example:
-------
And I've been successfully using this 'method' on a different server using
v4.x of the php java bridge. That server does not run any servlet engine
excepting that which is autostarted by the java bridge. Does anyone else use
this 'method' for lightweight java access?

Another thing is, in the example that you had given,
http://php-java-bridge.sourceforge.net/pjb/examples/source.php?source=startJava.php
it includes this line:
require_once("java/Java.inc");
Do I just extract and place this Java.inc in the required directory
manually? Is that the way to do it?

Warm Regards,
Thangaraj


-------------
Hi,

The bridge cannot "autostart". Basically you write or include() PHP code to
connect to a Java back end and then use the provided VM bridge protocol to
invoke java and/or php code.

If you want to manage a java back end from PHP, use PHP exec() and
java("java.lang.System")->exit(), please see this example for details:
http://php-java-bridge.sourceforge.net/pjb/examples/source.php?source=startJava.php

Please remove all php "java.so" and "php_java.dll" you can find and then
follow the install instructions on
http://php-java-bridge.sourceforge.net/pjb/installation.php

Regards,
Jost Boekemeier

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-03-27 09:59:42

We used to use a binary protocol in 1.x. It has since been replaced by a
faster XML protocol mechanism. We have deprecated (4.x) and then removed
(v5.x) all native code so that the bridge runs on any cpu, php or java
version.

You need a PHP "Java" class, yes. Either this one
http://php-java-bridge.sourceforge.net/pjb/java/Java.inc or the simple PHP
code from our FAQ.

Regards,
Jost Boekemeier

Mrz 27, 2009 10:28 vorm. schrieb am <
php...@li...>:

Hi Jost,

I see this in my java.ini (which was autoinstalled):
-------
;; If you want to start the default JVM automatically when the HTTP
;; server starts, disable java.hosts, java.servlet and
;; java.socketname, set java.java_home=<VM_HOME> and
;; java.java=<VM_EXE>, for example:
-------
And I've been successfully using this 'method' on a different server using
v4.x of the php java bridge. That server does not run any servlet engine
excepting that which is autostarted by the java bridge. Does anyone else use
this 'method' for lightweight java access?

Another thing is, in the example that you had given,

http://php-java-bridge.sourceforge.net/pjb/examples/source.php?source=startJava.php
it includes this line:
require_once("java/Java.inc");
Do I just extract and place this Java.inc in the required directory
manually? Is that the way to do it?

Warm Regards,
Thangaraj


-------------

Hi, The bridge cannot "autostart". Basically you write or include() PHP code
to connect to a Java b...

------------------------------------------------------------------------------
_____________________...

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-03-28 08:21:54

Ok. So is it possible to use the 4.x version of the bridge to make this
thing work?

But when I compiled v4.3.2, I still get the same error.
----
PHP Warning:  php_mod_java(105) system error: Could not execute backend:
JAVA_HOME=/usr/java/j2sdk1.4.2_19
LD_LIBRARY_PATH=/usr/lib64/php/modules:/usr/lib64/php/modules:
/usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
-Djava.library.path=/usr/lib64/php/modules
-Djava.class.path=/usr/lib64/php/modules/JavaBridge.jar
-Djava.awt.headless=true -Dphp.java.bridge.base=/usr/lib64/php/modules
php.java.bridge.Standalone INET_LOCAL:0 4 /var/log/php-java-bridge.log :
Permission denied in Unknown on line 0
----
And again, running the command
--
/usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
-Djava.library.path=/usr/lib64/php/modules
-Djava.class.path=/usr/lib64/php/modules/JavaBridge.jar
-Djava.awt.headless=true -Dphp.java.bridge.base=/usr/lib64/php/modules
php.java.bridge.Standalone INET_LOCAL:0 4 /var/log/php-java-bridge.log
--
does not give any error.

So now, nobody has any suggestion to solve this, I'll have to try running
Tomcat or some other servlet runner. Have anyone used winstone
http://winstone.sourceforge.net/
to run the bridge? I'm just trying to stay lightweight. Any other
recommendations are welcome of course.

btw, I did try, at one time, running the war file with winstone, but ended
up getting an internal server error whenever the server is accessed at port
8080. So if there is no other option, I'll go with tomcat.

Thank you for the support, Jost. I appreciate it.

------
We used to use a binary protocol in 1.x. It has since been replaced by a
faster XML protocol mechanism. We have deprecated (4.x) and then removed
(v5.x) all native code so that the bridge runs on any cpu, php or java
version.

You need a PHP "Java" class, yes. Either this one
http://php-java-bridge.sourceforge.net/pjb/java/Java.inc or the simple PHP
code from our FAQ.

Regards,
Jost Boekemeier


On Fri, Mar 27, 2009 at 2:54 PM, Thangaraj (www.bootcd.us) <
tha...@gm...> wrote:

> Hi Jost,
>
> I see this in my java.ini (which was autoinstalled):
> -------
> ;; If you want to start the default JVM automatically when the HTTP
> ;; server starts, disable java.hosts, java.servlet and
> ;; java.socketname, set java.java_home=<VM_HOME> and
> ;; java.java=<VM_EXE>, for example:
> -------
> And I've been successfully using this 'method' on a different server using
> v4.x of the php java bridge. That server does not run any servlet engine
> excepting that which is autostarted by the java bridge. Does anyone else use
> this 'method' for lightweight java access?
>
> Another thing is, in the example that you had given,
>
> http://php-java-bridge.sourceforge.net/pjb/examples/source.php?source=startJava.php
> it includes this line:
> require_once("java/Java.inc");
> Do I just extract and place this Java.inc in the required directory
> manually? Is that the way to do it?
>
> Warm Regards,
> Thangaraj
>
>
> -------------
> Hi,
>
> The bridge cannot "autostart". Basically you write or include() PHP code to
> connect to a Java back end and then use the provided VM bridge protocol to
> invoke java and/or php code.
>
> If you want to manage a java back end from PHP, use PHP exec() and
> java("java.lang.System")->exit(), please see this example for details:
>
> http://php-java-bridge.sourceforge.net/pjb/examples/source.php?source=startJava.php
>
> Please remove all php "java.so" and "php_java.dll" you can find and then
> follow the install instructions on
> http://php-java-bridge.sourceforge.net/pjb/installation.php
>
> Regards,
> Jost Boekemeier
>



-- 
www.ishafoundation.org
www.projectgreenhands.org
www.bootcd.us
www.ecobuddy.in

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-03-28 08:48:18

Hi,

the 32/64 bit cpu/jvm issue you observed was one of the reasons for the
switch.

The bridge runs with any servlet engine out there, it even works with the
simple http server build into JavaBride.jar: java -jar JavaBridge.jar.

But for features like hot deployment, persistent connections, module
managemant, etc. you'll need tomcat or some other j2ee ontainer anyway.

On RedHat/Fedora or compatibles just do a

  yum -y install tomcat php
  rpmbuild -tb php-java-bridge*.tar.gz
  rpm -i php-java-bridge*.rpm

Regards,
Jost Boekemeier

Mrz 28, 2009 9:22 vorm. schrieb am <
php...@li...>:

Ok. So is it possible to use the 4.x version of the bridge to make this
thing work?

But when I compiled v4.3.2, I still get the same error.
----

PHP Warning: php_mod_java(105) system error: Could not execute backend:
JAVA_HOME=/usr/java/j2sdk1....

/usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
-Djava.library.path=/usr/lib64...
And again, running the command
--

/usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
-Djava.library.path=/usr/lib64...
--
does not give any error.

So now, nobody has any suggestion to solve this, I'll have to try running
Tomcat or some other servlet runner. Have anyone used winstone
http://winstone.sourceforge.net/
to run the bridge? I'm just trying to stay lightweight. Any other
recommendations are welcome of course.

btw, I did try, at one time, running the war file with winstone, but ended
up getting an internal server error whenever the server is accessed at port
8080. So if there is no other option, I'll go with tomcat.

Thank you for the support, Jost. I appreciate it.

------

We used to use a binary protocol in 1.x. It has since been replaced by a
faster XML protocol mechani...

On Fri, Mar 27, 2009 at 2:54 PM, Thangaraj (www.bootcd.us) <
tha...@gm...> wrote: > Hi Jost...

www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
www.ecobuddy.in ---------------------...

php-java-bridge-users mailing list
php...@li... https://lists.sourcef...

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-04-19 15:39:49

Jost,
We're finally going the tomcat route. But when building the rpm (rpmbuild
-tb php-java-bridge*.tar.gz), I always get an error message:
--
jc1: error: unrecognized command line option "-ftarget=1.4"
--
regardless of the java bridge version I am using. I've tried
php-java-bridge_5.2.2.4.tar.gz
 php-java-bridge_5.4.3.3.tar.gz
php-java-bridge_5.3.4.1.tar.gz and
 php-java-bridge_5.4.4.tar.gz


Am I missing something?

In the course of installing tomcat I've had to install the following:

Installed: tomcat5.x86_64 0:5.5.23-0jpp.7.el5_2.1
Dependency Installed: ant.x86_64 0:1.6.5-2jpp.2 axis.x86_64 0:1.2.1-2jpp.6
bcel.x86_64 0:5.1-8jpp.1 classpathx-jaf.x86_64 0:1.0-9jpp.1
classpathx-mail.x86_64 0:1.1.1-4jpp.2 eclipse-ecj.x86_64
1:3.2.1-19.el5.centos geronimo-specs.x86_64 0:1.0-0.M2.2jpp.12.el5.centos
geronimo-specs-compat.x86_64 0:1.0-0.M2.2jpp.12.el5.centos giflib.x86_64
0:4.1.3-7.1.el5.1 jakarta-commons-beanutils.x86_64 0:1.7.0-5jpp.1
jakarta-commons-collections.x86_64 0:3.2-2jpp.3
jakarta-commons-daemon.x86_64 1:1.0.1-6jpp.1 jakarta-commons-dbcp.x86_64
0:1.2.1-7jpp.1 jakarta-commons-digester.x86_64 0:1.7-5jpp.1
jakarta-commons-discovery.x86_64 1:0.3-4jpp.1 jakarta-commons-el.x86_64
0:1.0-7jpp.1 jakarta-commons-fileupload.x86_64 1:1.0-6jpp.1
jakarta-commons-httpclient.x86_64 1:3.0-7jpp.1
jakarta-commons-launcher.x86_64 0:0.9-6jpp.1 jakarta-commons-logging.x86_64
0:1.0.4-6jpp.1 jakarta-commons-modeler.x86_64 0:1.1-8jpp.3.el5
jakarta-commons-pool.x86_64 0:1.3-5jpp.1 java-1.6.0-openjdk.x86_64
1:1.6.0.0-0.30.b09.el5 java-1.6.0-openjdk-devel.x86_64
1:1.6.0.0-0.30.b09.el5 ldapjdk.x86_64 0:4.18-2jpp.3.el5 log4j.x86_64
0:1.2.13-3jpp.2 mx4j.x86_64 1:3.0.1-6jpp.4 regexp.x86_64 0:1.4-2jpp.2
tomcat5-common-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1 tomcat5-jasper.x86_64
0:5.5.23-0jpp.7.el5_2.1 tomcat5-jsp-2.0-api.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-server-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-servlet-2.4-api.x86_64 0:5.5.23-0jpp.7.el5_2.1 ws
Installed: gcc-java.x86_64 0:4.1.2-44.el5 mono-core.x86_64
0:1.2.4-2.el5.centos selinux-policy-devel.noarch 0:2.4.6-203.el5
Dependency Installed: libgcj-devel.x86_64 0:4.1.2-44.el5 libgdiplus.x86_64
0:1.2.5-1.el5.centos
Updated: cpp.x86_64 0:4.1.2-44.el5 gcc.x86_64 0:4.1.2-44.el5 libgcc.i386
0:4.1.2-44.el5 libgcc.x86_64 0:4.1.2-44.el5 libgcj.x86_64 0:4.1.2-44.el5
libgfortran.x86_64 0:4.1.2-44.el5 libgomp.x86_64 0:4.3.2-7.el5
libstdc++.x86_64 0:4.1.2-44.el5 libstdc++.i386 0:4.1.2-44.el5
libstdc++-devel.x86_64 0:4.1.2-44.el5 selinux-policy.noarch 0:2.4.6-203.el5
Dependency Updated: gcc-c++.x86_64 0:4.1.2-44.el5 gcc-gfortran.x86_64
0:4.1.2-44.el5 selinux-policy-targeted.noarch 0:2.4.6-203.el5
Complete!

Installed: xml-commons-apis.x86_64 0:1.3.02-0.b2.7jpp.10
Complete!

Here's the error line:
---
cat META-INF/java/JavaBridge.inc META-INF/java/Options.inc
META-INF/java/Client.inc META-INF/java/GlobalRef.inc
META-INF/java/NativeParser.inc META-INF/java/Parser.inc
META-INF/java/Protocol.inc META-INF/java/SimpleParser.inc
META-INF/java/JavaProxy.inc | sed -f extract.sed | sed '/^\/\*/,/\*\/$/d'
>JavaRaw.inc
cat JavaRaw.inc | sed -f append.sed | sed
's/JAVA/MONO/g;s/java/mono/g;s/Java/Mono/g;s/updateJarLibraryPath/updateLibraryPath/;s/^.*do
not delete this line.*$/$name="cli.".$name;/;' >META-INF/java/Mono.inc
gcj -w -ftarget=1.4 -classpath .:script-api.jar -C php/java/bridge/*.java
php/java/bridge/http/*.java
jc1: error: unrecognized command line option "-ftarget=1.4"
make[1]: *** [MonoBridge.exe] Error 1
make[1]: Leaving directory
`/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/server'
make: *** [/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/modules/stamp]
Error 2
error: Bad exit status from /var/tmp/rpm-tmp.83378 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.83378 (%build)
---

Help!

Warm Regards,
Thangaraj


On Sat, Mar 28, 2009 at 2:18 PM, <
php...@li...> wrote:

> Hi,
>
> the 32/64 bit cpu/jvm issue you observed was one of the reasons for the
> switch.
>
> The bridge runs with any servlet engine out there, it even works with the
> simple http server build into JavaBride.jar: java -jar JavaBridge.jar.
>
> But for features like hot deployment, persistent connections, module
> managemant, etc. you'll need tomcat or some other j2ee ontainer anyway.
>
> On RedHat/Fedora or compatibles just do a
>
>  yum -y install tomcat php
>  rpmbuild -tb php-java-bridge*.tar.gz
>  rpm -i php-java-bridge*.rpm
>
> Regards,
> Jost Boekemeier
>
> Mrz 28, 2009 9:22 vorm. schrieb am <
> php...@li...>:
>
> Ok. So is it possible to use the 4.x version of the bridge to make this
> thing work?
>
> But when I compiled v4.3.2, I still get the same error.
> ----
>
> PHP Warning: php_mod_java(105) system error: Could not execute backend:
> JAVA_HOME=/usr/java/j2sdk1....
>
> /usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
> -Djava.library.path=/usr/lib64...
> And again, running the command
> --
>
> /usr/lib64/php/modules/RunJavaBridge /usr/java/j2sdk1.4.2_19/bin/java
> -Djava.library.path=/usr/lib64...
> --
> does not give any error.
>
> So now, nobody has any suggestion to solve this, I'll have to try running
> Tomcat or some other servlet runner. Have anyone used winstone
> http://winstone.sourceforge.net/
> to run the bridge? I'm just trying to stay lightweight. Any other
> recommendations are welcome of course.
>
> btw, I did try, at one time, running the war file with winstone, but ended
> up getting an internal server error whenever the server is accessed at port
> 8080. So if there is no other option, I'll go with tomcat.
>
> Thank you for the support, Jost. I appreciate it.
>
> ------
>
> We used to use a binary protocol in 1.x. It has since been replaced by a
> faster XML protocol mechani...
>
> On Fri, Mar 27, 2009 at 2:54 PM, Thangaraj (www.bootcd.us) <
> tha...@gm...> wrote: > Hi Jost...
>
> www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
> www.ecobuddy.in ---------------------...
>
> php-java-bridge-users mailing list
> php...@li... https://lists.sourcef...
>
> ------------------------------------------------------------------------------
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>



-- 
www.ishafoundation.org
www.projectgreenhands.org
www.bootcd.us
www.ecobuddy.in

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-04-19 17:14:53

[-ftarget flag missing]
Doesn't gcc 4.1.2 shipped with RHEL5.3 support this flag?

I will check this and add a fix, if necessary.

Regards,
Jost Boekemeier

Apr 19, 2009 5:41 nachm. schrieb am <
php...@li...>:

Jost,
We're finally going the tomcat route. But when building the rpm (rpmbuild
-tb php-java-bridge*.tar.gz), I always get an error message:
--
jc1: error: unrecognized command line option "-ftarget=1.4"
--
regardless of the java bridge version I am using. I've tried
php-java-bridge_5.2.2.4.tar.gz
 php-java-bridge_5.4.3.3.tar.gz
php-java-bridge_5.3.4.1.tar.gz and
 php-java-bridge_5.4.4.tar.gz


Am I missing something?

In the course of installing tomcat I've had to install the following:

Installed: tomcat5.x86_64 0:5.5.23-0jpp.7.el5_2.1
Dependency Installed: ant.x86_64 0:1.6.5-2jpp.2 axis.x86_64 0:1.2.1-2jpp.6
bcel.x86_64 0:5.1-8jpp.1 classpathx-jaf.x86_64 0:1.0-9jpp.1
classpathx-mail.x86_64 0:1.1.1-4jpp.2 eclipse-ecj.x86_64
1:3.2.1-19.el5.centos geronimo-specs.x86_64 0:1.0-0.M2.2jpp.12.el5.centos
geronimo-specs-compat.x86_64 0:1.0-0.M2.2jpp.12.el5.centos giflib.x86_64
0:4.1.3-7.1.el5.1 jakarta-commons-beanutils.x86_64 0:1.7.0-5jpp.1
jakarta-commons-collections.x86_64 0:3.2-2jpp.3
jakarta-commons-daemon.x86_64 1:1.0.1-6jpp.1 jakarta-commons-dbcp.x86_64
0:1.2.1-7jpp.1 jakarta-commons-digester.x86_64 0:1.7-5jpp.1
jakarta-commons-discovery.x86_64 1:0.3-4jpp.1 jakarta-commons-el.x86_64
0:1.0-7jpp.1 jakarta-commons-fileupload.x86_64 1:1.0-6jpp.1
jakarta-commons-httpclient.x86_64 1:3.0-7jpp.1
jakarta-commons-launcher.x86_64 0:0.9-6jpp.1 jakarta-commons-logging.x86_64
0:1.0.4-6jpp.1 jakarta-commons-modeler.x86_64 0:1.1-8jpp.3.el5
jakarta-commons-pool.x86_64 0:1.3-5jpp.1 java-1.6.0-openjdk.x86_64
1:1.6.0.0-0.30.b09.el5 java-1.6.0-openjdk-devel.x86_64
1:1.6.0.0-0.30.b09.el5 ldapjdk.x86_64 0:4.18-2jpp.3.el5 log4j.x86_64
0:1.2.13-3jpp.2 mx4j.x86_64 1:3.0.1-6jpp.4 regexp.x86_64 0:1.4-2jpp.2
tomcat5-common-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1 tomcat5-jasper.x86_64
0:5.5.23-0jpp.7.el5_2.1 tomcat5-jsp-2.0-api.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-server-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-servlet-2.4-api.x86_64 0:5.5.23-0jpp.7.el5_2.1 ws
Installed: gcc-java.x86_64 0:4.1.2-44.el5 mono-core.x86_64
0:1.2.4-2.el5.centos selinux-policy-devel.noarch 0:2.4.6-203.el5
Dependency Installed: libgcj-devel.x86_64 0:4.1.2-44.el5 libgdiplus.x86_64
0:1.2.5-1.el5.centos
Updated: cpp.x86_64 0:4.1.2-44.el5 gcc.x86_64 0:4.1.2-44.el5 libgcc.i386
0:4.1.2-44.el5 libgcc.x86_64 0:4.1.2-44.el5 libgcj.x86_64 0:4.1.2-44.el5
libgfortran.x86_64 0:4.1.2-44.el5 libgomp.x86_64 0:4.3.2-7.el5
libstdc++.x86_64 0:4.1.2-44.el5 libstdc++.i386 0:4.1.2-44.el5
libstdc++-devel.x86_64 0:4.1.2-44.el5 selinux-policy.noarch 0:2.4.6-203.el5
Dependency Updated: gcc-c++.x86_64 0:4.1.2-44.el5 gcc-gfortran.x86_64
0:4.1.2-44.el5 selinux-policy-targeted.noarch 0:2.4.6-203.el5
Complete!

Installed: xml-commons-apis.x86_64 0:1.3.02-0.b2.7jpp.10
Complete!

Here's the error line:
---
cat META-INF/java/JavaBridge.inc META-INF/java/Options.inc
META-INF/java/Client.inc META-INF/java/GlobalRef.inc
META-INF/java/NativeParser.inc META-INF/java/Parser.inc
META-INF/java/Protocol.inc META-INF/java/SimpleParser.inc
META-INF/java/JavaProxy.inc | sed -f extract.sed | sed '/^\/\*/,/\*\/$/d'
>JavaRaw.inc
cat JavaRaw.inc | sed -f append.sed | sed
's/JAVA/MONO/g;s/java/mono/g;s/Java/Mono/g;s/updateJarLibraryPath/updateLibraryPath/;s/^.*do
not delete this line.*$/$name="cli.".$name;/;' >META-INF/java/Mono.inc
gcj -w -ftarget=1.4 -classpath .:script-api.jar -C php/java/bridge/*.java
php/java/bridge/http/*.java
jc1: error: unrecognized command line option "-ftarget=1.4"
make[1]: *** [MonoBridge.exe] Error 1
make[1]: Leaving directory
`/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/server'
make: *** [/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/modules/stamp]
Error 2
error: Bad exit status from /var/tmp/rpm-tmp.83378 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.83378 (%build)
---

Help!

Warm Regards,
Thangaraj

On Sat, Mar 28, 2009 at 2:18 PM, <
php...@li...> wrote: > Hi, > > ...
>
------------------------------------------------------------------------------
> _______________________________________________

> php-java-bridge-users mailing list >
php...@li...

> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users >
--

www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
www.ecobuddy.in
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________

php-java-bridge-users mailing list
php...@li...

https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-04-20 08:24:51

Thank you very much for the bug report.

This will be fixed in PHP/Java Bridge version 5.4.4.2.

As a workaround please edit Makefile.am within php-java-bridge*.tar.gz and
remove the text "-ftarget=1.4".
Or please use the binary download instead.

Regards,
Jost Boekemeier

Apr 19, 2009 7:14 nachm. schrieb am "Jost Bekemeier" <
jos...@go...>:

[-ftarget flag missing]
Doesn't gcc 4.1.2 shipped with RHEL5.3 support this flag?

I will check this and add a fix, if necessary.

Regards,
Jost Boekemeier

Apr 19, 2009 5:41 nachm. schrieb am <
php...@li...>:

Jost,
We're finally going the tomcat route. But when building the rpm (rpmbuild
-tb php-java-bridge*.tar.gz), I always get an error message:
--
jc1: error: unrecognized command line option "-ftarget=1.4"
--
regardless of the java bridge version I am using. I've tried
php-java-bridge_5.2.2.4.tar.gz
 php-java-bridge_5.4.3.3.tar.gz
php-java-bridge_5.3.4.1.tar.gz and
 php-java-bridge_5.4.4.tar.gz


Am I missing something?

In the course of installing tomcat I've had to install the following:

Installed: tomcat5.x86_64 0:5.5.23-0jpp.7.el5_2.1
Dependency Installed: ant.x86_64 0:1.6.5-2jpp.2 axis.x86_64 0:1.2.1-2jpp.6
bcel.x86_64 0:5.1-8jpp.1 classpathx-jaf.x86_64 0:1.0-9jpp.1
classpathx-mail.x86_64 0:1.1.1-4jpp.2 eclipse-ecj.x86_64
1:3.2.1-19.el5.centos geronimo-specs.x86_64 0:1.0-0.M2.2jpp.12.el5.centos
geronimo-specs-compat.x86_64 0:1.0-0.M2.2jpp.12.el5.centos giflib.x86_64
0:4.1.3-7.1.el5.1 jakarta-commons-beanutils.x86_64 0:1.7.0-5jpp.1
jakarta-commons-collections.x86_64 0:3.2-2jpp.3
jakarta-commons-daemon.x86_64 1:1.0.1-6jpp.1 jakarta-commons-dbcp.x86_64
0:1.2.1-7jpp.1 jakarta-commons-digester.x86_64 0:1.7-5jpp.1
jakarta-commons-discovery.x86_64 1:0.3-4jpp.1 jakarta-commons-el.x86_64
0:1.0-7jpp.1 jakarta-commons-fileupload.x86_64 1:1.0-6jpp.1
jakarta-commons-httpclient.x86_64 1:3.0-7jpp.1
jakarta-commons-launcher.x86_64 0:0.9-6jpp.1 jakarta-commons-logging.x86_64
0:1.0.4-6jpp.1 jakarta-commons-modeler.x86_64 0:1.1-8jpp.3.el5
jakarta-commons-pool.x86_64 0:1.3-5jpp.1 java-1.6.0-openjdk.x86_64
1:1.6.0.0-0.30.b09.el5 java-1.6.0-openjdk-devel.x86_64
1:1.6.0.0-0.30.b09.el5 ldapjdk.x86_64 0:4.18-2jpp.3.el5 log4j.x86_64
0:1.2.13-3jpp.2 mx4j.x86_64 1:3.0.1-6jpp.4 regexp.x86_64 0:1.4-2jpp.2
tomcat5-common-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1 tomcat5-jasper.x86_64
0:5.5.23-0jpp.7.el5_2.1 tomcat5-jsp-2.0-api.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-server-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1
tomcat5-servlet-2.4-api.x86_64 0:5.5.23-0jpp.7.el5_2.1 ws
Installed: gcc-java.x86_64 0:4.1.2-44.el5 mono-core.x86_64
0:1.2.4-2.el5.centos selinux-policy-devel.noarch 0:2.4.6-203.el5
Dependency Installed: libgcj-devel.x86_64 0:4.1.2-44.el5 libgdiplus.x86_64
0:1.2.5-1.el5.centos
Updated: cpp.x86_64 0:4.1.2-44.el5 gcc.x86_64 0:4.1.2-44.el5 libgcc.i386
0:4.1.2-44.el5 libgcc.x86_64 0:4.1.2-44.el5 libgcj.x86_64 0:4.1.2-44.el5
libgfortran.x86_64 0:4.1.2-44.el5 libgomp.x86_64 0:4.3.2-7.el5
libstdc++.x86_64 0:4.1.2-44.el5 libstdc++.i386 0:4.1.2-44.el5
libstdc++-devel.x86_64 0:4.1.2-44.el5 selinux-policy.noarch 0:2.4.6-203.el5
Dependency Updated: gcc-c++.x86_64 0:4.1.2-44.el5 gcc-gfortran.x86_64
0:4.1.2-44.el5 selinux-policy-targeted.noarch 0:2.4.6-203.el5
Complete!

Installed: xml-commons-apis.x86_64 0:1.3.02-0.b2.7jpp.10
Complete!

Here's the error line:
---
cat META-INF/java/JavaBridge.inc META-INF/java/Options.inc
META-INF/java/Client.inc META-INF/java/GlobalRef.inc
META-INF/java/NativeParser.inc META-INF/java/Parser.inc
META-INF/java/Protocol.inc META-INF/java/SimpleParser.inc
META-INF/java/JavaProxy.inc | sed -f extract.sed | sed '/^\/\*/,/\*\/$/d'
>JavaRaw.inc
cat JavaRaw.inc | sed -f append.sed | sed
's/JAVA/MONO/g;s/java/mono/g;s/Java/Mono/g;s/updateJarLibraryPath/updateLibraryPath/;s/^.*do
not delete this line.*$/$name="cli.".$name;/;' >META-INF/java/Mono.inc
gcj -w -ftarget=1.4 -classpath .:script-api.jar -C php/java/bridge/*.java
php/java/bridge/http/*.java
jc1: error: unrecognized command line option "-ftarget=1.4"
make[1]: *** [MonoBridge.exe] Error 1
make[1]: Leaving directory
`/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/server'
make: *** [/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/modules/stamp]
Error 2
error: Bad exit status from /var/tmp/rpm-tmp.83378 (%build)


RPM build errors:
   Bad exit status from /var/tmp/rpm-tmp.83378 (%build)
---

Help!

Warm Regards,
Thangaraj

On Sat, Mar 28, 2009 at 2:18 PM, <
php...@li...> wrote: > Hi, > > ...
>
------------------------------------------------------------------------------
> _______________________________________________

> php-java-bridge-users mailing list >
php...@li...

> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users >
--

www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
www.ecobuddy.in
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________

php-java-bridge-users mailing list
php...@li...

https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-04-20 10:31:19

Can you tell me which Makefile.am is to be edited? I got two files:
php-java-bridge-5.4.4/bin/Makefile.am
php-java-bridge-5.4.4/server/Makefile.am

btw, is there a method by which rpmbuild can be run for the extracted folder
and not need to recreate a tar.gz if I altered any files?

I actually edited both files and still I get the same error message when I
did rpmbuild of the recreated tar,gz.

Warm Regards,
Thangaraj

On Mon, Apr 20, 2009 at 1:54 PM, <
php...@li...> wrote:

> Thank you very much for the bug report.
>
> This will be fixed in PHP/Java Bridge version 5.4.4.2.
>
> As a workaround please edit Makefile.am within php-java-bridge*.tar.gz and
> remove the text "-ftarget=1.4".
> Or please use the binary download instead.
>
> Regards,
> Jost Boekemeier
>
> Apr 19, 2009 7:14 nachm. schrieb am "Jost Bekemeier" <
> jos...@go...>:
>
> [-ftarget flag missing]
> Doesn't gcc 4.1.2 shipped with RHEL5.3 support this flag?
>
> I will check this and add a fix, if necessary.
>
> Regards,
> Jost Boekemeier
>
> Apr 19, 2009 5:41 nachm. schrieb am <
> php...@li...>:
>
> Jost,
> We're finally going the tomcat route. But when building the rpm (rpmbuild
> -tb php-java-bridge*.tar.gz), I always get an error message:
> --
> jc1: error: unrecognized command line option "-ftarget=1.4"
> --
> regardless of the java bridge version I am using. I've tried
> php-java-bridge_5.2.2.4.tar.gz
>  php-java-bridge_5.4.3.3.tar.gz
> php-java-bridge_5.3.4.1.tar.gz and
>  php-java-bridge_5.4.4.tar.gz
>
>
> Am I missing something?
>
> In the course of installing tomcat I've had to install the following:
>
> Installed: tomcat5.x86_64 0:5.5.23-0jpp.7.el5_2.1
> Dependency Installed: ant.x86_64 0:1.6.5-2jpp.2 axis.x86_64 0:1.2.1-2jpp.6
> bcel.x86_64 0:5.1-8jpp.1 classpathx-jaf.x86_64 0:1.0-9jpp.1
> classpathx-mail.x86_64 0:1.1.1-4jpp.2 eclipse-ecj.x86_64
> 1:3.2.1-19.el5.centos geronimo-specs.x86_64 0:1.0-0.M2.2jpp.12.el5.centos
> geronimo-specs-compat.x86_64 0:1.0-0.M2.2jpp.12.el5.centos giflib.x86_64
> 0:4.1.3-7.1.el5.1 jakarta-commons-beanutils.x86_64 0:1.7.0-5jpp.1
> jakarta-commons-collections.x86_64 0:3.2-2jpp.3
> jakarta-commons-daemon.x86_64 1:1.0.1-6jpp.1 jakarta-commons-dbcp.x86_64
> 0:1.2.1-7jpp.1 jakarta-commons-digester.x86_64 0:1.7-5jpp.1
> jakarta-commons-discovery.x86_64 1:0.3-4jpp.1 jakarta-commons-el.x86_64
> 0:1.0-7jpp.1 jakarta-commons-fileupload.x86_64 1:1.0-6jpp.1
> jakarta-commons-httpclient.x86_64 1:3.0-7jpp.1
> jakarta-commons-launcher.x86_64 0:0.9-6jpp.1 jakarta-commons-logging.x86_64
> 0:1.0.4-6jpp.1 jakarta-commons-modeler.x86_64 0:1.1-8jpp.3.el5
> jakarta-commons-pool.x86_64 0:1.3-5jpp.1 java-1.6.0-openjdk.x86_64
> 1:1.6.0.0-0.30.b09.el5 java-1.6.0-openjdk-devel.x86_64
> 1:1.6.0.0-0.30.b09.el5 ldapjdk.x86_64 0:4.18-2jpp.3.el5 log4j.x86_64
> 0:1.2.13-3jpp.2 mx4j.x86_64 1:3.0.1-6jpp.4 regexp.x86_64 0:1.4-2jpp.2
> tomcat5-common-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1 tomcat5-jasper.x86_64
> 0:5.5.23-0jpp.7.el5_2.1 tomcat5-jsp-2.0-api.x86_64 0:5.5.23-0jpp.7.el5_2.1
> tomcat5-server-lib.x86_64 0:5.5.23-0jpp.7.el5_2.1
> tomcat5-servlet-2.4-api.x86_64 0:5.5.23-0jpp.7.el5_2.1 ws
> Installed: gcc-java.x86_64 0:4.1.2-44.el5 mono-core.x86_64
> 0:1.2.4-2.el5.centos selinux-policy-devel.noarch 0:2.4.6-203.el5
> Dependency Installed: libgcj-devel.x86_64 0:4.1.2-44.el5 libgdiplus.x86_64
> 0:1.2.5-1.el5.centos
> Updated: cpp.x86_64 0:4.1.2-44.el5 gcc.x86_64 0:4.1.2-44.el5 libgcc.i386
> 0:4.1.2-44.el5 libgcc.x86_64 0:4.1.2-44.el5 libgcj.x86_64 0:4.1.2-44.el5
> libgfortran.x86_64 0:4.1.2-44.el5 libgomp.x86_64 0:4.3.2-7.el5
> libstdc++.x86_64 0:4.1.2-44.el5 libstdc++.i386 0:4.1.2-44.el5
> libstdc++-devel.x86_64 0:4.1.2-44.el5 selinux-policy.noarch 0:2.4.6-203.el5
> Dependency Updated: gcc-c++.x86_64 0:4.1.2-44.el5 gcc-gfortran.x86_64
> 0:4.1.2-44.el5 selinux-policy-targeted.noarch 0:2.4.6-203.el5
> Complete!
>
> Installed: xml-commons-apis.x86_64 0:1.3.02-0.b2.7jpp.10
> Complete!
>
> Here's the error line:
> ---
> cat META-INF/java/JavaBridge.inc META-INF/java/Options.inc
> META-INF/java/Client.inc META-INF/java/GlobalRef.inc
> META-INF/java/NativeParser.inc META-INF/java/Parser.inc
> META-INF/java/Protocol.inc META-INF/java/SimpleParser.inc
> META-INF/java/JavaProxy.inc | sed -f extract.sed | sed '/^\/\*/,/\*\/$/d'
> >JavaRaw.inc
> cat JavaRaw.inc | sed -f append.sed | sed
>
> 's/JAVA/MONO/g;s/java/mono/g;s/Java/Mono/g;s/updateJarLibraryPath/updateLibraryPath/;s/^.*do
> not delete this line.*$/$name="cli.".$name;/;' >META-INF/java/Mono.inc
> gcj -w -ftarget=1.4 -classpath .:script-api.jar -C php/java/bridge/*.java
> php/java/bridge/http/*.java
> jc1: error: unrecognized command line option "-ftarget=1.4"
> make[1]: *** [MonoBridge.exe] Error 1
> make[1]: Leaving directory
> `/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/server'
> make: *** [/usr/src/redhat/BUILD/php-java-bridge-5.3.4.1/modules/stamp]
> Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.83378 (%build)
>
>
> RPM build errors:
>   Bad exit status from /var/tmp/rpm-tmp.83378 (%build)
> ---
>
> Help!
>
> Warm Regards,
> Thangaraj
>
> On Sat, Mar 28, 2009 at 2:18 PM, <
> php...@li...> wrote: > Hi, > > ...
> >
>
> ------------------------------------------------------------------------------
> > _______________________________________________
>
> > php-java-bridge-users mailing list >
> php...@li...
>
> > https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users >
> --
>
> www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
> www.ecobuddy.in
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
>
> php-java-bridge-users mailing list
> php...@li...
>
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> php-java-bridge-users mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/php-java-bridge-users
>



-- 
www.ishafoundation.org
www.projectgreenhands.org
www.bootcd.us
www.ecobuddy.in

Re: [Php-java-bridge-users] java status: not running - unable to autostart the java bridge

From: <php...@li...> - 2009-04-20 20:49:40

This has been fixed in php-java-bridge_5.4.4.2rc1.tar.gz.

If there are still issues, please let us know.

Apr 20, 2009 12:31 nachm. schrieb am <
php...@li...>:

Can you tell me which Makefile.am is to be edited? I got two files:
php-java-bridge-5.4.4/bin/Makefile.am
php-java-bridge-5.4.4/server/Makefile.am

btw, is there a method by which rpmbuild can be run for the extracted folder
and not need to recreate a tar.gz if I altered any files?

I actually edited both files and still I get the same error message when I
did rpmbuild of the recreated tar,gz.

Warm Regards,
Thangaraj

On Mon, Apr 20, 2009 at 1:54 PM, <

php...@li...> wrote: > Thank you very much
for the bug report. > > T...
--

www.ishafoundation.org www.projectgreenhands.org www.bootcd.us
www.ecobuddy.in ---------------------...