subject:"URGENT help needed\: app simply stopped working $sort of$"

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-30 Thread Markus Ruggiero

On 29.09.2014, at 22:35, Mailinglists mailingli...@kataputt.com wrote:

Why should Apache be the culprit? Direct connect bypasses Apache. Connecting
directly to port 2001 does not change a thing. And monitor as well as taskd
work and respond when talking to them wirh curl or Safari. But anyway will
look into this tomorrow.
Maybe the easiest thing to do might be restoring a backup and take it from
there again.

Thanks a lot for you help and suggestions (and if you have more good
ideas)
---markus---

Well, things aren't what they look like. It *was* Apache. And then it wasn't. I
have no idea what really happened.

Indeed, the Apache config has been zapped by the required Server.app update for
10.9.5. After fixing this the application is now again reachable. However still
no joy with direct connect. So the failing direct connect kind of ruled out
Apache and lead me to a false trail. Anyway, I am happy and the customer is
happy. And I have won time for further investigation.

This community is really great. I am sad that my bread and butter job currently
does not allow to give back more to the community. I am still toying with the
idea of writing a successor to Learning The Wonders. But right now I will have
to focus on teaching . and there I can introduce almost 50 students to
Wonder over the next couple months. Isn't it great when the federal regulations
only tell you what concepts the students must learn but not what
tools/languages/environments to use?

Again thanks a lot to all who helped me.

---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I
always install apache using homebrew and run that instead of the built-in
apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now
my application simply does not accept any network connection anymore.
Besides the system update I installed a patched bash. These are the only
changes. I do not suspect bash, I have already verified that the problem
is independent of bash version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no
deaths reported, logfile generated, last line reads waiting for requests
(the standard blabla), URL looks good. Monitor tells me the app is on port
2001.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or directly
to port 2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse
3.8 with matching WOLips). App runs fine inside Eclipse. Moving the
tarball over the the deployment machine, unpacking, setting correct
owner/group, starting via Monitor - everything looks great, still no
output at all. Tried with Safari as well as from the command line with
curl. - Empty response. Still Monitor is happy, no deaths reported,
logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and
there is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots
something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# EOF
er.extensions.ERXEC.safeLocking=true
er.extensions.ERXEC.useSharedEditingContext=false
er.extensions.ERXEnterpriseObject.applyRestrictingQualifierOnInsert=true
er.extensions.ERXEnterpriseObject.updateInverseRelationships=true

# MySQL Connection Dictionary
#dbConnectUserGLOBAL=
#dbConnectPasswordGLOBAL=
#dbConnectDriverGLOBAL=com.mysql.jdbc.Driver
#Movies.URL=jdbc:mysql://localhost/movies?capitalizeTypenames=truezeroDateTimeBehavior=convertToNullcharacterEncoding=UTF-8

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

# Misc Components
er.extensions.ERXWOForm.multipleSubmitDefault=true
#er.extensions.ERXWORepetition.checkHashCodes=true
#er.extensions.ERXWORepetition.raiseOnUnmatchedObject=true
#er.extensions.ERXWORepetition.eoSupport=true

er.component.clickToOpen=true
wolips.password=my_password

# ERJavaMail

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-30 Thread Chuck Hill

On 2014-09-30, 1:49 AM, Markus Ruggiero wrote:

On 29.09.2014, at 22:35, Mailinglists
mailingli...@kataputt.commailto:mailingli...@kataputt.com wrote:

Why should Apache be the culprit? Direct connect bypasses Apache. Connecting
directly to port 2001 does not change a thing. And monitor as well as taskd
work and respond when talking to them wirh curl or Safari. But anyway will look
into this tomorrow.
Maybe the easiest thing to do might be restoring a backup and take it from
there again.

Thanks a lot for you help and suggestions (and if you have more good ideas)
---markus---

Well, things aren't what they look like. It *was* Apache. And then it wasn't. I
have no idea what really happened.

Direct connect is disabled by default in deployment, have you explicitly
enabled it in the Monitor config?

It is great when the regulations are actually like that!

Chuck

Again thanks a lot to all who helped me.

---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman
li...@thetimmy.commailto:li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I always
install apache using homebrew and run that instead of the built-in apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock
frank.st...@telenet.bemailto:frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides the
system update I installed a patched bash. These are the only changes. I do not
suspect bash, I have already verified that the problem is independent of bash
version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the standard
blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no proper
html. The same happens whether I connect through Apache or directly to port
2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there is
no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

# Misc Components
er.extensions.ERXWOForm.multipleSubmitDefault=true

URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Markus Ruggiero

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides the
system update I installed a patched bash. These are the only changes. I do not
suspect bash, I have already verified that the problem is independent of bash
version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the standard
blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no proper
html. The same happens whether I connect through Apache or directly to port
2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there is
no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERJavaMail
er.javamail.centralize=true
er.javamail.adminEmail=mar...@example.com
er.javamail.debugEnabled=false
er.javamail.smtpHost=192.168.11.33
er.javamail.smtpAuth=false
er.javamail.smtpUser=
er.javamail.smtpPassword=

# Log4j Configuration
log4j.loggerFactory=er.extensions.logging.ERXLogger$Factory
log4j.rootCategory=INFO,A1
log4j.appender.A1=er.extensions.logging.ERXConsoleAppender
log4j.appender.A1.layout=er.extensions.logging.ERXPatternLayout
log4j.appender.A1.layout.ConversionPattern=%d{MMM dd HH:mm:ss} %$[%#] %-5p %c
%x - %m%n

# Log4j Categories
# Here are a few log4j sub-categories that are interesting.
# Don't forget that in developement mode this file will get reloaded
# everytime it changes, so if you say want to turn adaptor debugging
# on in the middle of the app simply set the below category to debug.
# Very handy.
# Base Category
log4j.logger.er=INFO

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO

er.extensions.ERXNSLogLog4jBridge=INFO
#log4j.logger.er.eo.ERXGenericRecord=DEBUG
#log4j.logger.er.validation.ERXEntityClassDescription=DEBUG
#log4j.logger.er.default.ERXEntityClassDescription=DEBUG
log4j.logger.er.extensions.ERXDatabaseContextDelegate=WARN
log4j.logger.er.extensions.ERXConfigurationManager=INFO
#log4j.logger.er.extensions.ERXApplication.RequestHandling=DEBUG

#ERXNavigation

er.extensions.ERXNavigationManager.localizeDisplayKeys=true

#
backupMailReceiver = mar...@example.com

er.extensions.ERXApplication.developmentMode = true
er.directtoweb.rules.D2WTraceRuleFiringEnabled = true
log4j.logger.er.directtoweb.rules.ERD2WTraceRuleFiringEnabled = DEBUG

log file **

Sep 29 20:07:01 ImmoData[2001] INFO org.apache.log4j.Logger - Updated the
logging configuration with

URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Frank Stock

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides
the system update I installed a patched bash. These are the only changes. I
do not suspect bash, I have already verified that the problem is independent
of bash version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the
standard blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or directly to
port 2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there
is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO

#ERXNavigation

er.extensions.ERXNavigationManager.localizeDisplayKeys=true

#
backupMailReceiver = mar...@example.com

er.extensions.ERXApplication.developmentMode = true
er.directtoweb.rules.D2WTraceRuleFiringEnabled = true

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Chuck Hill

This sounds like what can happen if there is an exception very early in the R-R
loop (maybe very late too). Are you getting a standard 200 response or a 500?
Did the Java version change? You might need to start instrumenting and getting
your app to use subclasses of WOWorkerThread and WOClassicAdaptor to sort this
out. Good fun!

Chuck

On 2014-09-29, 11:39 AM, Markus Ruggiero wrote:

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides the
system update I installed a patched bash. These are the only changes. I do not
suspect bash, I have already verified that the problem is independent of bash
version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the standard
blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no proper
html. The same happens whether I connect through Apache or directly to port
2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there is
no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERJavaMail
er.javamail.centralize=true
er.javamail.adminEmail=mar...@example.commailto:er.javamail.adminEmail=mar...@example.com
er.javamail.debugEnabled=false
er.javamail.smtpHost=192.168.11.33
er.javamail.smtpAuth=false
er.javamail.smtpUser=
er.javamail.smtpPassword=

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO

#ERXNavigation

er.extensions.ERXNavigationManager.localizeDisplayKeys=true

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Timothy Worman

This. Apple’s update likely changed your apache conf. For this reason I always
install apache using homebrew and run that instead of the built-in apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides
the system update I installed a patched bash. These are the only changes. I
do not suspect bash, I have already verified that the problem is independent
of bash version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the
standard blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or directly
to port 2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse
3.8 with matching WOLips). App runs fine inside Eclipse. Moving the tarball
over the the deployment machine, unpacking, setting correct owner/group,
starting via Monitor - everything looks great, still no output at all.
Tried with Safari as well as from the command line with curl. - Empty
response. Still Monitor is happy, no deaths reported, logfile is on waiting
for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there
is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERJavaMail
er.javamail.centralize=true
er.javamail.adminEmail=mar...@example.com
mailto:er.javamail.adminEmail=mar...@example.com
er.javamail.debugEnabled=false
er.javamail.smtpHost=192.168.11.33
er.javamail.smtpAuth=false
er.javamail.smtpUser=
er.javamail.smtpPassword=

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO

#ERXNavigation

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Chuck Hill

But Marcus said, The same happens whether I connect through Apache or directly
to port 2001.” — that should rule out Apache as the issue. And if it was
Apache, I’d expect a 404 or 500 response.

Chuck

On 2014-09-29, 11:53 AM, Timothy Worman wrote:

This. Apple’s update likely changed your apache conf. For this reason I always
install apache using homebrew and run that instead of the built-in apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock
frank.st...@telenet.bemailto:frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides the
system update I installed a patched bash. These are the only changes. I do not
suspect bash, I have already verified that the problem is independent of bash
version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the standard
blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no proper
html. The same happens whether I connect through Apache or directly to port
2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there is
no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded
log4j.logger.er.extensions.fixes.ERSharedEOLoader=INFO

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Mailinglists

Why should Apache be the culprit? Direct connect bypasses Apache. Connecting
directly to port 2001 does not change a thing. And monitor as well as taskd
work and respond when talking to them wirh curl or Safari. But anyway will look
into this tomorrow.
Maybe the easiest thing to do might be restoring a backup and take it from
there again.

Thanks a lot for you help and suggestions (and if you have more good ideas)
---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I
always install apache using homebrew and run that instead of the built-in
apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or directly
to port 2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse
3.8 with matching WOLips). App runs fine inside Eclipse. Moving the tarball
over the the deployment machine, unpacking, setting correct owner/group,
starting via Monitor - everything looks great, still no output at all.
Tried with Safari as well as from the command line with curl. - Empty
response. Still Monitor is happy, no deaths reported, logfile is on
waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and
there is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots
something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERExtensions
# Transaction - Switching this to debug will start the sql ouputting.
log4j.logger.er.transaction.adaptor.EOAdaptorDebugEnabled=DEBUG

# Fixes - Turning this on will show all the models that are loaded

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Chuck Hill

A couple of other thoughts: Monitor and wotaskd working suggest that the issue
is not in WO itself or in Wonder. That you app is talking to monitor/wotaskd
shows that it is accepting connections. So it is the standard direct or
component action that is causing problems. That would lead me to focus on your
Application, DirectAction, and Session subclasses. It is probably an exception
that is getting thrown and then swallowed and not logged or otherwise handled.
And that, sadly, is probably in WO.

Chuck

On 2014-09-29, 1:35 PM, Mailinglists wrote:

Why should Apache be the culprit? Direct connect bypasses Apache. Connecting
directly to port 2001 does not change a thing. And monitor as well as taskd
work and respond when talking to them wirh curl or Safari. But anyway will look
into this tomorrow.
Maybe the easiest thing to do might be restoring a backup and take it from
there again.

Thanks a lot for you help and suggestions (and if you have more good ideas)
---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman
li...@thetimmy.commailto:li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I always
install apache using homebrew and run that instead of the built-in apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock
frank.st...@telenet.bemailto:frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for a
couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5. Now my
application simply does not accept any network connection anymore. Besides the
system update I installed a patched bash. These are the only changes. I do not
suspect bash, I have already verified that the problem is independent of bash
version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

I start an instance of my app - Monitor is happy, app is running, no deaths
reported, logfile generated, last line reads waiting for requests (the standard
blabla), URL looks good. Monitor tells me the app is on port 2001.

When I try to connect to the app I get nothing, just a white screen, no proper
html. The same happens whether I connect through Apache or directly to port
2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse 3.8
with matching WOLips). App runs fine inside Eclipse. Moving the tarball over
the the deployment machine, unpacking, setting correct owner/group, starting
via Monitor - everything looks great, still no output at all. Tried with
Safari as well as from the command line with curl. - Empty response. Still
Monitor is happy, no deaths reported, logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and there is
no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# Log4j Categories
# Here are

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Fabian Peters

Hi Markus,

I'd first override dispatchRequest on application and log to see whether the
request gets to the app at all. It's along the lines of what Chuck suggested
already, just a tad simpler maybe. If it does, I'd enable remote debugging with
something like:

-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=6

You can attach to the app from eclipse and step through.

Fabian

Am 29.09.2014 um 22:35 schrieb Mailinglists mailingli...@kataputt.com:

Thanks a lot for you help and suggestions (and if you have more good
ideas)
---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I
always install apache using homebrew and run that instead of the built-in
apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and
there is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots
something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# Log4j Categories
# Here are a few log4j sub-categories that are interesting.
# Don't

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Philippe Rabier

Marcus, did you try to also deploy a very basic app?

Can you disable any security like firewall ?

What do you see in your apache logs? (You should see the requests and the http
code)

Philippe
-
http://twitter.com/prabier

Sent from my iPhone

On 29 Sep 2014, at 22:59, Fabian Peters lists.fab...@e-lumo.com wrote:

Hi Markus,

-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=6

You can attach to the app from eclipse and step through.

Fabian

Am 29.09.2014 um 22:35 schrieb Mailinglists mailingli...@kataputt.com:

Thanks a lot for you help and suggestions (and if you have more good
ideas)
---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I
always install apache using homebrew and run that instead of the built-in
apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for
a couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5.
Now my application simply does not accept any network connection anymore.
Besides the system update I installed a patched bash. These are the only
changes. I do not suspect bash, I have already verified that the problem
is independent of bash version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or
directly to port 2001.
I built another deployment tar from my build system (also 10.9.5, Eclipse
3.8 with matching WOLips). App runs fine inside Eclipse. Moving the
tarball over the the deployment machine, unpacking, setting correct
owner/group, starting via Monitor - everything looks great, still no
output at all. Tried with Safari as well as from the command line with
curl. - Empty response. Still Monitor is happy, no deaths reported,
logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and
there is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots
something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# Log4j Configuration

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Baiss Eric Magnusson

Hi Markus,

I agree with Chuck, I have caught similar problems caused by an Exception 
thrown in the Application class and the Main direct action class.

Have you launched the App from Terminal's command line?

On Sep 29, 2014, at 1:52 PM, Chuck Hill ch...@global-village.net wrote:

 A couple of other thoughts:  Monitor and wotaskd working suggest that the 
 issue is not in WO itself or in Wonder.  That you app is talking to 
 monitor/wotaskd shows that it is accepting connections.  So it is the 
 standard direct or component action that is causing problems.  That would 
 lead me to focus on your Application, DirectAction, and Session subclasses.  
 It is probably an exception that is getting thrown and then swallowed and not 
 logged or otherwise handled.  And that, sadly, is probably in WO.
 
 
 Chuck
 

-
Baiss Eric Magnusson  
http://cascadewebdesign.com 








 ___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list  (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: URGENT help needed: app simply stopped working (sort of)

2014-09-29 Thread Hugi Thordarson

The Cancer is in the 5th house and Libra is in the 8th house. Clearly not a
good day to deploy on Mac OS X.

- hugi

On 29.9.2014, at 21:37, Philippe Rabier prab...@icloud.com wrote:

Marcus, did you try to also deploy a very basic app?

Can you disable any security like firewall ?

What do you see in your apache logs? (You should see the requests and the
http code)

Philippe
-
http://twitter.com/prabier

Sent from my iPhone

On 29 Sep 2014, at 22:59, Fabian Peters lists.fab...@e-lumo.com wrote:

Hi Markus,

-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=6

You can attach to the app from eclipse and step through.

Fabian

Am 29.09.2014 um 22:35 schrieb Mailinglists mailingli...@kataputt.com:

Why should Apache be the culprit? Direct connect bypasses Apache.
Connecting directly to port 2001 does not change a thing. And monitor as
well as taskd work and respond when talking to them wirh curl or Safari.
But anyway will look into this tomorrow.
Maybe the easiest thing to do might be restoring a backup and take it from
there again.

Thanks a lot for you help and suggestions (and if you have more good
ideas)
---markus---

Sent from my mobile phone

Am 29.09.2014 um 20:53 schrieb Timothy Worman li...@thetimmy.com:

This. Apple’s update likely changed your apache conf. For this reason I
always install apache using homebrew and run that instead of the built-in
apache.

Tim
UCLA GSEIS

On Sep 29, 2014, at 11:47 AM, Frank Stock frank.st...@telenet.be wrote:

Marcus,

did you check the Apache settings?

Folks,

I don't get it anymore. I have a Mac Mini Server running one Wonder app.
Deployment is with JavaMonitor from Wonder. The app has been running for
a couple months. This weekend I updated Max OS X from 10.9.4 to 10.9.5.
Now my application simply does not accept any network connection
anymore. Besides the system update I installed a patched bash. These are
the only changes. I do not suspect bash, I have already verified that
the problem is independent of bash version.

wotaskd runs and answers properly on port 1085
Monitor runs, configured to use port . Works perfectly.

When I try to connect to the app I get nothing, just a white screen, no
proper html. The same happens whether I connect through Apache or
directly to port 2001.
I built another deployment tar from my build system (also 10.9.5,
Eclipse 3.8 with matching WOLips). App runs fine inside Eclipse. Moving
the tarball over the the deployment machine, unpacking, setting correct
owner/group, starting via Monitor - everything looks great, still no
output at all. Tried with Safari as well as from the command line with
curl. - Empty response. Still Monitor is happy, no deaths reported,
logfile is on waiting for requests.

The same happens when I start the app manually from the command line.
Everything looks good, just nothing comes back from the port 2001 (and
there is no connection failure, connect but empty reply!)

HELP! What the h** is going on here? Any idea how to debug such a thing?
I'll attach the log file as well as Properties. Maybe anybody spots
something

Properties **

# Project Encoding
er.extensions.ERXApplication.DefaultEncoding=UTF-8

# OGNL
ognl.helperFunctions=true
ognl.inlineBindings=true

# Misc
er.extensions.stackTrace.cleanup=true

# Migrations
#er.migration.migrateAtStartup=true
#er.migration.createTablesIfNecessary=true
#er.migration.modelNames=YourModel

er.component.clickToOpen=true
wolips.password=my_password

# ERJavaMail
er.javamail.centralize=true
er.javamail.adminEmail=mar...@example.com

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

URGENT help needed: app simply stopped working (sort of)

URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

Re: URGENT help needed: app simply stopped working (sort of)

13 matches

Site Navigation

Mail list logo

Footer information