|
From: <php...@li...> - 2009-11-30 11:04:07
|
Hello, I'd like to ask for some advice when deploying the php-java bridge on JBoss 4.2.3. I'm facing 2 issues: 1) logging 2) An exception when jboss starts The exception is this one: ERROR [ServerThread] Failed to initialize java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read1(BufferedInputStream.java:258) at java.io.BufferedInputStream.read(BufferedInputStream.java:317) at java.io.ObjectInputStream$PeekInputStream.read(ObjectInputStream.java:2266) at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2279) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2750) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:780) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:280) at org.jboss.invocation.pooled.interfaces.OptimizedObjectInputStream.<init>(OptimizedObjectInputStream.java:147) at org.jboss.invocation.pooled.server.ServerThread.dorun(ServerThread.java:265) at org.jboss.invocation.pooled.server.ServerThread.run(ServerThread.java:156) It happens immediately after deploying JavaBridgeTemplate554.war. Another troubling fact is that sometimes (but very rarely) I don't see this exception when JBoss starts. For example, if I do 10 jboss startups, 9 times I see this exception and 1 time I don't. The second issue is the logging. The JavaBridge war somehow gets in the way and after it gets deployed it blocks any jboss console logging. I understand that this is a somewhat default behaviour as I see in the documentation, however, I'd like to solve this if possible and re-enable JBoss console logging. Is it possible ? I'm looking in README.J2EE, it mentions nothing about it, so I'm only left with the FAQ. However, the FAQ's instructions on enabling logging do not apply for a JBoss environment, because: 1) Starting the log4j viewer is not possible, since it uses port 4445, which is already taken by the JBoss running instance. 2) Using -Dphp.java.bridge.default_log_level=5 in JBoss' JAVA_OPTS makes absolutely no difference. I'm currently successfully using the php-java bridge for bridging 2 completely remote projects (that communicate with each other), one running on PHP/Apache and one running on JBoss. But, if possible, I'd like to solve these JBoss issues as well. I've exploded the JavaBridgeTemplate554.war, expecting to find some related properties files (for example log4j.properties, application properties and so), but that also didn't help. Could you please provide some help ? I'm going to use the bridge in a production environment but need these issues ironed out! :) Thanks in advance for any help. -- Thanos Kyritsis <djart at linux.gr> |